Key Takeaways
- All seven red flags below are visible in the briefing process — before any contract is signed
- The red flag most frequently ignored is No. 3 (vague production specification) — it is also the one most likely to produce a show-day surprise
- A company that cannot tell you who the show-caller is at the briefing stage is a company that has not assigned one
The seven
Red Flag 1: Cannot name the show-caller. "Our experienced team" is not a show-caller. A show-caller is a named individual with a CV. If the company cannot name who will be calling your show at the briefing stage, it is because the role does not exist in their production structure or has not been assigned. Neither is acceptable for a 500-person event.
Red Flag 2: The portfolio has no references. If a company with ten years in production cannot provide contact details for three client-side project leads from the past 12 months, there is a reason. Ask for references in the briefing meeting. If they say they will send them "after the proposal," the references are being constructed. If they cannot provide them at all, the client relationships are not what the portfolio implies.
Red Flag 3: Vague production specification. A proposal that describes the PA as "professional audio system appropriate for the event" has not specified a PA system. A proposal that describes the lighting as "designed lighting for the conference" has not specified a lighting rig. The specification should be specific enough that you could issue it to a second supplier and get a comparable quote. If it is not specific, the company has not yet designed your event.
Red Flag 4: All-inclusive pricing with no scope definition. A proposal that quotes a single figure "for the complete event" without a scope definition is a proposal designed to be opened later — when additional scope items are added to justify a higher fee. Require a scope definition alongside any all-inclusive quote.
Red Flag 5: No process for scope changes. Every event has scope changes. A company with no defined change request process manages scope changes reactively — with verbal agreements on day, informal cost adjustments and post-event billing surprises. Require a written change request process in the contract.
Red Flag 6: Excessive upfront payment requirement. A payment structure requiring 70%+ before load-in from a new client relationship is unusual. Standard is 40% at contract, 40% at load-in, 20% post-event. Deviations from this structure warrant explanation — the most common legitimate reason is a supplier who has been burned by non-payment and is protecting themselves. Understand the reason before accepting unusual terms.
Red Flag 7: No direct production failure examples. A company that has never had a show go wrong in any material way has either not produced enough events to generate real failure, or is misrepresenting its track record. Ask specifically: "Tell me about a show that went wrong and what you did." A company that cannot describe a specific failure and its resolution is not a production company with deep operational experience.