Export hour looms. The client review is scheduled, the delivery window is tight, and the timeline is already stretched. In a typical post-production pipeline, the gap between the final picture lock and the export is where most preventable errors surface — missing renders, mismatched color spaces, broken audio paths, or even a single offline clip buried in a timeline. We have seen teams lose hours chasing a glitch that a five-minute pre-export check could have caught. This guide offers a practical, repeatable checklist — seven steps to run before you hit export — designed for editors, assistant editors, and post supervisors who need to move fast without cutting corners.
1. Why the Pre-Export Window Is Where Pipelines Break
The period between picture lock and final export is deceptive. The creative work feels done, the timeline is locked, and the urge to rush to render is strong. But this is exactly where pipeline fragility shows up. A single offline media file, an unlinked audio reference, or a color space mismatch in a nested sequence can cascade into a failed export, a corrupted deliverable, or a client-facing error that erodes trust.
Many teams treat pre-export checks as optional or rely on memory. That works until it does not. The cost of a failed export goes beyond the lost render time: it delays the review, forces re-queuing, and often requires re-conforming, which can introduce new errors. In a busy post house, one botched export can ripple across multiple projects sharing the same storage and render nodes.
What usually breaks first is the stuff no one double-checks: a composite shot that was never fully rendered, a color space tag that was set wrong during an overnight conform, or an audio stem that was updated but not relinked. These are not exotic problems — they are routine, and they are exactly what a structured checklist catches.
The checklist we outline here is not a theoretical ideal. It is built from common failure patterns we have seen across different post pipelines — from small freelance setups to larger facility workflows. It assumes you are working with a typical NLE or finishing tool (Premiere, Avid, Resolve, or FCP) and that your pipeline includes some form of media management, color grading, audio mixing, and deliverable packaging. Adapt the order and depth to your specific chain, but do not skip any step entirely.
Who Should Use This Checklist
This is for editors who are responsible for their own exports, assistant editors who prepare sequences for finishing, and post supervisors who need a standard to hand to the team. It is also for freelancers who walk into a new project and need a reliable process that works regardless of the facility's habits. If you have ever sat through a re-render because someone forgot to check the frame rate, this is for you.
When Not to Rely Solely on This List
No checklist replaces a solid conform process or a proper quality control (QC) pass. This list targets the moments before export — not the color grade review, not the audio mix approval, not the mastering stage. If your pipeline has known issues (e.g., frequent offline media, unstable network storage), fix those first. The checklist is a safety net, not a foundation.
2. Prerequisites: What Should Be Settled Before You Start the Clock
Before you run through the seven checks, make sure your project and system are in a known good state. Trying to verify a pipeline that is already in chaos is like checking the tires on a car with no engine. Here are the baseline conditions that should be true before you begin.
Project and Media Foundation
Your timeline should be picture locked — meaning no more creative edits, no temp shots that need replacing, no unresolved notes from the last review. The color grade should be signed off, and the audio mix should be final. If any of these are still in flux, your pre-export checks will be wasted because the deliverable will change anyway. Wait for sign-off before you start the export checklist.
Media should be fully online and consolidated. All clips, graphics, and renders should reside on storage that the system can access without reconnecting or relinking. This is especially critical in shared storage environments where a file might have been moved or renamed by another user. Run a media locator or relink check before you start: confirm that every clip in the timeline has a valid path and that no offline indicators are present.
System and Software State
Close other applications that might compete for system resources — browser tabs, chat apps, background syncing tools. A render that crashes because of a memory conflict is frustrating and avoidable. Ensure your NLE or finishing software is up to date with the latest patch, but be cautious about updating right before an export. If a new version introduced a bug, you will discover it at the worst moment. Stick with the version you have been using throughout the project.
Check that your render cache is cleared or at least not corrupted. A stale cache can cause weird glitches in transitions, titles, or effects. Some editors prefer to clear the render cache entirely before a final export to force fresh renders for every frame. Others keep it if they are confident in the cache integrity. Either way, know what state it is in.
Delivery Specs on Hand
Have the delivery specification document open and ready. This is not the time to guess frame rate, resolution, codec, audio sample rate, or bitrate. The spec should come from the client or the broadcaster, not from memory. If the spec is ambiguous (e.g., "ProRes 422 HQ" without specifying resolution or frame rate), clarify before you start. Misinterpreting a spec is one of the most common export errors, and it is entirely preventable.
If you are delivering multiple versions (e.g., a broadcast master, an online proxy, and a social cut), list them all before you begin. The checklist will help you verify each version against its own spec, but you need to know what those versions are first.
3. The Seven Pre-Export Checks: Step by Step
Here is the core workflow. Run these checks in order, and do not skip any, even if you are confident. Each step builds on the previous one, and a failure early in the chain will invalidate later checks.
Check 1: Timeline Integrity and Media Status
Open your timeline and scan it visually for any offline clips, missing effects, or unresolved media. Do not rely on the "media offline" banner alone — sometimes a clip appears online but has a broken path to a high-resolution version that will fail during render. Use the project's media management tool to confirm that every clip has a valid source file. In Avid, run a Media Tool scan; in Premiere, use the Project Manager; in Resolve, check the Media Pool for any red indicators. If you find offline clips, relink them now. If you cannot find the source, replace the clip with a placeholder or a lower-resolution version that you can render, and flag it for the assistant.
Check 2: Color Space and Gamma Consistency
Color space mismatches are a silent killer. A clip that looks fine on your monitor might have a wrong color space tag that shifts the entire timeline when exported. Check that all clips in the timeline have the correct input color space set (Rec. 709, Rec. 2020, sRGB, etc.) and that the timeline color space matches your delivery spec. In Resolve, this is straightforward with the Color Management settings. In Premiere, verify the Interpret Footage settings and the sequence color space. If you are working with HDR or wide color gamut, pay extra attention: a single clip with a missing or incorrect tag can throw off the whole grade.
Check 3: Audio Path and Sync
Audio issues are common and often discovered only during QC. Listen to the first and last few minutes of the timeline — not just the waveform display. Check that all audio tracks are assigned to the correct output channels (e.g., stereo pair, 5.1, or stems). Verify that any external audio sources (voiceover recordings, music stems) are properly linked and not referencing temp files. If your pipeline includes a separate audio mix, confirm that the mix's timecode matches the locked picture. A sync offset of even a few frames can be jarring.
Check 4: Render Cache and Effects
Clear any old render cache that might be stale. Then, force a re-render of all effects, transitions, and titles. Do not rely on the green render bar — some effects may appear rendered but are actually cached from a previous version of the timeline. If your NLE has a "render all" or "render in to out" function, use it. Watch the render progress for any error messages. Common failures include missing font files for titles, corrupted GPU-accelerated effects, or nested sequences with incompatible settings. If a render fails, investigate immediately: the export will likely fail at the same point.
Check 5: Frame Rate and Resolution Consistency
Check that your sequence settings match the delivery spec exactly. A common pitfall is a timeline that was created at 23.976 fps but has a single 29.97 fps clip that forces a pulldown or conversion. Inconsistent frame rates can cause stuttering or dropped frames. Use your NLE's metadata panel to inspect each clip's frame rate. If you find a mismatch, either conform the clip to the timeline rate (with proper pulldown handling) or replace it with a correctly transcoded version. Resolution mismatches are similarly problematic: a 4K clip in a 1080p timeline is usually fine, but a 1080p clip in a 4K timeline might scale poorly or introduce aliasing. Verify that scaling is set to the correct method (e.g., scale to frame size, or maintain aspect ratio with no scaling artifacts).
Check 6: Nested Sequences and Compound Clips
Nested sequences are a frequent source of hidden errors. A nest might contain its own timeline with a different frame rate, color space, or effect stack that is not visible from the parent timeline. Open each nest and run a quick visual inspection. Confirm that the nest's settings match the parent timeline. If the nest was created from a different project or conformed from an older version, it may contain offline media or outdated effects. Consider flattening nests for the final export if the pipeline allows it — this reduces the risk of nested errors. However, flattening can break some workflows (e.g., multi-language versions), so weigh the trade-off.
Check 7: Delivery Spec Verification and Metadata
Before you export, double-check the export settings against the delivery spec document. Common mistakes include wrong codec, wrong bitrate, wrong audio channel mapping, or wrong file naming convention. Set the export to the correct resolution, frame rate, field order (if interlaced), and pixel aspect ratio. If the spec requires a specific file format (e.g., MXF OP-1a for broadcast), make sure your NLE or transcoding tool supports it and that you have tested it earlier in the project. Also, verify that any metadata (timecode, reel names, closed captions) is included or excluded as required. A simple checklist: codec, resolution, frame rate, bitrate, audio format, file name, output folder.
4. Tools and Environment: What You Need to Run These Checks Efficiently
Running the seven checks manually is feasible for a single short project, but for a busy pipeline, you want tools that automate or accelerate parts of the process. Here is what we recommend having in your environment.
Media Management and Verification Tools
Your NLE's built-in media manager is the first line of defense. Learn its capabilities: most can consolidate, transcode, and check for offline media. For advanced verification, tools like Hedge, DaVinci Resolve's Media Management, or Avid's Media Scanner can identify offline clips, duplicate media, or missing renders. Some third-party tools (e.g., PostLab, Silverstack) offer deep media checks that go beyond what the NLE provides, including checksum verification and metadata validation. If your pipeline handles a high volume of media, investing in a dedicated media management tool saves time and reduces errors.
Color Space and Format Checkers
For color space verification, a color-accurate monitor and a calibration tool are essential. But for quick checks, software scopes (waveform, vectorscope, histogram) are your best friend. Use them to confirm that the overall luminance and color balance match the expected values for your delivery spec. Some NLEs have built-in color space conversion tools (e.g., Lumetri in Premiere, Color Space Transform in Resolve). If your pipeline involves multiple color spaces, consider a LUT-based workflow with a standardized transform LUT for the entire timeline — this reduces the chance of individual clip mismatches.
Automated QC and Monitoring
For teams that export regularly, an automated QC tool like Baton, VidCheck, or Telestream's Aurora can catch errors that human eyes miss: black frames, frozen frames, audio silence, loudness violations, and format compliance. These tools are especially useful for broadcast and streaming deliverables where strict specifications apply. They are not a replacement for the pre-export checks, but they add a safety net after the export. If you have access to such a tool, run it on every deliverable before sending to the client.
Checklist Management
Do not keep the checklist in your head. Use a shared document (Google Doc, Notion, or a project management tool) that the team can access and update. Some post houses use a physical whiteboard with the seven checks listed, and editors mark them off as they complete each step. The format matters less than the habit: every export goes through the same verification process, every time.
5. Variations for Different Pipeline Constraints
Not every post pipeline looks the same. The seven checks above assume a relatively straightforward NLE-to-export workflow, but real-world pipelines have twists. Here are common variations and how to adapt the checklist.
Remote and Distributed Workflows
When editors work remotely on shared storage or cloud-based proxies, the pre-export checks become more critical because you cannot physically verify the storage or the system. In a remote setup, add a step to confirm that all media is synced to the local cache before rendering. Network interruptions during render can cause corrupted files. Also, verify that the export destination (cloud bucket, FTP, or shared folder) has enough space and that the upload process is configured correctly. If the pipeline uses a hybrid proxy/online workflow, make sure the conform step is complete and that the online media is properly linked.
Multi-Platform Deliverables
If you are exporting the same content for broadcast, web, and social media, you will run the checklist multiple times — once per version. Do not assume that a check that passed for the broadcast master also passes for the social cut. The social cut might be a different aspect ratio, have different audio requirements (e.g., stereo downmix), or need a different color space (e.g., Rec. 709 for web vs. DCI-P3 for cinema). Create a separate checklist instance for each deliverable, and mark each one as complete independently. It takes more time upfront but prevents sending the wrong version to the wrong platform.
Tight Deadlines and Rush Jobs
When the deadline is hours away, the temptation is to skip checks. Resist that. Instead, prioritize the checks that catch the most common and most damaging errors: media status (offline clips), color space consistency, and audio sync. You can defer less critical checks (like nested sequence flattening) if you are confident in the timeline's structure. But be honest about what you are skipping. If you skip a check, make a note of it and schedule a re-export if time allows after the review. A rushed export that passes QC is better than a perfect export that misses the deadline.
6. Pitfalls and Debugging: When the Checklist Reveals a Problem
No checklist is foolproof, and sometimes a check will fail. Here is how to handle the most common failures without panicking.
Offline Media That Will Not Relink
If a clip is offline and you cannot find the source file, do not delete it or replace it with a random file. Instead, mark it with a placeholder clip (a color bar or a slug) and note the timecode range. Export the timeline with the placeholder, and then fix the missing media in a re-export. If the client needs the full timeline immediately, you can send a note explaining the missing shot. This is better than a failed export or a corrupted file.
Color Space Mismatch Across the Timeline
If you discover that half the timeline is in Rec. 709 and the other half is in Rec. 2020, do not try to fix it clip by clip unless you have a clear mapping. Instead, set a timeline-level color space transform that maps both to the output space. In Resolve, use a Color Space Transform node on the timeline level. In Premiere, apply a LUT to the entire timeline or adjust the sequence color space. If the mismatch is severe, it may be faster to re-conform the problematic clips with the correct color space tags than to grade the whole timeline again.
Audio Sync Drift
Audio drift (where the audio slowly goes out of sync over the duration) is often caused by a sample rate mismatch between the timeline and the audio file. Check the audio sample rate of the timeline (usually 48 kHz) and compare it to the source files. If a source file is 44.1 kHz, the NLE may be playing it back at the wrong speed. Re-import the file at the correct sample rate or convert it in an audio editor before relinking. If the drift is consistent (e.g., 1 frame out every 10 minutes), it might be a pulldown or timebase issue. In that case, check the frame rate of the audio mix against the video timeline.
Render Errors from GPU-Accelerated Effects
If a render fails with a GPU error, try rendering that effect on the CPU instead. Temporarily disable GPU acceleration in the NLE's settings, render the problematic section, then re-enable GPU acceleration for the rest. If the effect is essential and cannot render on CPU, you may need to update your GPU drivers or roll back to a previous driver version. Keep a known-good driver version documented for your pipeline.
7. Prose Checklist and Common Questions
This final section consolidates the entire checklist into a single prose summary and answers frequent questions teams ask about pre-export verification.
The Full Checklist in Prose
Before you export, confirm that every clip in the timeline is online and properly linked. Verify that the color space of each clip matches the timeline and the delivery spec. Listen to the audio for sync, drift, and channel assignment. Clear stale render caches and force a full re-render of effects and transitions. Check that the frame rate and resolution of every clip are consistent with the sequence settings. Open and inspect each nested sequence for hidden issues. Finally, compare your export settings against the delivery spec document — codec, bitrate, audio format, file name, and output location. Run these checks in order, and do not proceed to the next until the previous one passes.
Frequently Asked Questions
How long should these checks take for a typical 30-minute project? For an experienced editor with a clean timeline, the seven checks should take 15 to 30 minutes. If you encounter problems, budget extra time. The goal is to catch issues before the export, not to rush through the checklist.
Can I automate any of these checks? Yes. Media management tools can automate offline media detection and relinking. Color space verification can be partially automated with scopes and LUTs. Automated QC tools can check the exported file for compliance. However, human judgment is still needed for creative aspects like sync and effect accuracy. Use automation for the mechanical checks and save your attention for the nuanced ones.
What if I find a problem after starting the export? Stop the export immediately. Fix the problem, clear any partial renders, and restart the export. Continuing a flawed export wastes time and may produce a corrupted deliverable. It is better to lose the render time than to deliver a broken file.
Should I run the checklist on every version of a multi-version delivery? Yes. Each version (broadcast master, web proxy, social cut) has its own spec and may have different media or settings. Treat each version as an independent check. A common mistake is to assume that if the master passes, the proxy will too — but proxies often have different codecs, resolutions, and color space requirements.
Next Moves After the Checklist Passes
Once all seven checks pass, you are ready to export. But do not walk away. Stay near the system for the first few minutes of the render to watch for error messages. After the export completes, run a quick visual and audio QC on the output file: open it in a media player, check the first and last few minutes, and verify the file size and metadata match the spec. Then, deliver the file to the client or upload it to the designated location. Finally, archive the project and the delivery spec for future reference. A disciplined post-export routine is just as important as the pre-export checklist.
Comments (0)
Please sign in to post a comment.
Don't have an account? Create one
No comments yet. Be the first to comment!