A hyperlocal reporter network, investigative newsroom, fact-checking team, community-media programme, membership publication and media funder each carries different workflows and risks. This playbook connects editorial work without turning judgement into automation.
| Handpumps dry, Dhamtari | Rekha? | unassigned 4d |
| Dhamtari pumps | dup? |
Five places, one story. Nobody can see the reply is still missing.
Many organisations combine two or three. Start with the closest match, then borrow only the parts that solve a real programme problem.
A distributed network finds, reports and follows stories rooted in local communities.
Teams pursue longer investigations using documents, datasets and collaborative review.
Teams receive claims, verify evidence and publish transparent ratings and corrections.
A publication combines editorial work with grants, memberships or audience revenue.
A funder supports outlets, fellows or projects and learns across a portfolio.
People learn reporting, audio, video or media literacy and publish with support.
Not sure which one you are? Bring one tracker and describe a normal week. The model usually becomes clear quickly.
These come up in almost every first conversation we have with media & journalism teams.
"The tips come to my personal WhatsApp."
Tips arrive all day and die in someone's phone. When an editor leaves, the tip history leaves with them.
"Our reporter got threats after the story. The desk heard a week later."
Safety lives in phone calls and WhatsApp. Nobody has a record of which assignments were risky or what we did when something went wrong.
"Our screenings don't exist in any report."
Hundreds watch a story in a panchayat hall, and analytics only counts the web. The offline audience vanishes.
"The funder asked for impact. We sent pageviews."
The collector's order lives in a reporter's memory. Before the annual report, we rebuild it in a panic.
Newsroom systems are a newer area for us. The building blocks are ones we've built for years: phone-based field reporting, prioritised queues, WhatsApp intake, restricted fields and many tools connected into one record.
A telecalling system that pulls students from their database and shares calls fairly across 10 to 15 telecallers. Live in four months.
Read the case study →The/Nudge Institute10+tools connected into one recordFuture Perfect runs admissions, payments and refunds, the learning platform, Zoom and WhatsApp through one system, with screens for trainers, telecallers and verifiers.
Read the case study →Recognise your programme? Tell us where the work gets stuck and we'll suggest a useful first version.
This is one operating model, not a template for every media & journalism organisation. Use it to see how everyday work, follow-up and management decisions can connect.
Stage 01 · Tips and pitches
Stringers in districts others ignore are the whole point. If you don't know who covers which block, in what language, the story budget is a wish list.
| ID | Story | District | Status |
|---|---|---|---|
| ST-2322 | Ration cuts | Bastar | Unassigned 3 days |
| ST-2325 | School meals claim | Raipur | Checker needed |
| ST-2327 | Mandi prices | Kanker | Pitch revised |
| ST-2318 | Handpumps dry | Dhamtari | Assigned today |
Stage 02 · Check and clear
Verification is the product. A wrong verdict or a missed legal flag costs more credibility than a year of good work earns.
| ID | Story | Verdict | Status |
|---|---|---|---|
| ST-2318 | Handpumps dry | Misleading | Reply pending |
| ST-2309 | Hospital beds claim | False | Second check |
| ST-2311 | Scholarship delay | Ground report | In legal |
| ST-2304 | Dam height claim | True | Cleared, 3 languages |
Stage 03 · Reach every channel
Much of your audience meets the story on a WhatsApp forward, on community radio or on a projector in the panchayat hall. Web analytics see a fraction of that.
| ID | Story | Channel | Status |
|---|---|---|---|
| ST-2296 | Ration cuts, part 1 | Community radio | Reach not logged |
| ST-2290 | Anganwadi rations | Village screening | Notes pending |
| ST-2304 | Dam height claim | Most viewed | |
| ST-2301 | Mandi prices | Web and partners | Republished 4 times |
Stage 04 · Prove what changed
Impact is a collector's order, a corrected figure, a claim retracted. It's rare and slow, and it has to be logged the week it happens or it's gone.
| ID | Story | Impact | Status |
|---|---|---|---|
| ST-2189 | Ration cuts | No follow-up logged | 90-day prompt missed |
| ST-2247 | Scholarship delay | Assembly question | Link unconfirmed |
| ST-2204 | Hospital beds claim | Figure corrected | Strong link |
| ST-2231 | Handpumps, Kurud block | Repair order issued | Evidence attached |
Choose modules around your newsroom or network. A grant-maker should not receive confidential source material, and a membership database should not shape editorial decisions.
Protect source identity, consent, documents, provenance and access history.
Move ideas through assignment, reporting, editing, legal review and publication.
Connect each claim to evidence, method, rating, reviewer and visible updates.
Track risk plans, incidents, equipment, contracts, fees and timely payment.
Manage applicants, milestones, funder separation, members, events and retention.
Keep versions, credits, licences, reuse terms, responses and policy or community impact.
Most AI projects stall because the records underneath are messy. So we work in a fixed order.
Every field has to earn its place by helping someone decide something. If nobody uses it, we don't collect it.
A system people avoid is worse than a spreadsheet. We design around shared phones, patchy signal and WhatsApp.
On clean, connected records, AI can read paperwork, draft reports and flag who needs attention. A person always checks.
Where you start depends on where you are. If your records are already in good shape, we can move to AI quickly. If they're in notebooks, we start there, and we don't start from zero.
Offline forms, local languages, links to government IDs and AI features are set up to suit each programme's needs and consent rules, so not every build includes all of them.
We picked the jobs that save media & journalism teams the most hours. Each starts with a problem we hear often, and each keeps a person in charge of the decision. How we think about AI →
“Reporters spend hours scrubbing through interviews in Bundeli or Awadhi to find the quote.”
Your team still decides: it runs on a private tool, and the reporter checks every quote against the audio.
“An official acts on our story and we only hear about it if the reporter happens to go back.”
Your team still decides: the standards editor confirms the link before it enters the impact log.
“We've covered the same village's water problem before, but nobody can find the old story.”
Your team still decides: the reporter re-checks any old fact before reusing it.
“Every video needs a title, thumbnail text, captions and a post for four platforms, and the editor writes them all at midnight.”
Your team still decides: the audience editor checks every version against the story before it goes out.
“We don't know which beats and formats our audience actually stays for.”
Your team still decides: editors set the story budget, so slow accountability work keeps its place.
“Funder reports get rebuilt from memory and old WhatsApp chats every year.”
Your team still decides: the editor-in-chief edits every contribution claim.
Your sources trust you with their safety. These lines don't move, whoever's asking.
Pitches taken up, deadlines, payment status and how their story did in their own district.
Past verdicts on similar claims, the evidence trail, and which of their own verdicts got challenged.
Pitches waiting, claims trending, reporter workload and districts that have gone quiet.
Web, WhatsApp, radio and screenings against one Story ID, with the tips each story brought in.
Impact events with evidence attached, and an honest rating of how much the story caused.
A story that ran before a policy changed didn't necessarily cause it. Every impact event carries a contribution rating from your standards editor, and weak links get reported as weak.
Funders notice overclaiming. They notice honesty too.Most systems launch in three to four months. The timeline moves with the number of programmes and roles, how messy the old data is, and how many tools need connecting.
Tell us where the work gets stuck today. Spreadsheets, notebooks, WhatsApp groups, all of it.
You show us how the programme runs. We'll tell you straight if you need a new system, a better workflow or nothing at all.
We map how your programme works, talk to the people who'll use it, review the tools you use today and hand you a System Blueprint, a clear plan of what we'll build.
Working screens every 2 to 4 weeks, tested by your field team in your own terms. We clean up your old spreadsheets and move them across.
Field training and launch, then 30 to 60 days of close support. After that, the system keeps changing as your programmes do.
We connect to YouTube and Facebook analytics, WhatsApp tiplines, your CMS or paywall, Google Drive rushes folders and payment tools for stringers, rather than replacing what already works. Zoho licences sit in your organisation's name, and everything exports whenever you want it.
The questions your finance head and IT lead will ask, answered before the call.
Zoho licences are bought in your organisation's name and hosted in the Zoho data centre region you choose, including India. We work inside your account.
Every record exports to Excel or CSV whenever you want, including the day you stop working with us. You're not locked in to us for support either.
Each person sees only the records their role needs. Source details and reporter locations are restricted field by field, and never go into any AI tool.
Edits are logged with who made them and when, so an audit or a funder query doesn't start from memory.
Consent is recorded for each purpose, and we agree up front how long data is kept and when it's deleted. ZolaShield, our DPDP platform, shows where you stand.
AI features run on your records under your account's controls. Beneficiary records never go into public AI tools.
We’ll map what your team does now, identify the smallest useful first version and show where follow-up, learning and reporting can share the same information, without forcing your programme into a generic template.
If budget is tight, ask about the Built for Impact Programme, which gives eligible nonprofits free Zoho credits.
The same approach, shaped to each kind of work.
