How to Refresh Your Corporate Volunteering Programme Mid-Year
Somewhere between end of Q2 and the start of Q3, most Indian HR teams responsible for corporate volunteering programmes take a quiet honest look at how the year is actually going. Which activities landed. Which quietly did not. Which workforce segments participated well. Which felt distant from the programme. What documentation is ready for year-end disclosures. What is scrambling to catch up.
This mid-year review is one of the most useful moments in the corporate volunteering year. It is early enough to change course meaningfully, late enough to have real data to work with, and quiet enough that HR teams can think clearly rather than reacting to a quarterly deadline.
The problem is that many mid-year reviews get compressed into a single meeting where the team asks whether targets are being hit and moves on. That produces a review that catches numbers but misses substance. A more thoughtful mid-year refresh looks at programme design, workforce reach, dignity considerations, documentation readiness, and what the second half of the year should look like differently.
This article is a practical framework for Indian HR teams thinking about how to refresh their corporate volunteering programme at mid-year. Seven dimensions worth reviewing. Practical questions for each. And the honest note that a mid-year refresh is course-correction rather than rescue.
One thing to name upfront. Mid-year refresh is not about pushing employees harder to hit targets. Participation should stay voluntary throughout. What changes in a good refresh is programme design, format diversity, and inclusion, not the pressure applied to workforce members.
Why Mid-Year Refresh Matters :Corporate Volunteering
Three reasons make mid-year the most valuable moment for corporate volunteering programme review.
There is enough programme data to see patterns
At end of Q1, most programmes have not accumulated enough data to distinguish signal from noise. At end of Q3, there is often not enough time to change course meaningfully before year-end. Mid-year sits in the useful middle where patterns are visible and adjustments can produce real second-half improvements.
Second-half planning benefits from honest first-half review
Q3 and Q4 planning is stronger when it starts from an honest assessment of what worked and what did not in H1. HR teams that skip this assessment often replicate first-half patterns without knowing whether those patterns were working.
Year-end documentation preparation is easier when started at mid-year
CSR-2 disclosure, BRSR Core reporting, and internal engagement documentation all benefit from mid-year preparation. HR teams that identify documentation gaps at mid-year have time to fix them. HR teams that discover the gaps in February scramble.
7 Dimensions to Review at Mid-Year
Here are seven dimensions worth reviewing at mid-year, with practical questions for each.
1. Participation Data Across Workforce Segments
Look at who has actually participated in the programme so far this year, broken down meaningfully by workforce segment.
Questions worth asking:
Which workforce segments have participated well? Which have not? Is participation concentrated in head-office employees while distributed teams remained excluded? Have specific role types, seniority levels, or business units engaged more than others? Is family-inclusive participation reaching parents specifically, or is it excluding employees without children?
What refresh looks like:
Where certain segments have low participation, examine whether the programme design excluded them (activity format, timing, location) rather than assuming those segments do not want to participate. Adjust format diversity in H2 to reach the segments that H1 missed.
Important note:
Low participation from a workforce segment usually reveals a programme design issue, not an engagement problem with the workforce. Blaming the workforce is not the correct read.
2. Activity Format Diversity
Review the mix of activity formats across the year so far, and whether the mix is genuinely serving different workforce segments and community needs.
Questions worth asking:
Has the programme been dominated by one or two activity formats? Has hands-on volunteering crowded out skills-based volunteering (or vice versa)? Are virtual and distributed formats represented? Have family-inclusive activities happened? Are in-office activities providing an entry point for employees with mobility or scheduling constraints?
What refresh looks like:
If format diversity is thin, plan H2 with the missing formats added. If hands-on has dominated, add skills-based. If head-office has dominated, add distributed and virtual. Match format to workforce segment that was under-served in H1.
3. Safeguarding and Dignity Review
Any programme involving children, vulnerable communities, or beneficiary engagement needs safeguarding review at mid-year. This is non-negotiable.
Questions worth asking:
Have all activities involving children maintained appropriate safeguarding (adult supervision, background awareness, no unaccompanied volunteer time with children)? Has photography of beneficiaries been handled with proper consent? Have activities involving vulnerable communities been designed with dignity (no distress-tourism, no observation-visit framing)? Have communities been engaged as participants rather than props?
What refresh looks like:
Any safeguarding gap identified should be addressed immediately, not deferred to H2 planning. Photography practices that need consent structures fixed should be fixed now. Activity designs that drift into dignity-eroding territory should be redesigned for H2.
Important note:
Safeguarding gaps are not a reason for blame. They are a reason for immediate correction. Handle the correction constructively with the implementation partner.
4. Community Impact Documentation
Review the documentation captured across H1 activities and assess readiness for year-end disclosure.
Questions worth asking:
Are utilisation certificates being collected properly for CSR-funded activities? Are beneficiary records being maintained where relevant? Are photographs being captured with appropriate consent? Is impact documentation being built beyond participation counts? Is data feeding into BRSR Core disclosure requirements cleanly? Is the implementation partner's reporting meeting internal standards?
What refresh looks like:
Where documentation is thin or inconsistent, work with the implementation partner to strengthen H2 documentation practice. Where consent structures need improvement, coordinate on updated practices for H2. Where BRSR Core data feed is incomplete, identify and close the gaps now.
Important note:
Year-end reporting is much easier when mid-year documentation practices are strong. Do not defer this dimension.
5. Employee Engagement Quality Beyond Participation Counts
Look at engagement quality, not just participation numbers.
Questions worth asking:
Have employees who participated reported meaningful experiences? Are participants returning for multiple activities across the year or is engagement one-time? Are internal communications about the programme resonating? Is there qualitative feedback from participants worth acting on? Are activity ratings, if collected, showing patterns?
What refresh looks like:
Where engagement quality is thin, review activity design, community partnership quality, and internal communication. Programme design that produces participation numbers but low engagement quality often improves with better community partner engagement and richer activity design.
Important note:
Participation counts are the shallowest measure of a programme. Engagement quality is the meaningful one.
6. Budget Review and H2 Planning
Review budget deployment against the year's plan and identify any adjustments needed for H2.
Questions worth asking:
Is budget deployment on track? Are certain programme areas under-spent while others over-spent? Has any planned activity been deferred that should be restarted for H2? Are there approved budget lines that have not been deployed at all? Do any FY 2025-26 CSR obligations require H2 planning attention?
What refresh looks like:
Where budget deployment is uneven, plan H2 to close the gaps. Where planned activities have been deferred, decide whether to restart or reallocate. Where CSR compliance obligations require year-end deployment, plan H2 with those requirements in mind.
Important note:
For CSR-funded volunteering programmes under Section 135 of the Companies Act 2013, budget deployment discipline is a compliance issue as much as a programme issue. Coordinate closely with your CSR committee and finance team.
7. Q3 and Q4 Calendar Design
Use the mid-year review to build the Q3 and Q4 calendar with intent, not by default.
Questions worth asking:
Which calendar-day activities are worth planning for Q3 and Q4? UN International Day of Persons with Disabilities (December 3), World AIDS Day (December 1), Human Rights Day (December 10), and Republic Day (January 26) all fall in H2 planning windows. Which of these fit the programme direction? Are there seasonal considerations (winter, festival season, financial year-end urgency) affecting H2 planning? Do H2 activities include appropriate diversity of formats and workforce segment reach?
What refresh looks like:
Build the H2 calendar with the H1 lessons applied. Add the formats that H1 missed. Include the workforce segments H1 excluded. Plan around the calendar days that fit the programme. Coordinate with the implementation partner on delivery capacity.
Important note:
H2 planning is easier when it happens in September. It becomes rushed by November and reactive by January.
A Constructive Framing Note
Mid-year review can drift into criticism of the programme, the HR team, or the implementation partner. That is not what a useful refresh looks like.
The refresh should assume that the H1 team did their best with what they knew at the start of the year. New information from H1 experience is what makes H2 planning better. That is the value of the review, not identifying blame.
If specific challenges emerged in H1, address them constructively with the implementation partner. Programme design conversations, format additions, safeguarding practice improvements, and documentation strengthening all work better as forward-facing collaborations than backward-facing critique.
What Mid-Year Refresh Can and Cannot Do
A measured note on what refresh can and cannot achieve.
Refresh can adjust programme direction, add missing formats, strengthen safeguarding and documentation, improve workforce inclusion, and set up stronger H2 execution. Refresh works well when there is genuine capacity to change course.
Refresh cannot fix a fundamentally mismatched programme, rescue a partnership that has structural problems, or transform participation targets that were set unrealistically at the year's start. If the underlying issues are structural rather than tactical, more significant conversations may be needed alongside the refresh.
For most Indian corporate volunteering programmes, mid-year refresh produces meaningful H2 improvements. For programmes where structural issues exist, refresh is a starting point for larger conversations rather than a solution on its own.
Distributed Workforce Inclusion Deserves Extra Attention
One dimension of mid-year review that often gets under-served: whether the programme is genuinely reaching workforce members outside head-office locations.
Distributed workforce inclusion is one of the fastest-growing areas of corporate volunteering programme design in 2026. Programmes that reach only head-office employees while distributed teams remain excluded produce weaker engagement outcomes and expose the programme to internal criticism.
At mid-year, ask specifically: What percentage of distributed workforce members have participated in the programme so far? Which regional offices are under-represented? Which remote employees have found nothing that works for them? Is the H2 calendar planning distributed activities across cities, virtual formats, and formats that work for remote employees?
Where distributed workforce inclusion has been weak in H1, dedicate specific H2 attention to fixing it.
Voluntary Participation Stays Foundational
Mid-year review should not translate into more pressure on employees to participate. Programmes that increase participation pressure at mid-year damage engagement quality across H2.
What changes in a good refresh is programme design that makes participation easier and more meaningful for a broader set of employees. Better formats, better inclusion, better communication about what activities involve, better time flexibility, better matching of activity type to workforce segment.
Employees who choose to participate produce meaningful engagement. Employees who feel pressured produce participation numbers without engagement.
Compliance and Reporting Notes
For companies where the volunteering programme is CSR-funded under Section 135 of the Companies Act 2013, standard CSR compliance considerations apply to mid-year review and H2 planning.
Schedule VII alignment. All H2 activities must fall within Schedule VII categories.
Implementation partner eligibility. Partners must hold valid 12A, 80G, and Form CSR-1 registrations for CSR-funded activities.
Documentation for CSR-2 and BRSR Core. H1 documentation should be reviewed for readiness. H2 documentation practices should close any identified gaps.
Budget deployment discipline. Under-deployed CSR budget by mid-year signals H2 planning attention needed. Coordinate with your CSR committee, finance team, and Chartered Accountant on any specific compliance planning.
BRSR Core alignment. Review the year's data feed against Principle 3 (employee wellbeing), Principle 4 (stakeholder engagement), and Principle 8 (inclusive growth) requirements. Identify gaps early.
For HR-funded volunteering programmes not classified as CSR, coordinate with finance and HR policy on any budget adjustments, family-inclusive activity consent structures, and internal engagement reporting refresh.
How Marpu Foundation Supports Companies With Mid-Year Refresh
At Marpu Foundation, we work with companies across India as an implementation partner for corporate volunteering programmes, including mid-year refresh conversations.
What Marpu offers for mid-year refresh:
We help HR teams assess H1 programme performance across participation, engagement quality, workforce segment reach, format diversity, safeguarding practice, community engagement, and documentation.
We work with HR teams on H2 planning that addresses the gaps H1 revealed, including adding activity formats that H1 missed, extending reach into distributed workforce segments, improving safeguarding practice, strengthening documentation for year-end disclosure, and calendaring H2 activities across the specific calendar days and community themes that fit the programme direction.
We handle refresh conversations constructively, not critically. Programme design improvements in H2 build on what H1 taught us, not on blame for what did not work.
We coordinate H2 activities across in-person, virtual, family-inclusive, skills-based, distributed multi-city, and hands-on formats, so H2 programme design reaches workforce segments H1 may not have.
We provide complete documentation refresh support including participation records, beneficiary records, photographs with appropriate consent, impact reports, and BRSR-ready data feeds.
Our experience:
We work across 23 states with over 250 corporate partners, including organisations from the Fortune 500. We hold valid 12A and 80G registrations and Form CSR-1 filing. We understand the documentation, safeguarding, and programme design standards Indian HR teams require for mid-year refresh and H2 planning.
If you are conducting mid-year review of your corporate volunteering programme and would benefit from an implementation partner who can support constructive H2 refresh across programme design, workforce inclusion, safeguarding, and documentation, reach out to Marpu Foundation at connect@marpu.org or visit www.marpu.org. Mid-year refresh is easier when done in September, and we would be happy to support your team's H2 planning.
Comments