Most CSR partnerships in India do not fail in year five. They fail quietly in year one and limp through years two and three before everyone agrees to walk away.
I have spent the better part of a decade watching this pattern up close. Some of those partnerships became long-term collaborations that defined Marpu’s growth. Others ended after a single project, both sides slightly disappointed, neither side fully understanding why. The difference between the two outcomes is rarely about budget. It is rarely about activity choice. And it is almost never about the public chemistry of the people in the room at signing.
What it is actually about is harder to talk about because it sits in the operational layer that nobody discusses publicly. Documentation discipline. Reporting expectations. Internal continuity. Multi-year planning horizons. The unglamorous things that decide whether the partnership survives the first audit cycle.
This article is for the CSR heads, the HR leaders, and the founders who are about to start a new partnership and want to know what actually predicts whether it will work. It is also for the ones whose past partnerships did not last and who are wondering what to do differently the next time.
The five things that actually matter
In my experience, five things separate the partnerships that compound from the ones that quietly disappear. None of them are about the project. All of them are about how the two sides work together around the project.
One: A multi-year planning horizon, even if the contract is annual
The partnerships that work treat the first project as the start of a longer arc. The partnerships that fail treat the first project as the entire commitment.
This sounds obvious. It is not. The default mode in Indian CSR is annual. Budgets are annual. Approvals are annual. CSR-2 disclosures are annual. The financial year deadline of March 31 dominates every conversation. Projects are designed to finish by March, even when the work itself does not respect financial-year logic.
The partnerships that succeed have one or both sides quietly thinking in three-year frames even when the paperwork is annual. The CSR head has a private plan for what year two and year three look like. The implementation partner is designing the year one project to set up year two. Both sides know this is going to compound.
When this thinking is missing on either side, the partnership becomes a transaction. The project gets executed. The certificate gets filed. The relationship sits in administrative limbo until next April, when somebody remembers to send a renewal email or, more often, somebody else gets the budget instead.
The fix is simple to describe and difficult to actually do. Both sides need to ask, in the first conversation, where this could be in three years. Not as marketing language. As an operational planning question. The answer changes how the first project is designed.
Two: Documentation as a shared discipline, not a deliverable
The biggest single reason partnerships fail in year two is documentation drift in year one.
This is not the discussion that happens at the signing meeting. The discussion at signing is about activities, beneficiaries, geographies. Documentation is treated as something the implementation partner will handle in the background, and the CSR team will receive at the end.
This framing kills partnerships. Documentation is not a delivery item. It is the shared discipline that protects both sides through audit, board review, and the next year’s renewal conversation. It is the basis on which the CSR team defends the spend internally. It is the basis on which the implementation partner defends its work externally. And it is the single artefact both sides will revisit when something goes wrong, which something always does eventually.
The partnerships that succeed treat documentation as a shared standard from day one. What gets photographed. What gets geo-tagged. How beneficiary records are kept. How utilisation certificates are formatted. What the impact narrative actually claims. Both sides agree on this before the first activity is scheduled.
The partnerships that fail discover at the end of March that the documentation is not in the format the company’s audit team needs, the photographs are insufficient, the beneficiary records are inconsistent, and the impact claims do not align with what the BRSR team can disclose. Each side blames the other. Both lose trust. The partnership does not renew.
The fix here is also simple. Treat the documentation discussion as central, not peripheral. Spend the time on it that the issue deserves.
Three: Internal continuity on the corporate side
This is the variable I cannot control as the implementation partner, but it is the one I have learned to watch most carefully.
The CSR head who signed the partnership is not always the CSR head reviewing it twelve months later. CSR teams turn over. Procurement teams shift. Internal champions get rotated. New leaders bring new themes. Foundations restructure.
The partnerships that survive these transitions are the ones where the original conversation was documented internally, the partnership is anchored to multiple people inside the company, and the work has visibility outside the CSR team alone. When the new CSR head walks in, they read the file, see the work, talk to colleagues who have visited the site, and the partnership continues.
The partnerships that do not survive transitions are the ones anchored to a single internal champion. When that champion leaves, nobody else has the context. The new person looks at the line item, asks why this partnership exists, finds no internal advocate, and quietly redirects the budget elsewhere.
The implementation partner cannot solve this for the company. But the implementation partner can notice when the corporate side is over-anchored to one person and gently expand the conversation. Bring colleagues into project visits. Send updates to multiple stakeholders. Build relationships that survive the inevitable internal change.
Four: Genuine engagement, not photo-op engagement
There is a difference between a CSR partnership where the company genuinely wants employee engagement and one where the company wants employee-engagement photographs.
The two look identical at the start. They diverge sharply by the second project.
Genuine engagement looks like this. The company wants employees who are physically present at project sites, who interact meaningfully with the community, who come back to the office and tell colleagues what they saw, who feel something they cannot easily put into a slide. The company is willing to spend on transport, on time, on the operational logistics that real engagement requires.
Photo-op engagement looks like this. The company wants employees in matching t-shirts holding saplings or kits or banners for fifteen minutes. The photographs are needed for the internal newsletter, the sustainability report, and the LinkedIn post by Friday. After the photographs are taken, the engagement ends.
Both kinds of partnerships exist in the Indian CSR landscape. The first kind compounds. The second kind exhausts both sides. The implementation partner gets tired of staging photogenic moments. The corporate team eventually realises the activity has not actually changed anything internally.
The fix requires honesty in the first conversation. Both sides should be clear about what kind of engagement is being designed for. If the company genuinely cannot do more than fifteen-minute photographs, that is fine. The activity should be designed for that and priced for that. Pretending it is something else is what creates the year-two collapse.
Five: Aligned reporting expectations, set upfront
The single most avoidable cause of partnership friction is reporting expectations that were never explicitly aligned.
The CSR team needs reporting in a specific format because their internal review process requires it. The implementation partner produces reporting in the format that fits their standard practice. These two formats do not match by default.
When the gap is discovered in March, with three weeks until the financial year ends, the relationship gets stressed. The CSR team feels the partner is not delivering what they need. The partner feels the CSR team is moving the goalposts. Both are partly right and partly wrong.
The fix is to align on reporting in the first month, not the last. What format does the CSR team need. What documentation does the company auditor need. What data does the BRSR team need. What photographs does the internal communication team need. What stories does the internal newsletter need. All of this can be specified upfront.
Once it is specified, both sides can plan against it. The implementation partner builds the reporting infrastructure into the project design. The CSR team has clarity on what to expect and when. The end-of-year crunch never becomes a crisis.
What none of this is about
It is worth being explicit about what this article is not arguing.
It is not about budget size. The partnerships that compound and the partnerships that fail come in every budget bracket. Money is not the variable.
It is not about industry. CSR partnerships work and fail across IT, BFSI, manufacturing, pharma, FMCG, and every other sector. The dynamics are universal.
It is not about NGO size or capability. Plenty of small implementation partners deliver beautifully. Plenty of large ones disappoint.
It is not about activity choice. Education, environment, healthcare, livelihood. All of these can compound. All of these can fail. The activity is downstream of the relationship logic.
It is also not about the public chemistry at the signing meeting. Some of the smoothest first conversations have produced the most disappointing partnerships. Some of the most awkward first conversations have produced the most enduring ones. Chemistry is not the predictor.
The five things above are the predictors. They are operational. They are unglamorous. And they decide whether the partnership turns into a real long-term collaboration or fades into the long quiet list of CSR projects that ran for one year and then disappeared.
What corporate CSR heads can do differently
If you are a CSR head reading this, here is the practical takeaway.
In the first conversation with any new implementation partner, ask three operational questions before you ask any project questions. Where do they think this could be in three years. How do they handle documentation. How does their reporting plug into your specific format requirements.
The answers tell you more about whether the partnership will work than any amount of pitch deck or past project showreel.
Then internally, ask whether your own organisation is set up to make the partnership work. Is the CSR team continuity strong enough that the partnership survives a transition. Is leadership genuinely interested in employee engagement or only in engagement photographs. Are reporting expectations aligned with finance, BRSR, and audit before the partnership begins.
If any of these answers is unclear, fix it before the partnership starts. Not after.
What implementation partners need to do differently
If you run an NGO, social enterprise, or implementation organisation, the inverse questions matter.
Are you anchoring the partnership to multiple people inside the company, not just the CSR head you happen to know. Are you setting reporting expectations explicitly in the first month, not at the end of the year. Are you treating documentation as central, not peripheral. Are you helping the CSR team see how this work could compound across three years, not just deliver this year.
The implementation partners that grow over a decade in Indian CSR are the ones that take responsibility for the partnership infrastructure, not just the project execution. The ones that stay small are the ones that wait for the corporate side to provide all the strategic clarity.
The clarity that compounds
The Indian CSR sector is now mature enough that the underlying patterns are visible. Both sides have done enough partnerships to know what works. What is missing is the willingness to talk about it operationally, in plain language, before the partnership starts.
When both sides come into the first conversation honest about what good partnership looks like and what bad partnership looks like, the work becomes simpler. The documentation gets done properly. The reporting matches the disclosure needs. The engagement is what it claims to be. The three-year arc actually exists.
When that clarity is missing, the partnership becomes a series of accommodations. Both sides try to make the relationship work in spite of the misalignment, until eventually one side decides it is not worth the effort.
The five things in this article are not a checklist. They are a description of what the partnerships I have seen succeed have in common. Every CSR head who has been in the sector long enough recognises the pattern when it is named. Every implementation partner who has been around long enough has learned the same lessons, often the hard way.
Naming the pattern publicly is the easiest way to stop both sides from learning it the hard way again.
Write to me at raghu@marpu.org.
KADIRI RAGHU VAMSI 
Leave a comment