CSR teams used to accept a PDF with a few photos and a utilisation certificate. Fewer do now. Since the January 2021 amendment to the Companies (CSR Policy) Rules, 2014, larger CSR spenders must get independent impact assessments of bigger completed projects and annex those reports to their annual CSR report (MCA CSR FAQ, section 9). The same FAQ notes that money handed to an implementing agency doesn't count as spent until the agency actually uses it, and that the Board must satisfy itself the funds were used as approved. So the questions reach you, the NGO: where exactly was this done, when, and can someone check?
Geotagged proof is how you answer before you're asked. This guide covers what it means in practice, how to turn field data into a report a funder trusts, and the failures we see most often.
What "geotagged proof" actually means.
A photo is not proof. A photo with three things attached is:
- 01Location. GPS coordinates captured by the phone at the moment of capture, not typed in later.
- 02Time. A timestamp from the device, stored with the photo when it's uploaded.
- 03Identity. A unique ID for the asset in the photo: tree T-0412, toilet block B-07, classroom 3 at a named school. Without an ID you can't show the same asset again next quarter, and "again next quarter" is what proves it survived.
There are two ways to capture this in the field. A field app enforces it: the camera opens inside the app, GPS is required, and the photo is attached to an asset ID before it can be saved. WhatsApp capture is easier to start with, since staff already use it, but WhatsApp compresses images and can drop location data, and photos arrive mixed into chat threads. If you use WhatsApp, have staff share location as a separate message and sort photos into a structured record the same day.
What we learned mapping 11,000+ trees.
We built a proof-of-life platform for tree planting. Most tree projects hand over a photo at planting and go quiet. This one keeps a life record per tree: dated visits, growth and survival, on a public satellite map, with sponsor portals and science-based carbon reports. It runs on a production database with 11,000+ trees mapped.
Alongside it, PlantationOS handles the operations side. Create a forest and it generates the full 49-task, three-year care lifecycle, with assignments, checklists and automations, so site visits happen on schedule. That matters for reporting: the evidence is only as good as the visits that produce it.
Three lessons carry over to any asset an NGO builds or maintains:
- AOne record per asset, forever. Every later photo attaches to the same ID. The history is the proof.
- BSchedule the evidence. If visits aren't planned, they don't happen, and gaps show up in the report.
- CLet the funder look. A live map a CSR manager can open on their own is more convincing than any photo you choose.
From field data to a funder report.
Once each asset has an ID, location and dated photos, the report mostly writes itself. Build three layers:
- 1A live map. Every asset as a pin. Click one and see its photos over time. Filter by funder, so each CSR partner sees only their project.
- 2Per-site pages. A page per village, school or plantation site: what was done, when, by whom, with the photos.
- 3A quarterly report filled from the data. Counts, survival or usage rates, before and after photos, and a list of exceptions. Generated from the records, not rebuilt by hand each quarter.
This also helps the funder's own obligations. When an independent agency arrives to assess the project, a structured record with locations and dates makes their job faster and your project easier to verify.
"A photo is not proof. A photo with a location, a time and an asset ID is."
Where evidence usually breaks.
- ✕Duplicate photos. The same good photo reused for three sites. Funders and auditors notice. Store a hash of each image and flag repeats automatically.
- ✕Missing GPS. Location turned off, or stripped by a forwarding app. Block saving without coordinates rather than discovering it at report time.
- ✕Spreadsheets at scale. Fine for 50 assets. At a few thousand, with photos as links and several people editing, rows go out of sync and nobody knows which version is right.
- ✕Photos lost on phones. A staff member leaves, or a phone breaks, and a season of evidence goes with it. Upload from the field the same day, to storage the organisation owns.
Off-the-shelf platform or a custom build?
Several CSR and monitoring platforms exist, and generic form tools with GPS capture are a sensible start. If your projects are standard (one type of asset, one or two funders, simple reporting), use one. Our NGO software guide gives the same advice: buy when a tool fits 80% of your workflow.
Build custom when your assets need long-lived records rather than one-off survey responses, when each funder wants their own view of shared data, or when field operations and reporting should run from the same system. That's where a tool like PlantationOS paid for itself: the care schedule and the evidence are the same records.
Checklist for your next CSR proposal.
- 01Define the asset and its ID format before the project starts.
- 02Promise a specific evidence set: geotagged, timestamped photo at handover, then at fixed intervals.
- 03State the visit schedule and who is responsible for each visit.
- 04Offer the funder a live map or dashboard link, not only a final PDF.
- 05Say how you'll handle failures: dead saplings, broken fixtures, and how they're replaced and recorded.
- 06Name where data is stored and confirm the NGO owns it.
- 07Agree the report format and frequency up front, so you build once and generate each quarter.
- 08Ask whether the project may need an independent impact assessment, and plan the data that assessor will want.
Who's telling you this.
OIAS is a Bengaluru studio. Our NGO practice builds donor systems, field tools and funder reporting, and OIAS Labs built the tree proof-of-life platform and PlantationOS described above. If a form tool will do the job for your project, we'll tell you that.
Book a free call → · See what we build for NGOs → · See OIAS Labs →
Prefer email? business@oias.in