The event proposal that gets lost in its own revisions

The first proposal rarely wins. Round two adds a second venue option. Round three cuts the dinner, grows the guest list and asks for a new payment schedule. Most agencies handle this inside one Excel file: they copy the budget tab, rename it "v2" or "rev3", change a few lines and send the file back. The client edits it, sometimes colours the cells they touched, sometimes doesn't, and returns it.

In the most extreme case I've seen, a single proposal went through 40 revisions. Most never get near that, but the trouble starts in round two.

On a large budget with hundreds of lines, nobody can reliably say what changed between two tabs unless the client marked the cells or wrote it down in an email. A quantity edited on the wrong tab, a formula that now points to last round's sheet, a supplier cost overwritten by hand: mistakes like these are easy to make, and nobody tends to notice until the margin has gone. eventIQ's Business Engine moves that work out of the file and onto one commercial record, with a live client area where the client reviews the budget, makes changes and compares scenarios, and an Excel export when someone still needs the file.

Key takeaways

• The real risk sits inside the one Excel file where revisions pile up as copied tabs. Extra attachments are a smaller problem.
• In a large budget, a change nobody marked is a change nobody sees. Errors slip through the same way.
• eventIQ gives the agency's client a web-based client area to view budgets, make changes, create scenarios and download Excel if needed.
• Versions and scenarios sit side by side on the same opportunity, linked to suppliers, approvals and margin.
• Each round starts from the last agreed version, never from the first meeting.

Why does one Excel file break across revision rounds?

It breaks because the file has no memory of who changed what. Excel holds numbers well. It doesn't tell you which of those numbers moved since the client last saw them.

The usual pattern looks like this. The agency builds the budget on one tab. For each round someone duplicates it, so the file now holds Budget, Budget v2, Rev3 client, Rev3 final. The client opens the latest tab, changes headcount, deletes the speaker dinner, lowers an AV line and saves. If they colour those cells yellow, the producer can find them. If they don't, the producer has to compare two tabs line by line, and on a 300 line budget that is hours of work nobody budgeted for.

Four things tend to go wrong:

• Changes are invisible by default. Unless the client marks cells or lists the edits, the agency learns what changed by hunting for it.
• Formulas cross tabs. A total on Rev3 still reads a cell on v2. The sheet looks fine and the number is wrong.
• Margin lives somewhere else. The internal cost and margin sit on a hidden tab or a separate file, so a price change on the client tab doesn't show its effect on profit.
• Mistakes go unseen. An overwritten unit price or a deleted row doesn't raise an alarm. It turns up later, at invoicing or at close.

Formal RFP teams treat buyer amendments as controlled changes for exactly this reason. In a July 2026 guide to tracking addenda, GreenLight RFP describes the steps: capture the change from the official source, compare it with the prior version, classify the impact, update every affected document and set a new baseline. Private client revisions are looser, yet the same test applies, and a shared Excel file makes the "compare with the prior version" step the hardest one.

Put the budget where the client can work on it

The answer is to stop sending the budget back and forth. In eventIQ the agency's client gets a web-based client area tied to the opportunity the team is already working on. There the client can view the budget, make changes, create scenarios and download an Excel file if their procurement or finance team still wants one.

That changes the shape of a revision round:

• One place, one link. The client opens the same client area every round. There is no question of which attachment or tab is current.
• Changes land on the shared record. The client edits the budget in the client area, so the agency works from the same numbers rather than a file that came back by email.
• Excel stays available as an output. If someone needs a spreadsheet, they download it from the current version. It no longer acts as the master copy.

eventIQ's proposals and lead management page describes the client proposal page as a place to review, comment, approve and export, with one version tied to the opportunity. The meetings, notes, budgets and next actions stay on that same record, so the context behind the numbers is there when the client asks why a line moved.

Keep versions and scenarios side by side

When the client wants to compare two venues or a smaller and larger production, the Excel habit is another tab. In eventIQ these become scenarios on the same budget. The budget and finance module lets you create client alternatives or internal scenarios and compare revenue and profitability as attendance, supplier cost, scope or selling price change, without duplicating spreadsheets.

This helps you sort each request before you reprice:

