Chapter 27 — Exercises

Workflow is a habit, and habits are built by repetition, not by reading. Most of these exercises are things you do at the desk with real media — your own footage, or the Project 2 material you gathered across Part IV. A few need no computer at all; they train the judgment the pipeline runs on. Do the starred ones especially: they build directly toward a documentary edit you can actually finish. The single most valuable thing you will make in this chapter is your own permanent edit-prep checklist (Exercise 33) — everything else feeds it.

Exercises are graded by effort and depth:

• ⭐ Warm-up — a few minutes; locks in a concept.
• ⭐⭐ Core — the real practice; do as many of these as you can.
• ⭐⭐⭐ Stretch — deeper or more ambitious; where the biggest gains are.

Model solutions and critiques for the starred and odd-numbered exercises are collected in Answers to Selected Exercises at the back of the book. Try each one before you read its answer — a workflow you fumbled once teaches more than a checklist you only read.

A. Seeing the workflow (Eye & Ear Training)

No computer needed — just your judgment. These train the instinct behind the pipeline.

1. ⭐ Name the pipeline. From memory, write the eight steps of the edit-prep pipeline (FIGURE 27.6) in order, from card to string-out. Then check yourself against the figure. Which step did you forget or put in the wrong place? The two most commonly missed are back up (people fold it into "offload") and sync before selects (people try to choose keepers from picture with no sound). Note which you missed — that's your personal weak point to guard. (Answer provided.)

2. ⭐ The two-copy reflex. A friend says, "I copied the wedding footage to my laptop, so I formatted the cards for tomorrow." In one sentence, tell them exactly what's wrong and what they should have done instead. Then ask yourself the harder question: have you ever wiped a card on faith? Most of us have, once. This exercise is how you make it never again. (Answer provided.)

3. ⭐⭐ Findability audit. Open the most recent edit project you have — any kind, any editor. Time yourself finding three specific clips: your widest shot, your cleanest piece of audio, and one specific take. Write down each time in seconds. Anything over ten seconds is a structure problem, not a memory problem — name the single bin you'd add, or the labeling change you'd make, that would drop it under ten. Findability is measurable; measure yours.

4. ⭐⭐ Heavy or light? For each clip, predict whether it will play smoothly on a modest laptop or need a proxy, and say why in terms of resolution, bitrate, and codec: (a) 1080p at 24 fps in an all-intra editing codec; (b) 4K/60 HEVC straight off a phone; (c) 6K RAW from a cinema camera; (d) a 720p screen recording. Then, if you can, test one of your predictions on real footage. The gap between what you predicted and what actually stuttered is where your intuition sharpens. (Answer provided.)

B. Ingest and offload (Do This Safely)

5. ⭐ The verified copy. Offload one real card using a verified (checksum) copy — your editor's clone/ingest tool or a dedicated offload app — instead of a plain drag-and-drop. Watch for where the tool reports success or failure, and note it. Then answer: why does that explicit confirmation matter more than a file simply appearing in the destination folder? What could be wrong with a file that "looks fine"? (Answer provided.)

6. ⭐⭐ Two drives, one shoot. Take any shoot and get it onto two separate destinations with verification. If you own only one external drive, use your internal drive plus a cloud folder, or two folders on two physically different disks — the point is two independent copies that won't die together. Confirm both open and play a clip before you'd consider the card reusable. Write down what your two destinations are; that's the start of a real backup habit (the full version arrives in Chapter 37).

7. ⭐⭐ The offload log. Design a tiny one-line-per-card log you could actually fill in at every offload: card ID, what's on it, copied-to-A ✓, copied-to-B ✓, verified ✓, safe-to-wipe ✓. Write out the template as you'd really use it. This unglamorous little table is the single habit that turns "did I copy that card?" from a stomach-dropping guess into a two-second glance. Keep it with your gear. (Model provided.)

8. ⭐⭐⭐ Simulate the disaster (safely). On a copy of a test project — never your real one — rename or move the source footage folder, then reopen the project and watch it go "media offline." Now relink it and bring the media back. You've just experienced, harmlessly, the single most common media-management failure and its fix, so it never surprises you for real. Write two sentences: what triggers "media offline," and the one habit that prevents you ever triggering it on a real project? (Answer discusses relinking and why you freeze structure at ingest.)

C. Folders and bins (Organize This)

9. ⭐ Build the tree. On disk, create the FIGURE 27.2 folder structure for a real or imagined project, numbered so it always sorts in workflow order rather than alphabetically. Screenshot it. Then sanity-check: does every kind of asset you'd capture — footage, separate audio, room tone, music, graphics, exports, documents — have exactly one obvious home? If any asset is homeless, add its folder now. (Answer shows a model tree.)

