It was 10:48 PM the night before a wedding.
My phone rang. The florist.
She had never received a production file. She didn't know what time load-in was. She didn't know how many centerpieces to bring. She didn't know where the ceremony arch was supposed to go. I spent the next 45 minutes on the phone rebuilding every detail from memory — guest count, table layout, ceremony timing, the exact measurements of the reception hall entrance.
When I hung up, I thought: every coordinator in this industry has had this call.
The florist who showed up to the wrong entrance because no one sent the floor plan. The caterer who brought 15 extra staff because the headcount spreadsheet was from three months ago. The AV team that started teardown during the after-party because nobody updated the timeline. We've all accepted these moments as "just how this industry works."
They don't have to be. The production file is the solution — and this article explains exactly what it is, what's in it, and how to build one without it consuming your entire week.
What Is an Event Production File?
An event production file is a comprehensive operational document — or more accurately, a set of documents — that contains everything every vendor, staff member, and stakeholder needs to execute an event successfully. It's not a guest list. It's not a run-of-show. It's not a proposal deck.
It's all of those things, organized into a single packet that anyone could pick up on day one and understand exactly what's happening, when, where, and with whom.
Think of it as the operational nervous system of your event. When something goes wrong — and something always goes wrong — it's the document you reference to recover.
The 11 Documents in a Complete Production File
A well-built production file contains eleven core components. Here's what each one does:
1. Proposal
The agreed-upon scope of the event. What's included, what's not, client expectations, and the high-level vision. This is what everyone references when someone says "I thought we were doing X."
2. Production Notes
The director's commentary on the event. Special considerations, client preferences, known complications, VIP guests, anything that a first-time staff member couldn't know from the other documents alone. This is the institutional memory of your planning process.
3. Rental Order
Every piece of furniture, linens, dishes, glassware, and equipment — with quantities, supplier names, delivery windows, and setup instructions. The rental order is how you catch the discrepancy between "60 charger plates" and the 62 guests you're actually seating.
4. Kitchen Prep
The culinary production timeline. When prep begins, when dishes need to be finished, plating sequences, dietary accommodations by table, service timing. This document lives with your catering lead from the moment they arrive on site.
5. Staffing Plan
Names, roles, arrival times, break schedules, and contact information for every person working the event. Proper staffing ratios by event type (1:8 for plated dinners, 1:12 for cocktail hours). This is what you hand your venue coordinator and what you reference when someone doesn't show.
6. Timeline
The minute-by-minute run of show from load-in through teardown. Vendor arrival windows, ceremony and program cues, meal service timing, sound checks — all of it. The timeline is the heartbeat of the production file. Everything else exists to support it.
7. Shopping List
Everything that needs to be sourced and who is sourcing it. Day-of supplies, décor elements, specialty items the rental company doesn't carry. This is the document that prevents the 9 AM call asking "did anyone grab the taper candles?"
8. Budget
Actual costs versus estimates, by line item. Deposit paid, balance due, payment dates. This document is how you protect yourself when a client says the final bill is higher than expected.
9. Floor Plan
A scaled diagram of the space: table layout, stage position, bar placement, lounge areas, AV equipment, exits, and load-in access. Vendors who've never seen your venue should be able to look at this and know exactly where they're going.
10. Weather Backup
For any event with an outdoor component: the contingency plan. Exactly what changes, who is responsible for making the call, what the threshold is (winds over X mph, rain probability over Y%), and the timing window for the decision. This document is the one you'll wish you had when the forecast changes 36 hours out.
11. Vendor Emails
Drafted confirmation emails for every vendor — catering, rentals, AV, florals, photography, transportation, security. Pre-written, ready to send, with all the relevant details from the production file already populated. This document alone saves three to four hours per event.
Why the Production File Is Mission-Critical
Without a production file, you are the production file. Every question — "what time does the caterer arrive?", "where does the photo booth go?", "is the backup tent still on?" — comes to you, personally, because you're the only one who holds all the information.
That's the 10:48 PM florist call. That's why coordinators work 70-hour weeks leading up to a large event. Not because events are inherently that complicated — but because the operational knowledge is concentrated in one person's head instead of distributed across a document.
A good production file does three things:
- Reduces incoming questions — vendors can self-serve most answers before calling you
- Accelerates recovery when things go wrong — you spend 2 minutes finding the relevant information instead of 20 minutes reconstructing it from memory
- Protects you legally and professionally — a documented scope, timeline, and budget is what you reference in a vendor dispute
How Long Does It Take to Build One?
Manually? Four to six hours for a standard 100-person event. More for larger, multi-day, or logistically complex productions. This is the time you spend pulling information from your email threads, updating the spreadsheet, reformatting the timeline, and making sure the floor plan matches the current guest count.
That's four to six hours you're not doing anything else. It's the cost of doing business that most coordinators just accept.
With Middleman, it takes 60 seconds.
You describe your event in one sentence — "Corporate mixer for 120 guests in San Francisco, rooftop venue, cocktail format, November 14th" — and Middleman generates the complete production file: all 11 documents, populated with the right details, formatted and ready to send.
Not a template to fill out. Not a form with 47 fields. A conversation. And then a production file.
Start Building Yours
The production file is the most important document you'll create for any event. It's also the one that gets skipped or half-finished when the timeline is tight — which is exactly when you need it most.
Start with the one-time preview at middleman.madethis.app/plan. Describe your event, watch the opening workflow build, and unlock the full production file on a paid plan.
Then you can get back to the part of this work that actually requires you.