Separating confirmed sponsor money from a pipeline
The sponsor list on the committee agenda has fifteen names, and nobody can say how much of it is real.
The short answer
Sponsor money is confirmed only when there is a written agreement, a stated amount, an agreed benefit scope and a payment date. Everything before that point is pipeline, however warm the conversation felt.
Keep the two on separate lines in the budget. Pipeline can be shown as a labelled scenario, never added to the base.
A status ladder that avoids wishful counting
Give every sponsor conversation exactly one status, and let the status decide where the amount is shown.
| Status | Evidence needed | Where it appears |
|---|---|---|
| Identified | A name and a reason the audience fits | Not in the budget |
| Contacted | A message sent, no reply yet | Not in the budget |
| In discussion | A named contact has asked for details or a proposal | Scenario only |
| Verbally agreed | Interest stated, nothing signed | Scenario only, flagged |
| Confirmed | Signed agreement or written acceptance, amount and benefits stated | Base budget, at net |
| Paid | Funds received in the account | Cash position |
| Declined or lapsed | Written no, or deadline passed | Excluded, kept in the record |
Why verbal agreement is not enough
A senior person saying yes in a corridor usually means interest in principle. Scope, amount, invoicing entity, payment date and what the sponsor receives are still open.
Any of those can change the value or delay it past a cost you must pay. Record verbal agreements, but treat them as scenario.
Using probabilities honestly
You may weight pipeline amounts in a scenario, but the weights are your own judgement, not a forecast. Label them as such, for example Committee view, entered by the secretary.
The sponsor revenue sensitivity calculator takes confirmed, possible and lost amounts with probabilities you type in, and keeps committed net income apart from pipeline.
Keeping one source of truth
- Create one tracker with a row per sponsor and one status per row.
- Name one person who may change a status, and require a document reference for Confirmed.
- Review the tracker at each committee meeting before the budget is discussed.
- Record the date and reason for every move to Declined or lapsed, so the scenario can be updated quickly.
Related decisions
How far confirmed income can carry the budget is in what sponsor income can and cannot solve. Deciding when the pipeline must convert, or the plan changes, is in setting a sponsor funding deadline and fallback plan.
Worked example · Fictional example
Fifteen names reduced to what the budget can use
Fictional organisation and figures, illustrative only. They are not rate benchmarks.
A fictional professional-development association lists fifteen prospective sponsors with a combined hoped-for amount of RM 150,000. The treasurer converts the list to statuses before the budget meeting.
Two are confirmed with signed letters, four are in discussion, three are verbally agreed, two were declined and four have not replied. Only the two confirmed are in the base budget.
| Status | Count | Net amount | Treatment |
|---|---|---|---|
| Confirmed | 2 | 18,000 | Base budget |
| Verbally agreed | 3 | 21,000 | Scenario, flagged |
| In discussion | 4 | 30,000 | Scenario |
| Declined | 2 | 0 | Excluded |
| Contacted, no reply | 4 | 0 | Not shown |
Use this yourself
Sponsor status tracker columns
Set up these columns in a shared spreadsheet. One row per sponsor, one status per row.
- Sponsor name and the person who owns the relationship:
- Status from the ladder above:
- Evidence reference for Confirmed, such as signed letter file name and date:
- Gross amount, estimated delivery cost, net amount:
- Benefits promised, linked to the sponsor inventory builder:
- Payment date and invoicing entity:
- Date of last contact and next step with owner:
- Committee-entered probability for scenarios, labelled as judgement:
- Reason and date if declined or lapsed:
Handle it in-house, or bring in help?
Your team can usually handle this when
- There are few sponsors and one person tracks them.
- Agreements are short and signed by someone with authority.
- The committee accepts that only confirmed net income enters the base.
Outside planning help earns its fee when
- Several people talk to sponsors and statuses disagree.
- Senior members have made verbal promises that are not recorded.
- Finance needs a clean split between committed and possible income before approving spend.
Need the sponsor tracker and budget view set up?
An Event Blueprint can plan the commercial workstream with you: a status ladder agreed with your committee, a tracker, a budget view that keeps confirmed and possible amounts apart, and decision dates. Your team keeps every sponsor conversation, and no sponsor result is promised.
Questions organisers ask
Is an email saying we are interested enough to count?
No. Interest is a good sign and belongs in discussion or scenario. Count money once an agreement states the amount, the benefits and the payment date.
Can I add a percentage for likely sponsors to the base budget?
Keep percentages in a scenario and label them as your own judgement. The base budget holds only confirmed net amounts.
What if a confirmed sponsor later withdraws?
Move the row to Declined or lapsed with the date and reason, then use the fallback agreed in advance. Check what the agreement says about cancellation.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.