Prepare an investor and board finance update

Direct answer

For this review, give a simple monthly investor-update structure: wins, misses, metrics, runway, asks, and next milestones.

Why this question comes up

Founders either overbuild investor updates or send vague updates that do not build trust. This guide turns that concern into a review that can be repeated with a defined period, consistent inputs, and a visible trail back to the records.

Records to gather

• Financial statements for the period, on a consistent basis
• Prior update, so figures and commentary stay comparable
• Budget or plan the period is measured against
• Cash position, runway, and any covenant status
• KPIs previously committed to, whether or not they improved

Review workflow

1. Lead with the headline and the ask. Board time is scarce. State performance against plan, cash position, and what you need from the room in the first paragraph.
2. Keep the metric set stable. Changing which metrics you report between updates reads as selection, even when it is not. If a metric is dropped, say why.
3. Report against the number you previously gave. The comparison that matters is against the plan or forecast you committed to, not a revised one.
4. Explain variances with causes, not restatements. “Revenue was 12% below plan because two enterprise deals slipped to Q3” is an explanation. “Revenue was below plan” is not.
5. Put the bad news early and plainly. Boards discover problems eventually; discovering them late costs credibility that is hard to recover.
6. Separate fact from forecast. Actuals, estimates, and projections should be visually distinct and labelled.

What a useful answer should include

• Headline performance, cash, runway, and the ask up front
• A consistent metric set, with any change explained
• Comparison against the previously committed plan
• Variance explanations traced to specific causes
• Risks and bad news stated early rather than buried
• Clear labelling of actual, estimate, and forecast

Common failure modes

• Rotating the metric set. It looks like hiding, even when it is not.
• Burying the risk on slide 30. The delay is what damages credibility, more than the problem itself.
• Restating variances as explanations. It wastes the meeting and invites harder questions.
• Blending forecast into actuals. Any figure a board cannot categorise, they discount entirely.

Community context

The linked community posts show why people search for this topic and which parts create confusion in practice. They are anecdotal. Use the reference sources and your organization’s policies for accounting treatment, tax, compliance, and final decisions.