Organizations often have policies, but staff may not know which version is current or when it needs review. A practical system helps leadership make the issue visible, assign responsibility and keep evidence current before a donor or auditor asks for it.
Start with the governance decision
Begin by create one register for policies donors frequently request. Define what the organization needs to know, who owns the decision and what evidence proves the control is operating rather than merely documented.
Focus on material areas
Review finance, procurement, HR, safeguarding, whistleblowing, data protection, conflict of interest and anti-fraud policies. Prioritize gaps that could affect eligibility, donor confidence, financial exposure or the organization’s ability to manage a larger award. Not every administrative weakness deserves the same urgency.
Create one controlled record
Use a shared register or dashboard with owner, status, evidence link, review date and next action. Controlled records reduce reliance on individual memory and make staff handovers easier.
Define review triggers
Review after major staffing changes, new banking arrangements, policy updates, audit findings or significant grants. A fixed annual review is useful, but event-triggered updates prevent the system from becoming stale between cycles.
Useful fields
- Control or evidence area.
- Current status.
- Owner.
- Approval authority.
- Evidence location.
- Last review date.
- Next review date.
- Open action.
Example
A donor requests the current procurement policy. The register shows the approved version, board approval date and next review date immediately. This is the difference between a governance process that exists on paper and one that can be demonstrated under donor review.
Common weaknesses
Common failures include outdated records, unclear ownership, missing approval evidence and actions that are discussed but never closed. Keep the process proportionate and link significant gaps to leadership follow-up.
What to do next
Use the Grant Evidence Inventory to identify the next readiness action and keep closure evidence with the organization’s grant-readiness records.
For practical funding intelligence, subscribe to Africads Grant News.
Frequently asked questions
Which policies should be tracked in a grant-readiness register?
Common examples include safeguarding, procurement, finance, HR, anti-fraud, whistleblowing, conflict of interest, data protection, and partner management policies.
What fields should the register include?
Track policy name, owner, approval date, approving authority, next review date, current version, and whether implementation evidence exists.
Is an approved policy automatically donor-ready?
Not always. Some donors may also expect staff awareness, training, implementation records, or evidence that the policy is actually used.
Who should own policy updates?
Each policy should sit with the function responsible for implementing it, while leadership or the board provides the required approval under organizational governance rules.
How often should the register be reviewed?
Review it at least quarterly or before major due-diligence processes so expired or superseded policies are identified early.
Conclusion
A policy register turns scattered governance documents into a manageable readiness system. Your NGO should track ownership, approval, review dates, and implementation evidence so policy gaps are visible before a donor asks.
