The Archival Workflow: Source-First vs. Story-First for a Calmer Edit

This overview reflects widely shared professional practices as of May 2026; verify critical details against current official guidance where applicable.

1. The Editing Crossroads: Why Your Workflow Determines Your Sanity

Every editor, whether working on a documentary, a podcast series, or a digital archive, eventually faces a pivotal choice: do you let the source material dictate the narrative, or do you impose a narrative structure first and then find supporting footage? This decision, often made unconsciously, shapes the entire editing process—and, more importantly, determines how calm or chaotic that process will be. In my years of working with editorial teams, I've seen projects stall not because of technical issues, but because the team never aligned on a fundamental workflow philosophy. The Source-First approach treats the raw material as a treasure to be discovered, letting themes emerge organically. The Story-First approach begins with a script or outline, using the archive as a library to verify and illustrate pre-decided beats. Both are valid, but they suit different project types, team sizes, and editor personalities. Choosing the wrong one can lead to endless cycles of re-editing, missed deadlines, and burnout. This guide will help you understand the trade-offs and select the approach that leads to a calmer, more productive edit.

The Cost of Misalignment

Consider a typical documentary project: a team of three editors is given 200 hours of interview footage and archival clips. If one editor works Source-First, reviewing everything and building sequences organically, while another works Story-First, cutting to a pre-written script, they will clash on priorities. The Source-First editor will feel constrained; the Story-First editor will feel the project lacks direction. This friction, multiplied across weeks, erodes morale and quality. In my experience, teams that explicitly discuss and agree on a workflow at the outset finish edits 20-30% faster, with fewer major revisions.

Defining the Two Poles

Source-First (also called discovery editing): You begin by ingesting, logging, and reviewing all source material. Themes, characters, and narrative arcs emerge from the footage itself. Editing proceeds inductively. This approach is ideal when the story is unknown or when the material is rich and surprising—for example, a verité documentary or a personal archive project where the editor is also the researcher.

Story-First (also called scripted editing): You start with a written script, treatment, or storyboard. The archive serves as evidence to support the predetermined narrative. Editing is deductive: you locate clips that match the script and assemble them in order. This approach works well for projects with strict narrative constraints, such as educational videos, corporate histories, or series with tight episode arcs where the story is already clear from the research phase.

Neither is inherently superior. The choice depends on project goals, timeline, and team expertise. In the following sections, we will explore each workflow in detail, compare their tools and economics, and provide a decision framework to help you choose wisely.

2. Core Frameworks: How Source-First and Story-First Actually Work

To understand the practical implications of each approach, we need to examine their underlying mechanisms. These are not just preferences—they are distinct cognitive and procedural frameworks that affect every decision from ingest to final export.

Source-First: The Inductive Framework

In a Source-First workflow, the editor acts as an archaeologist. The process begins with a broad survey of all materials: interviews, B-roll, archival footage, documents, and audio recordings. The editor logs each piece, often using metadata tags for themes, tone, and content. This stage is time-consuming but yields a deep familiarity with the material. Next, the editor begins to cluster related clips, looking for patterns, contrasts, and emotional beats. These clusters become potential scenes. The story is built from the bottom up, with each scene informing the next. A key advantage is that the final narrative often includes unexpected discoveries—moments that would have been missed if the editor was too focused on a pre-written script. For example, in a project about a small-town festival, an editor working Source-First might discover a subplot about a local rivalry that becomes the emotional core of the piece. This approach requires patience and tolerance for ambiguity, but it can produce deeply organic, surprising work.

Story-First: The Deductive Framework

In a Story-First workflow, the editor begins with a detailed script or treatment. The script defines the narrative arc, key scenes, and even specific lines of narration or dialogue. The editor's task is to find footage that matches these specifications. This approach is highly efficient when the story is well-understood before editing begins. For example, a corporate video about a product launch might have a script approved by stakeholders weeks before any footage is shot. The editor knows exactly what each scene needs: a shot of the product, a customer testimonial, an executive interview soundbite. The archive is searched strategically, often using keywords or timecodes provided by the script. This reduces the time spent reviewing irrelevant material and ensures that every piece of footage serves a clear purpose. However, this efficiency can come at a cost: the editor may overlook compelling footage that doesn't fit the script, potentially missing opportunities to enrich the story. Additionally, if the script is poorly researched or based on assumptions that don't match the reality of the footage, the editor may face significant rework.

