Grant-makers, residencies, arts educators, traditional training programmes, production houses, venues and heritage archives all organise work differently. This playbook starts from that model and connects administration without making artists work for the database.
| Anjali Munda | Theatre | Hindi audio? |
| A. Munda | theatre | 2021 too?? |
Five places, one artist. Nobody can see her project has stalled.
Many organisations combine two or three. Start with the closest match, then borrow only the parts that solve a real programme problem.
Artists or organisations apply, are selected and deliver supported work over milestones.
Artists receive time, space, mentoring and peer learning over a defined period.
Artist-educators deliver sustained creative learning in schools or communities.
Gurus, practitioners and learners sustain embodied knowledge across generations.
Creative teams develop, rehearse, produce and tour performances or exhibitions.
Organisations programme spaces, welcome audiences and preserve cultural material.
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 arts & culture teams.
"Every year's open call is a new Google Form."
Different fields each cycle. After five years, nobody can say whether the call is reaching new artists.
"The funder asked what happened to the 2019 cohort."
Answering means a week of digging through inboxes, old reports and whoever still has the artists' numbers.
"We trained two thousand teachers. We can't say how many teach the arts period."
Training attendance is in one sheet and classroom visits are in WhatsApp photos. The state asks for fidelity and we send estimates.
"It's called final_final_2.mp4 and nobody knows who's in it."
Recordings sit on a hard drive with no credits or rights. Five years on, you can't use them.
We haven't published an arts case study yet. For programmes in schools, the closest work is Compass for Simple Education Foundation (teacher training and classroom observations at state scale) and MukkaMaar (trainer-led sessions in schools).
Compass MIS runs state-wide teacher training, classroom observations and multilingual assessments. The first week of a new-state pilot logged 2 million interactions.
Read the case study →MukkaMaar3,300+girls in school programmesStudents, trainers and sessions in one system, with location-stamped trainer attendance, a restricted case module for abuse disclosures and donor reports.
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 arts & culture organisation. Use it to see how everyday work, follow-up and management decisions can connect.
Stage 01 · Open call & jury
Open calls tend to reward artists who already write proposals in English. If you don't track who applies, from where and in what language, you can't tell whether the call is open.
| ID | Artist | Region | Status |
|---|---|---|---|
| AR-0497 | Thenmozhi R. | Madurai | Scores missing |
| AR-0512 | Salim Qureshi | Bhopal | Translation check |
| AR-0381 | Anjali Munda | Ranchi | Shortlisted |
| AR-0455 | Kiran D'Souza | Mumbai | Ineligible, reason sent |
Stage 02 · Residency & mentoring
Creative work doesn't move in straight lines. You still need to know tranches went out, mentors showed up and projects are alive, without turning artists into form-fillers.
| ID | Artist | Milestone | Status |
|---|---|---|---|
| AR-0381 | Anjali Munda | Script draft | Tranche 2 overdue |
| AR-0419 | Tashi Dolma | Research trip | No session in 60 days |
| AR-0402 | Meghna Sen | Studio showing | Check-in next week |
| AR-0366 | Imran Sheikh | First draft | Tranche released |
Stage 03 · Shows & audiences
Festival numbers are easy to inflate and hard to read. Ticketing, free event headcounts and school sessions have to sit together, or you'll only see your paying regulars.
| ID | Event | Venue | Status |
|---|---|---|---|
| EV-0233 | Jal Katha premiere | Ranchi | Open 12 days |
| EV-0219 | Folk music evening | Bhopal | Headcount only |
| EV-0228 | School session | Govt HS, Khunti | Return visit asked |
| EV-0241 | Exhibition opening | Kolkata | Closed |
Stage 04 · Archive & alumni
The archive is often a hard drive in a drawer. Alumni careers are the long-term evidence, and they only show up if you ask every year and link the answers to the original grant.
| ID | Artist | Cohort | Status |
|---|---|---|---|
| AR-0147 | Devraj Gond | 2020 | No reply in 2 years |
| AR-0163 | Leela Iyer | 2021 | Rights pending |
| AR-0112 | Ruksana Bano | 2019 | Commission, 2026 |
| AR-0129 | Arun Pillai | 2019 | Teaching and practising |
Choose modules around the relationship you hold with artists and communities. Collect only what improves support, accountability, rights or access, not data for its own sake.
Manage calls, eligibility, review, conflicts, decisions, agreements, milestones and tranches.
Keep ownership, permissions, licences, credit lines, reuse and payments with each work.
Coordinate people, tasks, rehearsal, logistics, technical needs, venues and settlements.
Follow cohorts, sessions, mentoring, observation, creative evidence and alumni pathways.
Plan programmes, access, ticketing or free attendance, feedback and repeat engagement.
Catalogue context and rights, or connect makers, products, orders, sales and payments.
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 arts & culture 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 →
“Our artist educators hate filling forms, so session reflections never get written.”
Your team still decides: it runs privately, with consent, and the programme manager reads flagged notes in full.
“We collect hundreds of reflections from children and teachers and nobody has time to read them.”
Your team still decides: the director reads every safeguarding, access or safety comment directly.
“Thousands of artworks come in on WhatsApp and we can't tell which school or activity they belong to.”
Your team still decides: a coordinator checks consent before anything is shown publicly.
“Great artists apply in Hindi, Punjabi or by voice note, and our jurors can't all read them.”
Your team still decides: only with the applicant's consent, and a native-language reader reviews every shortlisted translation.
“Our drive is full of performance photos and videos with no names, dates or consent status.”
Your team still decides: the archivist confirms every tag, and children are never identified by face.
“Cohort reports take a month to pull together from surveys, logs and photos.”
Your team still decides: the director edits any claim about your role in a child's or artist's growth.
An artist's work and voice are theirs. These lines don't move, whoever's asking.
Their tranche schedule, plus audience numbers and feedback they can use in their own funding applications.
Sessions logged, the next check-in date and what other mentors have noted.
Milestones, check-ins due and tranches waiting on finance, for every grantee.
Attendance, first-timers and school sessions by venue and format, free events included.
Alumni careers by cohort and discipline, linked back to the original grant.
If only the alumni who are doing well answer the survey, your practising rate looks better than your programme is. We report the response rate next to every alumni number.
Funders notice. It's the kind of honesty that gets you renewed.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 your application forms, ticketing and box office, WhatsApp and IVRS for teachers, and your archive or media library, 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. Parental consent is recorded before any child's image or video is stored.
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.
