Budget and revenue of an event

Track an event’s discussed budget, expected revenue and signed amount to manage profitability from the first conversation.

Knowing an event's value from the start helps you prioritize, negotiate and steer your profitability. Joinways distinguishes three separate amounts: the budget the client mentions, the expected revenue you estimate, and the amount actually signed. Tracking these three figures turns a gut feeling ("this file looks big") into a numbers-based read on every opportunity.

For a venue manager, the difference matters: a stated budget is not guaranteed revenue, and an estimated revenue isn't signed yet. By separating these three stages, you see where each file sits between the first conversation and the signature, and you measure your estimation gaps over time.

The point isn't just to fill in boxes: it's to keep, file after file, an honest view of what your order book is worth. A well-maintained pipeline tells you at any moment how much revenue is hoped for, how much is signed, and where your best opportunities are concentrated.

Prerequisites

An event created in Joinways, ideally linked to a contact and an inquiry.
A quote so the signed amount fills in automatically on acceptance.
The right to edit the event in order to enter the budget and expected revenue.
Access to revenue reports if you want to use these amounts in aggregate.

What you'll learn

Enter the discussed budget and expected revenue on an event.
Understand how the signed amount links to accepted quotes.
Track the value of your pipeline and compare forecast with actual.
Use these amounts in your reports and commercial decisions.

The amounts tracked

Joinways tracks three amounts for each event, each matching a stage in the commercial relationship. Understanding them avoids mistaking an intention for a commitment.

Discussed budget: what the client has in mind, often extracted from the incoming inquiry. It's an intention, not a commitment.
Expected revenue: your estimate of the file's value, in light of what you plan to propose.
Signed amount: the total of accepted quotes — that is, the revenue actually committed by the client.

The logic runs from least certain to most certain: the discussed budget opens the conversation, the expected revenue reflects your judgment, the signed amount is authoritative. That progression is what your reports compare.

Reference: the money fields

Here's each field in detail, its source and how it updates.

Discussed budget — entered manually, often taken from the inquiry or the automatic extraction of the incoming email; editable at any time.
Expected revenue — entered manually by you; reflects your estimate and can be adjusted as the file matures.
Signed amount — calculated automatically from accepted quotes; you don't enter it by hand.
Accepted quotes — the source of the signed amount; each signed quote feeds the file's total.
Amendments — included in the signed amount, which reflects the latest validated version.
Revenue reports — consume all three amounts to compare forecast and actual across the portfolio.

Where to enter them

The discussed budget and expected revenue are entered from the event sheet. The signed amount fills in on its own: it derives from the quotes. So you only fill in two fields; the third follows.

Open the relevant event.
Enter the discussed budget as the client stated it.
Enter the expected revenue according to your estimate.
Let the signed amount update automatically when quotes are signed.
Adjust the expected revenue if your estimate changes.

How it works

The first two amounts are declarative: they reflect what you know or estimate at a given moment. The third is derived: Joinways adds up the file's accepted quotes to produce the signed amount, and updates it on every signature or amendment.

You enter the discussed budget and expected revenue.
The client signs one or more quotes.
Joinways recalculates the signed amount from accepted quotes.
A signed amendment updates the signed amount to reflect the latest version.
All three amounts flow into your revenue reports.

Why track all three

Tracking a single amount isn't enough to steer. It's the combined read of all three that reveals a file's health and, across the portfolio, that of your business.

Prioritize: the discussed budget tells you, from qualification, which files deserve the most attention.
Forecast: the expected revenue aggregates a view of upcoming revenue before any signature.
Measure: the gap between expected revenue and signed amount reveals how accurate your estimates are.

Edge cases

A few situations to know so you read the figures correctly.

Budget not disclosed: if the client states no budget, leave the field empty rather than inventing a figure — a wrong discussed budget skews your analyses.
Several quotes on one file: the signed amount adds up all accepted quotes, not just the latest one.
Quote rejected then re-signed: only an accepted quote counts; a rejected quote doesn't enter the signed amount.
File with no quote: until a quote is accepted, the signed amount stays at zero even if the expected revenue is filled in.

💡 Good to know: these amounts feed your revenue reports (forecast vs signed). The earlier and more honestly you enter them, the more reliable your revenue forecasts.

Best practices

Capture the budget at qualification to prioritize big files.
Estimate a realistic rather than optimistic expected revenue, for usable forecasts.
Compare expected revenue and signed amount to measure your estimation gaps.
Use this data to fine-tune your offers and sales pitch.
Revisit the expected revenue after each major exchange with the client.
Keep the discussed budget faithful to what the client said, without rounding it up.

Troubleshooting

Problem: the signed amount stays at zero even though a quote was sent.

Cause: a sent quote is not an accepted quote; until it's signed, it doesn't feed the signed amount. Solution: check the quote's status and wait for (or chase) the client's signature.

Problem: expected revenue and signed amount diverge sharply.

Cause: your initial estimate was too high or too low, or the file's scope changed. Solution: analyze the gap, refine your estimation method, and adjust the expected revenue on open files.

Problem: the discussed budget looks inconsistent with the rest of the file.

Cause: the field may have been pre-filled by the automatic extraction of an ambiguous email. Solution: correct the discussed budget manually so it reflects what the client actually stated.

Real-world example

An inquiry mentions "budget around €15,000." The planner notes it as the discussed budget, estimates expected revenue of €16,500 expecting to propose a few extra services, and finally signs at €17,200 with two added options. The three amounts tell the file's story: an intention at 15,000, an estimate at 16,500, a commitment at 17,200.

Another example

For a wedding, the couple share no precise budget. The planner leaves the discussed budget empty but estimates an expected revenue of €22,000 based on comparable files. After two successive quotes (venue then catering) are accepted, the signed amount settles at €20,400. The €1,600 gap with the estimate informs the next forecast on this type of file.

FAQ

Does the signed amount include amendments?

Yes. It reflects the latest validated version, amendments included. A signed amendment updates the file's signed amount.

Who enters the discussed budget and expected revenue?

You do, manually, from the event sheet. The discussed budget can be pre-filled from the incoming inquiry, but stays editable.

Can the signed amount be edited by hand?

No. It's calculated from accepted quotes. To change it, act on the quotes (signature, amendment).

What's the point of expected revenue if it's only an estimate?

To steer your pipeline: it gives you a revenue forecast before signature and a benchmark to measure your estimation gaps.

What happens if several quotes are signed on the same event?

The signed amount adds up all the file's accepted quotes, to reflect the total committed revenue.

Do these amounts appear in reports?

Yes. They feed your revenue reports, which notably compare forecast (expected revenue) and actual (signed amount).

Should I enter a budget even if it's approximate?

Enter it if it's meaningful, otherwise leave it empty. A made-up figure degrades your analyses; missing data beats wrong data.