10. ⭐⭐ Mirror it in a project. Import a real shoot and rebuild that same structure as bins inside your editor, so the disk folders and the project bins match one-to-one. Then add the two project-only bins — Selects and Timelines — and explain, in one line, why those two have no matching folder on disk. Understanding that answer (bins hold pointers, not files) is the key to why organization costs no extra disk space. (Answer provided.)

11. ⭐⭐ Recreate It: steal a pro structure. Find a published project-folder template from a working editor or studio — many share theirs freely online. Adapt it to your own work: keep what genuinely serves you, cut what's overkill for your scale. Write one sentence naming the single idea you took from it that FIGURE 27.2 didn't already have. Stealing structure from people who've been burned more than you have is one of the fastest ways to level up.

12. ⭐⭐ Bins for a multicam day. You shot an event with three cameras across two days. Design the bin structure that lets you find "day 2, camera C, the speeches" in under five seconds, and draw it as an ASCII tree. The trick is to divide by the axis you'll actually search on (day, then camera, then sequence). A structure that's logical but doesn't match how you search is still slow. (Model provided.)

13. ⭐⭐⭐ The label pass. Take 20 clips with camera-default names (A017_C022 and its cousins) and rename or label each so the name states project, setup/scene, subject or shot, and take. Then sort the bin by name and confirm that related clips group together. Which naming choice made the grouping work — and which chapter owns the full, career-spanning naming scheme this exercise only previews? (Answer provided.)

D. Proxies (Settings Drill & Decide)

14. ⭐ The one-question test. Drop your heaviest footage on a timeline and scrub it hard — jump around, play, reverse. Does it stutter and lag, or stay smooth and instant? Based on that single observation, decide: proxies or no proxies. Write the decision and the reason. The lesson is that this is an empirical call, made from a symptom, not a rule you apply on principle. (Answer provided.)

15. ⭐⭐ Settings Drill: spec a proxy. For a 4K/30 HEVC project on a modest laptop, write your complete proxy plan: proxy resolution, codec type (all-intra vs Long-GOP, and why it matters), roughly what bitrate priority, where the proxies live on disk, and the one thing you must not forget at export. Explain each choice in a phrase. If you can't justify a setting in a phrase, you don't yet understand why it's there. (Model provided.)

16. ⭐⭐ Do the round-trip. Generate proxies for one real clip, confirm the timeline now plays smoothly on it, then toggle the project back to the original and confirm it still renders from the full-quality master. You've now done the entire proxy round-trip on a single clip — which means you can trust it for a hundred. Note how the switch is made in your editor; that's the button you'll reach for on every future project.

17. ⭐⭐⭐ Five Ways: playback under pressure. Take one heavy clip and get it to play smoothly five different ways: (a) a half-resolution proxy, (b) a quarter-resolution proxy, (c) lowering the timeline playback resolution (no new files), (d) rendering/caching a section, (e) enabling GPU decode if your hardware supports it. Note the trade-off of each — quality, disk space, render time, hardware dependence. Then decide: which would you actually reach for on a deadline, and why? There's rarely one right answer, only the right answer for your machine. (Answer discusses trade-offs.)

E. Syncing double-system audio (Sync This)

18. ⭐ Shoot a sync test. Record a 20-second double-system clip: the camera rolling with its own scratch mic on, and a separate recorder (or a second phone) capturing the "good" audio. Clap once, clearly, on camera at the start. Keep this clip — the next three exercises all use it, and the whole point is to have a real scratch track and a real clap to work with. (Guidance provided.)

19. ⭐⭐ Sync by the clap. Import your sync-test clip and sync it by hand: find the clap spike in the camera scratch audio and in the recorder audio, and slide one until the two spikes stack on the same frame. Play it back — do the lips and the clap land together? Write down how many frames off your first attempt was, and how you knew. A frame or two of offset is visible on lips; training your eye to catch it is half the skill. (Answer provided.)

20. ⭐⭐ Sync by waveform. Sync the same clip using your editor's automatic waveform sync, if it has one. Compare the result and — more tellingly — the effort to the by-hand version from Exercise 19. Then answer the real question: when would you still sync by hand even though auto-sync exists? (Hint: think about what auto-sync needs in order to work, and what happens when it isn't there.) (Answer provided.)

21. ⭐⭐ The no-clap nightmare. Record a second double-system clip and deliberately don't clap — just start both devices and start talking. Now try to sync it with nothing to align against but the sound itself. Write a paragraph on how much harder it was and, specifically, what one on-set habit would have made it trivial. Do this exercise once and you will never again skip the clap "to save time" — it's the most persuasive argument for the slate you'll ever run on yourself.

22. ⭐⭐⭐ Read the Sequence: diagnose a sync fault. A described edit: an interview is synced perfectly at the clap, and looks great — but by the eight-minute mark the subject's lips are clearly ahead of their voice, drifting further apart the longer it runs. Name the fault, explain the mechanism (why does it get worse over time?), and give two fixes: one you'd apply in post right now, and one you'd change on the next shoot to prevent it. (Answer provided.)

