A company CSR team, a company foundation, an implementing partner and a pooled fund all work under the same rules and need different records. This playbook helps you find your model, what to record and the smallest useful system to begin with.
Many organisations combine two or three. Start with the closest match, then borrow only the parts that solve a real problem.
A CSR team inside the company chooses, funds and monitors partners, and reports to the board committee.
The company funds its own foundation, which designs and often implements programmes.
The company funds nonprofit partners to deliver, and the CSR team reviews reports and visits.
You deliver for several companies, and each has its own reporting and compliance asks.
The company runs volunteering, payroll giving or matched giving alongside grants.
Several companies fund a shared programme through a collaborative or a trust.
Not sure which one you are? Bring one tracker and describe a normal month. The model usually becomes clear quickly.
These come up in almost every first conversation we have with CSR teams and the partners they fund.
"We found out about the unspent amount in March."
Spend sat in one sheet and the project calendar in another, so the deadline arrived before the alert.
"Three companies fund us and want three formats."
The same school's enrolment is reported three ways, and nobody can say which version is current.
"The annual report claims reach, not change."
Counting participants is easy. Evidence that anything improved is a separate scramble.
"Which partners have current registrations?"
Due diligence lives in email attachments and is repeated for every new project.
CSR models differ, but most projects follow this path. Use it to see where your records should connect and where they usually break.
Set the annual CSR budget, themes and geographies, and take it to the board.
Find and vet implementing agencies.
Sign agreements and release instalments against milestones.
Site visits, third-party monitoring and partner reports.
Board reports, the annual report, regulatory filings and impact assessment where required.
Decide what to continue, scale or stop.
Choose the parts that match how your CSR actually works. Most teams need a focused combination, not every module.
Themes, geographies and approvals, linked to the projects that spend the money.
One profile per partner with registrations, past utilisation and risk notes, reused across projects.
Agreements, tranches, utilisation certificates and amendments.
Visits, third-party checks and indicators, with reported and verified results kept apart.
Spend, unspent balances, ongoing projects, impact assessments and filing dates, with an owner for each.
Prepared from the same records, with every claim linked to its source.
CSR sits between company compliance, partner management and proof of impact. These short reads cover what a CSR team needs to record, which systems it touches, what goes wrong and what success means to its board and its partners.
Rule of thumb. A CSR team needs money, compliance and proof of impact, not beneficiary files. Record what the law, the board and the auditor ask for, link it to results, and leave individual beneficiary data with the implementing partner.
CSR rules change, and they differ by country. Your company secretary and auditor confirm what applies. We build the record to match, and we use the equivalent in your country.
What goes wrongUnspent amounts or filings are noticed at year end, when options are limited.
How it is designed outA compliance calendar tied to project spend, alerts months ahead, and an owner for each item.
What goes wrongThe same school's enrolment differs across three CSR reports.
How it is designed outOne partner record and a core reporting pack, with company-specific views drawn from the same data.
What goes wrongAn annual report cites reach and outcomes with no evidence behind them.
How it is designed outEvery claim linked to its source and verification status, on the page that produces the report.
What goes wrongA CSR team collects individual records it neither needs nor can protect.
How it is designed outAggregates by default, identity kept with the partner, and access reviewed by the privacy lead.
A CSR head, a board and a partner ask different things of the same records. Start from the question the person will ask.
Is this year's budget committed and spent on plan, and what is still open?
Watch outA fully spent budget says nothing about whether it worked.
What did the money change, and can you show it?
Watch outParticipant counts are output. Show outcomes separately.
Which reports do we owe, to whom, in what format, and when?
Watch outTen formats for ten companies burns the partner's staff time.
This is India's April to March financial year. Companies elsewhere report on their own fiscal year, so we set the calendar at the start.
Most AI projects stall because the records underneath are messy. So we work in a fixed order.
Every field has to earn its place by helping someone decide something. If nobody uses it, we don't collect it.
A system people avoid is worse than a spreadsheet. We design around the CSR manager, the finance team and the partner.
On clean, connected records, AI can read long reports, draft board packs and flag what needs attention. A person always checks.
Where you start depends on where you are. If your records are already in good shape, we can move to AI quickly. If they are in spreadsheets and inboxes, we start there, and we don't start from zero.
Most systems launch in three to four months. The timeline moves with the number of programmes and roles, how messy the old data is, and how many tools need connecting.
Tell us where the work gets stuck today. Spreadsheets, notebooks, WhatsApp groups, all of it.
You show us how the programme runs. We'll tell you straight if you need a new system, a better workflow or nothing at all.
We map how your programme works, talk to the people who'll use it, review the tools you use today and hand you a System Blueprint, a clear plan of what we'll build.
Working screens every 2 to 4 weeks, tested by your field team in your own terms. We clean up your old spreadsheets and move them across.
Field training and launch, then 30 to 60 days of close support. After that, the system keeps changing as your programmes do.
We connect to your survey app (SurveyCTO, ODK or Kobo), BigQuery or Postgres, WhatsApp, your accounting software, grant portals and CRM, rather than replacing what already works. Zoho licences sit in your organisation's name, and everything exports whenever you want it.
The questions your finance head and IT lead will ask, answered before the call.
Zoho licences are bought in your organisation's name and hosted in the Zoho data centre region you choose, including India. We work inside your account.
Every record exports to Excel or CSV whenever you want, including the day you stop working with us. You're not locked in to us for support either.
Each person sees only the records their role needs. Beneficiary-level data stays with the implementing partner, and the CSR team sees aggregates. Board and committee papers stay restricted until they are approved.
Edits are logged with who made them and when, so an audit or a funder query doesn't start from memory.
Consent is recorded for each purpose, and we agree up front how long data is kept and when it's deleted. ZolaShield, our DPDP platform, shows where you stand.
AI features run on your records under your account's controls. Partner and beneficiary records never go into public AI tools.
We'll map how projects move through your team today, identify the smallest useful first version and show where plans, partners, spend and evidence can share the same information, without forcing your CSR into a generic template.
Four short questions. Plain language is perfect; you do not need to have the solution worked out.
The same approach, shaped to each kind of work.
