Use cases · Funded programs
Funded programsNot-for-profits & community programs
Grant-funded programs need to show the money went where it was meant to — including the IT.
How IT usually works in this setting
Community organisations run several funded programs side by side, often with volunteers and part-time staff, and report to funders on a fixed cycle.
What it costs you today
- Reporting to a funder means assembling evidence from several disconnected places.
- Volunteers need access that is granted quickly and removed the day they finish.
- Hardware is donated, shared and passed around with no register.
- Every dollar of overhead has to be defensible.
What the desk does about it
- Programs separated, overhead shared — Each program can have its own reporting and its own records while sharing the same platform — no duplicate systems per grant.
- Access that expires — Volunteer and short-term access is time-bound and reviewed, not left switched on.
- Donated hardware, properly recorded — Assets are registered with the program they serve, so you can account for them at any point in their life.
- Evidence on request — A funder's question about a period is answered from a report, not a search.
“Which program paid for that laptop?”
A defensible answer before the acquittal report is due.
What we show you, in order
A community services coordinator, three funded programs
- Import the asset list and assign each item to a program.
- Give each program coordinator a scoped view of their own records.
- Run the asset-by-program report for the reporting period.
- Attach the report to the acquittal and keep the underlying records for the audit trail.
- Set a review date so the next report is not a scramble.
Why it lands
The reporting cycle takes an afternoon instead of a fortnight of emails.
What we can stand behind
- Multiple programs or cost centres inside one platform, each reporting separately.
- Role-based access that can be scoped to a program and time-limited.
- Asset and licence register that stands up to a funder's question.
- Full data export, so nothing is lost if funding or the relationship changes.
What we would need from you
- Your program list and who coordinates each one.
- The reporting dates and the format the funder expects.
- The asset register as it exists — even if it is a shoebox and a spreadsheet.
- Your volunteer onboarding and offboarding steps.
What every one of these has in common.
The configuration changes by sector. The platform underneath it does not: one record per request, service levels per team, and tenancy enforced on the server.
One request, everything attached to it
The same data model behind all eight situations — which is why a sector change is a configuration change rather than a new product.