What a post-production coordinator actually does

A post-production coordinator supports the post-production supervisor by keeping the schedule, people, bookings, documents, media, and deliverables aligned from production through final delivery. ScreenSkills describes the role as understanding the sequence and duration of post activities, maintaining communication with facilities, organizing documents and masters, and arranging sessions such as ADR and previews. The coordinator does not replace the editor, sound team, VFX producer, colorist, or post supervisor. The job is to make dependencies visible and help the right material reach the right specialist at the right time. AI can summarize approved notes, compare trackers, or flag missing fields, but it cannot approve a cut, certify a master, or resolve an ambiguous creative decision. Reliability comes from accurate records, calm communication, and verified handoffs.

Map the post schedule as a dependency network

A useful schedule is more than a list of dates. Picture editorial, VFX, music, sound, ADR, graphics, color, online finishing, captions, audio description, localization, quality control, legal review, credits, mastering, and delivery depend on one another. Identify each milestone, owner, input, output, review time, approval authority, and fallback. Include turnover dates, vendor capacity, holidays, shipping or upload windows, and time zones. Track assumptions such as picture lock, because a late change can trigger new VFX, sound, color, subtitle, cue-sheet, and master work. Use a change log that records who requested the change, what downstream work is affected, and which dates moved. AI may propose dependency alerts, but the coordinator verifies them with department leads. A realistic schedule protects review and correction time instead of treating final delivery as a single export button.

Control turnovers with manifests and acceptance checks

Every turnover should state what is being sent, why, from which approved version, in which technical format, and to whom. For picture editorial, that might include reference video, sequence data, source identifiers, handles, notes, and approved naming. Sound, VFX, color, graphics, localization, and marketing each need different combinations. Create a manifest listing files, sizes, checksums where required, versions, frame rate, resolution, color information, audio mapping, timecode, and exceptions. Confirm the recipient can open a representative package before the deadline. Do not call a transfer complete because files left the sender. Record receipt and acceptance. OpenTimelineIO and related interchange tools can help preserve editorial timing relationships, but the production must still define its supported applications and versions. A coordinator keeps handoffs reproducible when people, vendors, and software change.

Media and metadata must remain traceable

Post relies on identifiers that connect camera originals, sound, editorial proxies, VFX shots, titles, subtitles, masters, and archive elements. Preserve source file names, reel or clip identifiers, timecode, version labels, color metadata, audio channel information, and the approved folder structure. Avoid casual renaming or duplicate version labels. Track where masters and offline materials are stored, who has access, and what retention rule applies. MovieLabs' media-creation documentation emphasizes common data and asset frameworks that allow participants and software to understand assets across a workflow. A coordinator does not need to engineer every system, but should recognize when a spreadsheet, database, file name, or transfer log no longer agrees with the source. AI can find inconsistencies faster; it should show the conflicting records so a person can decide which one is authoritative.

Color, sound, VFX, and editorial need shared context

Departments use different technical language, so the coordinator translates requirements without pretending to be the final technical authority. For color, record camera source, timeline color space, viewing transforms, approved look information, display assumptions, and master requirements. ACES and OpenColorIO are established color-management frameworks, but a production must still test its chosen workflow. For sound, track sample rate, frame rate, channel layout, pull-up or pull-down decisions, M&E needs, and mix versions. For VFX, track shot IDs, cut references, handles, plates, mattes, color information, review status, and finals. For editorial, preserve sequence and reference versions. When a conflict appears, bring the relevant leads together and document the approved answer. The coordinator's system should make the decision durable after the call ends.

Use AI to improve tracking without hiding uncertainty

Good AI tasks include extracting structured fields from approved delivery documents, comparing two schedules, grouping notes by department, detecting duplicate shot IDs, flagging missing approvals, drafting a status summary from verified tracker data, or transcribing an authorized meeting. Require links back to the record and make the system distinguish confirmed, proposed, blocked, and unknown. Test it on real workflow patterns with non-confidential sample data before using it on a production. Do not upload unreleased cuts, scripts, contracts, performer data, credentials, or client notes to an unapproved service. Never let an automated agent delete media, publish a master, alter a schedule, or send final instructions without human approval. The goal is less clerical duplication and earlier exception detection, not a polished summary that conceals a missing file or unapproved change.

