Asset Management for NGOs: Donor-Funded Equipment Registers
Donor-funded equipment is held in trust, not owned — how to run an asset register that survives office moves, staff exits, and the end-of-project disposition report.
When a donor funds a vehicle, thirty laptops, or a generator, your NGO usually holds that equipment in trust: the grant agreement says what it may be used for, who may use it, and what happens to it when the project closes. The asset register is your evidence that the trust was kept. Most registers cannot provide that evidence, because they were built once — for an audit — and never lived afterwards.
What a donor-defensible register records
| Field | Why it matters |
|---|---|
| Asset tag / serial number | Physical verification is impossible without unique identification |
| Funding grant & PO reference | Links the asset to the money that bought it — the core donor question |
| Custodian (a named person) | Accountability attaches to people, not offices |
| Location | Where it should be found during spot checks |
| Condition & maintenance history | Supports disposal decisions and insurance claims |
| Movement history | Every transfer, approved and dated — the register tracks reality |
| Disposition status | In use / transferred / donated / disposed, with donor instruction where required |
Custody: the rule that changes behavior
Issue every portable asset to a named person against a signed record — never to "the Kisumu office". When custody is personal: exit clearance catches unreturned items before the final paycheck; losses have an owner and an incident report; and physical verification means finding a person, not searching a building. Note that the clearance step is a process you run against the register, not something most systems — ours included — enforce by withholding the final payment.
Verification: quarterly, mobile, boring
- Physical checks quarterly for high-value and portable items, annually for everything.
- Verify with the register in hand — mobile checks with photos and condition notes beat clipboard-and-retype; this is where offline mobile workflows earn their keep.
- Every variance gets a disposition: found/corrected, incident report, or write-off approval. A register with unexplained gaps is worse than no register in an auditor's eyes.
The end-of-project disposition report
Project closeout asks one question: for every asset this grant bought — where is it, what condition is it in, and what happens to it now? Donors typically instruct transfer to a successor project, donation to a partner or community institution, sale (with proceeds treated per the agreement), or continued use with conditions. If assets carried their grant tag from purchase, this report is a filter. If not, it is a month of forensic work — the pattern we covered in grant budget tracking applies to equipment too.
Vehicles deserve their own discipline
Logbooks in the organization's name, movement logs, fuel records reconciled to mileage, and scheduled servicing. Vehicle findings (private use, missing fuel records) are among the most damaging because they suggest culture, not process, failure.
Your register is healthy when
- Any asset can be located — person and place — within a phone call.
- Every asset shows the grant and purchase that created it.
- The list of what a leaver holds can be produced on demand, so clearance is a filter rather than a memory test.
- Last physical verification is under a quarter old for portable items.
- A per-grant disposition report exports in minutes.
What AWRA OpsHub does today
- Unique identification — asset code, barcode, serial and model, which is what makes physical verification possible at all.
- Custody to a named person, with an employee link, plus current department, location and warehouse.
- Full movement history, with GPS audit fields on movements — so a transfer is a dated record rather than a recollection.
- Condition, status, risk level and warranty expiry, and an approval requirement flag on the assets that need one.
- Last-verified date and verifier, which is precisely the field that makes "under a quarter old" auditable.
- Retirement and disposal with a reason and a date — the disposition evidence closeout asks for.
- Pool tracking for quantities of identical low-value items, alongside individually tracked assets.
- Donor and grant reference as custom fields on assets, flowing through to reports and exports.
- Assets filterable by custodian, which is how you produce a leaver's holdings list.
More we can add to your workspace
- Asset creation from a received purchase order. The path today is stock-to-asset conversion through an inventory adjustment rather than a button on the delivered order. An earlier version of this post said otherwise; it was wrong.
- A grant tag inherited from the purchase, carrying the funding source from the order onto the asset. Today the tag is a field somebody fills in at registration — which is exactly why the disposition report is a filter for organisations that are disciplined and a forensic exercise for those that are not.
- A staff-clearance workflow. You can list what a person holds today; an offboarding process that blocks a final payment until items are returned is the build.
- A depreciation schedule. Book value for your financial statements is your accounting policy, computed outside the register.
- A vehicle-specific module. Fuel-to-mileage reconciliation and service scheduling — the discipline the callout above recommends — brought inside, so log books and fuel records stop living elsewhere.
- Verification reminders. The last-verified date is recorded, but nothing schedules the next check or chases an overdue one.
- A documents attached to an asset. Delivery notes, logbooks and donation certificates go to the document vault, which does not link natively to an asset record.
The pattern is worth stating plainly, because it repeats across this whole cluster: the register itself is strong — identification, custody, movement, verification and disposal are all genuinely there — and the automation around it is not. The grant tag, the verification schedule and the clearance step depend on people doing them. That is a workable register, and better than most NGOs run today, but do not buy it expecting the donor attribution to appear by itself. The general version of this discipline is in asset tracking and custody and disposal and retirement.
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 needsMake the register live
Named custodians, dated movement history, verification dates, retirement reasons, and donor tags that flow into reports — with the honest note that the grant attribution is a field you fill in, not one inherited from the purchase.
See NGO asset managementFrequently asked questions
Who legally owns donor-funded assets?
Read the agreement — commonly the NGO holds title while the donor retains disposition rights until closeout, but some donors retain ownership outright. Either way, treat the register as evidence of stewardship rather than a list of possessions.
What value threshold should the register use?
A common policy is registering everything above KES 5,000–10,000 plus all attractive items regardless of value (phones, drives, cameras — things that walk). Donor agreements sometimes set their own threshold; the stricter one wins.
How do we handle assets shared across projects?
Register the asset under the grant that purchased it, and document shared use through your cost-allocation policy. What you must avoid is charging two donors for the same purchase — allocation covers running costs, not double acquisition.
What about depreciation?
Track it for your financial statements per your accounting policy, but donor reporting usually cares about existence, condition, and disposition rather than book value. Keep both views from one register instead of maintaining two lists.
