An event production RFP is a specification, not an invitation to imagine. Its job is to make three or four companies quote the same event in enough detail that the differences between their proposals are real differences in approach, rather than differences in what each bidder guessed you meant. An RFP almost never fails because it was too short. It fails because it left the expensive variables — access, structure, drawings, and who owns them — for the bidders to invent on your behalf.
We read these documents from the other side of the table, and the pattern is consistent. The requests that come back with proposals you can actually compare are the ones that answer a production team’s questions before the team has to ask them. The requests that produce four wildly different numbers usually described a mood and a guest count, and nothing a shop can measure.
What follows is how to write an event production RFP that returns comparable, buildable proposals: what to include, what to leave open on purpose, and the handful of facts that change a bid more than any amount of creative language.
An RFP Is Not a Creative Brief
These are two documents with two different jobs, and collapsing them is the most common mistake we see. A creative brief tells a design team what the event is for — the audience, the objectives, the feeling in the room, the brand rules. It is written to unlock ideas. We have written separately about how to write an event brief that gets results, and that document still matters.
An RFP is a procurement instrument. It exists so that several companies can be measured against one another on a fixed set of facts. It is written to close variables, not open them.
Send both. Attach the brief so bidders understand the intent, and keep the RFP itself factual: site, scope, schedule, deliverables, and the form the response should take. When the two are merged into one document, the creative language tends to swallow the specification, and the section that determines whether a build is even possible gets two lines at the bottom.
Lead With the Facts That Move a Bid
Production companies price risk, not square footage. Every fact you withhold about the venue becomes an assumption, and assumptions are always padded in the direction that protects the bidder. The fastest way to sharpen every proposal you receive is to front-load the site conditions.
At minimum, state the following, and state it in the RFP rather than promising it later:
- The venue, the room, and the ceiling height at the lowest point over the build area.
- The loading dock or street access, and the freight elevator’s interior dimensions and door opening. This single measurement decides whether a structure ships assembled or as panels.
- Floor load limits and whether the floor may be penetrated, taped, or only covered.
- Rigging points, permitted overhead load, and whether the house crew or an outside crew hangs anything.
- Available power, its location, and who supplies distribution.
- The venue’s protection requirements and any restrictions on touching walls, columns, or landmarked surfaces.
- Whether a venue walkthrough is possible before responses are due, and when.
If you do not know some of these, say so explicitly and name the date you will know. A stated unknown is a shared risk. An unstated unknown becomes the bidder’s risk, and you pay for it in the proposal whether or not the condition turns out to be a problem.
The elevator dimension deserves its own sentence. A structure that fits an eight-foot opening and a structure that must break into four-foot panels are different builds, with different joinery, different finish schedules, and different install crews. That difference is set by a tape measure, not by design.
Describe the Build, Not the Feeling
The scope section is where an event production RFP earns its accuracy. Describe objects. A twelve-foot back-lit entry portal, a custom bar with a fabricated front and a functioning back bar, four scenic walls to conceal an existing interior, a suspended centerpiece — these are things a shop can draw, cut, and weigh. “An immersive, elevated arrival experience” is not.
If drawings exist, attach them, and say what stage they are at: concept sketch, design development, or construction-ready. If renders exist, label them as intent rather than specification, because a render will imply materials and joinery that nobody has engineered yet. The gap between a beautiful render and a set of shop drawings is where schedules die.
Working from a client’s existing files is entirely normal. The custom-fabricated Netflix trade show booth we built for the Meadowlands Complex came out of the brand’s own CAD drawings, and every one of those drawings went through engineering review in the first forty-eight hours — before a sheet of material was cut. Ask for that review to be named as a deliverable in the response. A bidder who does not mention engineering is either absorbing it invisibly or skipping it.
Be explicit, too, about ownership. Say who owns the drawings and the fabricated assets after the event, whether anything is intended to be reused or toured, and whether the pieces need to survive storage. Reuse changes construction: modular, crate-able, and repairable costs the shop more attention up front and saves the whole thing later. A bidder cannot make that trade-off if the RFP is silent.
Every fact you leave out of an RFP comes back as a padded assumption, a change order, or a surprise on install day. Usually all three.
Publish the Calendar, Not Just the Event Date
Most requests state the event date and stop. The event date is the least useful date in the document. What a production team needs is the sequence: when you will award the work, when design is locked, when drawings are approved, when the venue releases the space, and when the room must be clear.
Name these in the RFP:
- Proposal due date and award date.
- The date creative is frozen — the single most important line in the schedule.
- Load-in window, including the hour access begins and whether it is overnight.
- Rehearsal or client walkthrough, if any.
- Strike window and the hour the venue must be restored.
The gap between award and load-in is the real build cycle, and it governs what is achievable. Fast is possible when the decisions land early: the Café de Colombia activation at the San Diego Convention Center was designed, built, branded, and delivered in fourteen days, with retail-grade finishes and an integrated coffee bar built to retail operational standards. That compression worked because the scope stopped moving. A production schedule can absorb an aggressive calendar or a moving creative target, but not both.
If your date is immovable, say that plainly and ask each bidder what they would need frozen, and by when, to hit it. The answers are diagnostic. A team that has loaded structures into Manhattan freight elevators on a deadline will give you specific dates and a short list of decisions. A team that says it will “make it work” is telling you something else.
Ask for the Response in a Shape You Can Level
You cannot compare proposals that are organized differently. Dictate the structure of the response in the RFP itself, and the job of bid leveling stops being archaeology.
Ask every bidder to break the response into the same workstreams — design, fabrication, scenic finishes, lighting, AV, install labor, transport, strike — and to describe scope inside each one. Ask them to list what is explicitly excluded, and to state which elements they self-perform and which they subcontract. That last question quietly reveals the shape of the company. A firm with its own event fabrication shop answers it differently from a firm that brokers the build.
Then separate the core from the options. Define a base scope that every bidder must quote exactly as written, and list the additions you are curious about as named alternates. Now the comparison is clean: everyone quotes the same room, and the alternates tell you what each team thinks is worth adding.
Ask for a short assumptions section too. Where a bidder had to guess, you want the guess in writing. Assumptions surfaced in a proposal are negotiable. Assumptions discovered on site are change orders.
The Questions Worth Putting in Writing
Six questions belong in every event production RFP, because the answers separate bidders faster than any portfolio:
- Who performs engineering review on the structures, and at what stage?
- Which elements are built in your own shop, and which are outsourced?
- Who is on site during install, and who is the single point of accountability on show day?
- What is your test-fit process before anything ships?
- What happens if a drawing changes after fabrication starts?
- What did you have to solve on a similar build, and how?
The test-fit question is underrated. Assembling a structure in the shop before it goes on a truck is the difference between an install and an improvisation, and it is a practice you can ask about directly.
Send It to Fewer Companies
A request sent to eight firms produces eight shallow responses. A request sent to three or four, each chosen because their built work resembles what you are asking for, produces proposals with real thinking in them — because the bidders can see they have a genuine chance and will spend the hours accordingly.
Read the built work before you send anything. Look for structures at the scale you need, finishes at the quality you expect, and venues with constraints like yours. An RFP is a filter applied to a shortlist you have already earned, not a substitute for choosing one.
If you are drafting an event production RFP now and want a sanity check on the site facts, the scope language, or the schedule before it goes out, we are glad to read a draft. Our team handles full-service event production under one roof, which means we can usually tell you within a call which parts of your scope will drive the build and which will take care of themselves. Start a conversation with us and bring whatever you have, even if it is still a sketch and a date.