Most grants programmes don't have a calendar. They have a series of dates — application close, panel meeting, notification — that were agreed without modelling the work between them, without accounting for staff capacity, and without considering how the dates interact with each other and with the wider organisational calendar.
The result is a predictable pattern: application rounds that run over, assessment windows that get compressed, notifications that go out late, and staff who are stretched to breaking point at the same two or three points every year. Then a post-mortem, some adjustments, and the same pattern next year.
Building a proper grants calendar doesn't eliminate pressure. It makes pressure visible and manageable — which means you can respond to it rather than just surviving it.
The Grants Clock is a planning approach built on a single principle: start at the end and work backwards.
The reason this matters is that grants programmes have a fixed endpoint — the point at which grants need to be active, contracts signed, and grantees informed. Everything else is upstream of that point. If you build your calendar forward from "when should we open applications?" you're optimising for the start of the process. If you build it backwards from "when do grants need to be in place?", you're optimising for the outcome.
What date do grants need to be active? This is usually dictated by one of three things:
Your own funding cycle. If your operating funds are appropriated annually, grants probably need to be contracted and active within that year. If your funding year starts on 1 July, grants approved after 30 June sit in limbo until the next appropriation.
Grantee project requirements. If you're funding time-sensitive projects — summer holiday programmes, academic year activities, seasonal community initiatives — the project needs to start on a particular date. Work backwards from that.
Your own funder's requirements. If you report to a government department, a parent foundation, or a board that meets on a fixed schedule, your grants programme needs to be complete in time to feed that reporting cycle.
Once you have the end-point, everything else is calculated backwards from there.
Before you build the variable parts of your calendar, identify the things you can't control:
Board meeting schedule. If grant approvals require a board resolution and your board meets six times per year, you have six possible approval dates. Every other date is not an approval date. Map those six dates first.
Staff leave. Grant rounds have a way of colliding with Christmas, Easter, school holidays, and the annual leave that staff have been planning for months. Map the leave calendar before you set round dates, not after.
Fiscal year boundaries. Payments that straddle a financial year create accounting complexity. If your fiscal year ends 30 June, you may want to avoid rounds where payment schedules cross that date.
Other organisational commitments. Board strategy days, major events, significant reporting deadlines to your own funders. These absorb staff time and attention during periods that are supposed to be routine.
Working backwards from your board approval date, map each stage:
Panel deliberation to board approval: How long do panel recommendations take to reach the board in an approvable form? Who prepares the board paper? How long does that take? Is there a sign-off chain before the board sees it? Allow at least one to two weeks for a straightforward process; more if there are multiple sign-offs.
Assessment completion to panel deliberation: Your panel needs materials prepared before they can deliberate. Who prepares those materials? How long does that take? Allow a minimum of three to five working days for materials preparation after assessment is complete.
Assessment period: How long do reviewers need to complete their assessments? For a 100-application round with 90-minute reviews per application and each reviewer assessing 30–40 applications: a minimum of three weeks. But add buffer: reviewers who are slow, reviewers who declare conflicts late, reviewers who go on leave. A realistic assessment window for a medium-sized round is four to six weeks.
Eligibility processing to assessment opening: After applications close, you need time to log applications, check eligibility, assign reviewers, and distribute materials. For a well-run programme with good systems: three to five working days. For a spreadsheet-based process: one to two weeks.
Application window: How long do applicants need to prepare a quality application? For a full application (not an EOI): four to six weeks minimum. Less than three weeks is not enough time for applicants with part-time staff or volunteer governance. More than eight weeks is counterproductive — applicants will start late regardless.
Pre-launch preparation: Before applications open, you need to finalise and publish guidelines, set up the application portal, prepare applicant support resources, and notify potential applicants. Allow two to three weeks.
Once you have the calendar mapped, look at where the high-intensity periods fall:
For a single round, these periods are manageable because they're sequential. For two or more concurrent or overlapping rounds, you need to explicitly model where high-intensity periods from different rounds fall simultaneously.
If Round 1 notification overlaps with Round 2 application support — which is very common in rolling or staggered programmes — you need either additional resource during that period or a deliberate gap between rounds to separate the intensity peaks.
Setting the panel meeting before assessment is complete. Panel meetings are often scheduled first, because panels are made up of busy people with diaries. But a fixed panel date with a variable assessment end-point means assessment always has to hit the panel date, regardless of whether the work is done. Set the panel date at least two weeks after your expected assessment completion, not the day after.
Not accounting for holidays in the assessment window. A four-week assessment window that includes two public holidays and a long weekend is a three-and-a-half-week assessment window. Check the public holiday calendar before you finalise assessment windows.
Conflating "application close" with "assessment ready." Applications close on a Monday. Assessment starts — when? Logistically: after applications have been logged, eligibility has been checked, conflicts have been declared, and materials have been distributed. This typically takes three to five working days. A programme that plans assessment to start on the day applications close is a programme that's always behind.
No contingency in the panel-to-notification gap. Something will come up between panel deliberation and notification. A decision that needs a second opinion. A funding condition that needs to be negotiated. A grantee that's hard to reach. Build a minimum of one week of contingency between panel decisions and notification dates.
Annual rounds on the same dates every year regardless of what's changed. Your programme dates should be reviewed annually. Staff changes, board changes, shifts in your applicant community, and changes to your own organisational calendar all affect what's workable. A calendar that was right three years ago may not be right now.
Before each round opens, run a planning session with your team that covers:
This meeting should happen at least eight weeks before the application window opens — ideally longer. Decisions made eight weeks out are options. Decisions made two weeks out are crises.
If you run multiple rounds or programmes, you need a portfolio-level calendar — not just individual programme calendars.
Look across all your programmes simultaneously. Where are the assessment windows? Where do they overlap? Which staff members are involved in multiple programmes, and when are they required in two places at once?
Portfolio-level calendar planning is the only way to see the systemic capacity constraints that individual programme planning misses. It's also the only way to have an honest conversation with leadership about resource requirements — which requires knowing, concretely, what the demand on your team looks like across the whole year, not just for the next round.
Build the portfolio calendar as a shared, visible artefact — not a spreadsheet that lives on one person's desktop. When everyone can see where the pressure points are, everyone can help manage them.
At minimum: round open and close dates, assessment period, decision date, grant start date, reporting due dates, and acquittal deadlines. A more complete calendar also includes internal milestones — panel recruitment, guidelines review, board approval dates — and sector calendar notes flagging periods to avoid for deadlines.
Planning six to twelve months ahead is best practice. Budget confirmation triggers programme design; advance notice of the round should go out two to three months before it opens. Applicants who know a round is coming can prepare better applications.
Stagger deadlines by at least four to six weeks, maintain a programme status dashboard updated weekly, define clear role ownership for each programme, and use a grants management system that keeps programme records separate rather than relying on individual memory to keep multiple spreadsheets distinct.