F. Selects and the string-out (Cut This)

23. ⭐ Circle the takes. Take one bin of footage and do a selects pass: watch every clip and flag only the keepers — a star, a favorite, a colored marker. Here's the discipline: resist flagging everything. If more than half your clips end up as "selects," you haven't actually selected, you've just re-labeled. Force yourself to leave the mediocre takes un-flagged, even the ones with a good moment buried in them. (Answer discusses ruthlessness.)

24. ⭐⭐ Carve the good part. Pick one long take — a two-minute answer, say — and use in and out points to isolate only the ten or twenty seconds actually worth keeping, then add that range to a Selects bin rather than the whole clip. Answer: why is selecting the good part of a clip more useful than flagging the whole clip as a keeper? What does your string-out gain when it contains only usable material? (Answer provided.)

25. ⭐⭐ Build a string-out. From your selects, lay a string-out on the timeline — end to end, rough story order, no frame-trimming, no music, no transitions. Watch it through once, start to finish. Then write the single sentence of story it tells. If you can't write that sentence, diagnose which is missing: better selects (the material is thin), or a better order (the pieces are there but don't add up to anything yet)? That diagnosis is the exact fork Chapters 29 and 30 teach you to resolve. (Answer provided.)

26. ⭐⭐⭐ Cut This: string-out to first cut. Take the string-out from Exercise 25 and turn it into a rough cut: order the beats into a real beginning–middle–end, cut the obviously dead weight, and get it watchable top to bottom. Do not perfect any single scene — resist the urge to polish scene one. Then write two sentences: now that you can finally see the whole shape, what does the piece most need next? A good answer names a whole-piece problem (the middle sags, the ending's weak), not a single-cut nitpick. (Model critique provided.)

G. Fix the workflow (Fix the Shot)

27. ⭐⭐ Fix it: the exported proxy. An editor delivers a documentary and the client says it "looks soft and blocky," almost low-resolution — but the editor swears they shot and cut in 4K. Name the single most likely cause, the fix, and the one checklist item that prevents it forever. This is the most common "how did I ship that?" mistake in the proxy era, and it's entirely preventable with one habit. (Answer provided.)

28. ⭐⭐ Fix it: the vanished footage. Halfway through an edit, half the clips suddenly read "media offline." The editor had spent the morning "tidying up" their drive — renaming and moving the footage folders into something neater. Explain precisely what happened and give the two-part fix: how to recover now, and the rule that prevents it forever. (Answer provided.)

29. ⭐⭐⭐ Fix it: the unfindable good take. An editor complains they "know there's a better take of that line somewhere" but can't find it, so they're grudgingly using a weaker one. Diagnose the workflow failures that led here — there are at least three, and they span both the shoot and the post. For each, prescribe the specific habit that would have prevented it. (Hint: think selects, think labels, think what the shoot should have logged.) (Answer provided.)

H. Interleaving and synthesis

Mixing this chapter with earlier ones — where real skill lives.

30. ⭐⭐ Interleaved: the shoot–post handshake. List three specific things you do on set — drawing on Chapters 15, 18, and 20 — purely to make the edit-prep in this chapter faster, and name which pipeline step each one pays off. This is "you shoot for the edit" made concrete: production and post are one craft, and this exercise is the seam where you can see it. (Answer provided.)

31. ⭐⭐ Interleaved: codec to proxy. Using Chapter 3's vocabulary, explain to a beginner — in 120 words or fewer — why their phone footage stutters worse than a friend's "professional" camera footage, and why a proxy fixes both. Keep it plain enough that a non-technical friend actually understands it; if you have to use a word you can't define, you don't own the concept yet. (Model provided.)

32. ⭐⭐⭐ Teach it back. In about 200 words, explain to an absolute beginner why "the edit is won before the first cut." Use at least three of this chapter's terms (ingest, media management, bins, proxy, sync, selects, string-out, rough cut) and one concrete example. Teaching a concept in your own words, with a real example, is the strongest test that you own it rather than just recognize it. (Model answer provided.)

33. ⭐⭐⭐ Build your permanent checklist. Adapt FIGURE 27.6 into your edit-prep checklist — your drives, your editor's actual button names, your naming habit, your proxy trigger — as a document you will genuinely reuse on every project. Then run it, once, on a real shoot from card to string-out, and revise anything that didn't fit reality. This is the single most valuable artifact you'll make in Part VI. Print it, keep it, and let it get better every project for the rest of your career.

When you've done these — especially the sync tests, the string-out, and your own checklist — you have the one habit that separates finishers from starters. Everything in Chapters 28–30 assumes a project that's already ingested, organized, synced, and strung out. You built that project here. Now go make it sing.