• Clarification: settles an open assumption ("about 200 guests" is now 180). Update the current version.
• Option: an alternative the client wants to compare. Keep the current version and add a scenario.
• Change: alters scope, price, timeline or exclusions. Treat it as a new commercial version before any supplier option moves.

Because scenarios live on one record, the client can look at option A and option B together, and you can show the price effect of each without rebuilding the plan.

Write down the assumptions you priced against before round one goes out: headcount, format, venue status, programme, commercial model, inclusions, exclusions and open questions. A one-line confirmation such as "we are pricing for 180 seated, one language, no livestream" saves you from learning in round two that they meant 250 standing with a bilingual stream. In eventIQ those assumptions sit on the opportunity with the meetings and notes that produced them.

Tie every change to cost, margin and suppliers

A revision is only safe when you can see what it does to profit. In a spreadsheet the client tab and the margin tab drift apart. On the Business Engine page, eventIQ lists "scope changes recorded beside financial impact" and scenario planning for scope creep as part of commercial continuity.

In practice that means:

• Suppliers sit on budget lines. The budget and finance module assigns suppliers directly to budget items, so a venue or AV change updates the line that carries that quote. Our guide to supplier management for event agencies covers keeping each supplier's quote versions in one record.
• Profitability is visible while you revise. Scenarios compare revenue and profitability, so a discount the client asks for in round four shows its margin cost before you accept it.
• Approvals follow the money. Approvals and workflows route decisions by transaction type, role, department and spending threshold, so a material price move reaches the person who owns margin.
• The won budget carries into delivery. After approval the same budget continues into supplier invoices, expenses and collections. Real-time budget control is the habit that takes over once the work is won.

Price movements still need words. When the total moves, name the lines that moved. A bare "total up 8%" (an illustrative figure) invites the client to reopen everything, while "AV up because of the second stage, catering down because the dinner moved to a cocktail" closes the question.

Run each round from the last agreed version

Professional services firms protect a signed scope with change orders. Rework's guide to the change order process (January 2025) keeps the agreed scope, the proposed change, its cost and schedule impact and the approver in one record, so a verbal "just one more thing" can't wipe out the baseline. Before signature, the opportunity record in eventIQ does that job for a proposal.

A practical routine:

Round one: set the baseline

Price the assumptions you have and label the open questions. Share the client area with one recommended version and, if useful, one cheaper or richer scenario. Ask the client to confirm the assumptions before the creative story.

Round two: collect changes in the client area

Ask the client to make their edits in the client area instead of sending a file. Sort them into clarifications, options and changes, and only then update the commercial version. If two venues are on the table, show them as two scenarios on the same budget.

Later rounds: decide, then lock

From round three on, everyone is tired and shortcuts look tempting. Check which version you are changing. If a request undoes something already approved, say so and show the price effect. Then ask for a clear decision: approve this version, pick the other scenario, or pause while procurement reviews. Leaving the loop of small tweaks open costs you margin and time.

Start with your next budget revision

Take the next proposal that comes back with comments and count the tabs in the file. If you can't say what changed since the last round without comparing them by hand, that proposal is a good test case. Bring it to a Business Engine demo and we'll rebuild it as one budget with scenarios and a client area, so you can see where the next round's changes would show up. The platform tour shows how proposals, budgets and approvals connect.

FAQ

How do I track client changes in an Excel event budget?

In a single Excel file you depend on the client colouring cells or listing edits, or on comparing tabs line by line. That works for small budgets and fails on large ones. Moving the budget into a shared client area means the client edits the same record the agency works on, with Excel kept as a download.

Can clients still get an Excel file from eventIQ?

Yes. The client area lets clients download Excel files when they need them, for example for internal procurement. The file is exported from the current version, so it doesn't start a parallel chain.

What is the difference between a version and a scenario?

A version is the commercial package currently on the table. A scenario is an alternative you compare against it, such as a second venue or a smaller guest list. Keeping both on one budget replaces the copied tabs.

How many revision rounds should an event proposal allow?

There is no fixed industry number. Agree a practical limit at the start, for example two structured rounds and then final sign-off, and treat anything beyond it as a commercial change with a new version. When rounds keep piling up, it usually means the baseline was never locked.