Chapter 64. Contracts, Acceptance, and Working with Clients#

64.1 Scope, staged confirmation, payment, and revision rounds#

A contract has to constrain production reality.

"Produce one AI microdrama" cannot manage episode count, duration, aspect ratio, style, assets, revisions, compute, rights and delivery. The contract and its annexes should reference the brief, the milestones, the acceptance criteria and the delivery list.

This chapter is a producer's checklist. It does not replace drafting and review by a lawyer.

Scope of work.

State whether planning, script, characters, locations, shot design, keyframes, video, voice, music, subtitles, ad variants, platform versions, source files and project files are included. State the target duration per episode and the permitted variance.

Staged confirmation.

Typical nodes: brief and premise, series bible, first ten episodes, styleframes, golden characters, shot design, pilot, rough cut, fine cut, master. Downstream begins once upstream is approved; a client later overturning an approved asset is a change request.

Payment and cash flow.

Set an advance and milestone payments against project risk. Creators commonly describe splits like 30/40/30 or 50/50, and these are not fixed rules. The contract should address tax, late payment, the right to suspend, third-party costs and cancellation fees.

Without an advance or a clear procurement process, do not start large amounts of compute and outsourcing.

Revision rounds.

Define how many rounds each stage includes, the feedback window per round, what constitutes one round, and who is responsible for consolidating feedback. Free revisions do not cover reversing an approved direction, scope increases, newly added platforms, or errors in client-supplied information.

Revisions bind to an issue ID, a timecode and an acceptance criterion, which avoids notes like "make it a bit more premium."

64.2 Acceptance, rights, AI clauses, and change requests#

Acceptance.

The acceptance annex uses observable criteria: file specification, character versions, key text, loudness, P0/P1, phone preview. What happens when a client does not respond within the window must be stated in the contract rather than assumed as deemed acceptance.

Rights and credit.

State the legality and warranty for client-supplied IP, the licences for the producer's tools and materials, ownership of the final work, the conditions tied to completion of payment, credit, portfolio use, confidentiality and source files. Whether the client may train on generated assets outside the project also needs stating.

AI-specific clauses.

Describe the types of AI used, randomness that cannot be entirely eliminated, a reasonable consistency standard, platform labelling, third-party service interruptions, model updates and data handling. "AI is unstable" cannot excuse delivery obligations, and you must not promise absolute consistency that is technically impossible.

The client feedback protocol.

Name a single final feedback owner; the client consolidates internal opinions. Classify feedback by story, assets, shots, sound, subtitles and technical. Conflicting feedback returns to the decision-maker rather than leaving the production team to guess.

Change requests.

change_request:
  id: CR_017
  request: change Lin Yun's grey suit to a red dress
  stage: motion_generation
  conflicts: style bible and character phase
  affected: 46 keyframes, 31 videos, 3 edits
  cost: estimated
  schedule_impact: estimated
  decision: pending_client

Only an approved request enters the queue.

64.3 Production interfaces, client responsibilities, and termination#

Make the annexes a production interface.

The main contract settles the legal relationship; the production annexes settle how work happens daily. You need at minimum a scope statement, a delivery matrix, milestones, acceptance criteria, the revision policy, a list of client-supplied materials, the rights provenance table and an escalation path. Names, versions and dates in the annexes match the project system, so the contract does not say "character locked" while the system holds three different locked versions.

The delivery matrix states item by item whether source files, editable projects, training or fine-tuning material, prompts and parameters, separate audio tracks, textless masters, other languages and ad versions are included. Buying a finished episode does not automatically confer the producer's general templates, third-party model accounts or unlicensed source material.

Client-supplied materials and responsibility for waiting.

Where the client must supply brand guidelines, trademarks, likeness permissions, factual material, legal text, platform accounts or approvers, state the delivery date, format and responsibility for accuracy. A client delaying critical material moves the dependent schedule; a team cannot be asked to wait and to hold the original delivery date.

Client-supplied text and data still pass production verification, while legal accuracy is usually warranted by the supplier. If a client changes an amount, a product claim or a performer likeness close to release, the system computes the affected dialogue, graphics, subtitles, shots and campaign material through a change request.

Review meetings and their protocol.

Each review round states the version, the current stage, what is locked, the questions to be decided this round, and the feedback deadline. The client's single decision-maker consolidates feedback using timecodes or asset IDs; conflicting notes do not enter the production queue directly.

In the meeting, separate notes into defects, preferences and new requirements. Defects are repaired against acceptance criteria. Preferences get limited choices within the included rounds. New requirements are assessed for scope and cost. Afterwards, circulate a decision log recording approvals, rejections, pending items and owners, so verbal opinions are not reinterpreted in the next round.

Suspension, cancellation and termination.

The contract states how work suspends for late payment, prolonged non-response, unavailable third-party services, missing rights materials or a major change of direction. State which subscription, staffing and vendor costs continue during suspension, and whether the schedule is re-confirmed on resumption.

Cancellation terms address completed work, non-refundable third-party costs, approved assets, undelivered source files and intellectual property. Termination does not mean the producer must delete statutory records and rights evidence, and it does not permit continuing to disclose confidential content.

A worked change: the red dress.

After characters and the first three episodes' keyframes were approved, the client asked to change Lin Yun's grey suit to a red dress, arguing it would stand out in campaign material. Rather than arguing aesthetics, the team submitted the change impact: the character's phase logic changes, 46 keyframes, 31 motion clips, 3 edits and the advertising need updating, the schedule extends, and red in the office scenes conflicts with the brand mark.

