A production schedule should connect deliverables to owners, dependencies, review gates and final acceptance. A calendar full of dates is not enough if the team cannot see which tasks block the next stage or who is responsible for approval. The templates below can be adapted for photography, video, social content and multi-platform campaigns.
For established guidance on building and maintaining a schedule model, see PMI’s Practice Standard for Scheduling.
For a practical integration model linking people, assets and approvals, see digital creative workflows.
For the review, permission and version-control layer, see our guide to creative collaboration software.
Template 1: Master production schedule
| Workstream | Task / deliverable | Owner | Start | Due | Dependency | Status / gate |
|---|---|---|---|---|---|---|
| Brief | Approved creative brief | Producer | Day 1 | Day 2 | Client inputs | Approval required |
| Pre-production | Shot list, locations, releases | Creative lead | Day 2 | Day 4 | Brief approved | Ready-to-shoot gate |
| Capture | Photography / video shoot | Photographer / DP | Day 5 | Day 5 | Pre-production sign-off | Media ingest begins |
| Post | Selects, edit, grade, retouch | Editor | Day 6 | Day 9 | Verified ingest | Internal QC |
| Review | Client proof and revisions | Producer | Day 10 | Day 12 | Internal QC passed | Client approval |
| Delivery | Final exports and metadata | DAM / delivery lead | Day 13 | Day 14 | Final approval | Delivery receipt |
| Archive | Masters, source and records | Media manager | Day 14 | Day 15 | Delivery complete | Archive verified |
This is a sample sequence using relative working days, not a promise that every production can be completed in 15 days. Add public holidays, client response times, reshoots and external dependencies to the real schedule.
Template 2: Asset-level schedule
- Project ID: [Enter]
- Asset ID / deliverable: [Enter]
- Format and dimensions: [Enter]
- Owner and reviewer: [Enter]
- Source assets ready: [Yes / No]
- Rights and releases confirmed: [Yes / No]
- Capture / production complete: [Date]
- First proof: [Date]
- Revision deadline: [Date]
- Final approval: [Name / date]
- Delivery and archive location: [Enter]
Template 3: Dependency and critical-path register
| Dependency | Blocks | Owner | Required by | Fallback |
|---|---|---|---|---|
| Product sample received | Capture | Client | [Date] | Reschedule or use approved sample |
| Model release signed | Publication | Producer | [Date] | Do not publish identifiable image |
| Colour reference approved | Final grade | Client colour owner | [Date] | Escalate and hold master |
| Final legal approval | Release | Legal / rights owner | [Date] | Hold distribution |
Template 4: Review and approval cadence
Set a fixed review window, one consolidated feedback owner and a clear number of included revision rounds. Record the version under review, comment owner, requested change, impact and approval state. New deliverables or material scope changes require a change request before work proceeds.
Schedule governance
Update the schedule when a dependency changes, not only at weekly status meetings. Record the baseline, current forecast, variance, reason, owner and recovery action. Avoid moving due dates without preserving the original baseline; otherwise schedule performance cannot be measured.
For the end-to-end capture, review and delivery stages, see our professional photography workflow guide.
Conclusion
Useful production schedules connect dates to owners, dependencies, approval gates and evidence. Use the master schedule for coordination, the asset schedule for individual deliverables and the dependency register for risks that can move the critical path.