Draft versus Approved Labeling

In production, the baseline is the official version of a plan that everyone follows. It is the single source of truth for dates, locations, and requirements. When an unapproved draft is mistaken for the baseline, it creates a ripple effect of errors across every department.

Consider this scenario: A production coordinator uses an AI agent like Dots to generate a first-pass shooting schedule. Because the AI makes the document look professional and complete, the coordinator circulates it to the crew as a 'working version.' However, the producer has not yet reviewed the dates or the budget. Relying on this unapproved draft, the Art department orders custom set pieces for a Tuesday shoot, and the Locations department signs a contract for a venue on Wednesday.

When the producer finally reviews the plan, they move the shoot to the following week to save costs. Now, the production faces expensive cancellation fees from the venue and a logistics nightmare with the set pieces. To prevent this, you must treat every AI-generated document as unstable until it is formally locked as the baseline.

To prevent booking errors, every production document must be categorized as either a flexible working version or a locked authority. This distinction separates the creative and planning phase from the execution phase.

Take a scene breakdown generated by an AI agent. In the Working Draft stage, the document is a playground. The AI might suggest a high-end crane for a shot or a specific set of lighting rigs based on a prompt. The producer and director can tweak these suggestions, add notes, or reject them entirely without consequence because no one is spending money yet. It is a document of possibilities, not commitments.

Once the producer reviews these choices and signs off, the document becomes the Approved Baseline. At this point, the suggestions are locked. The equipment list is no longer a suggestion—it is a requirement. The budget is set, and the department heads now use this locked version to secure rentals and crew. By clearly separating these two states, you ensure that AI-generated 'ideas' never accidentally trigger a purchase order.

Because AI agents produce polished, professional-looking documents, the danger is not that they look like drafts, but that they look like final versions. A well-formatted spreadsheet can trick a department head into believing a plan is final. To prevent this mistaken identity, every single output generated by an AI agent must be explicitly labeled as a draft from the moment it is created.

For example, if you are using Claude Duet to generate a shooting schedule in an XLSX format, you should configure the agent to include a mandatory, high-visibility header on every page and tab. Instead of simply naming the file 'Schedule_V1', the document itself should start with a bold header: "STATUS: WORKING DRAFT - NOT FOR BOOKING."

This label acts as a constant warning to anyone who opens the file. If a coordinator forwards that spreadsheet to a grip or a gaffer, the recipient immediately sees that the dates are not yet locked. As a production lead, your task is to enforce this labeling rule for every agent in your pipeline, ensuring that no document ever enters the production ecosystem without a clear status marker.

A labeling system only works if it is backed by a hard rule: the Booking Gate. This is a production mandate stating that no department is authorized to commit funds, sign contracts, or book vendors based on any document unless it is explicitly labeled as an 'Approved Baseline.' This gate transforms the label from a helpful suggestion into a legal and financial shield for the production.

Imagine a Location Manager who has found the perfect farmhouse for scene forty-two. The owner is ready to sign, but the Location Manager looks at the supporting shooting schedule provided by the coordinator. The document is clearly labeled "STATUS: WORKING DRAFT - NOT FOR BOOKING." Despite the pressure to secure the venue, the Location Manager refuses to sign the rental contract. They know that if they book now, and the producer later shifts the dates, the production will be liable for a breach of contract or a costly rescheduling fee.

As a production lead, you implement this gate by instructing all department heads that a 'Working Draft' is a signal to prepare and research, but never to spend. You only open the gate for spending once the 'Approved Baseline' label is present.

A status system fails if anyone can change the labels. To maintain the integrity of the Booking Gate, you must establish a strict Authority Path. This means that while AI agents and production coordinators can create, edit, and suggest changes to a Working Draft, they lack the permission to promote that document to an Approved Baseline. Only the producer or the director holds the authority to change a document's status. This ensures that every financial commitment is backed by a conscious human decision.

For example, a production coordinator might use a planning agent to resolve a conflict between a location's availability and a talent's schedule. Once the coordinator believes the plan is feasible, they do not simply change the label themselves. Instead, they send a formal request to the producer: "The schedule for scene forty-two is now optimized; requesting status change to Approved Baseline." The producer reviews the AI-generated plan, verifies the budget, and then manually updates the label. As a production lead, you manage this by restricting file permissions or requiring a digital sign-off before any 'Draft' becomes a 'Baseline.'

Consistent labeling prevents unapproved AI drafts from propagating through the production pipeline. When AI agents generate multiple iterations of a plan in minutes, your digital workspace can quickly become cluttered with conflicting versions. Without a strict status system, a crew member might accidentally open an outdated version and begin planning based on incorrect data.

Imagine you are reviewing a folder containing ten different scene breakdowns for a complex sequence. Six are labeled 'Working Draft,' two are 'Discarded,' and one is the 'Approved Baseline.' By sorting the folder by status, you immediately isolate the single source of truth. You can safely ignore the 'Working Drafts'—which might contain AI-suggested lighting rigs that were never budgeted—and focus only on the 'Approved Baseline' for the day's call sheet.

As a production lead, you use this system to audit your pipeline. If you find a department head is working from a 'Working Draft,' you stop the workflow immediately. You ensure that only the document with the 'Approved Baseline' marker is shared in final handoffs, keeping the entire team aligned on the same set of facts.