Festival ops · 9 min read
How a festival cuts its sponsor-asset cycle from eleven weeks to two
Pick any regional festival with 60-80 sponsors. Ask the sponsorship manager how long it takes to get from "sponsor signed" to "assets delivered to the print vendor." You'll hear a number between 8 and 14 weeks. Most of it is not creative work. Most of it is coordination.
Here's what's actually happening inside that window.
Week 1-2: The asset list.
The sponsorship manager emails the sponsor a Word document listing what's needed: full-page program ad, LED loop, crew-shirt logo, pre-show video. The document has specs in it — some written in 2019, some updated last year, some contradicted by the actual printer's current requirements. Nobody knows which.
The sponsor emails back: "What format for the LED loop again?" The sponsorship manager goes to ask the AV team. The AV team says "16x9 or ultrawide, we can run either, what's the client doing?" The sponsorship manager goes back to the sponsor. The sponsor doesn't respond for 4 days.
Week 3-4: The first draft.
The sponsor's agency sends a Dropbox link. It contains everything labeled "DRAFT_v3_final_ACTUAL.pdf" and two JPGs labeled "logo.jpg" and "logo_2.jpg." The JPGs are 1200 pixels wide. The festival needs vector.
The sponsorship manager writes back asking for vector. The sponsor's agency is out for a team offsite. Four days later, a new Dropbox link arrives. The SVG has a clipping mask that renders fine in Figma but not in the printer's RIP. The printer flags it.
Week 5-6: The spec debate.
The PDF ad is in RGB. The printer needs CMYK. The agency converts it and re-sends. The colors look different now. The sponsor is unhappy. A call is scheduled for the following week.
The call happens. The sponsor approves a new version. The agency ships the updated PDF. The bleed is 0.125" instead of 0.25". Reprint.
Week 7-9: The coordinator becomes the spec.
The sponsorship manager now has a shared Google Sheet with 60 rows, each representing a sponsor, each with 4-7 assets, each in its own state. They spend half their day updating status: "waiting on logo," "rejected, asked for vector," "approved but wrong bleed," "approved and sent to printer." They send 30 status-update emails per day.
The coordinator has no time to actually run the sponsor relationships. They're administering a spreadsheet.
Week 10-11: Panic.
Print deadline is Friday. 8 sponsors still haven't delivered. The sponsorship manager starts calling. Three are overseas. Two are on vacation. One has changed agencies. The replacement agency doesn't have the brand files.
The festival pays for a rush print run at 3x the normal rate.
---
Where the 9 weeks goes.
If you timestamp every event in this story, the breakdown looks like this:
- Creative work (actual design time): ~40 hours across all sponsors combined
- Spec clarification and chasing: ~160 hours
- Rejected-and-redo cycles: ~80 hours
- Status tracking and updates: ~120 hours
- Escalation and panic: ~40 hours
Creative is 40 hours. Coordination is 400 hours. The ratio is always like this. Nobody measures it because nobody thinks of it as a measurable problem.
---
What a verified brief does to the same timeline.
Week 1, day 1: The sponsorship manager picks a template ("Festival Sponsor Activation, 4 assets") and sends one branded link to each of 60 sponsors. The link is festivalname.gobrief.co/b/abc123xyz. Each sponsor sees their specific asks + specs + deadlines + a trust header explaining what happens next.
Week 1-2: Sponsors upload. Validation runs in their browser. An off-bleed PDF is rejected before it uploads. An RGB PDF is flagged with "convert to CMYK" as a suggested fix. A low-res logo is flagged with "upload vector or we'll auto-vectorize."
Week 2: Out of 60 sponsors, 48 are done. Reminders go out automatically to the other 12. Each reminder is a soft nudge, then a firm one, then an escalation to the account owner at the sponsor if it goes past the deadline.
Week 3: The sponsorship manager reviews the 60 approved packages in one view. Approves with one click each. Everything routes automatically: PDFs to the printer, LED loops to the AV team, shirt logos to the apparel vendor.
Week 3 ends and the festival's program-book file is at the printer. Nine weeks ahead of the old timeline.
That's where the 400 hours of coordinator time go. We don't build a tool to hold the files. We build the infrastructure that removes the person who manages the files.
That's the business.