Skip to main content
Skip to Content
← All insights
Procurement · 7 min read

The four numbers that kill an event production RFP, and the six inputs we'd rather have.

Most of the corporate event RFPs we read are missing the same handful of numbers, the ones that actually let a producer price the work in 24 hours instead of two weeks. Here's what's missing, what to hand us instead, and what a scoped brief looks like when it's done right.

If you're on the procurement side, your instinct is to keep an RFP neutral: let the field propose, compare on the back end. That's correct for commodity categories. Event production isn't one of them. The more specific your brief, the sharper the bid spread you'll see, and the easier it is for your scoring committee to compare apples to apples on inputs that actually move the number.

1. The venue: named, not described.

The single biggest swing factor in a corporate event production quote is the venue. Load-in rules, rigging plot, union labor tier, power on the floor, freight elevator schedule, these are venue-specific facts, and on a Houston flagship we routinely see them swing the production line by a meaningful percentage between two rooms that look similar on a venue deck.

"A downtown Houston hotel ballroom for 1,200" is not a scope. "Hilton Americas Grand Ballroom A, 72-hour load-in window starting October 12" is. If the venue is TBD, say so explicitly and hand us the shortlist, we'll scope against the most expensive likely room so you're not the one explaining a surprise to the CFO.

2. The count: as a band, not a ceiling.

Attendee count drives staging size, sight-line design, audio zoning, camera count, and breakout-room distribution. A registration cap of "up to 1,500" tells us to design for 1,500, but if your three-year average attendance is 850, we're over-spec'ing audio and lighting noticeably and you're paying for empty seats.

Hand us two numbers instead: your target (what your event marketing is driving toward) and your lower-bound commitment (what you're contractually obligated to cover regardless of registration). We design around the target and scope contingency against the floor, that's what protects the budget and the show flow at the same time.

3. The lead time: in business days, not a calendar date.

When you write "event is October 17, RFP decisions by July 1," you're saying: "responses need to accommodate a 108-business-day production cycle with procurement approval at business day 40." Tight, but workable.

When you write "RFP due Friday, award Monday, event in three weeks," you've selected for rental-desk vendors who can spin up inventory on a Tuesday. The crews doing flagship-quality work are already booked on that timeline, and the ones who aren't, you don't want.

Rule of thumb: 12 business days between award and load-in is the floor for a corporate flagship of any size. Less than that, expect premium pricing, thinner crew bench, and a shorter list of quality bids in your inbox.

4. The scope tier: light, moderate, heavy.

Production scope sorts into three tiers that any competent producer prices against, even if your RFP doesn't name them. Make it easy on yourself and name yours up front:

  • Light, slide deck on LED, lower thirds, walk-in music, two wireless mics. The general session runs clean: no custom scenic, no video packages, no rehearsal day on-site.
  • Moderate, custom scenic (wings, header), three or four video packages (open, transition, close, award montage), one rehearsal day, breakout AV for up to six rooms.
  • Heavy, full scenic build, cinematic content package, multi-camera broadcast or IMAG, two or three rehearsal days, dedicated show caller, multi-room breakout with bonded switching.

Tell us which tier you're buying and we'll come back inside a tight range. Don't tell us, and you'll see bids from three different tiers in the same stack, which makes your scoring committee's apples-to-apples job impossible.

The six inputs we'd rather have.

The four numbers above are the ones whose absence kills a response. Here's the affirmative version, the same six-input brief our producers fill in before they pick up the phone. Hand us these and a senior producer can come back inside 24 hours with a real range, not a placeholder.

  1. Named venue, or a named shortlist with the load-in window for each. (Tells us labor tier, rigging plot, power, freight.)
  2. Attendance band, your target and your contractual floor. Two numbers, not one. (Tells us staging, audio zoning, breakout distribution.)
  3. Lead-time runway, business days from award to load-in. Twelve is the floor for a corporate flagship. (Tells us crew bench and rehearsal posture.)
  4. Scope tier, light, moderate, or heavy, declared by you. (Tells us where on the production-cost curve you're shopping.)
  5. The outcome the event has to land, the board approval, the pipeline target, the re-signal moment your CEO owes the market. (Tells us what we're actually being hired to protect.)
  6. The decision-maker and the decision date who signs, by when, with procurement in the loop. (Tells us how to structure the response so it survives your internal process.)

That's the brief. Three paragraphs of input from you, a 24-hour turnaround from us, and a scoring committee that can actually compare like-for-like. The producer-caliber field of vendors, the ones you want bidding, can all work from this same six-input frame. That's the version of "apples to apples" that survives procurement.

What a good RFP brief actually looks like.

Three paragraphs. Ten minutes to write, six weeks of back-and-forth saved. Notice it hits all six inputs without reading like a form:

"We're producing our annual customer summit, October 12-14 at Marriott Marquis Houston. Target attendance is 1,400 (floor: 1,100). Load-in begins October 9, rehearsal day October 11, strike October 14 afternoon."

"Scope tier: moderate, custom scenic for the general session stage, four video packages, six breakout rooms with standard AV, one rehearsal day. No broadcast or hybrid, in-room only."

"Decisions by July 30, contracts signed by August 15. Outcome we need to land: this summit re-signals our enterprise roadmap to our top fifty accounts, with our CRO speaking on day two. Primary contact is Jane Patel, head of events; she'll run the RFP with procurement. Reach her at [email protected]."

One last thing.

If you want the producer-caliber field actually interested in your event, tell them the outcome it has to land, the board approval, the pipeline target, the re-signal moment your CEO owes the market. That's Input #5, and it's the input that separates an event experience partner who's thinking about your show from a rental desk who's quoting against your spec sheet. The same instinct that shows up on the production-cost side as the levers we publish at /investment shows up on the procurement side as this: fewer inputs, better signal, faster scope.

Want a producer to help structure your next RFP?

Fifteen minutes on the phone with a senior SCP producer, no pitch, we'll help you write the six-input brief that gets you a clean bid spread and a 24-hour turnaround from the partners worth talking to.

Book a strategy call
Book a strategy call Skip to main content