01 · What breaks
Design for the failure modes, not only the happy path.
CSR systems often make life easier for the company and harder for the nonprofits it funds. The four failure modes below are where that happens, and where the company's own reporting quietly weakens.
Asking partners for the same data repeatedly
Every new project restarts due diligence: registration certificates, audited accounts and board lists, all emailed again. Partners lose days to it and the files scatter across inboxes. Hold documents once on the organisation record with expiry dates, and ask only for what has changed since the last check.
Mixing due-diligence risk with programme performance
A partner with a lapsed registration is a compliance risk. A partner whose attendance fell this quarter is a programme question. Put both under one red flag and the conversation turns punitive, or a real compliance gap hides behind good results. Keep due-diligence status and programme performance as separate fields with separate owners.
Dashboards without evidence links
A board slide claiming thousands of children reached cannot answer the obvious follow-up: according to whom, and counted how? Every figure on a portfolio view should link through to the partner report, verification note or site visit behind it, and say plainly whether it is self-reported or verified.
Automation that disadvantages smaller organisations
Scoring rules that reward polished proposals, large budgets and quick email replies can screen out grassroots organisations that deliver well on the ground. Test any automated screening on past applications and compare who it excludes. Keep a human review route for partners without professional fundraising staff.
02 · Minimum viable model
Connect the partner, the grant and the evidence so each claim can be traced.
A CSR portfolio is a chain: a vetted organisation, an approved project, a grant with obligations, programme evidence, money disbursed and used, and a review that decides what comes next. These six records keep the chain intact. The CSR and corporate giving playbook sets out the operating models behind them.
| Requirement (as of October 2026) | What to record | Whose duty |
|---|---|---|
| Entities implementing CSR projects register with MCA through Form CSR-1 (since 1 April 2021; revised form from July 2025) | CSR registration number on the partner record | Implementing agency registers; company checks |
| CSR spending must fall within Schedule VII activities | Schedule VII category on each project | Company |
| Annual action plan recommended by the CSR Committee and approved by the Board | Plan version linked to each project | Company |
| Ongoing projects run up to three years, not counting the year they start | Start year and planned end year | Company |
| Unspent money on ongoing projects moves to an Unspent CSR Account within 30 days of the financial year end | Unspent amount per project and transfer date | Company |
| Administrative overheads capped at 5% of total CSR expenditure | Overhead tag on expenses | Company |
| Independent impact assessment where the average CSR obligation is ₹10 crore or more, for projects of ₹1 crore or more completed at least a year earlier; its cost counts as CSR up to 2% of the year's CSR spend or ₹50 lakh, whichever is higher | Project outlay, completion date and assessment due date | Company |
| Annual CSR reporting to MCA in Form CSR-2 | Filing status per financial year | Company |
| Requirement (as of October 2026) | What to record | Whose duty |
|---|---|---|
| Entities implementing CSR projects register with MCA through Form CSR-1 (since 1 April 2021; revised form from July 2025) | CSR registration number on the partner record | Implementing agency registers; company checks |
| CSR spending must fall within Schedule VII activities | Schedule VII category on each project | Company |
| Annual action plan recommended by the CSR Committee and approved by the Board | Plan version linked to each project | Company |
| Ongoing projects run up to three years, not counting the year they start | Start year and planned end year | Company |
| Unspent money on ongoing projects moves to an Unspent CSR Account within 30 days of the financial year end | Unspent amount per project and transfer date | Company |
| Administrative overheads capped at 5% of total CSR expenditure | Overhead tag on expenses | Company |
| Independent impact assessment where the average CSR obligation is ₹10 crore or more, for projects of ₹1 crore or more completed at least a year earlier; its cost counts as CSR up to 2% of the year's CSR spend or ₹50 lakh, whichever is higher | Project outlay, completion date and assessment due date | Company |
| Annual CSR reporting to MCA in Form CSR-2 | Filing status per financial year | Company |
03 · Implementation sequence
Move through reviewable gates.
Work through these gates with two or three implementing partners before rolling out across the portfolio. Partners will tell you quickly which requests are a burden and which help them run their own programmes.
Map the partner and grant lifecycle
Trace one project from the annual action plan to closure: discovery, due diligence, proposal, committee approval, agreement, tranches, reports, site visits, utilisation, review and renewal or exit. Mark where documents travel by email and where approvals happen in meetings with no record. Those gaps are where deadlines and evidence get lost.
Standardise only essential evidence
Agree a short common core across partners: people reached, services delivered, spend by budget head, and one or two outcome measures per programme with written definitions. Leave everything else to each partner's own system. A long template applied to every partner produces compliance, not learning.
Separate partner self-report from verification
Store what the partner reported, what your team verified, how it was verified (site visit, sample call, document check) and when, as separate fields. A verified figure can then be shown with confidence and a self-reported one labelled as such. Neither is wrong on its own. Mixing them is.
Connect obligation and reporting calendars
Generate due dates from the agreement and from the CSR rules: tranche reports, utilisation, the year-end deadline for unspent ongoing amounts, impact-assessment windows and CSR-2. Send reminders to the partner and the company owner together, and spread report dates so they do not all fall in the final quarter.
Build portfolio review views
Build views for the decisions the committee actually makes: which projects are behind plan, which partners have registrations expiring, where unspent amounts are building and which projects are due an impact assessment. Use one view per decision rather than one dashboard for everything, and link every number to its evidence.
Improve requests using partner feedback
Ask partners once a year, anonymously, which requests cost them most time and which they found useful, then drop or merge the costly ones. Share portfolio learning back with them. Project Tech4Dev's published lessons warn against funders prescribing tools to nonprofits, and the same caution applies to reporting formats.
The CSR Rules place the duty to confirm that CSR money was used for the approved purposes on the company's own Board, with certification by its Chief Financial Officer or whoever handles its finances. Utilisation certificates from implementing agencies are common practice or a contract term, not a requirement the rules place on the agency. This reflects the rules as of October 2026 and is not legal advice; confirm with your company secretary, CA or legal adviser.
The CSR Rules place the duty to confirm that CSR money was used for the approved purposes on the company's own Board, with certification by its Chief Financial Officer or whoever handles its finances. Utilisation certificates from implementing agencies are common practice or a contract term, not a requirement the rules place on the agency. This reflects the rules as of October 2026 and is not legal advice; confirm with your company secretary, CA or legal adviser.
04 · Evidence
Measure whether the work became clearer.
The test of a CSR system is whether the committee can answer a question about any project in minutes, with the evidence, and whether partners spend less time reporting than before. Funders running grant portfolios beyond CSR will find a similar model in the philanthropy and foundations playbook.
05 · Responsible automation
Let systems prepare. Keep consequence with people.
Systems can support
- Holding partner documents once, with expiry alerts
- Generating obligation and report due dates
- Labelling figures as self-reported or verified
- Linking portfolio numbers to their evidence
People should decide
- Funding and rejection decisions
- Interpreting contextual risk
- Responding to safeguarding concerns
- Approving outcome claims
06 · Common questions
Practical questions teams ask.
Questions CSR heads, foundation programme teams and their implementing partners ask about CSR systems.
What technology does a CSR team need?
At minimum, a partner register with due-diligence documents and expiry dates, a project and grant tracker tied to the annual action plan, a calendar of obligations and reports, and a portfolio view that links figures to evidence. Many teams begin with spreadsheets. Move to a system once several partners, tranches and reporting deadlines start slipping between sheets.
How can CSR teams reduce the reporting burden on nonprofit partners?
Ask for less, and ask once. Hold registrations and policies on the partner record and request only changes. Agree a short common set of indicators with clear definitions, accept partners' own report formats where they cover it, and avoid a separate template for every project. Ask partners each year which requests cost them most, and cut those first.
What drives the cost of a CSR management system?
The number of partners matters less than the variety of funding models you run, the number of approval steps, whether partners will enter data themselves and the integrations with finance and company reporting. Migrating years of documents out of email is often the largest one-off effort. Configuring an existing platform usually costs less than a custom build.
How should a CSR team evaluate a technology partner?
Ask them to model one of your real projects end to end, from due diligence to the CSR-2 figures, including an unspent ongoing-project amount and an impact-assessment trigger. See how they separate self-reported from verified data, how implementing partners would use it and whether you can export everything. A partner who only shows dashboards has skipped the hard part.
When should a CSR team move off spreadsheets?
When deadlines start being caught late, the same partner documents are requested again and again, or nobody can say which version of a figure went to the board. Those are signs the tracking has outgrown its sheets. Before moving, agree the lifecycle and the common indicators on paper, so the system captures a settled process rather than a moving one.