Guide
What goes in a board package, and how often
A board package is the set of documents a company sends its directors before each board meeting: a short letter from the CEO on what happened and what needs deciding, the financial statements against budget with the variances explained, the key operating metrics, cash and runway, the resolutions being voted on, and the minutes of the last meeting. Send it five to seven days before the meeting. Most companies between seed and Series B meet quarterly, with a one-page monthly update in between; the package should take a director thirty minutes to read and should never be the first place they learn bad news.
By Vanward. Published 2026-09-14. Updated 2026-09-14.
The board package is the one document a company produces on a schedule for people who have the power to replace the CEO. That makes it worth getting right, and it makes it worth keeping short. A good package lets a director walk into the meeting already knowing what happened, so the meeting can be spent on what to do next.
What goes in, in order
1. CEO letter (one to two pages)
What happened since the last meeting, what you expected to happen, and the difference. The three or four decisions you need from the board, stated as questions. What keeps you up at night. Written in plain prose by the CEO, not assembled from slides. Directors read this first and many read only this closely, so the letter should be able to stand alone.
2. Financial statements against budget
Income statement, balance sheet, and cash flow for the period and year to date, each with the budget (or the plan the board approved) alongside and a variance column. Every variance over a threshold you set in advance (say, 10 percent or $25,000, whichever is larger) gets one sentence of explanation. The statements should be on the same basis every period, and the balance sheet should have been reconciled to the bank and the ledger before it goes out. A footnote states whether the numbers are management-prepared, reviewed, or audited.
3. Key metrics (one page)
The five to eight numbers the business actually runs on, each with the definition, the current period, the prior period, and the plan. For a software company that is usually revenue or ARR, net revenue retention, gross margin, customer count and churn, sales pipeline or bookings, and burn. Pick them once, define them in writing, and do not change the definitions without saying so in the letter. A metric whose definition drifts is worse than no metric.
4. Cash and runway
Cash today, net burn for the period, months of runway at current burn, and the date you expect to need new capital. If runway is under twelve months, this section moves up to the front of the letter. Show the forecast the runway number comes from, at least in summary, so the board can see the assumptions.
5. Resolutions and consents
Every item the board is being asked to approve, with the exact text of the resolution and a short memo on why. Option grants (with the grant list and the 409A valuation they rely on), new hires above a threshold, financings, material contracts, changes to the plan. Sending the text in advance is what lets the vote take two minutes instead of twenty.
6. Minutes of the last meeting
For approval. Minutes record attendance, the decisions taken, and the votes, not the discussion. Keep them short and keep them boring; they are a legal record.
7. Appendices
The detail behind any of the above: the full forecast model, the hiring plan, the sales pipeline, a product roadmap, customer references, a competitor note. Label each appendix with the section it supports. Nobody is obliged to read an appendix, which is why the important things are not in one.
How often, by stage
| Stage | Board meetings | Written update | What changes |
|---|---|---|---|
| Pre-seed and seed | Quarterly, often informal | Monthly one-pager: cash, runway, revenue, three priorities | The package is the monthly update plus a financial summary; observers may be on the list |
| Series A | Quarterly, sometimes every other month | Monthly one-pager to the board and major investors | Full package as above; budget versus actual becomes the spine of the financial section |
| Series B and later | Quarterly, with committees (audit, compensation) meeting in between | Monthly reporting package with a metrics dashboard | Reviewed or audited statements, committee reports, a formal risk section |
Whatever the cadence, send the package on the same schedule every time. A package that arrives five days before one meeting and the morning of the next tells the board more about the company than anything inside it.
Timing and the close
The package cannot go out until the books for the period are closed, and the close cannot finish until the reconciliations are done. If the board meets in the third week of the month after quarter end, the close has to finish by business day ten. Companies that struggle to send the package on time almost always have a close problem, not a reporting problem; the month-end close checklist is where to start.
Six mistakes that cost credibility
| Mistake | Why it hurts | Instead |
|---|---|---|
| Bad news first appears in the package | Directors feel managed rather than informed | Call the chair before the package goes out |
| Metrics redefined between meetings | The board cannot compare periods and stops trusting the page | Define once in writing; flag any change in the letter |
| Financials that do not tie | One number that does not reconcile puts every number in doubt | Close, reconcile, then report; footnote the basis of preparation |
| A sixty-slide deck | Nobody reads it, so the meeting becomes the reading | Two-page letter, short statements, appendices for the rest |
| Resolutions introduced in the meeting | Directors vote on text they have not read, or defer | Exact resolution text in the package |
| Sending the package as an email attachment | It is forwarded, it goes stale, and it cannot be withdrawn | A link the company controls, with the current version and a record of who opened it |
Distribution
A board package is the most sensitive routine document a company produces. Send it through a link scoped to each director, so the company can see who opened it, replace a page without resending, and close access when a director leaves. In Vanward, BoardReadi builds the package from the same verified evidence the readiness score reads (statements, cap table, and the executive narrative) and shares it as a ReadiLink stamped “Prepared with Vanward”, one per director, revocable at any time.
Questions founders ask
- How long should a board package be?
- Short enough to read in thirty minutes: a two-page letter, three to five pages of financials, one page of metrics, and the resolutions. Appendices can be as long as you like because nobody is obliged to read them. A sixty-page deck is a sign the company is reporting instead of governing.
- How far in advance should the board package go out?
- Five to seven days before the meeting, and never less than three. Directors who read it in advance ask better questions and the meeting spends its time on decisions. If the numbers are not final, send the package with the prior month closed and a note on what is still open rather than sending everything late.
- Do I need a board package before I have an outside investor?
- You need the habit. A monthly one-page update to yourself and your co-founders (cash, runway, revenue, the three things that matter this month) takes an hour and is the draft of the package you will send when the first investor joins the board.
- Should the financials be audited or reviewed?
- Management-prepared statements are normal until Series B; say so on the page. What matters is that they are prepared on a consistent basis each period, that they tie to the bank and the general ledger, and that the board receives the same numbers investors and lenders receive.
- What should I leave out of a board package?
- Surprises. If a customer churned, a key hire resigned, or cash is shorter than planned, the chair and any director with a right to know hear it by phone before the package lands. The package documents the situation; it should not announce it.
Related