NGO Procurement Policy Template (Free Template)
A complete, adaptable procurement policy structure for Kenyan NGOs — thresholds, committees, conflict-of-interest rules, and emergency procedures you can copy into your own manual.
Most NGO procurement policies fail in one of two ways: they are copied from a large INGO and are too heavy to follow (so staff route around them), or they are too vague to defend in an audit ("management approval shall be obtained"). This template aims for the workable middle — strict where money is large, light where it is small, and specific enough that an auditor and a program officer read it the same way.
Copy the structure below into your own document, adjust the thresholds to your scale and donor rules, and have your board adopt it formally. Where your donor's procurement rules are stricter, the donor's rules win.
1. Purpose and scope
State that the policy governs all procurement of goods, services, and works using organizational or donor funds, by all staff, in all locations. Name the exceptions explicitly (e.g. payroll, rent under an existing lease, statutory payments) so nobody invents their own.
2. Procurement thresholds
The heart of the policy. A common structure for small-to-mid Kenyan NGOs:
| Value (KES) | Method | Approval |
|---|---|---|
| Under 10,000 | Direct purchase with receipt | Budget holder |
| 10,000 – 100,000 | Three written quotations | Budget holder + finance review |
| 100,000 – 500,000 | Three quotations + comparison memo | Procurement committee |
| 500,000 – 2,000,000 | Formal RFQ/tender to ≥3 suppliers | Committee + Executive Director |
| Above 2,000,000 | Open or restricted tender, advertised | Committee + ED + Board notification |
Anti-splitting clause
Include this sentence verbatim: "Procurement requirements shall not be split into smaller lots to circumvent threshold requirements. Related purchases within 30 days are treated as one procurement for threshold purposes." Splitting is the first thing auditors test.
3. Procurement committee
- Composition: minimum three members — finance, programs, and one rotating member; the requester may present but not vote.
- Quorum and decisions recorded in minutes, retained with the procurement file.
- Membership rotates annually so the same trio does not award everything indefinitely.
4. Conflict of interest
Every committee member and approver declares, per procurement, any relationship with a bidding supplier — and steps aside where one exists. Keep a standing register of staff business interests, updated annually. This single section prevents more findings than any other; our post on NGO procurement challenges shows why.
5. Supplier management
- A prequalified supplier database, refreshed every 1–2 years through an open call.
- Supplier performance (delivery, quality, price stability) recorded per order and consulted at award.
- Suppliers can be suspended for documented non-performance or integrity issues — with the reason on file.
6. Emergency procurement
Define an emergency narrowly: threat to life, safety, or critical program continuity that could not have been foreseen. Emergency purchases require the next-level approver, a written justification within 48 hours, and appear in a quarterly exceptions report. Activity deadlines caused by late planning are explicitly not emergencies.
7. Receiving and payment
- Goods received against the purchase order by someone other than the requester, with quantities and specs verified.
- Payment only on three-way match: PO, delivery note, invoice.
- Partial deliveries documented; substitutions require approval before acceptance.
8. Records
One file per procurement — requisition, quotes, comparison, minutes, PO, delivery note, invoice, payment reference — retrievable within a day and retained for at least seven years or the donor-specified period, whichever is longer. The transactional spine of that file assembles itself in a procurement system and is heroic in a filing cabinet. The narrative documents — minutes, signed delivery notes, comparison memos — are a different matter, as the next section explains.
What AWRA OpsHub does today
- Section 2, thresholds — enforced. Approval rules read the amount on a document, so each band routes to its approver in software rather than from memory.
- Section 3, committee — largely enforced. Multi-step approval chains with consensus rules record a committee decision as several named approvals, not one signature.
- Section 5, supplier management — enforced. A prequalified supplier database with an application flow, weighted reliability scores consulted at award, and suspension carrying a reason, a date and the person who applied it.
- Section 7, receiving and payment — enforced. Three-way matching compares ordered, received and billed quantities and prices and reports each discrepancy before payment.
- Section 8, the transactional file — automatic. Requisition, RFQ, quotation, order, check-in, invoice and payment are linked records, so producing the chain is a lookup.
- Documents attach to the transaction itself — shipped 2026-08-01. Expenses, purchase orders, requisitions, quotations and assets all take Document Vault files directly: checksummed on upload, classified, every download logged, and archived rather than deleted when removed. The receipt now lives on the record it evidences instead of in a naming convention.
More we can add to your workspace
- Section 2's anti-splitting clause, enforced. Detection of related purchases inside a 30-day window, treated as one procurement. Include the sentence in your policy anyway, because auditors test the rule against it — and until this ships, enforce it by review.
- Section 4, conflict of interest: a per-procurement declaration and a standing register of staff business interests. This is the section the post rightly calls the most finding-preventing of all, and until it is built it is your paperwork.
- Section 6, emergency procurement: an emergency lane, a 48-hour justification clock and a quarterly exceptions report. Configure a higher-approver rule and run the exceptions review by hand in the meantime.
- Section 7's segregation of duties, enforced — a block on the requester also receiving the goods. Make it a role assignment you audit until then.
- Section 8's documents made compulsory. Minutes, quotes and signed delivery notes now hang off the requisition or order directly; blocking an award that has none of them is the build.
- Section 8's retention — not per-donor. Retention is a setting you review deliberately, not a clock that tracks each grant's own period and acts on it.
This mapping is the most useful thing on the page if you are choosing software, so use it as a scorecard rather than a disclaimer: thresholds, committee approvals, supplier governance and matching are real enforcement, and they cover the bands where the money is. Conflict of interest, anti-splitting and the emergency lane stay in the policy manual and the review meeting — with us and, in our experience, with most vendors who imply otherwise. Ask any of them to demonstrate the split-purchase detector on screen.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsEnforce the clauses that can be enforced
Thresholds routed by amount, committee approvals recorded as named steps, prequalified suppliers scored and suspendable, and payment gated on a three-way match — with [conflict of interest](/glossary/conflict-of-interest), anti-splitting and the emergency lane named plainly as policy work no system does for you.
See the NGO procurement systemFrequently asked questions
Should we copy our donor's procurement policy wholesale?
No — adopt your own policy sized to your organization, with a clause that donor rules prevail where stricter. Copying an INGO's 60-page manual you cannot follow creates findings, because auditors measure you against your own adopted policy.
What thresholds are right for a small NGO?
Scale them to your typical spend: the three-quote band should catch meaningful purchases without burying staff in paperwork for stationery. The figures in this template suit organizations spending roughly KES 20–200 million annually; halve or double the bands to fit yours.
Who should sit on the procurement committee in a 10-person NGO?
Three people is enough: whoever handles finance, one program lead, and a rotating third member. The essentials are that the requester does not vote and that decisions are minuted — not headcount.
How do we handle procurement where only one supplier exists?
Single-source is legitimate when justified: document the market situation, get the same threshold approval, and record why competition was not possible. The finding is not single-sourcing itself — it is undocumented single-sourcing.
