Preserve the original brief
Keep the exact text beside the plan. Identify audience, purpose, deliverables, constraints, budget assumptions and unanswered questions. Record ambiguities rather than silently filling them with plausible details.
CLIENT BRIEFS · PRODUCTION PLANNING
Keep the brief
connected to the work.
Select the exact requirement. Name the deliverable. Make the dependency visible. A plan should explain why each piece of work exists.
Turn intent into explicit work.
Read the brief, clarify its requirements, define deliverables and acceptance checks, break the work into owned tasks, connect actual dependencies, calculate a provisional sequence, then review scope and assumptions with the client. This is an original practical workflow, not a universal contract or a substitute for production judgment.
Extract requirements you can trace
Select the actual phrase that a requirement comes from. Write your interpretation separately. A short request may need a clarification before the team can estimate or accept it.
Define the acceptance conversation
Name the output, reviewer and concrete check. For a video, distinguish format, runtime, captions, versions and review rounds. A checked field is not a signed client agreement.
Make owned work items
Use a title, owner, entered duration and deliverable note. Separate substantive production work from review, revisions and delivery. These durations are your assumptions, not measured productivity.
Connect real prerequisites
A dependency means the next item cannot start until the preceding one finishes. Do not turn every task into a chain by habit. Equally, do not assume unrelated owners can use the same resource simultaneously.
Calculate, then challenge the sequence
The desk computes earliest and latest starts from your directed graph. Zero-slack items sit on a critical path under the declared duration model. It does not schedule weekends, holidays, people, locations or equipment.
Review scope before committing
Discuss uncovered requirements, unknown owners, approvals, exclusions and likely revisions. Preserve the revised brief and plan together. Changes to the source or graph require another calculation and human review.
Primary context reviewed October 5, 2026: Milanote’s creative-brief guide, its film preproduction guide, and Asana’s scope guide support briefing, planning and scope discussions. StudioBinder article retrieval returned an access block and is not used as substantive evidence. No authenticated product or client outcome is claimed.
A worked example.
Clearly an illustration.
The fictional client asks for a captioned launch video and two square cutdowns. The team agrees the structure, develops the master edit, creates the cutdowns and reviews the delivery. The brief remains the source of each deliverable.
Entered durations: structure 2 work units, master edit 3, cutdowns 2, delivery review 1. The declared chain totals 8. If a parallel caption task takes 2 after structure, it finishes at 4 and has 3 units of slack before final review begins at 7. The example deliberately ignores resources and calendar dates. Load it below to inspect the actual graph calculation.
One unit means one entered working-day duration.
The tool uses nonnegative schedule offsets beginning at zero, not calendar dates. Duration must be a positive whole number of work units. Earliest finish minus earliest start equals duration. Latest values are calculated backward from the longest finish. Unlimited simultaneous resources are assumed; real production needs a separate resource and date review.
The brief-to-work trace desk.
Select actual brief text before capturing a requirement.
Source requirements
Owned work and prerequisites
JSON preserves the exact brief, source selection offsets, interpretations, acceptance notes and graph. The memo always preserves your source; an uncalculated plan is labeled accordingly. CSV is a formula-safe interchange file, not a vendor import guarantee. Saved derived schedules are ignored on restore. There is no automatic semantic extraction, approval, booking or publishing connection.
What the calculation can answer.
Does a critical path give me a delivery date?
No. It gives a longest dependency sequence under your entered durations and unlimited-resource assumption. Real dates require a separate calendar, availability and resource review.
What if I edit the original brief?
The exact selected excerpts may no longer match their saved offsets. The tool marks those traces as stale; recapture or clarify them rather than silently treating the old quote as current.
Does a requirement with a linked task count as accepted?
No. A link records your planning interpretation. The acceptance note remains a human discussion; the tool cannot authenticate a client or establish agreement.
What if the tasks contain a cycle?
The graph cannot have a valid topological schedule. The source remains editable and exportable, while calculated exports stay disabled until the cycle is resolved.