Find partners, conduct due diligence, sanction grants, disburse funds, track LFA-based impact, and meet CSR-2, AAP, Impact Assessment, and the full set of MCA compliances — in one enterprise-grade, DPDP-aligned platform. Purpose-built for how CSR actually works in India.
Most Indian CSR teams and foundations still run the full grant lifecycle on scattered spreadsheets, long email threads, and shared drives. It works until it doesn't — and the moment it breaks, it's a compliance fire.
Multiple email threads make RFPs and proposals nearly impossible to track and manage.
Chasing DD documents across emails — hard to track, harder to verify.
Standardising annual reports across projects in one format is a recurring challenge.
No single source of truth across donors, partners, grants, and geographies.
Tracking project-level KPIs in one place is painful when data lives in 20 spreadsheets.
Filing CSR-2, AAP, and Impact Assessment becomes a quarter-end fire drill.
Approvals over email chains cause slow partner cycles and version confusion.
Collating last-mile impact across projects, donors, and geographies is a quarter-long exercise.
Indian CSR spans a wide range of operating philosophies — by focus (plant, geography, theme) and by implementation (direct grants, foundation-led, hybrid, vendor-led). mGrant is built to support all of them from the same platform.
Manufacturing corporates doing CSR in the communities around their factories and plants — typically within a 10–20 km radius. Geography-tight, community-first.
Focused on specific states, districts, or the NITI Aayog Aspirational Districts. Policy-aligned and broader in reach than plant-based giving.
Cause-first funders — e.g., scholarships, women's empowerment, child health, livelihoods. National or multi-state scope, no geography bias.
In practice most funders blend two — "healthcare in my priority states," "education near my plants," "livelihoods in Aspirational Districts." mGrant supports any combination.
The money can stay with the CSR team, go entirely to a foundation set up by the company, or be split. Once inside a foundation, there are two distinct ways it's run.
CSR team keeps the money in-house. ~99% goes out as grants to NGO partners (a small share may go to vendors). The CSR team is the funder and governor; NGOs drive programme design and execution.
The full CSR amount is routed to a corporate-set-up foundation. Once in the foundation, it's spent through one of the models shown below.
A share stays with CSR team (direct grants to NGOs); the rest goes to the foundation. A common pattern at large corporates running both tracks in parallel.
Foundations typically pick up flagship thematic programmes — water, child nutrition, rural livelihoods, Anganwadis — and drive them with their own programme design, SOPs, and governance. How the programme gets implemented varies:
The foundation runs 100% of programmes in-house — with its own field teams, M&E, and operations. Flagship programmes are designed, delivered, and measured entirely by the foundation.
The foundation owns programme design, governance, SOPs, and controls — and implements through NGO grants, vendor partners, or both. Mixes can be anything from 70% vendors / 30% NGOs to the reverse. Foundations in this model are far more involved in partner governance than a direct-CSR team.
From partner onboarding to project closure, mGrant covers every phase of the donor lifecycle — with no gaps, no handoffs to spreadsheets, and a full audit trail.
Profile & vet partners
Submission & review
Approval & scoring
Agreement & signing
Setup & kick-off
Multi-level approval
Utilisation & KPIs
QPR, QFR, field visits
Extend or close
NGO profile creation, document vault, 3-layer due diligence.
GAF creation, review, approval, MOU, Project & Grant Year setup.
Tranche planning, fund requests, multi-level approval, disbursement with UTR.
Budget utilisation, LFA/KPI, project reports, renewal or closure.
Release calls for proposals in two modes, configure templates per programme, assess with in-line commenting and scoring, and run multi-level approvals — all in one pipeline.
The RFP is published on a public URL — discoverable and shareable. Any NGO can find it, register, and apply. Best for broad discovery and first-time partner sourcing.
The RFP is not publicly listed. Instead, it's distributed via targeted email notifications to a shortlist of NGOs — drawn directly from the 3,000+ NGO Directory at the RFP release stage.
Define custom questions, budget formats, and selection criteria per programme or donor.
Proposal Details → Timeframe → Geography → Budget Allocation → LFA → Payment Tranches → Reporting Plan → Submit → Under Review → Approved/Rejected/Sent Back.
Before money moves, you need the right partners with verified paperwork and completed due diligence. mGrant covers all three stages in one workflow.
Most grant tools assume you already know your partners. mGrant helps you find them. Every NGO has valid 12A/80G, NGO Darpan, and FCRA — a curated base, not scraped data.
By theme, geography, Schedule VII category, NGO size, past grant history.
"Early Literacy partners in UP" · "Schedule VII Goal 3 partners in Maharashtra."
Send invitations directly from the portal; each NGO gets an email notification.
Your shortlist becomes the invitation list for a Closed RFP.
Every partner has a structured profile with a Documents section. Upload, version, and track statutory paperwork — with automated expiry reminders.
Due diligence isn't just document review. mGrant supports all three layers — each donor chooses how much to digitise in-system vs externally.
Documentary review, scoring, in-system.
Site visit, observation, beneficiary/staff interviews — via mForm or external upload.
Third-party references from prior donors, govt, auditors.
Configurable scoring rubrics per donor policy. Travels with the partner across grants. Feeds downstream approval decisions.
Once a proposal converts to a signed MoU, a grant is created and tracked against budget, timeline, milestones, and KPI-based performance.
Once an MoU is generated, send it straight for e-signing from within mGrant. Signed document returns and attaches automatically to the grant record.
Impact assessment is conducted by an independent agency, outside the software. Results — reports, findings, scores — are captured and attached to the project record, and feed into portfolio dashboards.
A multi-year Proposal is approved → a Project is created for the full duration with one MoU covering all years → execution runs as Grant Year 1 → Renewal → Year 2 → Renewal → Year 3, each with its own budget, targets, and reporting cycle. At closure: renewal, no-cost extension, cost extension, or project closure.
A Programme is a thematic umbrella (e.g., Water Conservation, Livelihood Generation). Under it sit one or more Projects — each a specific approach to the programme's goal. And within a single Project, grants flow to multiple NGO partners, typically one per location.
Illustrative. One programme can contain many projects. A single project can route sub-grants to multiple NGO partners — typically one per geography or implementation area.
Multi-year budget allocation, dual budget heads, tranche planning, fund requests with multi-level approvals, disbursement with UTR capture, and utilisation reconciliation — all audit-trailed.
Each donor defines their own Budget Heads and (optionally) Sub-Budget Heads. Under each head or sub-head, create multiple line items. Some donors use heads only. Some use heads + sub-heads. Some use all three levels. Fully configurable.
Bulk-upload budgets across quarters and years per grant. Allocate by programme, grant year, budget head, and line item.
Partial payments, combined tranches, 1:many mapping between planned tranches and actual receipts — all supported.
Finance records every payment with UTR number, date, amount. NGO partner auto-notified. Bank reconciliation ready.
Sanctioned · Planned · Received · Utilised · Unutilised — visible at grant, programme, and portfolio level.
mGrant doesn't replace your financial system — it connects to it. Two production-tested integration points, live at multiple client deployments.
Partners and vendors can be onboarded from either side. Create in mGrant and push to SAP/Tally/Oracle as a vendor registration, or create in the ERP and pull into mGrant. Either way: no duplicate data entry and a single source of truth.
Once an NGO fund request is approved in mGrant, the entry is pushed to your ERP. Finance creates the voucher and makes the payment in the ERP. mGrant then pulls the disbursement data back (UTR, date, amount) and notifies the NGO — all without re-keying.
Disbursement data (UTR, date, amount) synced back from ERP to mGrant automatically. One source of truth, both directions.
Before any new disbursement, mGrant calculates what's already unspent with the NGO — combining the unspent principal from previous tranches and the interest earned on it — and nets that against the new request. No donor over-funds a partner by accident.
System-calculated. Full transparency to donor and NGO. Over-funding eliminated.
mGrant calculates variance between allocation and utilisation at every reporting cycle (quarterly or otherwise). If the variance on any budget head exceeds a configurable threshold (e.g., 10%), the system requires mandatory justification and comments before the report can be submitted.
Procurement, capex, services inside the project boundary — tracked in the same fund-flow view as NGO pass-through.
GST, MSME, PAN, category, bank — separate from NGO master.
RO plants, medical equipment, IT hardware — against grant budget heads.
Installation, training, maintenance contracts. KYC vault with expiry.
Same RFP engine for impact assessment agencies, training partners, admin vendors.
Plan and measure impact using the Logical Framework Approach, with two configurable reporting paths. Complement the numbers with Stories of Change — narrative, photo, and video submissions from the ground.
Grouped phases with start & end dates
Dates nested within milestone
Direct deliverables
Resulting changes
Long-term societal change
Every activity's dates must fall within its parent milestone. When all activities complete, the milestone closes. Activities feed Outputs; Outputs drive Outcomes; Outcomes contribute to long-term Impact.
At the GAF / proposal stage, set the reporting frequency for each grant or project — monthly, quarterly, or semi-annual. The same frequency applies to budget utilisation and KPI reporting for that project. Two projects under the same programme can run on different frequencies. Planning, reporting cadence, and reminders all flow from this setting.
Upcoming: decouple budget and KPI frequencies within the same project (e.g., monthly budget reporting + quarterly KPI reporting).
Manual monthly / quarterly / annual entry of achievement numbers against each KPI. NGO uploads supporting files (photo, report, attendance sheet) as means of verification.
KPI auto-calculated from mForm or any field data collection / survey platform. Best for grants with active field data collection and beneficiary tracking.
A donor can configure, for example, 10 KPIs across a grant — 7 on Path A (aggregate) and 3 on Path B (platform-driven). The system adapts to what's feasible per indicator.
The same variance logic that applies to budgets applies to KPIs. If a quarterly target was "train 100 students" and the reported achievement deviates by more than a configurable threshold (e.g., 10% under or over), the system requires a mandatory justification before the report can be submitted. Thresholds are set per donor policy — and the feature can be switched off entirely.
A single platform-wide library for every document that matters — MoUs, sanction letters, board notes, audit reports, impact assessments, partner documents. Upload once, tag, search, and reuse across grants, programmes, and partners. No silos, no duplicate copies.
Not per-grant — searchable across your entire portfolio.
Every upload versioned; all accesses logged.
Finance sees financial docs; programme teams see programme docs.
Numbers on a dashboard tell half the story. NGO partners submit narrative stories from the ground — with photos, videos, and supporting media — to bring impact to life.
Repurpose stories for branding, social media, annual reports, board decks, and external reports.
A structured way to capture success stories, field photos, beneficiary journeys, and video testimonials.
Stories visible to the donor's other NGO partners — acting as a peer knowledge base of what's working in the field.
Work plans, quarterly reports, field visits, review meeting notes, task management — everything a grant manager needs for day-to-day execution, with automated reminders and escalation.
KPI achievement · Budget utilisation · Beneficiary counts · Activity counts
Work plan activity completion · Narrative reports · Field visit reports · Stories of Change · Compliance documents · Meeting notes · Third-party impact assessment reports
Planned activity reporting (Work Plan) lives inside the project; ad-hoc cross-team asks (Task Management) live on the main navigation. Same underlying engine.
At proposal stage, NGO proposes activities + frequency. On approval, line items auto-generate with due dates.
Standalone module on the main nav. Ad-hoc asks to internal team or NGO partners. "Send me photos," "share the revised budget."
All the qualitative reports NGOs submit to donors — quarterly progress, quarterly fund utilisation, annual audit, fund utilisation certificates — scheduled at proposal stage, delivered through the Reports tab, approved per workflow.
Submit within 10 days of site visit. Photo, video, geo-tag capture via mForm. Structured observation templates. Travels with the grant record.
CSRs run regular review meetings with partners. Capture each meeting — date, attendees, key notes, decisions, follow-ups — as structured notes attached to the partner or grant.
Across all grants: submitted, pending, overdue — sliceable by partner, programme, and reporting period.
Real-time dashboards with multi-dimensional slicing — donor, programme, pillar, geography, financial year — all drill-down enabled, from portfolio to village level.
Illustrative screen — real dashboards are fully interactive with drill-down to grant, district, village, and beneficiary level.
Budget · Committed · Disbursed · Utilised · Unutilised · Unspent — at portfolio, programme, or grant level.
Output and outcome achievements, planned vs actual, by programme, geography, and quarter.
India heat map with state-wise and district-wise project count, budget committed, beneficiaries reached.
Slice by Schedule VII pillar, SDG, or custom taxonomy. Stackable filters with one-click reset.
State → District → Block → Village → Grant → Beneficiary. Multi-dimensional, hierarchical, instant.
No-code drag-and-drop report builder. Export to Excel, PDF, CSV. Scheduled auto-email distribution.
mGrant ships with a library of ready-to-run reports, grouped by category. Each is filterable by FY, programme, partner, geography. Donors can also build custom reports without writing SQL.
Illustrative catalogue — final report set is tailored per client during implementation.
The full stack of MCA obligations under Section 135 and the Companies (CSR Policy) Rules 2014 — including the July 2025 amendments on geo-tagging and asset mapping.
Data auto-populated from the grant portfolio for MCA filing. The single annual CSR filing to the registrar.
Board-approved AAP tracking across the financial year, with project-level mapping and variance alerts.
Every grant classified against the 11 Schedule VII activity categories. Portfolio view by goal. (Classification, not a separate filing.)
Track the 2% of average net profits mandate (3-FY average). Real-time spend-to-target view. Board disclosure support if there's a shortfall.
Ongoing projects: 30-day transfer rule and 3-FY spend window tracked. Non-ongoing: 6-month transfer to Schedule VII fund. Automated deadline alerts.
Mandatory for CSR obligations ≥ ₹1 Cr over the last 3 FYs. Structured third-party assessment workflow with report upload and board review.
Per the Companies (CSR Policy) Amendment Rules 2025: every capital asset created through CSR funding is registered with geo-coordinates, ownership, and asset identity. Built on mGrant's native geo-tagging capability plus mForm field capture.
Every partner NGO's CSR-1 registration validated and stored in the compliance vault. Linked to grant approvals.
Automatic alerting when administrative expenses approach the statutory 5% ceiling.
Immutable, system-generated change logs — user ID, timestamp, old/new values, IP. Configurable 8-year retention. Suitable for statutory audit.
Every filing, renewal, and deadline — CSR-2, AAP, Impact Assessment, 12A/80G renewal of partner NGOs. Automated reminders 60/30/7 days out.
Any CSR or foundation workflow that needs field data — beneficiary surveys, intervention forms, field DD, stakeholder interviews — plugs into mForm, Dhwani's offline-first mobile data platform.
Capture data anywhere, sync when back online.
Hindi, Marathi, Tamil, Bengali, and more regional languages.
Skip logic, validation, sections, consent flow — no code.
Multi-media capture with geo-tags for every submission.
Data flows back into KPI calculation and impact dashboards.
Architecture-ready for any survey / field data platform via REST API.
mGrant is built for organisations that take compliance, data protection, and audit seriously. Hosted on AWS Mumbai, ISO 27001-certified, VAPT-cleared, DPDP-aligned — with a full immutable audit trail suitable for MCA audit.
Client = Data Fiduciary · Dhwani = Data Processor (covered by DPA). Consent capture and withdrawal logged. Data Principal rights supported: export, edit, erasure (subject to legal holds). Breach runbook with client notification SLAs. In-country hosting by default, cross-border off. DPA with sub-processor list; RoPA and DPIA templates available.
Connect mGrant to your ERP, BI tool, identity provider, and field data platform — or run it standalone. Open REST APIs and webhooks for anything we haven't built yet.
A focused roadmap of AI capabilities for grant-making. No hype. Every item below is either in active development or scoped for the next release cycle.
Ask questions in plain English or Hindi and get contextual answers with the underlying data. Built on Model Context Protocol (MCP) with 30+ tools across NGO, proposals, fund management, reporting, and approvals.
Extract key findings from lengthy QPR, narrative, and field-visit reports. Identify themes across many submissions. Auto-generate executive summaries for board decks.
Given a programme brief — theme, geography, budget, timeline — surface the best-matched NGOs from the 3,000+ directory, ranked by fit and historical track record.
AI-assisted scoring of incoming proposals against your rubric. Flag missing sections, weak theory of change, unrealistic budgets, or inconsistent LFA chains — before the assessor reads it.
Read and validate any document the NGO submits — compliance certificates, bills and invoices, fund utilisation reports, audit statements. Verify GST numbers, match names and amounts against mGrant records, cross-check FUC totals against reported budget utilisation, flag anomalies, send clarifications back to the NGO.
"Grant X is 60% through timeline but only 30% utilised." Early warnings from pattern analysis across utilisation, KPI variance, missed reporting deadlines, and NGO-side signals.
Pre-fill CSR-2 and AAP drafts from portfolio data. Answer natural-language compliance questions. Flag gaps against the latest MCA rules before filing season.
Given KPI data and Stories of Change, draft impact narratives for donor-facing reports, annual reports, and board updates. Human in the loop for final review.
Spot unusual utilisation patterns, outlier variance reports, duplicate expense claims, and suspicious beneficiary counts — across the full portfolio, not one grant at a time.
mGrant is a platform, not a product. Adapt it to your process instead of the other way around — with low-code configuration, white-label options, and enterprise-grade infrastructure.
Visual form designer, 50+ field types, custom fields without code, automatic UI generation from metadata.
State-based workflows per module — Draft → Submitted → Approved → Cancelled — configurable per client. Approval levels, rejection routing, notification routing.
Downloadable Excel templates with cascading, name-based dropdowns — State → District → Block → Village. Download, fill, upload. No Frappe IDs, no power-user Excel skills needed.
Template-based PDF and print formats — MoU, Letter of Award, Fund Letters, Board Notes — with organisation branding.
Module, record, and field-level permissions. Role hierarchies and user groups. Dynamic updates without downtime.
No-code, drag-and-drop. Dynamic filtering, grouping, aggregation. Multiple views — tabular, calendar, Gantt, Kanban, tree.
Multi-site deployment, tenant isolation via database, shared infrastructure with separate schemas.
Deployed under your brand, colour palette, and logo. Your platform, powered by mGrant.
Role-based views for every CSR-side and partner-side user — from the System Admin down to the NGO field officer. Each role comes with default permissions you can fine-tune at module, record, and field level.
Custom roles configurable per deployment. Every role can be fine-tuned at module, record, and field level.
40+ donor organisations already use mGrant for their grant lifecycle — from corporate CSR to philanthropic foundations.
A sample of mGrant's client roster. Full list shared in direct conversation.
Three-stage implementation, named team with a client POC, annual subscription, clear SLA on issue response.
Spreadsheets work until they don't. Generic CRMs don't know what a tranche is. Point tools cover fragments, not the whole lifecycle. mGrant is built for this, end to end.
Key terms used in mGrant — for anyone new to Indian grant-making and CSR.
The organisation funding grants — corporate CSR, foundation, bilateral, or government body. Primary tenant of mGrant.
Structured proposal form. Once approved, converts into a Grant and a Project.
Request for Proposal / Terms of Reference. Released in Open Call or Invite-Only mode.
The legal grant agreement between donor and NGO, triggered on GAF approval.
A Project is created from an approved (often multi-year) Proposal — e.g., 3-year project with one MOU. Grant Year = the annual execution slice (Year 1, Year 2, Year 3) with its own sanction, budget, and targets, with renewal between years.
A thematic umbrella containing multiple Projects. E.g., Water Conservation Programme → Project A: Check Dam Construction; Project B: Plantation. Within each Project, grants flow to multiple NGO partners (typically one per geography).
By focus: Plant-based · Geographic · Thematic (or combinations). By implementation: Direct grants · Foundation self-implementation · Hybrid · Foundation + vendor-led.
Before disbursement, mGrant calculates the NGO's unspent amount + interest earned from previous tranches and nets it against the new fund request. Prevents over-funding.
Configurable cost-control thresholds on allocation-vs-utilisation variance. E.g., if variance exceeds 10% on a budget head, mandatory justification before submission. Optional per donor.
The NITI Aayog list of 112+ districts prioritised for development. Many geographic-focused CSR programmes target these districts.
Statutory list of 11 permitted CSR activity categories (Section 135, Companies Act). It's a classification used to tag grants — not a separate reporting obligation.
Per Companies (CSR Policy) Amendment Rules 2025 (in force July 14, 2025) — capital assets created through CSR funding must be registered with geo-coordinates, ownership, and asset identity.
For ongoing projects: unspent CSR must transfer to an Unspent CSR Account within 30 days of FY-end and be spent within 3 FYs. For non-ongoing: transfer to a Schedule VII fund within 6 months.
Annual CSR reporting form filed with MCA. Auto-populated from the grant portfolio.
Board-approved CSR plan for the financial year. Tracked through mGrant.
FC = foreign contribution. Non-FC = domestic. Tracked separately per FCRA requirements.
Income Tax registrations enabling tax-exempt grants. Stored with expiry tracking.
Partner vetting across 3 layers: desk (documents), field (site visit), reference.
A scheduled payment instalment. Grants disbursed across multiple tranches.
NGO's request for a tranche payment. Multi-level approval before disbursement.
Unique Transaction Reference — captured on disbursement for bank reconciliation.
Expense category / specific line item. Donor heads + natural heads with mapping.
Logical Framework Approach — Activities → Outputs → Outcomes → Impact.
Key Performance Indicator — measurable value tracking project progress.
Quarterly Progress / Fund utilisation / Review Reports. FUC = Fund utilisation Certificate.
Qualitative narrative reports with photos and videos. Cross-partner peer knowledge.
Dhwani's offline data-collection app and learning management system.
Information-security standard · Vulnerability testing · India's data protection law.
Mandatory immutable change log in accounting software, per MCA rules.
Indian multilingual NLP capability — supports form translations across regional languages.
See mGrant live, tailored to your CSR or foundation workflow. 30 minutes. No slideware — just the platform and your use cases.
Book a Session →