Capacity Milestone Agreement¶
Document — instantiates Donor-Coupled Capacity Governance
Defines the recipient capabilities and evidence required before support changes or autonomy claims are accepted.
A Capacity Milestone Agreement is a written schedule of the specific, evidenced capabilities the recipient must demonstrate before the level of support is allowed to change — and before anyone is permitted to call the recipient independent. Its whole reason for existing is to stop two failures at once: support that steps down on a calendar rather than on readiness, and an "it's self-sustaining now" claim asserted from performance numbers that the donor's flow is quietly propping up. The agreement fixes each milestone to observable evidence (a capability demonstrated for N periods without the subsidy, a reserve held, a function run locally through a real incident), so a change in support is triggered by proof, not by hope or by the donor's fatigue. It is prospective and recipient-facing: it says what the recipient has to earn, not what the two parties owe each other.
Example¶
An international NGO has funded a maternal-health clinic in a rural district for six years — paying the salaries of two midwives, covering the cold chain for vaccines, and supplying the referral ambulance. The plan is to hand the clinic to the provincial health ministry. Left as a date on a grant timeline, "handover in 2028" would simply move the clinic onto a ministry payroll that may or may not actually carry it. Instead the two sides write a Capacity Milestone Agreement.
It first records a baseline: what the clinic can already do on ministry resources alone — reception, basic antenatal visits — versus what exists only because donor money is flowing. Then it lays out milestones, each with its evidence test: the ministry has funded both midwife salaries from its own budget line for four consecutive quarters; the district has maintained cold-chain temperature logs above the failure threshold through one supply disruption without NGO backstop; a local supervisor has passed the last two audits unaccompanied. Only when a milestone's evidence is on the table does the corresponding slice of support step down. The final milestone is an explicit autonomy test: the clinic must run a full quarter — including one referral emergency — on ministry resources before the NGO will certify it as locally sustaining and close the grant. The agreement turns a hopeful date into a set of earned gates.
How it works¶
The distinguishing move is that every milestone is a pair: a capability plus the evidence that would count as having reached it. The method:
- Separate baseline from subsidized performance. Before setting targets, record what the recipient already does unaided, so milestones measure the gap the recipient must actually close rather than re-crediting work the donor is doing.
- Write milestones as demonstrated capability, not activity. "Ran the function locally for three periods through one real stressor" beats "attended training" — the evidence has to survive the subsidy being absent, not merely present.
- Bind each support change to a milestone, not a date. The schedule of when support drops is a lookup on which milestones are met, so slippage in readiness automatically slips the drawdown.
- Reserve one milestone as the autonomy gate. Certification of independence is itself a milestone with the strictest evidence — a live period run without the flow — so no autonomy claim can be signed on subsidized numbers.
Tuning parameters¶
- Evidence stringency — how hard the proof bar is set (a single clean period vs. sustained performance through a real shock). Higher stringency prevents premature drawdown but delays handoff and can strand a ready recipient.
- Milestone granularity — many small gates vs. a few large ones. Fine granularity gives early warning and partial credit; coarse gates cut administrative load but hide near-misses.
- Coupling tightness — how mechanically a met milestone forces a support change. Tight coupling removes discretion (and donor foot-dragging); loose coupling keeps human judgment but reopens the calendar-vs-readiness argument.
- Baseline recency — how often the endogenous-capacity baseline is refreshed. A stale baseline lets ordinary drift masquerade as earned progress.
When it helps, and when it misleads¶
Its strength is that it makes "ready" a checkable claim instead of a negotiation, and it protects the recipient from a drawdown that arrives before capability does. It gives both sides a shared, evidenced answer to the question the archetype cares about most — is this capacity endogenous yet?
Its failure mode is that a milestone is a target, and targets get gamed: once the metric is written down, effort flows to producing the evidence rather than building the capability the evidence was meant to signal — Goodhart's law in miniature.[1] A clinic can pass "four quarters of local salary funding" by borrowing against next year, satisfying the letter of the gate while the underlying capacity is hollow. The classic misuse is abandonment dressed as milestone completion: a donor eager to exit sets soft, easily-produced evidence bars and certifies autonomy that will not survive contact with a real shock. The guarding discipline is to tie the highest-stakes milestone to performance under a genuine stressor observed by the donor, not to a document the recipient produces — and to keep the baseline fresh so gamed progress shows up as an unexplained gap.
How it implements the components¶
local_capacity_milestone— the document is the ordered set of capability gates and their evidence tests; this is its spine.recipient_capacity_baseline— it opens by recording endogenous capacity so each milestone measures a real gap, not re-credited donor work.autonomy_claim_test— the final gate is an explicit live-period test that no independence claim can bypass.
It does not price or formalize the ongoing relationship's mutual terms — the reciprocity_or_obligation_rule and equity_and_legitimacy_review belong to Cross-Boundary Support Agreement, its nearest document-twin — and it does not keep the running subsidy_visibility_ledger of what actually flows, which is Subsidy Ledger. This agreement sets what the recipient must earn; those set the relationship's terms and its factual record.
Related¶
- Instantiates: Donor-Coupled Capacity Governance — supplies the readiness gates that govern when support may change.
- Consumes: Subsidy Dependency Assessment — its baseline and dependence findings tell the agreement which capabilities actually need milestones.
- Sibling mechanisms: Cross-Boundary Support Agreement · Subsidy Ledger · Taper and Handoff Plan · Source-Sink Monitoring Dashboard
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Defines the recipient capabilities and evidence required before support changes or autonomy claims are accepted, making its operative form a standing rule, threshold, contractual commitment, or policy constraint governing future conduct.
Independent corroboration: The frozen evidence defines Capacity Milestone Agreement as 'Defines the recipient capabilities and evidence required before support changes or autonomy claims are accepted', so its operative form is Rule, Policy & Commitment.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Public Administration & Policy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Development and program-governance practice conditions step-down support or autonomy on evidenced recipient capacity rather than elapsed time.
Related originating lineages:
- Law & Governance — The agreement form fixes obligations, evidence standards, change triggers, and review rights in advance.
- Organizational & Management Science — Capability management supplies observable milestones demonstrated under real operating conditions.
Review resolution: Public administration is the agreed primary lineage because donor-recipient programs tie support changes to demonstrated local capacity and locally owned evidence. Law supplies the written commitment and organizational management supplies handover governance; the agreement is a cross-disciplinary synthesis.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Sources consulted:
References¶
[1] Campbell, D. T. "Assessing the Impact of Planned Social Change". Evaluation and Program Planning 2(1), 67–90 (1979). Shows that decision-linked quantitative indicators invite corruption pressures and can distort the processes they are intended to monitor. registry ↩