Organize a large event collection by separating ingest, working edit, approved masters, guest delivery, and long-term archive. Give every camera and event segment a stable identity before files are copied. Then use metadata and status, not a maze of manually renamed folders, to track what is ready.
The goal is to make every file's stage and owner clear.
Start with verified ingest
Synchronize camera clocks before the event. Assign camera or photographer codes. On ingest, copy to two controlled destinations and verify the transfer before clearing cards. Record missing card ranges and failures immediately.
A practical initial structure is:
- Event
- Originals by date and camera
- Working catalog
- Approved masters
- Urgent selects
- Guest derivatives
- Sponsor or client exports
- Delivery records
Do not place edited files back into the original folder.
Use naming and metadata for different jobs
A filename can carry event, date, camera, and sequence. Metadata should carry location, session, people when useful, rating, rights, and delivery status. Keep filenames operational and easy to scan.
Standardize controlled terms such as start, finish, keynote, sponsor, awards, and backstage. Free-form variations make filtering unreliable.
Cull in passes
- Remove corrupt, accidental, and severe technical failures.
- Group bursts and obvious duplicates.
- Select the best expression or action within each group.
- Check coverage against the brief.
- Flag client holds and approval-dependent images.
- Create the delivery set.
- Run a final quality and rights check.
Do not spend detailed edit time on a frame before deciding whether it belongs in the final story.
Build the guest layer separately
The guest gallery should use optimized derivatives and a deliberate access model. For large participant sets, Event Face Finder can add event-scoped recovery without changing the master archive.
Operational checklist
- Clocks and camera IDs standardized
- Two verified source copies
- Originals protected from editing
- Duplicate and reject rules agreed
- Brief coverage checked
- Restricted images flagged
- Public, client, sponsor, and guest outputs separated
- Delivery status recorded
- Final archive owner and handoff date assigned
- Restore and delivery processes tested
Record each batch at ingest, preserve the source files, and mark when a collection moves from working set to delivered gallery to archive.
Set up the gallery before you share it
Create the event, choose access and download rules, then test the guest route from a phone.
Create an event