Comparison at a Glance

3. Execution: Workflows and Repeatable Processes for Each Approach

Moving from theory to practice, this section outlines step-by-step processes for implementing Source-First and Story-First workflows. These are not rigid recipes, but adaptable frameworks that teams can modify based on their specific constraints.

Source-First Workflow: A Step-by-Step Guide

1. Ingest and Conform: Import all media into your editing environment. Create a consistent naming convention based on source, date, and tape/reel number. Generate proxies if working with high-resolution files.
2. Logging and Tagging: Watch all material at 2x speed or higher, marking in/out points for key moments. Use a metadata schema that includes themes, characters, emotional tone, and technical quality. Tools like descriptive markers or spreadsheet logs are essential.
3. Cluster and Sequence: Group related clips into bins or collections based on emerging themes. Create rough string-outs—long sequences that assemble all material on a theme. These become the building blocks of scenes.
4. Fine-Cut and Refine: Once you have a structure that feels right, begin trimming and ordering. Add narration or transitions as needed. This phase often involves multiple iterations as the story tightens.
5. Review and Revise: Share with a small group of trusted colleagues for feedback. Expect structural changes because the story is still evolving. This is normal and healthy.

Story-First Workflow: A Step-by-Step Guide

1. Script Finalization: Ensure the script or treatment is approved by all stakeholders before any editing begins. Include timing estimates for each scene.
2. Footage Matching: For each scene, list required shots and soundbites. Use the script's timecodes or keywords to search the archive. If material is missing, flag it immediately—do not assume you will find it later.
3. Assembly Edit: Place the script on a timeline as a guide track (e.g., scratch audio or text). Insert found footage into the corresponding slots. This should be a fast, mechanical process.
4. Fine-Cut and Polish: Once all scenes have matching footage, refine pacing, add B-roll, and adjust audio. Because the structure is locked, this phase focuses on execution rather than discovery.
5. Stakeholder Review: Present the fine cut to stakeholders. If the script was accurate, changes should be minor—tighter edits, alternative takes, color correction.

Both workflows benefit from a clear division of roles: a lead editor, an assistant editor for logging, and a producer for stakeholder communication. In practice, many teams use a hybrid approach: start with a Source-First exploration to understand the material, then pivot to a Story-First structure once themes emerge. This hybrid method combines the strengths of both while mitigating their weaknesses.

4. Tools, Stack, Economics, and Maintenance Realities

The choice between Source-First and Story-First has significant implications for the tools you use, the cost of the edit, and ongoing maintenance—especially for archival projects that may need to be updated or reused.

Software and Infrastructure

Source-First tools prioritize metadata management and non-linear browsing. Applications like DaVinci Resolve, Adobe Premiere Pro with extensive marker systems, or specialized tools like Kyno and MediaSilo are common. The key requirement is a robust logging workflow: editors need to tag clips with custom metadata, create smart bins, and search across large libraries. Cloud-based collaboration platforms (e.g., Frame.io) help share string-outs with remote team members. For very large archives, asset management systems (MAM) like Iconik or CatDV become necessary. The investment in tooling and training for Source-First is higher, but the payoff is faster discovery and more organic narratives.

Story-First tools focus on script integration and version control. Avid Media Composer has long been the industry standard for script-based editing because of its ScriptSync feature, which links transcribed dialogue to source clips. Adobe Premiere Pro's Text-Based Editing is a newer alternative. The economic advantage of Story-First is that it requires less logging infrastructure—editors can search for specific lines of dialogue rather than tagging every moment. This reduces the time and cost of pre-edit preparation. However, the script itself represents a significant upfront investment in research and writing. For projects with tight budgets, this can be a trade-off: spend money on research and writing, or on logging and discovery?

Economic Considerations

A typical documentary edit using Source-First might require 2-3 weeks of full-time logging for 100 hours of footage, costing roughly $5,000-$10,000 in assistant editor time. The edit itself may take 8-12 weeks. A comparable Story-First project might spend 2-3 weeks on research and script development ($5,000-$10,000), then 6-8 weeks on editing. The total cost can be similar, but the risk profile differs: Source-First risks overshooting the budget if the editor gets lost in material; Story-First risks expensive rewrites if the script is wrong. For series or long-running projects, the Story-First approach often has lower maintenance costs because the script provides a clear reference for updates. For archival projects that need to be repurposed (e.g., a museum exhibit that changes annually), Source-First metadata pays dividends because the material is already tagged and discoverable.

