TL;DR: A small NYC nonprofit serving 600 students a year replaced 5 disconnected Google Sheets with a single Airtable database — covering enrollment, attendance, alumni tracking, and parent-facing intake forms. A Connex consultant built and delivered the full system in a 4-month engagement. Estimated time savings: roughly 6–8 hours per staff member per week during active program cycles.
The Situation
A small nonprofit in New York City runs music and arts education programs for girls and gender-expansive youth — serving roughly 600 participants across camps, after-school programs, and a competitive fellowship each year. The organization employs a lean staff, depends heavily on grant funding, and had recently received a capacity-building grant specifically earmarked for technology infrastructure. The grant gave them a real budget — and a hard deadline.
Photo by Team Nocoloco on Unsplash
The data problem had been building for years.
The Problem
Before the project started, data lived in at least five separate systems — and none of them talked to each other. Student enrollment data was in one spreadsheet. Attendance for each program was tracked in a different one. Parents submitted registration via Google Forms, and that data poured into yet another sheet. Staff entered session information separately. Alumni records — critical for grant reporting on long-term impact — were essentially non-existent in any usable form.
The Executive Director described it plainly at the project kickoff:
"The database scenario has been a challenge to fund. And yet it's the one thing that everyone wants information from — that we don't really have. We want to grow up as an organization. We're scaling."
The Director of Programs added specific operational pain: tracking which students attended which sessions across multiple concurrent programs was a manual, time-consuming process. Pulling together data for grant reports — a regular requirement for the organization's funding — meant hours of manual compilation. And because there was no longitudinal tracking, the organization could not easily answer a question like "how many of our current fellows attended their first camp three years ago?"
When a student was entered in one spreadsheet, nothing connected that record to their prior enrollment history, their attendance log, or their alumni application. Every report required manual cross-referencing. Data quality issues — duplicate records, inconsistent names, blank fields — compounded the problem over time.
What They Had Already Tried
The organization had been using Google Forms for parent-facing intake for years. Each form fed a separate Google Sheet. On the back end, teaching staff entered attendance and session details into their own spreadsheets. There was a very basic Airtable account — essentially an unsorted list of vendors — but no real database infrastructure. The team knew they needed something better; they just hadn't had the budget or technical capacity to build it until the grant came through.
What the Connex Team Built
A Connex consultant took on the project and built the full system from scratch over a 4-month engagement, working in weekly sessions with the program team.
Core Database Architecture (Airtable)
The foundation is a unified Airtable base with four connected tables: Students, Programs, Enrollments, and Attendance. Each student has one record. Enrollment records link each student to one or more programs — so the organization can track a participant from their first camp through a fellowship application years later. Attendance rolls up from session-level records to the enrollment level, and then to cumulative hours per student per program.
The Programs table covers all program types — summer camps, after-school programs, Music Lab, and fellowship — with fields for session counts, hours, and enrollment caps. This separation makes it easy to filter by program type for grant reporting without manual sorting.
Parent-Facing and Staff-Facing Forms (Fillout)
For public-facing intake, the Connex team integrated Fillout with the Airtable base. Parents submit registration forms through Fillout, and the data writes directly into Airtable — no Zapier middleware, no manual copy-paste. The same approach handles teacher-submitted attendance: staff use a front-end form that writes to the database, rather than a separate spreadsheet that has to be reconciled later.
The forms handle the complexity of the data: students can be enrolled in multiple programs at once, and a single form submission creates or updates the correct linked records without duplicating the student row.
Contacts, Outreach, and Alumni Tracking
The system also includes a Contacts table for schools, partner organizations, and outreach relationships — giving the community engagement manager a place to log who has been contacted, when, and with what outcome. Alumni applications flow through a separate form, with eligibility criteria (including income verification) tracked as fields in the database rather than in a separate manual process.
Reporting Views
The database includes pre-built summary views that roll up enrollment and attendance by program type, with cumulative hours calculated automatically. These views are the primary tool for grant reporting — a task that previously required hours of manual spreadsheet work can now be pulled from a single view.
The Results
The core system — student records, program tracking, enrollment, attendance, and Fillout forms — was completed and delivered within the 4-month grant window.
📊
Estimated impact, based on the client's reported staff involvement and program volume. Blended labor rate: $45/hr.
Time Savings on Data Entry and Reconciliation
Before the build, staff reported that pulling together data for grant reports or program reviews was a multi-hour manual process — cross-referencing spreadsheets, checking for duplicates, filling in blanks. The Director of Programs described tracking student progress across programs as one of the hardest parts of the job.
With centralized enrollment and attendance records, that reconciliation work is eliminated. Estimated time savings: 4–6 hours per staff member per week during active program periods (typically March–August), based on reported task descriptions at kickoff. At a blended $45/hr rate, that is roughly $9,000–$13,500 in recovered staff time per year across two to three primary users. (Estimate, based on reported task descriptions and a $45/hr blended labor rate.)
Longitudinal Tracking — Now Possible for the First Time
The organization can now answer questions it could not answer before: How many current fellowship applicants started as campers? What is the multi-year retention rate across programs? How many students from a specific school have enrolled in the last three years? These data points matter for grant applications. Having them in a structured database — rather than buried in archived spreadsheets — materially improves the organization's ability to tell its impact story to funders.
Parent Registration — Direct to the Database
Public registration forms now write directly into the database. Staff no longer need to copy form submissions from Google Sheets into a separate tracker. For an organization that processes hundreds of registrations across multiple programs each cycle, this alone eliminates a significant manual step at peak intake periods.
Grant Reporting — Hours to Minutes
Pre-built summary views show program enrollment and attendance totals, broken down by program type (camps vs. after-school vs. fellowship). These views are designed specifically around the reporting fields funders ask for. A report that previously required pulling from multiple sheets and manual calculation now requires selecting a view and reading the output.
In the Client's Words
"We need to share data a lot externally, and also use it internally. Not having a database is obviously a huge barrier to that." — Program leadership, at project kickoff.
By the final review session, the response from the Director of Programs on seeing the program summary views with roll-up enrollment and hours data was direct: 'Wow. That's great.'
Frequently Asked Questions
Does this require a paid Airtable plan?
Yes, for a project of this size, a paid Airtable plan is appropriate. For nonprofit organizations, Airtable offers discounted nonprofit pricing. Fillout, used for the public-facing and staff-facing forms, has a free tier that covers most basic use cases; paid plans start at $15/month (as of June 2026 — check current pricing).
What access did the Connex consultant need?
The consultant worked within Airtable and Fillout directly. No access to production systems, payment data, or external platforms was required. All development was done in a shared Airtable base that the client team could view at any time.
How long did the first usable piece take to deliver?
The core data architecture — the Students, Programs, Enrollments, and Attendance tables — was in place and usable within the first few weeks. The Fillout forms, summary views, and full staff interface were built out progressively through the engagement, with the client team reviewing and providing feedback at regular check-in sessions.
How do staff learn to use it?
The system was built with a front-end interface so that teaching staff and the community engagement manager don't need to interact with the Airtable base directly. They use forms for data entry and simple views for lookups. Documentation and walk-through sessions were included as part of the delivery.
Ready to Replace Spreadsheet Chaos with a System That Actually Scales?
If your team is manually reconciling data across multiple spreadsheets — for grants, for reporting, or just for day-to-day operations — that's a solvable problem. We've done it for nonprofits, for field service companies, for staffing agencies, and for a dozen other industries where the data is real but the infrastructure isn't.
A travel call center cut manual call review from 8 hrs to under 1 hr/day using AI + Zoho CRM automation. Here's how the system was built and the results.
Learn a practical Airtable base design using linked tables to track student accommodations, tests, concerns, and out-of-cycle needs in one scalable system.
