Utilisation certificates without the panic: a reporting calendar for funded incubators

The CohortOS team · · 3 min

If your incubator runs on grant money, you know the week before a utilisation certificate is due. Someone is chasing receipts, someone else is rebuilding a spreadsheet of which startup received what, and the program itself stops. The certificate is never the hard part. The hard part is the evidence, collected all at once, months after the fact.

The fix is boring and it works: collect a little evidence every month, on a calendar everyone can see.

1. Work backwards from the funder's dates

Start with the dates you cannot move: the end of the financial year, your sanction letter's reporting schedule and any review visits. Put them on one calendar, then add internal deadlines two to three weeks earlier. The internal date is the one your team works to.

WhenWhatOwner
MonthlyDisbursements and receipts filedFinance
MonthlyStartup milestones reviewedProgram manager
QuarterlyStartup KPIs refreshedFounders
QuarterlyDraft progress reportProgram lead
Year endUtilisation certificateFinance and director
A starting calendar. Match the rows to your sanction letter.

2. Keep one folder per startup, from day one

Every disbursement needs a paper trail: the agreement, the invoice, the proof of payment and the startup's own record of what the money did. Create the folder structure when a startup joins the cohort, not when the auditor asks. Name files the same way every time so anyone on the team can find them.

3. Tie money to milestones

Funders don't only ask where the money went. They ask what it achieved. If each tranche is linked to a milestone with a due date (a prototype, a first paying customer, a pilot), the progress section of your report is already written. You only have to show which milestones were completed and explain the ones that slipped.

4. Refresh startup numbers every quarter

Ask founders to update the same handful of numbers every quarter: revenue, burn, runway, team size and funding raised. Keep the request short and on a fixed date, and founders will learn to expect it. Export a snapshot each quarter and keep it with the report, so you can show the change over the year.

5. Draft the report before you need it

Write a rough progress report at the end of each quarter, even if nobody asked for one. By year end you have four drafts to merge instead of a blank page. The utilisation certificate then becomes what it should be: a summary of numbers you already trust.

Keep reading

Run your next cohort from one place.