Make a shoot media manifest that catches missing files
List the clips a small edit needs, distinguish same-named files and show which dependencies are missing.
A local media inventory, a small dependency map and an explicit missing-file list before editing begins.
Original FreeStack editorial workflow, checked 19 November 2026.
About this guide & its examples
The example is a fictional process illustration, not a provider screenshot, executed automation or customer result.
Illustrations are FreeStack concepts, not provider screenshots. Check the free limits below and test your own files before delivery.
Free boundaries before you start
What’s free, whether you need an account, and when we last checked.
draw.io · checked 2026-11-19
Published browser/desktop applications are free for personal/business diagramming under provider terms; editor source is Apache 2.0. Local files have no provider credit, watermark, cloud-storage or seat quota. Choose and back up your own storage. Atlassian apps and third-party platforms have separate terms.
No account needed for the local-device diagramming workflow. Optional cloud storage requires its own account.
LibreOffice · checked 2026-11-19
Free MPL2.0 office suite with separate component licences. Core local editing/export has no provider credit, watermark, storage or seat quota.
Core local work does not require a provider account.
A small example to aim for
The missing clip needs a route.
The detail clip is unconfirmed. Hold the dependent edit.
Process illustration only. Not an executable flow, provider screenshot, tested automation or customer result.
Illustrative example · adapt it to your project.
Jump to a step
Write the expected set first
For a fictional three-clip shoot, list what the brief says should exist: establishing shot, detail and closing shot. In LibreOffice Calc create an Expected sheet before inspecting the folder. Keep uncertain expectations marked unconfirmed. This is a manual preparation exercise, not a claimed file scan.
Record files without renaming originals
On a separate Inventory sheet record relative folder path, exact filename, clip role, observed duration, optional displayed file size and source revision. Add expected/present/missing status. Copy values you can actually inspect; unknown metadata stays unknown. Use authorised files and keep originals unchanged. Do not put private access URLs or personal data in the example.
Resolve same-name collisions
Two camera folders can both contain clip001.mp4. Treat folder plus filename as the reference, not the filename alone. Record which source belongs to which role; do not assume matching names, sizes or thumbnails prove files are identical. This guide does not compute checksums or certify backup integrity.
Show the dependencies of one edit
In draw.io choose a local-device diagram, reviewing the provider terms yourself. Make a document shape for each required source and a central Review cut shape. Connect only the files the proposed cut needs. Label a missing clip MISSING rather than drawing it as present. This map describes dependencies; it does not move, validate or render media.
Compare expected with observed
For each expected role, record the matching inventory reference or leave MISSING. If a clip is absent, ask the authorised source owner or inspect an approved backup; never substitute an unrelated clip silently. Record any agreed replacement and its revision. Hold the dependent edit until the source decision is clear.
Export a handoff that preserves names
Keep the editable Calc workbook and .drawio source locally. Export the inventory as a CSV copy if the recipient needs one, then reopen it and check delimiters, paths, special characters and any identifiers with leading zeros. Export a diagram PNG or PDF and check that the MISSING labels survive. Local files still need backup; no export test is claimed for this editorial example.
Save the kit and name a real upgrade
Save this toolkit keeps the two catalogue links in a private signed-in stack, not the media or inventory. Guest saves stay browser-local. FreeStack editorial upgrade triggers: a large recurring library, required checksum verification, proxy relinking or governed shared storage that manual records cannot reliably handle. Check the specific requirement before paying for an asset manager or automating access.
Your workflow, connected.
Follow the steps and carry the output into the next stage. These are suggested handoffs, not automatic integrations.
Provider information
Check current plans and documentation before committing to a workflow.
A couple of useful questions
What is free?
draw.io’s published applications are free for personal and business diagramming under its terms; its editor source has an Apache 2.0 licence. LibreOffice is MPL2.0 software with other component licences. This local workflow has no provider export-credit, watermark, hosted-storage or seat allowance. Your device, backup and asset rights remain separate; Atlassian integrations have separate terms.
Do I need accounts?
No account is required for draw.io’s local-device workflow or core local LibreOffice work. Cloud storage and third-party integrations have their own account and service conditions.
Does this replace a media asset manager?
No. It is a manual inventory and dependency exercise for one small edit, not automatic indexing, checksum verification, backup or Mermaid Flow’s production stack.
What does Save this toolkit save?
Catalogue links in your private signed-in stack. It does not upload the diagram, connect cloud storage, accept provider terms for you or run a workflow.
What would you try?
Share your result or ask a specific question about this workflow.
Join the conversation