An email software budget template with reforecast triggers and stop rules

Cost family : One of the separate budget groupings: subscription, implementation, operation, assurance, failure or exit.

Line cash : Unit price multiplied by quantity and periods.

Economic cost : The cost view that keeps internal effort visible alongside supplier cash.

Allowance : The purchased amount kept distinct from forecast use.

Confidence : The evidence-backed reason a cost estimate is rated high, medium or low.

Trigger : An agreed event or variance that requires a reforecast or other action.

Approval ceiling : The agreed limit beyond which the specified recovery action applies.

Variance log : A record of budget, actual amount, cause, owner and corrective action.

Start with the complete commitment

Budget the full commitment by showing subscription, implementation, operation, assurance, failure and exit separately, with internal effort beside supplier cash. Use the whole-life cost framework to organise the scope, not to supply a forecast. If a family is absent, rebuild the total before approval.

Record the model version, owner, approver, base date, decision horizon, currency, tax basis, inflation treatment, exchange-rate source, populations, message volume, chosen product edition and next review. The template was checked on 5 September 2026 for organisations in England. Finance and tax owners approve currency, accounting and VAT treatment.

Show internal effort as its own amount because supplier invoices do not capture work performed by the organisation. Calculate it as loaded hourly rate x hours, and record the rate source and denominator. Keeping this amount beside supplier cash makes the work visible even when no invoice is raised.

Use line cash = unit price x quantity x periods. For illustration only, £10 per user per month x 30 users x 12 periods equals £3,600 net. Applying 20% VAT gives £4,320 gross cash. Eight internal hours at a loaded rate of £50 per hour add £400; these figures are arithmetic examples, not market quotes.

Before approval, check that every amount can be tied to a unit, quantity and period, and that internal effort has not disappeared into supplier cash. Keep the supporting evidence so a later reforecast can be traced to its inputs. If any of those details cannot be named, the estimate is not ready for sign-off.

Populate the six-family map

Create a separate line for every item of work, with its deliverable, edition or role, unit, quantity and period stated. Subscription and usage lines should account for contact or send overage, users, storage and add-ons. A combined allowance without its parts hides scope and makes later review harder.

Project and assurance work can include discovery, cleansing, migration, integrations, DNS and authentication work, templates, accessible testing, privacy and PECR assessment, legal review, security assurance, training and project management. Give each activity its own line, so its scope and price evidence can be inspected rather than bundled into a general allowance.

Operating lines should cover approvals, list maintenance, suppression reconciliation, complaints, content, reporting, support, access reviews, incident exercises and recovery. Include renewal and exit planning, with contract review, notice management, export, validation, transition, dual running, deletion evidence and decommissioning. Price each activity rather than hiding the group in one allowance.

The Technology Code of Practice applies to government technology work in its defined setting. It offers lifecycle prompts for costs that may sit outside procurement, including accessibility, security, privacy and integration. Record those needs as explicit budget lines instead of leaving them inside a general allowance.

Keep all six families distinct and connect each item to a defined deliverable. A family without a named line leaves part of the commitment unaccounted for, whether the work is paid to a supplier or done internally. The budget is incomplete until each family has an identifiable place and supporting evidence.

Make every row reproducible

Give each budget item a row of its own and fill in scope, period, price evidence, VAT handling, confidence, accountable owner and revision trigger. These fields let another reviewer reproduce the amount later, instead of relying on memory or treating an unexplained pooled figure as evidence.

Use the blank row as the starting layout for a spreadsheet or CSV. Its columns follow the field dictionary, so the owner can carry the same information into a working template. Complete every field from evidence, and keep assumptions visible rather than concealing them in a total.

A complete row exposes the assumptions behind its amount and gives a reviewer what is needed for a later update. Do not leave an empty field if it could conceal scope, evidence, ownership or a revision event. Each line should remain traceable from its source to its current estimate.

Match the unit before comparing prices

Define the buyer-side unit and map the supplier's term before comparing prices whenever billing measures differ. Contact, marketable contact, send, active user, stored event and gigabyte can describe unlike quantities. Until the definitions match, the apparent unit prices do not provide a reliable comparison.

Keep purchased allowance and forecast use in separate columns, with a unit dictionary beside the cost-line sheet. This makes differences traceable without mixing incompatible measures. Compare pricing models only after the units agree, and give every quantity a clear, consistent basis.

The price comparison becomes useful only when both sides count the same thing and distinguish the purchased allowance from expected use. Settle the definition first, then compare the price. If the unit remains unclear, pause the comparison instead of treating a difference in terminology as a saving.

Let triggers determine the next action

Set a warning tolerance, approval ceiling and recovery action for each cost family, using the organisation's evidence rather than adopting the example values as universal limits. Reforecast when scope, quote, tax treatment, usage, defects, supplier terms or actual internal hours breach a defined trigger.

Use the recovery action that matches the cause and the agreed limit for that cost family. The example tolerances are illustrations, not recommended thresholds. A breached trigger calls for a reforecast; a stop condition calls for pausing commitment and taking the specified recovery action.

Keep a variance log beside the scenarios, recording budget value, actual value, cause, owner, corrective action and whether the remaining forecast changed. Classify each difference as timing, quantity, price, scope or error. An early monthly invoice and an unexpected contact-counting rule have different causes, so they need responses suited to the recorded variance.

Apply the warning, ceiling and recovery action to the cause in the log, not to an unexplained total. A trigger becomes usable only when an owner and action are assigned. If either is missing, the record does not yet tell the organisation what to do when the limit is reached.

Rebuild scenarios from their inputs

Revise low, central and high totals at input level whenever the results move without showing which assumptions changed. Vary specific quantities and prices, and record their source and confidence. Each scenario should expose the conditions behind its result instead of concealing unexplained adjustments in a final figure.

Inputs to vary include contact growth, send volume, remediation hours, support demand, exchange rate and renewal movement. Record the evidence and confidence behind each change. Do not alter a total without naming the input that moved, so differences remain attached to assumptions rather than becoming unsupported forecasts.

The Green Book 2026 discusses sensitivity, optimism bias and switching values for public appraisal. Apply its method proportionately without importing unsupported percentages. Record the evidence and the point where the decision changes; treat each scenario as a test, not a prediction.

Keep every scenario change linked to a named input and its evidence. That makes the case a decision test rather than an unexplained forecast, and lets reviewers see what would alter the result. Change an assumption and show its effect; do not adjust the total on its own.

Separate financial approval from other decisions

State what each reviewer is authorised to approve if a finance signature could be mistaken for risk clearance. Present the relevant cost views and identify each reviewer's authority separately. Financial approval alone does not show that privacy, accessibility, cyber or commercial requirements have been cleared.

Present totals by cash and economic cost, one-off and recurring, net VAT and gross cash, with quotes and assumptions attached. Show economic cost beside cash cost, and list unresolved matters with the value at which the decision changes for that organisation.

Record the scope and date of each signature, along with any unresolved matters. A finance approval covers the financial case, not another reviewer's decision. Privacy, accessibility, cyber and commercial reviewers keep separate stop authority, and the person responsible for each outstanding matter should be named.

Keep commitment on hold until checks close

Stop commitment when a required check lacks either an owner or evidence, and keep it stopped until both are available and the checklist is complete. An open legal, privacy, security, accessibility or exit item leaves an obligation untested. Financial approval cannot substitute for the missing review or evidence.

Keep the completed checklist with the assumptions and approval record once every required check has an owner and supporting evidence. The record should preserve the distinction between financial approval and specialist clearance. If either ownership or evidence is absent for a required check, commitment remains stopped.