Writing the variance narrative for your 12-month update

Most founders know they should keep trading reports. Far fewer attach a written explanation whenever the numbers in those reports drift from the original forecast — and that omission is the single easiest thing to fix in this entire area. A variance narrative is short, it takes minutes to write at the time something changes, and it is the piece of documentation that does the most work when an endorsing body eventually asks what happened.

Why the narrative matters more than the number

A trading report that shows only numbers forces the reader to guess at causation. A trading report that pairs each significant variance with a short written explanation removes the guesswork and, just as importantly, demonstrates that the founder is actively monitoring their own business rather than simply watching numbers pass by. This is the natural companion practice to monthly trading report discipline — the report shows what happened, the narrative shows that you understand why.

It also directly answers the concern raised in why endorsing bodies compare year-one actuals to plan: the risk is not variance itself, it is unexplained variance. A narrative written contemporaneously, with a specific date attached, is far more credible than an explanation constructed after the fact — because it cannot be accused of being reverse-engineered to fit whatever the number turned out to be.

The four-part structure

1. State the number and the original forecast, side by side

Do not bury the gap or lead with the explanation before showing the figures. State both numbers plainly, in the same sentence if possible:

This might feel uncomfortable to write, but hiding or downplaying a gap only makes it more visible when someone else does the subtraction. Leading with the numbers, unhedged, signals confidence that you can explain what follows.

2. State the specific reason for the gap

This is where founders most often go vague ("the market has been challenging") when they should go specific. A credible reason names a mechanism, not a mood:

Specificity is what separates a defensible narrative from an excuse. If you genuinely do not yet know the full reason, say so honestly and state what you are doing to find out — that is still more credible than a confident-sounding guess.

3. State what changed in strategy, and since when

A variance narrative that stops at "here's why the number is different" is incomplete. The stronger version shows the founder responded to the information rather than simply observing it:

This is the piece that connects directly to pivoting after endorsement without losing it — a real strategic response to a real signal, dated and specific, is exactly the kind of change that reads as good judgement rather than drift.

4. State the new forecast going forward

Close the narrative by updating the number, not leaving the reader to wonder whether the original forecast still stands:

This keeps your financial model current rather than static — see build a living business plan, not a museum piece for the broader discipline this feeds into — and gives your next reporting period a fresh, honest benchmark rather than one already known to be stale.

A worked before-and-after snippet

Before (no narrative — just the numbers):

After (numbers plus a written variance narrative):

Variance note: Gap driven by enterprise sales-cycle length running at ~11 weeks vs. a 5-week forecast assumption, based on 3 signed deals and 2 in final-stage procurement. Since Month 7, we introduced a paid pilot stage ahead of full contracts, shortening the cycle to ~6 weeks for the 2 deals opened under the new process. Revised Month 12–18 forecast: £9,000–£16,000/month; we will revisit at Month 12 with more data.

The table is identical in both cases. The second version is the one that survives a contact point meeting without a single follow-up question about whether the business is still viable.

Making this a habit, not a one-off

The founders who benefit most from this structure are not the ones who write one excellent narrative right before a review — they are the ones who write short, honest ones every month as part of routine reporting, so that by the time a formal checkpoint arrives, there is already a dated, coherent story running from the original plan through every subsequent change. If you are also actively changing direction as you go, the assumptions log is the natural companion document, tracking each individual assumption's history rather than the headline revenue number alone.

You can benchmark how well your current reporting and forecast structure would hold up against endorsement viability criteria using the free assessment tool.

Sources and further reading

• GOV.UK: Immigration Rules Appendix Innovator Founder — the ongoing viability and activity conditions your reporting should evidence.
• GOV.UK: Indefinite leave to remain — Innovator Founder visa — how consistent, credible reporting supports the ILR growth criteria.
• DavidsonMorris: Innovator Founder Visa — solicitor commentary on ongoing compliance and monitoring expectations.

Key takeaways

• A variance narrative is a short written explanation attached to a trading report whenever actuals diverge meaningfully from forecast — write it at the time, not before a review.
• Use a four-part structure: state the number against the forecast plainly, state the specific reason, state what changed in strategy and since when, and state the updated forecast.
• Specificity is what makes a narrative credible — name a mechanism, not a mood, and be honest if you don't yet know the full reason.
• A dated, contemporaneous narrative is more credible than an explanation reconstructed after the fact, because it cannot be accused of fitting the number in hindsight.
• Make this monthly practice, not a one-off exercise before a review — a running history of narratives is the strongest evidence of active, competent management.

• trading-reports
• variance-narrative
• endorsing-bodies
• business-plan
• annual-review