Single-round grants programmes are hard enough to manage. Multi-round programmes — where applicants can progress from expression of interest through to full application, or through sequential funding stages — introduce a layer of complexity that catches many teams off guard.
The problem isn't that multi-round programmes are fundamentally more difficult. It's that the dependencies between rounds create cascading consequences that don't show up in a simple timeline. A delayed assessment in Round 1 doesn't just push back Round 1 outcomes — it compresses Round 2, which compresses your review window, which reduces decision quality, which generates complaints, which requires management time. Everything is connected, and most of that connection is invisible until it breaks.
This piece is about making those dependencies visible before they become crises.
The failure modes in multi-round programmes are predictable. They show up in the same places, in the same sequence, almost every time.
Round 1 assessment overruns. The panel needs an extra two weeks. This seems manageable — until you look at what's downstream. If Round 2 application opens on a fixed date (as advertised to applicants), a two-week assessment overrun in Round 1 means applicants have two fewer weeks to prepare their Round 2 application. If Round 2 opens when Round 1 outcomes are announced (more common), a two-week overrun is a two-week compression of everything that follows.
Notification delays cause applicant confusion. Applicants who progressed from Round 1 don't hear anything for three weeks. They email to check. Some of them make other plans. When Round 2 invitations go out, a portion of the invited applicants have already committed elsewhere. The Round 2 pool is smaller than expected, which affects your ability to make good selections, which affects programme quality.
Internal approvals aren't factored into the timeline. The panel makes recommendations. Those recommendations need to go to the board (or a delegated committee) for formal approval. The board meets monthly. If the panel's recommendations are ready on the 5th of the month and the board meets on the 25th, you have a three-week gap that wasn't on anyone's Gantt chart.
Staff availability isn't modelled. The same people who run Round 1 assessment run Round 2 application support. If Round 1 runs over, those people are still managing Round 1 when Round 2 is trying to start. Multi-round programmes that look feasible on paper often aren't feasible in practice because the same team is required at full intensity in two places at once.
The Programme Clock is a framework for making the dependency structure of a multi-round programme visible before you lock in any dates.
Start at the end. Work backwards.
What's the final grantee notification date? This is usually dictated by when grants need to be active — a funding year start, a reporting requirement from your own funder, or a commitment you've made publicly. This date is your anchor.
What needs to happen before that notification? Board or delegated approval. How much lead time does that require? When does the board next meet? Put that date in.
What needs to happen before approval? A complete panel recommendation with supporting documentation. How long does the panel need to deliberate? When are they available? Put that in.
What needs to happen before panel deliberation? Complete assessment from all reviewers. How long does reviewer assessment take? (This is usually underestimated — allow for reviewers who are slow, busy, or who need to recuse.) Put that in.
What needs to happen before assessment begins? Applications closed and processed. Eligibility checked. Conflicts declared. Materials distributed. This typically takes 3–5 working days for a well-run programme. Put that in.
When does the application window need to open? How long do applicants need to prepare a full application? For a complex programme: 4–6 weeks. For an expression of interest: 2–3 weeks. Put that in.
What needs to happen before the application window opens? Round 1 outcomes announced. If you're running a two-stage process, applicants need to know they've progressed before they can apply to Round 2. Put that in.
Keep working backwards. You'll eventually reach a date that represents when Round 1 assessment must be complete in order for everything else to work. Compare that date to when you're planning to complete Round 1 assessment. If there's a gap — and there usually is — you've identified a structural problem before it becomes an operational crisis.
The Programme Clock will always produce a timeline that's tighter than the one you started with. That's the point. Most multi-round programme timelines are optimistic by design — they assume everything goes to plan, nobody is sick, every reviewer turns their assessment in on time, and the board is available when needed.
Build explicit buffer into your timeline for:
Assessment overrun: Add 30–40% to your reviewer assessment window. If your baseline is ten working days, plan for fourteen.
Internal approvals: If your approval process requires a board meeting, don't assume the meeting immediately after assessment completion will be available. Boards fill their agendas. Build in one meeting of contingency.
Notification and response time: When you invite applicants to Round 2, they need time to confirm they're proceeding. Build in a response window. Some won't respond promptly. A week is the minimum; two weeks is better.
Technical and administrative: Applications get submitted with missing attachments. System errors happen. Allow for processing time that isn't purely assessment.
The most underrated constraint in multi-round programme management is staff capacity. Programmes are often designed by people who won't be running them, which means the timeline is built on an assumption of unlimited staff availability.
The practical question is: at what points in the programme does your team need to be at full stretch, and can those points overlap?
Map the high-intensity periods for each round:
- Application support period (staff answering queries, assisting applicants)
- Post-close processing (logging, eligibility checking, materials prep)
- Assessment period (managing reviewers, handling queries, tracking progress)
- Panel preparation (compiling ranked lists, preparing panel materials)
- Notification period (processing outcomes, sending letters, managing responses)
In a two-round programme, you'll have two of each of these. The question is whether any high-intensity periods from Round 1 overlap with high-intensity periods from Round 2. If Round 1 notification overlaps with Round 2 application support — which is common — your team is managing two intensive workstreams simultaneously with no relief.
There are three responses to this:
1. Extend the gap between rounds to avoid the overlap. This is the simplest solution and the one most often overlooked in programme design.
2. Bring in additional resource for the overlap period. Contractors, secondments, or internal redeployments.
3. Reduce the intensity of one workstream. For example, if Round 1 notification is standardised and mostly automated, it doesn't require the same staff intensity as a complex application support period.
None of these is cost-free. The point is to make the trade-off explicit rather than discovering it at 10pm on a Tuesday when your sole grants coordinator is trying to process 47 Round 1 outcome letters while answering Round 2 application queries.
Multi-round programmes require more proactive communication than single-round programmes. Applicants who are waiting to hear whether they've progressed are often also planning their next steps — they may be preparing a Round 2 application, or deciding whether to pursue other funding options.
Commit to a communication date, not just an outcome date. Tell applicants: "Round 1 assessment will be complete by [date]. Regardless of the outcome, all applicants will receive notification by [date]." Then hit that date, or communicate proactively if you're not going to.
Late notifications in multi-round programmes don't just inconvenience applicants. They generate a wave of enquiries that your team has to respond to, which takes time away from the assessment that's causing the delay, which makes the delay worse. Getting ahead of the communication — even if the update is "we're running two weeks behind and new expected date is X" — is operationally better than silence.
Once you're running the programme, you need to be able to see where you are against the Programme Clock in real time. The minimum dashboard for a multi-round programme:
If any of these is amber or red, you need to know before it becomes a crisis — not after.
The programmes that run well aren't the ones where nothing goes wrong. They're the ones where problems are visible early enough to respond to. The Programme Clock, and the tracking that follows from it, is how you build that visibility.
A multi-round grants programme runs two or more separate funding rounds — each with its own application period, assessment process, and funded cohort — within the same programme framework. This may be sequential rounds or simultaneous parallel rounds targeting different applicant types or geographies.
Write your scoring rubric with detailed descriptors for each score level before the first round, run a calibration session at the start of each round, monitor scoring distributions across rounds to detect drift, and retain at least one experienced assessor across rounds for continuity.
Maintain a real-time commitment register — total budget approved minus total paid — that updates with every funding decision. Grants management software does this automatically. Build in a 10–15% budget buffer for grant variations and contingencies.