5 live days · Your work, in practice
Keep revisions moving through a checked workflow.
Choose Intensive when you can frame a useful prompt and want recurring proactive agents to coordinate the preparation around a sequence.
A script change travels through shots, schedules and the edit. Learn to produce useful first passes, delegate recurring planning work to bounded proactive agents, and direct a Factory of proactive AI agent teams that keeps a sample sequence coherent from scene to review.
Protect the creative intent while keeping departments working from the same script, references and decisions. Know which changes affect the plan and which need a director, producer or department lead to decide.
What you learn
Learn to build and supervise proactive agents that monitor approved revisions, update planning records and prepare continuity and post-production handoffs for review.
Create and test proactive AI agents for sequence preparation. Name a role such as Sequence Desk, then hand suitable work to OpenAI Dots to follow script changes and keep story, planning and post preparation in step. Choose one run or a continuing responsibility, with approved connections, agreed reports and a clear way to pause or retire the work.
Proactive Agents · OpenAI Dots
Create it. Name it. Put it to work.
Create and test a proactive AI agent, give its role a stable name, and define what it may do. Then hand supported work to OpenAI Dots for one run or a continuing responsibility. Your Dot can keep working between conversations, using approved context and connected tools, and return results or ask for a decision without a fresh prompt for every step.
Give the role a name and a brief
Name the role Sequence Desk. Give it the approved script revision, scene identifiers, permitted references and department checks. Connect only the cleared script or planning workspace; retain the accepted revision and decisions between runs.
Choose a run or an ongoing responsibility
A Dot has its own cloud computer and browser. When the assignment, files and tools are available there, it can work while your phone or computer is off. Always-on means available to continue the responsibility; it may wait for a schedule, input or approval and remains subject to access and usage limits. Work using local files or applications still needs that connected computer online with the ChatGPT app open.
Set the return and the review rhythm
Return revision-linked impacts, department questions and outstanding post decisions under the same named responsibility, with source versions and completed, waiting and blocked work clearly separated. Agree whether you need a scheduled report, an update on a material change, or a decision request. Department owners retain scheduling, resource and release decisions.
Agree when results are due, which changes deserve an alert and where to review them. Confirm recurring schedules, time zones and end dates; connecting an app alone does not enable monitoring. Test a changed input and a blocked step. Before retiring the responsibility, stop its delegated work and cancel its schedules separately. Keep the reviewed instructions so you can recheck access and resume when needed.
Connect only what the role needs
Use approved scripts, licensed references and cleared sample footage. Protect unreleased story material, performer information and private crew records. A Dot does not grant likeness or voice permissions, approve production commitments or release footage on behalf of the production.
Cloud coordination can work with approved script and planning exports. Editing, rendering or media stored only on a local workstation still requires that workstation and the necessary application access.
This practice is part of the existing proactive agent assignments and review time. It does not add class days or extend the hours shown in your booking.
The learning map
Work units by day
5 days of practical work for Filmmakers, producers, editors and production teams coordinating a story across development, planning and post-production. Every unit below has an output and a review point.
Your learning plan: these are the tasks you will practice. The time suggested for each task is a guide; your booking shows the confirmed class dates and start and end times.
This is a five-day Intensive: curriculum days 3–7. Intro and the MasterCourse Capstone are separate stages, not included in this purchase.
Script revisions · Change history
Track what a script revision changes.
- 3.1Compare approved script versions
- 3.2Preserve the approved baseline
Breakdowns · Department dependencies
Turn changes into department questions.
- 4.1Update the affected breakdowns
- 4.2Route planning conflicts
Shot development · Review queues
Keep shot tests tied to their scene.
- 5.1Prepare the next shot requests
- 5.2Track returned tests and revisions
Post-production · Versioned handoffs
Prepare an edit handoff that survives revisions.
- 6.1Assemble the post packet
- 6.2Close the feedback loop
Continuity · Readiness checks
Test the sequence workflow under change.
- 7.1Run the sequence checks
- 7.2Pause and resume the workflow
The work behind the map
Daily detail
Follow the work from its starting material to a result you can inspect. Each checkpoint gives you a reason to approve, revise or stop.
Intensive
Days 3–7 · Proactive Agents
Keep recurring work moving.
Build proactive agents that run defined tasks over time. Give each one a trigger, working record and limits, then review its exceptions and results.
Build the proactive agent and test one complete run. Name its role, approve its inputs and connections, then hand suitable work to a Dot. Choose a single assignment or a continuing responsibility with clear reports, review points and a way to stop.
Day 03Track what a script revision changes.
Build a revision proactive agent that checks approved script versions on an event or schedule. It should explain the difference without silently replacing the planning baseline.
- 3.1
Compare approved script versions
Give the proactive agent two supplied revisions and a scene identifier scheme. Have it produce a change report linked to the affected scenes and source passages.
Suggested time for this task: 2 hours in Full Course; 1 hour in Crash Course. Part of your class day, not extra time.- Practice result
- A scene-level revision report.
- 3.2
Preserve the approved baseline
Rerun the comparison with an unchanged file and a missing revision. Keep prior decisions, suppress duplicate reports and pause when the version sequence is unclear.
Proactive agent practice. Create and test the sequence preparation proactive agent on one sample run. Name the role Sequence Desk and hand supported work to a Dot using approved script revisions, breakdowns and post handoff records. Define permitted actions and the return you expect; inspect the first result before giving it an ongoing responsibility.
Suggested time for this task: 2 hours in Full Course; 1 hour in Crash Course. Part of your class day, not extra time.- Practice result
- A tested revision proactive agent with a baseline and exception log.
By the end of the day
A revision proactive agent that separates new script changes from already reviewed work.
Review checkpoint
Verify that a proactive agent cannot treat an unapproved draft as the production baseline.
Day 04Turn changes into department questions.
Use a breakdown proactive agent to update affected scene records after an accepted script change. Give it clear limits around scheduling, staffing and safety decisions.
- 4.1
Update the affected breakdowns
Have the proactive agent compare accepted revision notes with current character, location and prop records. Update only affected entries and keep the source of each proposed change.
Suggested time for this task: 2 hours in Full Course; 1 hour in Crash Course. Part of your class day, not extra time.- Practice result
- A revised scene-requirements register.
- 4.2
Route planning conflicts
Introduce an unavailable location and a changed prop requirement. Have the proactive agent prepare department questions, stop dependent tasks and revisit them after a recorded decision.
Proactive agent practice. Connect the approved planning record and set when the proactive role checks script impacts. Return changed breakdowns and department questions while preserving the baseline; scheduling and resource commitments remain with production.
Suggested time for this task: 2 hours in Full Course; 1 hour in Crash Course. Part of your class day, not extra time.- Practice result
- A dependency queue with department owners and blocked items.
By the end of the day
A breakdown workflow that reveals who needs to resolve each planning conflict.
Review checkpoint
Check that the proactive agent flags feasibility questions instead of inventing availability, costs or safe operating instructions.
Day 05Keep shot tests tied to their scene.
Build a proactive agent that prepares shot requests and tracks returned visual tests. Run creative tools through their supported interfaces; use reviewed exports when a direct connection is unavailable.
- 5.1
Prepare the next shot requests
Have the proactive agent turn accepted scene requirements and references into a small queue of shot prompts. Link every request to the current scene and review standard.
Suggested time for this task: 2 hours in Full Course; 1 hour in Crash Course. Part of your class day, not extra time.- Practice result
- A versioned shot-test queue.
- 5.2
Track returned tests and revisions
Register supplied Higgsfield or Runway outputs and reviewer notes. Limit resubmission attempts, retain rejected versions and pause when references conflict.
Proactive agent practice. Keep shot-request preparation attached to the accepted scene and reference record. Let the proactive role return new tests and revision requests at agreed checkpoints, with scene versions and decisions clearly linked.
Suggested time for this task: 2 hours in Full Course; 1 hour in Crash Course. Part of your class day, not extra time.- Practice result
- A shot-history record with bounded revision requests.
By the end of the day
A repeatable shot-development queue that preserves why each version was accepted or rejected.
Review checkpoint
Check visual continuity yourself. A proactive agent can coordinate the records without being able to judge every frame reliably.
Day 06Prepare an edit handoff that survives revisions.
Give an editorial coordinator proactive agent a supplied media manifest and review notes. Its task is to prepare consistent handoffs as approved shot versions change.
- 6.1
Assemble the post packet
Have the proactive agent collect accepted shot references, sequence order and outstanding notes into a post-production manifest. Flag missing media rather than substituting another version.
Suggested time for this task: 2 hours in Full Course; 1 hour in Crash Course. Part of your class day, not extra time.- Practice result
- A post packet with shot identifiers and current versions.
- 6.2
Close the feedback loop
Add time-referenced editorial notes to the sample packet. Route each note to its owner, carry unresolved notes forward and stop retries when the source media is unavailable.
Proactive agent practice. Maintain the post handoff as an ongoing coordination role. Check the permitted record on the confirmed schedule and return linked edit notes, media references and unresolved feedback; native editing and rendering require verified application access.
Suggested time for this task: 2 hours in Full Course; 1 hour in Crash Course. Part of your class day, not extra time.- Practice result
- An editorial issue log linked to the relevant shot versions.
By the end of the day
An editorial coordination proactive agent that maintains one inspectable history of media and notes.
Review checkpoint
Confirm that old notes do not attach to a different cut or a replacement shot without review.
Day 07Test the sequence workflow under change.
Connect the recurring proactive agents around a small sequence. Examine how they respond to a new script revision, a missing shot and a delayed review.
- 7.1
Run the sequence checks
Have a checking proactive agent compare script, breakdown, shot and post manifests. Produce a readiness report showing mismatched versions, missing decisions and unresolved continuity notes.
Suggested time for this task: 1 hour 40 minutes in Full Course; 50 minutes in Crash Course. Part of your class day, not extra time.- Practice result
- A sequence-readiness report with evidence links.
- 7.2
Pause and resume the workflow
Withhold one approval, then supply a corrected packet. Verify that proactive agents retain state, update affected work and request human review before the sequence is marked ready.
Proactive agent practice. Let Sequence Desk continue a cloud-capable assignment while you leave the chat. Inspect the result, block one input and test recovery. Then retire the responsibility: stop active delegates, cancel future schedules and retain the reviewed instructions. Recheck access and inputs before calling it back into service.
Suggested time for this task: 2 hours 20 minutes in Full Course; 1 hour 10 minutes in Crash Course. Part of your class day, not extra time.- Practice result
- A tested planning workflow and recovery record.
By the end of the day
A recurring scene-to-post workflow with visible stop conditions and a human review queue.
Review checkpoint
Inspect whether the workflow remains blocked when an apparently complete sequence uses the wrong script revision.
Your time commitment
How long is each class day?
You attend 5 live classes, one on each scheduled day. Choose Full Course or Crash Course for all 5 days. The times below include breaks.
Full Course
6 hours per day
More time to practice, ask questions and review your work.
Suggested plan for one day
- Lessons and hands-on practice
- 4 hours
- Review and questions
- 30 minutes
- Lunch break
- 1 hour
- Two short breaks
- 15 minutes each
5 class days × 6 hours = 30 hours totalIncludes all scheduled breaks.
Crash Course
2 hours 30 minutes per day
The same topics in shorter classes, with prepared examples and less practice time.
Suggested plan for one day
- Lessons and hands-on practice
- 2 hours
- Review and questions
- 20 minutes
- One short break
- 10 minutes
5 class days × 2 hours 30 minutes = 12 hours 30 minutes totalIncludes all scheduled breaks.
Lunch, breaks and review time are already included in each day. The task times in Daily detail fit inside the practice time above. Your trainer may adjust the plan; the start and end times shown with your selected dates are the ones to follow.
Choose your starting point
One progression. Three choices.
Intro teaches individually directed prompts. Intensive puts recurring work into proactive agents. MasterCourse connects the whole pathway and adds the Factory Capstone.
Intro
Learn to prompt for a scene breakdown, trace it to the script and review a shot brief through a short-scene exercise.
Choose Intro for individually directed script, scene and shot-planning tasks.
Intensive
Learn to build and supervise proactive agents that monitor approved revisions, update planning records and prepare continuity and post-production handoffs for review.
Choose Intensive when you can frame a useful prompt and want recurring proactive agents to coordinate the preparation around a sequence.
Create and test proactive AI agents for sequence preparation. Name a role such as Sequence Desk, then hand suitable work to OpenAI Dots to follow script changes and keep story, planning and post preparation in step. Choose one run or a continuing responsibility, with approved connections, agreed reports and a clear way to pause or retire the work.
MasterCourse
Learn to connect film prompts and planning proactive agents into a Factory of supervised proactive AI agent teams, with version control, clear handoffs and production approvals.
Choose MasterCourse for the full ten-day progression and the Capstone that tests coordination across departments.
Build a Factory of proactive AI agent teams for sequence preparation. Use a Dot to coordinate continuing work across their handoffs and return revision-linked impacts, department questions and outstanding post decisions. Test changing inputs, blocked work and a later restart. Department owners retain scheduling, resource and release decisions.
Intensive is a five-day purchase, not a seven-day bundle. The three-day Capstone is available only inside the ten-day MasterCourse.
Live guidance · Continued reference
Come prepared. Keep what you learn.
Bring a computer, a reliable connection and a work example you are authorized to use. Sample or sanitized material lets you practice without introducing confidential source files.
Practice with guidance
Work through the assignments live, compare results and use trainer feedback to refine your prompts, proactive agent instructions and review standards.
Revisit your classes
Students have access to recordings of their classes in the members portal.
Specialist tools · Separate subscriptions
Tools serve the assignment.
Two specialist tools chosen for practical fit and an established learning ecosystem. Claude, OpenAI, Gemini and Open Source options support the prompt and proactive agent work. Specialist examples connect it to your field.
Higgsfield
Image and video generation for motion concepts, shot tests and creative alternatives.
Plan and access
Starter $19/month, billed annually, on the inspected pricing view.Starter includes selected models. Credits, model access and concurrency vary. Vendor excludes MCP/CLI, Canvas and Supercomputer from the website-only unlimited/free-generation benefits.
Runway
Generate and compare visual or motion studies, with paid credits and export features.
Plan and access
Free plan; Standard $15/month or $12/month billed annually.Generation length, resolution and model affect credit use. API/MCP availability is plan-specific; use reviewed exports if unsupported.
Do I need my own software access?
Yes. Arrange full access to the required features before class, including suitable paid plans, usage credits and organization permissions. Software costs are separate from tuition. Free access may not cover every exercise.
How these tools support your course
Intensive · Proactive Agents
Feed permitted Higgsfield and Runway exports into a versioned shot and post workflow. Proactive Agents prepare requests and track review decisions through supported connections or manual media handoffs.
Vendor information checked September 29, 2026. Plans and limits can change. Proactive Agents use supported connections or approved exported inputs; specialist subscriptions do not imply universal proactive agent integration. Human approval remains part of publishing, releasing work and professional decisions.
OpenAI Dots · Proactive agents at work
Hands-on proactive agent and Dots work starts in Intensive. Check Dots availability, supported connections and your organization’s permissions before class. You authorize each app or browser session; Dots does not inherit all your logins. Subscriptions and usage charges are separate from tuition. Some specialist work needs a reviewed export or an online local application.
Cloud coordination can work with approved script and planning exports. Editing, rendering or media stored only on a local workstation still requires that workstation and the necessary application access.
Before you choose
FAQ
Clear scope makes it easier to choose a course and arrive ready to work.
Which level should I choose?
Choose Intro for individually directed script, scene and shot-planning tasks. Choose Intensive when you can frame a useful prompt and want recurring proactive agents to coordinate the preparation around a sequence. Choose MasterCourse for the full ten-day progression and the Capstone that tests coordination across departments.
What does Factory mean?
A Factory coordinates supervised teams of proactive AI agents around a shared outcome. Each AI agent team has a defined responsibility, a deliverable and an acceptance check for the next handoff. You control permissions, review exceptions and approve release. The MasterCourse-only Capstone tests continuing cycles as well as individual runs.
Are recordings available?
Yes. Students can access recordings of their classes in the members portal.
How long is each class, and how many days do I attend?
This Intensive has 5 class days. Full Course lasts 6 hours each day, including lunch and two short breaks. Crash Course lasts 2 hours 30 minutes each day, including one short break. Choose one format for the whole course. Both cover the same topics; Full Course gives you more practice time. Check your selected dates for the exact start and end times in your time zone.
Which time zone will I see?
The class chooser detects your time zone automatically. Use Change time zone to select another location; the dates and hours update together.
Can Intro or Intensive tuition count toward MasterCourse?
The amount actually paid for Intro and/or Intensive can be credited once toward one MasterCourse enrollment within twelve months of each purchase. Intro and Intensive do not credit each other. No credit toward other programs, software or cash. Credit requests are reviewed against purchase records and eligibility; they are not an automatic checkout discount.
Full refund, transfer and credit policyWhat happens if I miss a day?
A missed day has a guaranteed place on the same curriculum day in a later cohort, free of charge, within twelve months of the original cohort's last scheduled day. After this window, new enrollment uses the then-published fee; day credits have no cash value and cannot buy a different curriculum day. An attended day may be repeated without charge within the same twelve-month window, subject to space. One free transfer of the whole seat or its unused days to a later cohort, in either published format, without a reason or a price increase, within twelve months of the original cohort’s last scheduled day. A day already consumed on one format is consumed on both; unused curriculum days are portable across dates and formats.
Full refund, transfer and credit policyWhat should I know before enrolling?
Full refund for a cancelled live program before its first scheduled session begins, including individual and group purchases and an approved MasterMind season. No refund after the purchased program starts, including dissatisfaction or absence, except for a session the provider fails to deliver. Statutory rights are unaffected. Partial attendance consumes the day under the published attendance rules. Read the full terms before choosing your class.
Full refund, transfer and credit policyWhen do I start using Dots?
Intro teaches individual tasks, clear prompts and review. Intensive teaches you to create proactive agents, test their work and hand supported responsibilities to OpenAI Dots. MasterCourse adds a Factory of proactive AI agent teams with shared records and coordinated handoffs.
Can the work continue after I close my phone or computer?
A Dot has its own cloud computer and browser. When the assignment, files and tools are available there, it can work while your phone or computer is off. Always-on means available to continue the responsibility; it may wait for a schedule, input or approval and remains subject to access and usage limits. Work using local files or applications still needs that connected computer online with the ChatGPT app open.
How do I stay in control over time?
Give the Dot and its assignments recognizable names, keep approved context current, and agree what deserves a report. It can surface missing input, access or decisions. To pause or retire work, check active delegates and saved schedules separately; pausing the main conversation does not stop them all. Review access and inputs before resuming.
What material can I use for the cloud exercises?
Use approved scripts, licensed references and cleared sample footage. Protect unreleased story material, performer information and private crew records. A Dot does not grant likeness or voice permissions, approve production commitments or release footage on behalf of the production.