Grant workflow on Zoho One: from proposal to utilisation report
Most nonprofits run grants across three places that don’t talk to each other: a fundraising tracker, the accounts, and programme reports. Every utilisation report becomes a week of reconciling. Sound familiar? This page is the build spec we use to connect them on Zoho One. For the wider architecture and pricing, start with our Zoho One for nonprofits guide.
The data model: one grant, four records
| Record | App | Key fields |
|---|---|---|
| Grant (Deal) | CRM | Funder (Account), grant ID, type (CSR / foundation / FCRA / government), amount, currency, start and end dates, stage, owner, reporting schedule |
| Grant budget | Books | Reporting tag or project per grant ID; budget lines matching the funder's heads (personnel, programme, travel, admin) |
| Deliverables | Creator | Grant ID (lookup synced from CRM), indicator, target, actual, location, period, evidence link |
| Documents | WorkDrive + Sign | One folder per grant: proposal, signed agreement, budget, reports, utilisation certificates |
The grant ID is the thread. Create it once in CRM and pass it everywhere else. Never retype it.
Stage-by-stage workflow
1. Identified → concept note (CRM). Log the funder as an Account and the opportunity as a Deal. Required fields at this stage: funder, expected amount, deadline and owner. A Blueprint stops the Deal moving forward without a deadline.
2. Proposal → due diligence (CRM + WorkDrive). On moving to “Proposal”, a workflow creates the grant’s WorkDrive folder from a template (Proposal / Agreement / Budget / Reports / UCs) and links it to the Deal. Due-diligence documents such as 12A, 80G, CSR-1, FCRA registration and audited accounts sit in one shared “Compliance” folder. Link to it; don’t copy it.
3. Awarded (CRM → Sign → Books). Marking the Deal “Awarded” does three things:
- sends the agreement for signature through Zoho Sign;
- creates the reporting tag or project in Books, named with the grant ID;
- generates the reporting calendar as CRM tasks (quarterly narrative report, half-yearly utilisation, final report), each with an owner and a 14-day reminder.
4. Budget loaded (Books). Finance enters the budget lines once. Every expense, bill and salary journal for this grant carries the tag. For FCRA-funded grants in India, keep the separate FCRA bank account and books that the law requires, and tag within them. Our grant-to-accounting integration field guide covers this hand-off in detail, including salary cost allocation.
5. Delivery (Creator). Programme staff log activities against the grant ID, many of them offline in the field. Indicators roll up by period. This is the step most grant trackers skip, and it is why their reports only show money and never outcomes.
6. Reporting (Analytics). One dashboard per grant joins Books spend and Creator outputs. The funder report is exported from it rather than written from scratch.
Utilisation report template
| Section | Source | Contents |
|---|---|---|
| 1. Grant summary | CRM | Funder, grant ID, period, amount sanctioned, amount received to date |
| 2. Budget vs actual | Books | Budget head, sanctioned, spent this period, spent to date, % utilised, variance note if > ±10% |
| 3. Outputs | Creator | Indicator, target, achieved, % achieved, locations |
| 4. Unspent balance | Books | Opening balance, received, spent, closing balance, proposed use |
| 5. Narrative | Programme lead | Three highlights, one challenge, one change requested |
| 6. Sign-off | Sign | Programme head and finance head (CFO or CA certificate where the funder requires one) |
Indian CSR funders and FCRA grants often ask for a utilisation certificate in their own format. Keep sections 2 and 4 as the data source and map them to the funder’s form.
Where this breaks, and how to stop it
- Two grant IDs. Fundraising and finance name the grant differently. Fix: CRM creates the ID and Books’ tag uses it exactly.
- Salaries not tagged. Staff work across grants, so payroll lands untagged. Fix: allocate salary percentages per grant in a monthly journal, approved by the programme lead.
- Reports written, not generated. If someone rebuilds the numbers in Excel every quarter, the system isn’t finished. Go back to step 6.
- Beneficiary data overshared. Funders need counts, not names. Share aggregates. Our DPDP compliance checklist for NGOs covers what personal data you may share and how.
When this is the wrong tool
If you are a funder running open calls with hundreds of applications, external reviewers and grantee portals, this pattern gets strained. Compare dedicated grantmaking systems in our grant management software guide. And if licence cost is the worry, Zoho One pricing for nonprofits explained shows when the same workflow is cheaper on individual apps (CRM, Books and Creator) than on the full suite.
Book a Zoho One fit check → Bring one live grant. We’ll map it onto this workflow with you and show you where your current set-up loses data.