Reporting to a Board Without Drowning in It
What a governing body actually needs each quarter, what it should not approve, and how to build a pack that takes an afternoon, not a fortnight.
The pack that takes a fortnight
The quarterly board pack is, in most incubation centres, a fortnight of work. Someone assembles numbers from a spreadsheet, a bank statement, an email folder and a colleague's memory, and produces thirty pages that are mostly narrative.
The board reads the first two pages, asks a question the pack does not answer, and the next quarter repeats.
Both halves of that are fixable, and they are the same fix: decide what the board is for, and record what it needs during the quarter rather than assembling it afterwards.
Decide what the board decides
The most common governance failure in incubation centres is a board that approves operational things.
A board should decide:
- The annual plan and budget
- Major policy: IP, equity, eligibility, fee structures
- Significant deviations from the plan
- Senior appointments
- Whether the centre's strategy is working
A board should not decide:
- Individual admissions
- Individual tranche releases
- Space allocations
- Day-to-day operational matters
The reason is timing. If a board approves admissions, selection runs at the board's meeting cycle - which means telling applicants they will hear in eleven weeks, which loses you every applicant with an alternative. It also makes your selection panel decorative, which is unfair to the people on it.
Where a board wants oversight of admissions, the right shape is reporting rather than approval: here is who was admitted, here is the process that was followed, here are the scores.
The one-page summary
Put a single page at the front that a member who read nothing else could still contribute from:
- Where the centre is against its annual plan, in three lines
- The two or three things that need a decision this meeting
- The one thing that is going wrong
- The one thing that is going well
The third item is the one people leave out, and it is the one that makes a board useful. A pack that reports only progress teaches the board that everything is fine, which means the first bad news is a surprise and is treated as a crisis rather than as something being managed.
What to include, and what to leave out
A workable structure, roughly ten pages:
1. Summary - one page, as above.
2. Activity this quarter - applications received and admitted, current cohort size, sessions delivered, events held, space occupancy. Numbers, with the previous quarter alongside.
3. Funding - committed, released, remaining, by source. Include committed-but-unreleased, because it is the number that produces year-end surprise and boards rarely ask for it until it is too late.
4. Outcomes - cohorts that have graduated: survival, stage progression, funding raised, jobs. Measured against the cohort that entered.
5. Risks - two or three, with what is being done. Not a register of everything imaginable; the ones that would actually change the year.
6. Decisions required - each with the options and a recommendation.
7. Appendix - the detail, for anyone who wants it.
Leave out narrative descriptions of individual startups unless a board member asked. It is the largest section in most packs and the least used.
Report outcomes against the entering cohort
The single most common way incubator board reporting misleads, usually unintentionally.
If a cohort of twenty admits twenty, fifteen finish, and twelve of those fifteen are still trading two years later, "80% survival" is technically about the graduating cohort and materially wrong as a picture of the programme. Against the twenty who entered it is 60%.
Pick the entering cohort as your denominator, say so in the pack, and keep it consistent. A board that later discovers the denominator changed will not trust any other number in the document.
Make the pack a query, not a project
The fortnight is spent assembling, not writing. It shrinks when the underlying records are kept as events during the quarter:
- Applications with their scores, retained per evaluator
- Disbursements with their milestone, evidence and approver
- Space allocations with their payment history
- Updates collected on a schedule, with a record of who has not answered
- Startups marked closed with a date and reason when they stop
With those, the activity and funding sections are queries. What is left is the summary, the risks and the recommendations - which is the part that actually needs a person, and the part that gets squeezed out when the assembly takes a fortnight.
Bring problems early
The strongest thing a centre head can do with a governing body is report a problem while it is still small.
A grant renewal that looks uncertain, a cohort that is under-subscribed, a key staff departure, a scheme condition you may not meet. Raised early, these are things a board can help with - members often have exactly the institutional relationships needed. Raised late, they are things a board has to react to, and the reaction includes wondering what else it has not been told.
A short quarterly checklist
- One-page summary, including what is going wrong
- Activity numbers with the previous quarter alongside
- Funding: committed, released, remaining, committed-but-unreleased
- Outcomes measured against the entering cohort
- Two or three real risks with actions
- Decisions stated with options and a recommendation
- Nothing in the pack that the board should not be deciding
Frequently asked questions
- What should a governing body approve?
- The annual plan and budget, major policy such as IP, equity and eligibility, and significant deviations. It should not approve individual admissions or individual disbursements, because that slows operations to the meeting cycle and makes the panel process decorative.
- How often should an incubator board meet?
- Quarterly is right for most centres. Monthly turns the board into operational management; twice a year is too infrequent to catch a problem while it is still small.
- How long should a board pack be?
- Ten to fifteen pages, with a one-page summary at the front that a busy member could read alone and still contribute. Longer packs get skimmed, which is worse than shorter packs that get read.
- What do boards most often ask for that is hard to produce?
- Outcomes for past cohorts. Most centres can report activity easily and outcomes badly, because outcome data requires having tracked companies after graduation - which is a decision made two years earlier, not at reporting time.
