--- title: "The 3-Collection Wedding Workflow: Dailies → Selects → Delivery (A Studio SOP That Scales)" author: "Cutsio Team" date: "2026-04-25" lastmod: "2026-04-25" category: "Video Workflows" excerpt: "Most wedding chaos comes from mixing raw footage, in-progress exports, and final deliverables. This guide shows the 3-Collection system in Cutsio—Dailies, Selects, Delivery—so your workflow stays organized, searchable, and easy to deliver." tags: - Workflow - Wedding Filmmaking - Video Management - Collections - Video Organization & Asset Management - Teams --- # The 3-Collection Wedding Workflow: Dailies → Selects → Delivery (A Studio SOP That Scales) If your wedding workflow keeps turning into scattered folders and “final_final_v3” exports, the fix is to separate raw footage, curated moments, and client deliverables into distinct stages. The best way to do that in 2026 is the **3-Collection system in Cutsio**: one Collection for Dailies (raw), one for Selects (curated), and one for Delivery (final). This keeps each wedding organized, searchable, and deliverable through a premium share page that works on every device. Here is the difference in practice: a polished Cutsio Collection share page for wedding films instead of an ugly Google Drive file link. ![Cutsio wedding film Collection share page compared with a Google Drive delivery link](/magica-films.jpeg) Want to see the live version? [Preview the Cutsio wedding film Collection](https://studio.cutsio.com/share/collection/8ce321ba-9f3b-47a8-839a-ec5408188880). ## Why do wedding studio workflows get messy as volume increases? Workflows get messy because studios mix stages: - raw footage sits next to exports - selects are scattered in timelines and local drives - delivery files are uploaded in different places each wedding This creates the most common operational failures: - you can’t find the latest export quickly - you lose the best moments for trailers and reels - re-delivery becomes a hunt across old folders - editors duplicate files to feel safe The solution is to treat each wedding as a staged pipeline, not as a folder. ## What is the “3-Collection system” and why does it work? The 3-Collection system is a simple SOP: 1. **Dailies Collection**: everything raw 2. **Selects Collection**: only the best moments 3. **Delivery Collection**: only the final package It works because: - each Collection has one job - you never confuse drafts with finals - the best moments are saved as reusable inventory - client delivery stays clean and consistent This is how wedding studios scale without turning into file administrators. ## What belongs in a Dailies Collection? Dailies should contain raw sources: - multicam footage - audio sources (lav, recorder, board) - ceremony camera masters - speeches camera masters - prep footage - reception coverage The Dailies Collection is not client-facing. It exists so: - your team has one home of footage - you can retrieve anything later - you can build selects without guessing where media lives If your archive is scattered today, start here: [The Wedding Film Library](https://cutsio.com/blog/wedding-film-library-home-of-footage/). ## What belongs in a Selects Collection? Selects should contain only what you would actually use: - best vows lines - best toast quotes - best reactions - best b-roll shots - strongest dance floor moments - iconic establishing shots The selects Collection is the compounding asset: - it makes editing faster - it makes trailers faster - it makes reels faster - it makes anniversary edits profitable If you want to build quote-driven selects faster, see: [Build a Vows + Speeches Library](https://cutsio.com/blog/wedding-vows-speeches-searchable-library/). ## What belongs in a Delivery Collection? Delivery should contain only final deliverables: - The Wedding Film (main) - Trailer - Ceremony (Full) - Speeches (Full) - Dances - Reels Pack - Add-ons (anniversary edits, family edit) This Collection is client-facing. It should be: - named cleanly - ordered intentionally - easy to play on any device For the delivery structure, see: [The Wedding Collection Delivery Workflow](https://cutsio.com/blog/wedding-collection-delivery-workflow-one-link/). ## How does this system reduce version chaos? Version chaos happens when: - exports live in multiple places - “final” means different things to different people With the 3-Collection system: - drafts live nowhere client-facing - finals live only in Delivery - selects live only in Selects If you do revision cycles, you version inside the Delivery Collection with clear names: - “Wedding Film (v1)” - “Wedding Film (Final)” The client never sees internal confusion. ## How does this system improve client experience? Client experience improves because delivery becomes consistent: - one link - one hub - all films and sub-films inside No: - multiple Drive links - folder confusion - download prompts This is why Collections are a delivery feature, not just organization. For the “platform” framing: [Best Wedding Video Delivery Platform in 2026](https://cutsio.com/blog/best-wedding-video-delivery-platform-2026/). ## How does this system reduce studio support workload? Support workload usually comes from: - “can you resend it?” - “my mom can’t access the folder” - “which file is the main film?” With the 3-Collection system: - re-delivery is one link - the Delivery Collection is always the official package - the structure stays stable over time That turns support into a non-event. ## How does this system help with guest phone footage? Guest footage is chaos unless you give it a destination. Add a fourth optional Collection: - “Guest Uploads” Then: - send an upload request link - everything lands in one place - you curate into Selects - you deliver the montage in Delivery For the full guest intake SOP: [How to Collect Guest Phone Footage](https://cutsio.com/blog/collect-guest-phone-footage-wedding-upload-collection/). ## How should a team collaborate inside the 3-Collection system? Teams need clear responsibilities: - Shooter/ingest role: populate Dailies - Editor role: promote best moments into Selects - Producer/QA role: ensure Delivery is correct and ordered When everyone knows where things go, you stop having: - random exports in random folders - “where did you put that?” messages This is a lightweight operations layer that doesn’t slow down creativity. ## What is a realistic step-by-step implementation plan for studios? Studios usually fail to adopt SOPs when the rollout is too big. The easiest implementation is to start with the Delivery Collection first (because it touches clients), then layer in Selects, then Dailies. Recommended rollout: 1. **Week 1:** Create Delivery Collections for new weddings only (one link, premium naming). 2. **Week 2:** Add Selects Collections so trailers and reels get faster. 3. **Week 3:** Add Dailies Collections as the canonical home for raw footage. This produces immediate value early, which increases adoption. ## What naming rules keep the system consistent across a team? Consistency beats creativity for operations. Use a deterministic pattern that never changes: - `LastName — YYYY-MM-DD — Dailies` - `LastName — YYYY-MM-DD — Selects` - `LastName — YYYY-MM-DD — Delivery` Then apply deliverable naming inside Delivery: - “The Wedding Film” - “Trailer” - “Ceremony (Full)” - “Speeches (Full)” - “Vertical Reels” When naming is predictable, you eliminate “where is it?” questions completely. ## What is the QA checklist before sending the Delivery Collection link? Before delivery, verify the Collection is client-ready: | Check | Pass criteria | |---|---| | Ordering | main film is first; trailer is second | | Naming | human names, no export codes | | Completeness | all promised deliverables included | | Clarity | long-form items labeled “(Full)” | | One-link policy | no separate links sent elsewhere | This is how delivery becomes productized instead of improvised. ## How do you promote moments from Dailies to Selects efficiently? Promoting should be a routine, not an art project. The simplest method is to do it in one focused pass: 1. Review the key story sections first (vows, speeches, first look, parent dances). 2. Save only the moments that would survive into the final film or trailer. 3. Keep selects tight: if a shot is “maybe,” leave it in Dailies. This keeps Selects small and high-signal, which is what makes it valuable. When Selects is curated, every future deliverable (trailers, reels, anniversary edits) gets faster. ## What are the most common mistakes when implementing this SOP? ### Putting everything in Delivery Delivery should be final-only. Otherwise clients see drafts and confusion. ### Not curating selects If Selects becomes “almost dailies,” it loses value. Curate aggressively. ### Overcomplicating naming conventions Keep naming consistent and simple: - `LastName — YYYY-MM-DD — Dailies` - `LastName — YYYY-MM-DD — Selects` - `LastName — YYYY-MM-DD — Delivery` ### Treating the system as optional SOPs work when they’re the default. If people bypass it, chaos returns. ## FAQ ### What is the best way to organize a wedding project? Use a staged system: one Collection for raw dailies, one for curated selects, and one for final delivery. This prevents mixing drafts and finals and makes retrieval and re-delivery easy. ### Why do I need a selects Collection? Selects are the compounding asset. They reduce editing time, speed up trailers and reels, and make future add-ons (anniversary edits) profitable because your best moments are already curated. ### How do I deliver multiple wedding films and sub-films cleanly? Deliver through a single Delivery Collection link that contains the main film and every sub-film in a clear order with human names. One hub link creates a premium client experience. ### Can I use this system with guest uploads? Yes. Use a dedicated Guest Uploads Collection for intake, curate the best clips into Selects, and deliver the final montage inside the Delivery Collection. ### Does this replace my editing workflow? No. It organizes your footage and deliverables. You can keep your existing editing pipeline while using Collections as the structure for intake, curation, and delivery.