Key Takeaways
- Most RFPs generate incomparable proposals because the brief is ambiguous about scope
- The brief should specify what the production company owns versus what the client owns
- Technical capability questions reveal more than portfolio questions
- Budget transparency in the RFP improves proposal quality — vendors who cannot work within the stated budget should say so, not underbid and scope-creep
- The evaluation criteria should be weighted before proposals arrive, not after
Why most event RFPs produce incomparable proposals
An event production RFP that asks three companies to respond to the same brief routinely generates three proposals that cannot meaningfully be compared: one is priced at ₹25 lakhs, one at ₹38 lakhs and one at ₹52 lakhs, each with a different scope assumption baked in. This is not a vendor problem — it is a brief problem. When the brief is ambiguous about what the production company is responsible for, vendors make different assumptions about scope, which produces different prices that are comparing different things.
The purpose of an RFP is to get comparable, evaluable proposals from credible vendors. That requires the brief to be unambiguous about scope, budget parameters and evaluation criteria — not as a negotiating tactic, but as a prerequisite for an efficient procurement process.
What to include in the brief
Event overview (one page maximum)
The what, the when, the where and the why. Not the brand's mission statement. Specifically: event type (conference, launch, gala, concert, etc.), date, duration, location or location shortlist, expected attendance, and the primary outcome — what does success look like operationally and experientially?
Scope definition
This is the section that most RFPs get wrong by omission. Define explicitly what the production company is and is not responsible for. Common scope items to address:
- Venue sourcing and negotiation (production company responsibility, or client-owned?)
- AV specification and supply (production company or separate AV vendor?)
- Stage design and build (production company or separate set designer?)
- Lighting design (production company or third party?)
- Creative and content (production company or separate agency?)
- F&B (venue, third-party caterer, or production company?)
- Guest registration and delegate management (production company or client in-house?)
- Photography and video (production company or separate)
- Entertainment booking (production company or client/talent agency?)
- Post-event documentation and reporting
Technical requirements (if known)
If you have specific technical requirements — a minimum screen size, IMAG for a large room, a specific PA specification — state them. If you do not know what you need technically, state that you expect the production company to propose a specification and explain the reasoning. Both are acceptable in a brief. What is not acceptable is an ambiguous statement like "standard AV required" — it tells the production company nothing and guarantees incomparable proposals.
Budget parameters
Include a budget range, or a total budget with a scope expectation. "Please propose within a production budget of ₹25–35 lakhs" produces more useful proposals than "please provide your best pricing." Vendors who cannot deliver the event within the stated range should say so in their proposal — and a production company that responds to a ₹25 lakh brief with a ₹70 lakh proposal has not read the brief.
The argument for withholding budget ("we don't want to anchor vendors high") consistently produces worse proposals than the argument for stating it. A vendor who knows your budget designs the best event they can deliver at that number. A vendor who does not know your budget either underscopes (and wins the contract, then scope-creeps) or ignores the brief entirely and proposes what they think is ideal.
Evaluation criteria and weighting
State how you will evaluate proposals. A standard weighting structure for event production procurement:
- Technical capability and approach: 30%
- Creative concept and production design: 25%
- Team and references: 20%
- Commercial: 20%
- Sustainability / ESG: 5%
This weighting should be published with the RFP, not revealed at debrief. Vendors who know evaluation criteria design their proposals around what you are measuring.
Timeline and process
Brief issue date, site visit (if relevant), questions deadline, submission deadline, shortlist notification, pitch presentations (if required), award decision. Make this explicit and stick to it — vendors who lose working time waiting for an overdue RFP response process become less responsive when you are trying to produce the event.
The RFP process sets the terms of the production relationship — the precision and completeness of the brief correlates directly with the quality of proposals received.
The technical capability questions that reveal competence
Portfolio links and case study PDFs tell you what a production company has done. The following questions tell you how they work — and which questions a vendor cannot answer fluently is as revealing as the answers themselves.
- Who is the show-caller for this event, and what is their specific experience with this format?
- What is your PA system specification for this room and audience size, and which suppliers would you use?
- Do you own your structural staging, or is it sourced from a rental supplier?
- What is your technical advance process for artist or speaker requirements?
- What is your redundancy protocol for a venue power failure during the event?
- Can you provide the contact details of the client-side project lead from your most recent comparable event (not a testimonial — a reference who can receive a call)?
The template
Section 1: Event overview
Organisation / client: [Name]
Event type: [Conference / Launch / Gala / Concert / etc.]
Event date: [Date]
Duration: [Hours / Days]
Location: [City and venue shortlist or confirmed venue]
Expected attendance: [Number]
Primary outcome: [One sentence]
Brand brief / positioning document: [Attached / Available on request]
Section 2: Scope of production company responsibility
Venue sourcing: [Yes / No / Already confirmed]
Stage design and build: [Yes / No / Separate brief]
AV (PA, lighting, video): [Full supply / Supplementation of venue in-house / Specification only]
Creative concept: [Yes / No]
Content production (films, graphics): [Yes / No]
Entertainment booking: [Yes / No]
F&B: [Yes / No]
Delegate management: [Yes / No]
Photography / video: [Yes / No]
Post-event report: [Yes / No]
Section 3: Technical requirements
Minimum screen / LED size: [Specify or leave to production company to propose]
IMAG requirement: [Yes / No / Propose based on room]
PA specification: [Specify or leave to propose]
Lighting: [Specify or leave to propose]
Specific technical requirements: [List any known constraints]
Section 4: Budget
Total production budget: ₹[X] – ₹[Y]
Scope of budget (items included / excluded): [List]
Payment terms preference: [e.g., 40% at signature, 40% at load-in, 20% post-event]
Section 5: Evaluation and process
Evaluation criteria: [Paste weighting]
Questions deadline: [Date]
Proposal submission deadline: [Date]
Shortlist notification: [Date]
Pitch presentations: [Yes / No, Date]
Award decision: [Date]
What to do when proposals arrive
Score against the published criteria before reading commercial proposals. This prevents the common procurement error of anchoring to the price before assessing the capability. Meeting Professionals International publishes procurement best practice guides for corporate event buyers — a useful reference for teams new to evaluating production proposals. The most expensive proposal that demonstrates genuine production competence and a credible team is almost always worth more than the cheapest proposal from a vendor whose answers to the technical capability questions were vague. You will spend 9–12 weeks producing an event with this company. The negotiable variable is the commercial — the non-negotiable variable is whether they can actually deliver what you need.