These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- NGO + Donor + Project Mgmt
- Features
- Restricted allocations
Restricted allocations
Review proposed uses against receipt balance and donor restrictions.
OverviewSubmitted Allocations×
NGO + Donor + Project Mgmt · Restricted allocations
New
Submitted Allocations
Approval conditions
| Parent | Organization | Program | Allocated USD | Donor restriction | Revision | |
|---|---|---|---|---|---|---|
| FC-86332 | ORG-5007 | PRG-424 | 200 | DR-385 | 570 | |
| FC-40949 | ORG-8286 | PRG-579 | 180 | DR-751 | 540 | |
| FC-59362 | ORG-2078 | PRG-642 | 150 | DR-399 | 140 | |
| FC-15738 | ORG-9766 | PRG-606 | 180 | DR-132 | 320 | |
| FC-93096 | ORG-3387 | PRG-429 | 30 | DR-785 | 790 |
6 of 6 records
PRG-424Restricted allocations · RA-69491
SubmittedParentFC-86332
OrganizationORG-5007
Allocated USD200
Donor restrictionDR-385
Revision570
What you can do
Allocation preparation
A restricted allocation links the case and organization and records the proposed program, allocated USD amount and donor restriction. Its status distinguishes draft, submitted, approved, rejected and completed work. The allocation decision and approval dates remain available with the record.
How the work is organized
- Working record. Finance Officer compares the proposal with confirmed receipt events for the case. A pledge alone does not make funds available. The Allocation Reviewer checks the remaining eligible receipt balance, the case restriction and the proposed use before deciding. A review decisions record can retain the reviewer and reason on the parent case; the allocation keeps its own status and decision dates.
- Decision point. The responsible reviewer checks the linked case, current status and supporting records before recording a decision or allowing the next step.
- Evidence. Keep the source reference, reason or attachment beside the case so another team member can retrace the result.
What to agree during setup
Agree how to interpret donor restrictions, who may prepare an allocation, and who makes the independent decision. Decide how Finance Officer reconciles refunds or disbursements against the same case. Rehearse an amount that would exceed the confirmed eligible balance.
Check the handoff on an actual case
A case has a confirmed restricted receipt and the Program Lead wants part of it for a named activity. Finance Officer confirms the eligible balance, prepares the allocation and submits it. The Allocation Reviewer checks the receipt reference, already approved allocations and donor restriction. If a request exceeds the eligible balance, Finance Officer stops before recording an allocation row and sends the discrepancy to the Allocation Reviewer for a case-linked reason. Once accepted, staff can see the approved amount and date on the allocation.
Open the same case from the next role’s view. Check that the organization and program still match, that the amount and restriction are understood, and that the next person can find the relevant decision or receipt. If a detail changes, keep the earlier source revision and decision history readable before acting on the revised case.
The allocation carries its own revision, decision date and approval date. Those details matter when a reviewer sees a later edit: the amount currently displayed may differ from the amount previously considered. Keep the case link and organization visible in the review queue. After approval, Finance Officer should compare the allocated amount with receipt and disbursement events so a completed allocation reflects actual use. A rejected proposal remains useful context when staff prepare a corrected request with a different amount or program.
What your team sees
- Submitted Allocations — Review requested amounts and restrictions against received funds.
- Allocation Board — Follow draft, submitted and decided uses on the same case.
Follow the work through
Start with funding case intake, then follow review and award and restricted use. The data model shows how the records connect.
What it keeps track of
Data model- Restricted allocations
- Domain-specific restricted allocations supporting approve a restricted funding allocation.
- Funding cases
- Funding Cases records; retain actual linked evidence and role scope.
- Fund events
- Fund Events records; retain actual linked evidence and role scope.
- Review decisions
- Review Decisions records; retain actual linked evidence and role scope.
- Organizations
- Organizations records; retain actual linked evidence and role scope.
Who uses it
Permissions- Allocation Reviewer
- , Finance Officer, Program Lead.
- Each person works within the organization and case scope agreed during setup.
Set up NGO + Donor + Project Mgmt your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.