Loading the interactive demo for "Audit the whole pack the night before"… The lesson text below is already here. The hands-on part loads next (requires JavaScript).
Studios don't eyeball packs. They table them. Drop up to twenty files and get dimensions, metadata tags and carrier scores per file, exportable as CSV.
This is the closest free taste of Distribution mode: the same gates, run by hand, once per pack.
Reading the table
Tags column: any number above zero ships location and device data unless you strip it. The metadata chapter is the fix.
Carrier column: green means standard methods, amber means robust, red means verify with a round-trip before trusting.
Unreadable rows are usually HEIC or TIFF. Convert to delivery formats first, then re-audit.
The night-before ritual
Audit, strip tagged files, assign methods by carrier tier, export the CSV into your release notes. Four steps, ten minutes, zero retractions.
The exported report is your paper trail: when a leak happens, it proves what shipped clean and when.
Takeaways
- Audit packs as tables, not vibes: every file gets dims, tags, carrier.
- Strip tagged files, assign methods by carrier tier.
- Export the report into your release notes for the paper trail.
Check yourself
Optional, local, instant. 0/2 answered.
- The tags column shows 14 on three files. What now?
- What goes into your release notes?
For your niche
Wedding deliveries run hundreds of files: audit in 20-file batches per gallery section and staple the CSVs together.
Monthly packs are small enough to audit whole. Make it the last step before the drop goes live.
Client revision folders accumulate strays. Audit the final delivery folder, not the working one.