The event scope of work template that makes vendor quotes comparable

Three vendor quotes land for the same event, and none of them sit next to each other. One priced a sit-down dinner, another a buffet nobody asked for. One included setup, another didn't say. The gap isn't really in the vendors — it's in what each one was actually asked.

Two documents share this name online. One is the contract an event agency signs with its own client. It lists what the agency will deliver, and what it costs. That's a different relationship, and a different document. This guide covers the other one — the brief an organiser sends to vendors. An agency sends the same brief too, on behalf of its client. It goes to the venue, the caterer, the AV crew, before any of them quotes.

Why quotes don't compare in the first place

The usual habit is a phone call, then an email. Then another email goes to the next vendor, worded slightly differently. Nobody writes it down once. Each vendor fills the gaps with their own assumptions — headcount, what's included, when they're needed on site. And prices those assumptions, not your event.

A shared brief removes the retelling. Everyone reads the same overview. And everyone answers against the same line, for their own category. What comes back can then only differ on price, lead time and fit. That's exactly what you want to compare.

What a scope of work actually is

The clearest definition isn't in a marketing template. It's in how the US federal government buys things. Federal contracting rules tell agencies to describe the work in terms of the required results rather than how the work is to be accomplished. Then you check performance against a measurable standard, not a guess. The same rules rank a performance-oriented document above a detailed, design-oriented one. State what you need, and let the vendor propose how.

UK procurement guidance says the same thing in plainer words: a specification is the document you give to suppliers explaining what you want to buy. It lists five things a good one carries: what you need, what it should do, how much, what quality, and when you need it. Swap “specification” for “scope of work” and those five lines become the columns of the table further down.

A scope of work states what you need; a request for proposal (RFP) wraps a process around it — deadlines, submission rules, scoring — and gets its own guide on this blog, later.

The overview every vendor reads first

Before any vendor category, write the event once, in plain language. Nine fields carry it all: the organisation, the event, its objective, audience and headcount, dates and times, venue, format, what's already decided, and a point of contact.

This block never changes between vendors. A caterer and a security firm read the exact same nine lines before they reach the one row written for them.

One row per vendor category

Under the overview sits the table that does the real work. One row per vendor category. Each row carries what's expected, the quantity, the constraints, load-in and load-out, an indicative budget, and the date a proposal is due. A venue, a caterer and a transport company each get their own line. Never a paragraph that mixes all three.

Meeting Professionals International puts the underlying goal plainly. Writing about vendor briefs, it says the first job of an RFP is to explain what the event is trying to accomplish, before any pricing question. Specifics matter just as much. A simplified running order lets a supplier estimate the resources that drive cost, instead of pricing blind.

What every proposal must include

Ask every vendor for the same eight things, and their answers line up on their own, without you reformatting a single quote.

• Price broken down by line item, tax shown separately.
• What is not included.
• Deposit and payment schedule.
• How long the quote stays valid.
• Load-in and load-out schedule.
• Certificate of insurance (liability).
• Cancellation terms.
• References from a comparable event.

Ask for the payment schedule specifically, not just the total. Leave it out, and default rules fill the gap instead of you. Between UK businesses, an unset schedule falls back to statutory interest of 8% plus the Bank of England base rate on late payment. Not a plan either side actually chose.

The timeline, and how you'll choose

Five dates carry a consultation. The scope of work sent, a deadline for questions, proposals due, the vendor selected, and the contract signed. Each one only makes sense after the one before it. A proposal deadline set before the sending date is a typo, not a plan. That's why the template turns that row red on sight.

Weigh your choice before the quotes arrive, not after. Six criteria, scored one to five: price, fit with the scope, references, availability and lead time, terms like the deposit and cancellation, and sustainability. Once quotes are back, score each vendor against these headings again in a dedicated comparison grid — weighted your way, not copied from here.

From the scope of work to a vendor's inbox

Once the scope is set, Squena turns each row into its own request — one need per vendor category, from your supplier database or typed in fresh. The budget stays private until you tick to state it.

One limit: the deadline set above isn't enforced. Nothing turns red here if a vendor runs late. That stays on you to track.

What a scope of work will not fix

A clear brief gets you comparable numbers. It does not get you a cheaper vendor, or a shorter list of candidates, or a guarantee that the right one answers by the deadline. Those are separate problems, worth solving separately, once the quotes you are comparing actually describe the same event.