Concept Design
Releasing grant instalments against the agreement actually in force
A grant system may show a milestone as submitted while a separate contract variation changed its value, scope or evidence requirement. Paying from the original schedule can release money against a superseded obligation.
System landscape
Source evidence comes from agreement, variation and claim. The proposed workflow sends the decision to programme delegate.
Proposed architecture
Link the executed agreement and approved variations to milestone claims, evidence, delegate authority and payment instructions. Distinguish partner submission, programme assessment, financial approval and actual release.
- Source recordsAgreement, variation and claim
- ProcessingResolve operative milestone
- Decision ownerProgramme delegate
- Operational outputSupported release instruction
Reliability and operating controls
The grant delegate decides whether conditions are met. Keep a partial claim open and separate a changed requirement from an unmet one. Permit a correction without erasing the earlier decision.
Illustrative operating scenario
A grantee delivers part of a revised project. The portal marks its report complete, but the payment pack presents the varied milestone and the amount the delegate has authority to release.
Delivery boundaries
Delegated public or programme officers own eligibility, referral and payment decisions. The system supplies a reproducible account of the evidence.
Expected business impact
Trace each paid amount to an operative milestone and authorised decision.
Acceptance test and handover
Replay a varied agreement and a duplicate claim across two reporting periods. Verify that every released dollar links to the operative condition, approved decision and unique payment reference.
Industry evidence
The audit describes responsibilities for assessing milestone reports, approving releases and coordinating between programme and grants teams. ANAO audit of the Community Health and Hospitals Program