Seven Steps from Footage to Publish
Post-production chaos usually comes from doing everything at once, not from lacking skill. Split the work into steps where each one has a single job, and the right order makes speed automatic.
Steps one and two: organize and rough cut
Organize: import and name, layer the folders, screen usable shots, so every later step can find material in minutes. Rough cut: structure only, placing shots in narrative order and cutting obvious dead weight, without polish. The goal is a skeleton that holds.
The classic rough-cut mistake is color-grading while cutting or scoring while cutting. Every context switch costs time. The bar for a rough cut: watch it top to bottom and the story holds with no major holes.
Steps three to five: fine cut, subtitles, mix
Fine cut tightens the skeleton: trims, pacing, transitions. Subtitles: prepare the transcript first (recognition, corrections, line breaks), then choose soft or hard subtitles, checking safe areas before burning in. Mix: separate voice, music and effects; voice loudness comes first, with music sitting underneath.
The shared discipline for these three steps: one dimension at a time. Do not touch subtitles while fine-cutting, do not rebalance the mix while placing subtitles. Crossing over is how steps never finish.
Step six: compression, watching both ends
Delivery compression reads two dials: who is watching (codec and resolution) and how big it can be (bitrate). Publish versions follow platform specs; local deliveries follow size targets; archives convert once to a high-efficiency codec. Then run a quality check to confirm it is not over-compressed.
Compression is the last lossy step, which is why it must come after everything quality-related. Subtitles after compression means burning them twice; a mix change after compression costs another generation. Wrong order is wasted work.
Step seven: deliver and review
Deliver three things: the finished file, a parameter sheet (codec, resolution, bitrate) for the recipient to verify, and a note of where masters and sources live. Verify the final file with a detection tool before sending; a screenshot beats a promise.
Review in three lines: which step ran over, which step needed rework, which step could be templated. Read it before the next project; that is how a pipeline actually forms.