How to Compare Event Production Quotations

Two totals can describe two different productions

One quotation includes setup, rehearsal, show operators and removal. Another lists equipment and delivery. Both might be headed “event production”, but they are not necessarily offering the same work.

That difference is easy to miss when the first thing being compared is the final amount.

Compare responsibilities and exclusions before comparing totals.

The task is to understand what each supplier proposes to deliver, how it responds to your event and which work still sits elsewhere. You do not need to become a system designer to ask those questions.

Give every supplier the same current requirement

Start with the production brief used for the enquiry. Check that each supplier has received the same event dates, venue space, programme, stage activity, content requirements and working windows.

If a remote presenter or performance was added after the first enquiry, send that change to all suppliers whose proposal it affects. A quotation based on an earlier programme cannot be treated as a response to the revised one without review.

Record which brief or revision each quotation answers. Where the requirement is still developing, distinguish confirmed work from allowances, options and items that depend on later information.

You can use the supplier-neutral Event Production Brief Builder to organise the starting information. It helps describe the requirement; it does not assess whether a supplier's proposed system is suitable.

Compare the delivery scope

For each required part of the event, ask what the supplier includes and what somebody else must provide.

Sound, video, lighting, staging and backline may each contain equipment, preparation, installation and operation. A heading naming the discipline does not explain the extent of that responsibility.

For example, “video” could mean supplying screens, operating presentations, producing graphics, providing cameras or recording the programme. Those are different tasks. Ask which ones form part of the proposal rather than assuming the heading includes all of them.

Check the interfaces too. If the venue provides a stage, who confirms it suits the programme? If the client supplies slides, who receives the final files and checks them for playback? If an artist carries part of the equipment, who confirms the remaining local supply?

An exclusion may be reasonable where another appointed team owns the work. It becomes a problem when the event needs the work and nobody is responsible for it.

Ask what the proposed system is intended to achieve

Suppliers can propose different technical approaches to the same requirement. A longer equipment list is not automatically a more suitable solution, and matching item names does not establish equivalent performance.

Ask the supplier to explain how the proposal supports the event: what the audience needs to hear and see, what happens on stage, what presenters or performers need, and how remote participation or other critical activity will be handled.

A technical rider may identify specific artist requirements. If a proposal changes those requirements, distinguish an alternative awaiting approval from one already agreed. “Equivalent” should not silently become permission to substitute whatever is available.

Where specialist assessment is needed, involve the appropriate technical people. Comparing proposals does not make the organiser responsible for approving engineering, electrical or structural work outside their competence.

People and time belong in the comparison

Check which people are included and what work they will do. Delivery crew, setup technicians, programme operators and production coordination have different functions. One general staffing line may not make those distinctions clear.

Review the relevant production schedule. Does the proposal cover the actual access, setup, checks, rehearsal, show and removal windows? Are the event dates and any overnight work understood? Do the people required for rehearsal remain available for the show?

Time is part of the production requirement. A proposal based on a generous build window needs review if the venue later allows much less time.

Ask how the supplier has allowed for load-in, movement routes, transport, storage and load-out. A delivery to the loading point is not necessarily the complete movement and installation requirement.

Do not assume a fixed crew multiplier, universal overtime rule or standard setup duration. Obtain the supplier's actual basis and identify what a change to the agreed working conditions would affect.

Make a comparison record

A short scope record can be more useful than placing two equipment lists side by side. Use your event's requirements as the rows, then record each supplier's answer and the owner of any work outside their scope.

Consider this illustrative comparison. It is not a real quotation or a supplier ranking:

• Presentation playback: Supplier A includes operation; Supplier B lists equipment but does not state operation. Ask Supplier B who will run the files.
• Rehearsal: Supplier A allows for the stated rehearsal window; Supplier B bases its proposal on show time only. Ask whether the required rehearsal is included and request a revised response if needed.
• Stage: Supplier A excludes it on the assumption that the venue provides it; Supplier B includes one. Confirm the venue provision before treating that difference as an unnecessary cost.

The useful result is a clearer scope, not a score awarded for the most line items.

For each important requirement, use explicit states such as included, excluded with another owner, optional, or awaiting clarification. These describe a proposal's status, not a new universal quotation format. Keep unknown information visible rather than treating a blank cell as “not required”.

Read the assumptions and conditions

Look beyond the equipment and labour sections. Identify stated assumptions about access, venue provision, content deadlines, artist requirements, connectivity and the programme.

Check which items are optional or provisional rather than included in the main total. Establish the quoted currency, whether stated taxes and other charges are included, the proposal's validity and any conditions affecting availability. Read the supplier's stated payment, change and cancellation terms through the appropriate commercial review process.

These are points to clarify in the actual proposal, not a legal interpretation or a claim that every supplier uses the same terms. If a condition is unclear, ask for it to be explained before relying on it.

Ask for a revised answer where necessary

Send specific questions. “Please sharpen your price” does not tell the supplier which responsibility appears missing.

A useful clarification might be: “The event includes a two-way remote interview. Does your proposal include the room's return audio and video, a technical test and someone to operate the connection? Please identify anything you expect us or the venue to provide.”

Ask the supplier to reflect material clarifications in the current written proposal. Keep the agreed scope, exclusions and assumptions together rather than spreading them across an old quotation and several unconnected messages.

If the programme, working windows or supplier responsibilities change, review the affected proposal. An earlier total should not be treated as confirming work that was never described to the supplier.

Choose against the requirement

Once the scope differences are understood, compare the totals alongside the proposed approach, delivery responsibilities and unresolved risks. A higher price does not automatically mean better production; a lower price does not automatically mean a missing item.

The question is whether the response is suitable for the event you intend to deliver, with responsibilities you understand and conditions you can work within.

Keep the accepted scope available during production advance. The quotation is part of that working information, not a replacement for coordinating the programme, venue, suppliers and later decisions.