Maintenance Realities

Archives are living entities. A Source-First workflow naturally builds a searchable, well-tagged library that can be reused. A Story-First workflow may leave untagged footage accumulating on drives, creating future work. I recommend that even teams committed to Story-First invest in basic logging (date, subject, key people) to avoid creating an unmanageable backlog. Additionally, both workflows benefit from regular reviews of the archive—every 6 to 12 months—to prune obsolete material and update metadata. This is especially important for projects that continue to add new content over time.

5. Growth Mechanics: Traffic, Positioning, and Persistence in Archival Work

Beyond the immediate edit, the workflow you choose affects how your archive grows in value over time. For organizations that produce ongoing content—like media archives, educational platforms, or corporate communication teams—the long-term implications are substantial.

Traffic and Discoverability

A Source-First workflow generates rich metadata as a byproduct. Each clip is tagged with themes, people, and contexts. This metadata becomes a searchable index that can power internal search tools or even public-facing archives. For example, a documentary series about urban farming could be repurposed into short webisodes, educational clips, or interactive maps. The metadata allows a content strategist to find every clip about 'composting' in seconds, enabling rapid creation of new assets. This drives traffic and extends the life of the content. In contrast, a Story-First workflow often produces minimal metadata—only what was needed for the original script. Repurposing requires a new round of logging, which is costly and time-consuming. Organizations that anticipate reuse should lean toward Source-First or a hybrid with robust logging.

Positioning and Authority

For brands and institutions, the archive is a strategic asset. A well-organized, Source-First archive positions the organization as a thought leader with deep, accessible knowledge. For instance, a museum that tags its oral history interviews by theme and period can quickly produce curated exhibitions, blog posts, or educational resources. This builds authority and public trust. Story-First projects, while efficient, can appear disjointed if the archive is not maintained. Audiences may perceive a lack of depth if content is not easily connected. Therefore, for organizations that want long-term positioning value, investing in Source-First logging is a strategic move.

Persistence and Future-Proofing

Archives must survive staff turnover, software changes, and shifting priorities. A Source-First workflow creates a structured, standardized archive that is easier to migrate and maintain. Metadata schemas can be exported and imported across platforms. A Story-First workflow, with its focus on the script, may leave the underlying footage disorganized. When a new editor takes over, they face a steep learning curve. I have seen several projects stall for months because the original editor left and the new editor could not find anything. To avoid this, even Story-First teams should adopt a minimum metadata standard: date, source, subject, and key participants. This small investment ensures persistence and reduces the risk of losing institutional knowledge.

6. Risks, Pitfalls, Mistakes, and Mitigations

Both workflows have known failure modes. Understanding these pitfalls in advance helps editors and teams avoid common traps and maintain a calmer edit.

Source-First Pitfalls

• Analysis Paralysis: The abundance of material can lead to endless reviewing. Mitigation: set a strict logging timebox. For example, allocate 40 hours for logging 100 hours of footage, no more.
• Losing the Thread: Without a script, the story can meander. Mitigation: after logging, create a one-page outline of the top three themes you've found. Use this as a compass.
• Budget Overruns: Discovery takes time, and time is money. Mitigation: build a contingency of 20% of the edit budget for exploration. If you run out, you must commit to a structure.
• Team Frustration: Some editors prefer structure. Forcing a Source-First approach on a Story-First editor can cause friction. Mitigation: align team roles with workflow preferences during hiring or project assignment.

Story-First Pitfalls

• Script-Footage Mismatch: The script may call for footage that doesn't exist or is weaker than expected. Mitigation: have the researcher and editor review the archive before finalizing the script. Create a 'feasibility pass'.
• Missed Opportunities: The best material may be left on the cutting room floor because it doesn't fit the script. Mitigation: schedule a 'discovery day' after the assembly edit where you watch unused clips and consider adding a new scene.
• Stakeholder Scope Creep: Stakeholders may request changes that require reshooting or refinding footage. Mitigation: lock the script contractually, and treat changes as a separate revision cycle with additional budget.
• Burnout from Repetition: If the script is long and the footage is limited, editors can feel like they are just 'filling slots'. Mitigation: rotate editors between projects or allow creative freedom within scenes (e.g., choosing B-roll without script constraints).