Both sides ultimately produced a red coat variant for standalone advertising while the episode kept the grey suit. The staged confirmation and the change request did not suppress creativity; they turned a vague note into a cost-controlled two-route decision.

64.4 The collaboration flow, diagnosis, and acceptance packages#

SOP for client collaboration.

First, have the contract reference the complete scope and the brief. Second, set staged confirmation and payment. Third, write revision rounds and change boundaries. Fourth, attach testable acceptance. Fifth, handle rights, confidentiality and AI use. Sixth, name the feedback owner. Seventh, route all scope change through change requests. Eighth, sign acceptance and rights documents on delivery.

Fault tree.

Symptom: unlimited client revisions. Scope, stages and rounds are unclear. Suspend and re-price through a change request.

Symptom: an approved style is later overturned entirely. Approval carries no impact rule. Show dependencies and cost rather than absorbing it silently.

Symptom: a dispute about source files after delivery. The contract never listed deliverables. Agree by file type and rights in advance.

Checklist, exercises and deliverables.

Check that scope is specific; that payment covers up-front cost; that approval is staged; that revisions have rounds; that acceptance is testable; that AI and rights are addressed; that there is one feedback owner; and that changes are costed.

Exercise one: convert a vague commission into a scope of work. Exercise two: design five payment and confirmation stages. Exercise three: complete change requests for three classes of client change.

Deliverables for this chapter: the scope of work, the milestone schedule, the acceptance annex, the revision policy, the AI use clause checklist, change requests, and the delivery receipt.

An acceptance package is not a review link.

Each milestone's acceptance package contains the version notes, the scope of review, what is locked, the file list, the difference from the previous version, open issues, acceptance criteria, a feedback template and a deadline. A pilot rough cut can state clearly that music and grading are temporary; golden character acceptance requires front, profile, expressions, wardrobe and rights to be complete.

When a client raises a note at the wrong stage, the project manager routes it to a later stage or a change request. At rough cut, pacing can be adjusted while an approved character cannot become a different face. A typo found at master is a defect; asking to rewrite the ending is new scope.

Payment nodes should cover irreversible commitments.

Payment is not evenly spaced; it corresponds to risk exposure. The early payment covers planning, visual development and third-party procurement. Before large-scale generation begins after golden asset approval, a milestone payment should cover compute and outsourcing. The final payment at master binds to delivery of rights, watermark-free files and the agreed source file scope.

Cancellation fees separate completed services, non-refundable procurement, staff time reserved for the client, and future work not yet performed. The contract states whether the client may publish, receive source files and hold rights before payment completes, so the producer is not left with collection as the only remedy after delivery.

64.5 Pricing, a single source of truth, delivery boundaries, and dispute evidence#

Three ways to price a change request.

Small changes take a fixed price or hourly rate. Cross-asset changes are estimated from the dependency list. Highly uncertain generation requirements use an exploration ceiling: pay for a limited test first, then decide whether to expand. You cannot give an unbounded fixed price for "make every shot more cinematic."

The change request states direct cost, schedule impact, approved work being discarded, downstream regression, and the consequence of not proceeding. With complete information the client can accept, reduce or drop it — rather than treating the production team's invisible overtime as the default buffer.

Conflict resolution and a single source of truth.

Email, chat, meetings and annotations can contradict each other. The project designates the decision log as the source of production decisions, and only consolidated feedback submitted by the named approver changes state. Urgent verbal decisions are recorded within a stated window; otherwise they do not trigger large-scale rework.

When a creative lead and legal disagree, rights and release blocking take precedence. When two client stakeholders disagree, the task stays blocked and the client resolves it internally. The production team does not guess and choose whichever note is most convenient.

Source files, model files, and the boundary of editable delivery.

The contract states item by item whether the final video, textless master, stems, project files, prompts, training material, character assets, data and workflows are delivered; whether what is delivered is a licence or ownership; and whether third-party tools permit transfer. Paying for a finished episode does not necessarily include the producer's general pipeline and restricted model assets.

Editable source files may contain third-party plugins, fonts, temporary music and material that cannot be re-licensed, so they need cleaning or replacing before delivery. If the client must modify the work independently over time, choose a transferable toolchain at greenlight and cost it — rather than demanding "all the source files" after completion.

Approval SLAs and the client-waiting state.

Each milestone agrees a feedback deadline, a single approver, a consolidation format and the consequences of overrun. While waiting, the task enters waiting_client, and the contract states whether key staff are released, how the schedule shifts and whether pricing changes. A producer cannot hold capacity indefinitely for free, and a client should not lose already-paid work because of internal delay.

Urgent feedback uses a dedicated channel and deadline for blocking issues only. Ordinary aesthetic suggestions go into the next review round. A clear SLA protects the relationship and lets an agentic scheduler know when to pause, remind and re-plan.

The order of evidence in an acceptance dispute.

In a dispute, check in order: contract and annexes, approved versions, change requests, the delivery list, technical reports, and communication records. Judge defect versus new requirement against observable criteria, and do not let "this is not what I imagined" override an approved stage.

The parties may agree on an independent expert or tiered arbitration. Legal terms should be drafted by qualified professionals for the relevant jurisdiction; the production templates in this book cannot substitute for formal legal advice.

A note on sources#

Staged confirmation, costed change and observable acceptance protect both sides. A contract that describes production reality is what turns "the client keeps changing their mind" into a series of priced, dated decisions.