Quality control and delivery are separate responsibilities

A coordinator can organize QC, collect reports, route fixes, and verify that a corrected version entered the next review. Qualified operators or designated approvers perform the actual technical and editorial review. Build a defect log with asset ID, timecode, category, severity, evidence, owner, status, fix version, retest result, and disposition. Common checks can include image, audio, subtitles, captions, credits, frame rate, aspect ratio, color, sync, channel mapping, encoding, and file integrity, but the exact specification comes from the recipient. Digital Cinema Initiatives publishes specifications for digital cinema systems, while broadcasters and platforms maintain their own requirements. Do not assume that one accepted master satisfies every destination. Track each deliverable against its governing specification and preserve the recipient's acceptance or rejection record.

Security and access are part of post coordination

Post-production material can contain unreleased story information, performer data, legal documents, personal details, and valuable content. Use approved transfer systems, unique accounts, least privilege, multifactor authentication where supported, expiration dates, and recipient verification. Avoid personal cloud drives, shared passwords, public links, or untracked downloads. Confirm vendor and remote-work requirements with the production's security team. The Motion Picture Association's content-protection program and the Trusted Partner Network provide industry context for safeguarding media workflows, but each production defines its controls. Record access requests and removals, especially when freelancers roll off. If a link is exposed or media is sent to the wrong recipient, report it immediately through the incident process. Quietly deleting an email does not undo a disclosure.

Build a portfolio around a fictional post schedule

Create a fictional ten-minute short with invented vendors and media. Build a master post schedule, contact sheet, booking calendar, turnover manifest, VFX shot list, ADR tracker, music cue sheet, change log, QC report, delivery matrix, and archive index. Show one late picture change and trace its effects across sound, VFX, color, subtitles, and mastering. Add an AI-assisted comparison that flags tracker differences and cite the source rows behind every alert. Use files you created or are authorized to use, reserved example domains, and fabricated names. Do not publish client schedules, unreleased images, vendor pricing, credentials, private contacts, or real delivery specifications supplied under confidentiality. The portfolio should demonstrate that you understand dependencies, version control, acceptance, escalation, and clear reporting under a deadline.

Write a resume and prepare for practical interviews

Relevant experience can come from production offices, editorial, VFX, sound, localization, media operations, scheduling, live events, or project coordination. Use concrete, honest bullets: built a multi-department schedule for a supervised short, reconciled a delivery manifest against received assets, or reduced duplicate status entry with a reviewed automation. Name tools only when you can explain how you used them. Expect interview questions about a late turnover, missing VFX shot, corrupt upload, conflicting version, unavailable ADR performer, rejected master, exposed link, or last-minute cut change. Describe how you verify facts, protect the current approved version, contact the decision owner, assess downstream impact, and document the resolution. Ask about schedule authority, review cadence, delivery destinations, overtime, remote access, security, vendors, and the production's definition of picture lock.

Follow a realistic route into post coordination

Common entry points include post-production runner, post-production assistant, edit assistant, production assistant, media operator, dailies assistant, or facility coordinator. ScreenSkills positions the coordinator as operational support to the post supervisor, which makes supervised experience especially valuable. Start by learning the order of post stages, common file and timecode concepts, basic color and audio vocabulary, version control, scheduling, and secure transfer. In the first month, complete the fictional portfolio and ask an experienced post professional to challenge the assumptions. Practice writing a status report that identifies decisions, risks, and next actions in one page. With experience, coordinators can progress toward post supervision, VFX production, localization, delivery operations, studio post management, or workflow production. The durable reputation is being accurate before being fast and making every handoff easier to trust.

Sources and further reading