General Risks Across Both Workflows

No matter which workflow you choose, inadequate communication between the editor, producer, and stakeholders is the most common cause of rework. Weekly check-ins with a shared timeline or progress board can mitigate this. Additionally, both workflows suffer when technical infrastructure is neglected—failing to back up, using inconsistent codecs, or ignoring metadata standards. Invest in a simple media management plan at the start, and you will avoid most crises.

7. Mini-FAQ and Decision Checklist

This section addresses common questions editors ask when choosing their workflow, followed by a practical decision checklist to guide your choice.

Frequently Asked Questions

Q: Can I switch from Source-First to Story-First midway? Yes, and many teams do. The hybrid approach—explore with Source-First, then lock structure with Story-First—is often the best of both worlds. The key is to set a clear transition point (e.g., after the first string-out review) and communicate it to the team.

Q: Which workflow is better for AI-assisted editing? AI tools like automated transcription and scene detection currently support both. For Source-First, AI can accelerate logging by generating tags. For Story-First, AI can help match script lines to footage. However, AI still requires human oversight to avoid errors.

Q: How do I convince stakeholders to allow time for Source-First exploration? Frame it as risk reduction. Show examples where a script-driven edit missed key material. Offer a trial on a small project to demonstrate the value. Many stakeholders are open once they see the depth of discovery.

Q: What if my archive is poorly organized from the start? You have two options: invest in a one-time organization effort (Source-First) or work around it with a very flexible script (Story-First). The former is better for long-term value; the latter is faster for a single project.

Decision Checklist

Use this checklist to determine which workflow to use for your next project:

• ☐ Is the story already well-defined by research or client brief? → If yes, lean Story-First.
• ☐ Is the source material rich and surprising? → If yes, lean Source-First.
• ☐ Is your timeline tight (
• ☐ Do you have a large team with diverse editing styles? → Hybrid with clear transition point.
• ☐ Is the archive intended for reuse? → Source-First or at least invest in metadata.
• ☐ Is your budget flexible? → Source-First can absorb discovery costs.
• ☐ Is the editor experienced with both approaches? → Let them choose based on material.
• ☐ Are stakeholders likely to request changes after seeing a cut? → Story-First reduces revision cycles.

If you checked more than 4 items on one side, that workflow is likely your best starting point. Remember, you can adjust as you go—the goal is a calmer, more intentional edit, not a rigid dogma.

8. Synthesis and Next Actions

We have explored the two fundamental approaches to archival editing—Source-First and Story-First—from conceptual frameworks to practical execution, tools, economics, growth mechanics, and risks. The key takeaway is that no single workflow is universally superior. The right choice depends on your project's goals, constraints, and team dynamics. However, the act of consciously choosing is itself transformative. Many editors fall into one approach by habit, unaware of the alternatives. By understanding both, you gain the flexibility to adapt to each project's unique demands.

Immediate Next Steps

1. Audit your current workflow: Review your last three projects. Which approach did you use? Was it effective? Note where you struggled—were those struggles related to discovery (Source-First) or script alignment (Story-First)?
2. Experiment with the opposite approach: On your next small project (e.g., a 3-minute video), try the workflow you don't normally use. Document what felt different, what was easier, and what was harder.
3. Establish a metadata baseline: Even if you prefer Story-First, implement a minimum set of metadata tags for every project: date, source, subject, and key people. This will pay dividends in future reuse.
4. Talk to your team: Share this article and discuss which workflow aligns with your collective strengths. If there is disagreement, consider a hybrid model with clear phases.
5. Set a review cadence: Schedule a 30-minute check-in at the midpoint of each edit to assess whether the chosen workflow is working. Be willing to pivot.

The calmest edit is not the one with the most tools or the fastest cutting—it's the one where the editor understands why they are making each decision. Source-First and Story-First are not just methodologies; they are philosophies of how we relate to our material. Choose wisely, and your edit will be more than efficient—it will be joyful.