A captioned fine cut and verified final export.
Students organize production media and move through assembly, rough cut, fine cut, sound, captions, credits, export, and quality control in CapCut.
Section 8: CapCut Editing Workflow · Lesson 1 of 5 (36 of 45) · 60 minutes · Evidence: Organized project and media folder
Picture a film with two hundred files: voice takes, animated clips, stills, music, captions. One is named final, another final_final, a third final_REAL. At eleven at night the night before screening, which one is the real final? Editing begins long before the first cut. It begins the moment you decide where every file lives and what it is called. Today you build the structure that protects every hour of work you have done so far.
Production journal: write your answer below.
What must a filmmaker understand before they can create a reliable CapCut project structure with named assets versions and backups?
In CapCut, or in a locally approved contingency editor, the project is a small file that remembers your edit: which clips sit where, how long they run, what you changed. It does not usually contain the media itself. It only points to your files. That one fact explains most editing disasters. If you move, rename or delete a file after importing it, the project cannot find it and shows a missing-media warning. So the media folder (the organized set of folders holding every picture, clip, voice take and sound file) must be settled before you import.
Mirror the order of production, so a teammate can find anything without asking you:
Every file in this course follows one pattern: AIF_S<section>-L<lesson>_<slug>_v<version>_<initials>. Section and lesson use two digits, the slug is a short lowercase description joined by hyphens, the version uses two digits, and the last part is your initials. An example from another section: AIF_S04-L02_character-reference-set_v01_AB. A voice take made in this section could be AIF_S08-L01_mara-voice-scene03-line02_v02_AB. Two-digit numbers sort in story order. Use no spaces, no symbols, and never the words final or new. The version number (v01, v02, v03) tells people which file to trust, and your log notes which version is approved.
To import is to bring media into the editor so you can place it on a timeline. Import from your organized folder only, never from Downloads or a phone gallery. If the computer is slow with large animated clips, check whether your editor can make lighter working copies (often called proxies) and use them while you edit; the full-quality files are used again at export. A backup is a second copy in a different place: a school drive, an approved cloud folder, or a separate storage device. A copy in the same folder is not a backup. Save a new project version (v01, v02) at the end of every session.
For Last Light, the student finds Mara’s voice line for scene 3 in three places: Downloads, the desktop, and the project folder, each with a slightly different name. She plays all three, keeps the take her director approved, renames it AIF_S08-L01_mara-voice-scene03-line02_v02_AB, moves the other two into _rejects, and writes one line in the log: v02 approved, recorded by me, no third-party material. Only then does she import.
Experienced editors treat the first twenty minutes of a project as insurance. As you study the setup sequence your teacher presents, notice that nothing creative happens, yet every later step depends on it. Pause at each decision point and ask: would a stranger be able to continue this project tomorrow?
The creator gathers files from several tools and devices, decides which takes are approved, and sorts them into folders before opening the editor. Only then do they create the project and import. Watch what is not done: nobody drags files in from random places and hopes. Notice, too, that the editor will happily import a badly named file. It never warns you that two clips are different versions of the same shot, or that a music file has no license. Those judgments stay with you. Record every decision point in your journal as you watch, and mark each one as a person’s call or the tool’s call, so you can see where your own judgment is required.
As you study, record each decision point in your production journal.
| Decision point | What the filmmaker does | What the tool automates | What still needs human review |
|---|---|---|---|
| Gather and sort files | Collects exports from every tool and device into one place and removes duplicates | Nothing; file systems do not know which take is best | Whether each kept file is the approved version and each rejected one is saved, not deleted |
| Name the files | Applies the naming pattern, with zero-padded numbers and version numbers | Sorts files alphabetically once the names are consistent | That the name matches the content, and no two files share a name |
| Import into the project | Imports from the organized folder only and checks the media panel | Reads each file and builds thumbnails and lengths | That every expected file appears, none is silent or the wrong shape, and the frame size is right |
| Back up and version | Copies the folder to a second place and saves the project as a new version | May auto-save the project in the background | That the backup actually opens and sits somewhere other than the working computer |
Studio task: Correct a disorganized sample folder and relink the intended assets.
Your teacher provides a deliberately messy sample folder for a short film. If you are working from your own film instead, build the same sheet from your real files. The sample contains items like these:
Coaching tips. If you cannot tell which of two takes is approved, play both against the script before deciding. If relinking fails, check that the file name is exactly the same as before. Do not rename files while the project is open.
Naming pattern: AIF_Sxx-Lxx_slug_vxx_initials My initials: ____ Old name | New name | Keep / Reject / Unknown | Source (made by me / licensed / generated with approved tool) | Terms or proof 1 ... Folders created: 00_admin 01_images 02_video 03_voice 04_music_sfx 05_captions_titles 06_project 07_exports 08_backup Backup location and date: ____ Latest approved voice file: ____ Latest approved animation file: ____
Studio task: Create the project folder import assets and verify file naming.
Set up the real project for your film. This folder and project become the working base for every remaining lesson in the section.
Checklist before you submit:
Locate the latest approved voice and animation files.
Deliverable: Organized project and media folder.
Submit the organized project and media folder. The file must use the course naming convention and include enough process evidence to show the student's decisions and revisions.
File name (course naming convention): AIF_S08-L01_organized-project-and-media-folder_v01_YOURINITIALS
| Criterion | Advanced | Proficient | Developing | Beginning |
|---|---|---|---|---|
| The work addresses the stated story or production purpose. | The folder tree and log fit this film exactly, and a stranger could continue the project from them. | The structure serves the film and the log lists every file with an approved version. | The structure exists but some files or approvals are unclear. | Files sit in one place with no clear structure or purpose. |
| The student applies the required method accurately and produces usable capstone evidence. | Every file follows the convention, imports cleanly, and the relink test and backup restore both pass. | Naming is consistent, import is complete, and a backup exists in a second location. | Naming is inconsistent in places, or the backup was never opened. | Names are unreliable and the project cannot be reopened with its media. |
| The student identifies at least one quality issue and records a meaningful revision decision. | Finds a specific organization problem, fixes it, and records why the fix prevents future loss. | Identifies at least one quality issue and records a meaningful revision decision. | Mentions a problem without saying what changed. | No problem or revision is recorded. |
| The work complies with consent rights attribution privacy disclosure and school policy. | Every file has a documented source and terms; unproven files are excluded and explained. | Source and terms are recorded for each file and school policy is followed. | Source information is missing for some files. | Unlicensed or unknown-source files are in the project. |
Requirement: Keep rights and provenance records beside the production assets.
Keep your rights and provenance log in 00_admin, in the same project as the files it describes. For each file write who made it, which approved tool or license it came from, and the date. Media you cannot account for does not go into the project folder. If AI tools helped make a file, note which kind of tool and what it did, because that note feeds the disclosure card you will build in the last lesson of this section. A voice, face or image of a real person needs written permission, kept with the file.