Independent Airtable prototype · Synthetic data
YPO OC Admissions
An Airtable admissions system modelled on a 20-step nonprofit membership workflow, built from a technical specification, with decision gates, ownership handoffs and exception queues.
From specification to working prototype
The specification defined a 20-step applicant journey, five business tables and four forms. I built a prototype that keeps the five tables and demonstrates the workflow's highest-risk controls, replacing live forms, email and applicant data with staged records and audit evidence.
It is an independent case study, not YPO Orange County's live system. Every applicant, email and decision is fictional; the interface is public and read-only, the forms are unpublished and the automations are off.
Applicants are the spine
- Applicants, Events, Members, Event Feedback and Site Visit Feedback are linked business tables.
- Two clearly labelled technical tables, Form Submissions and Workflow Log, handle matching, duplicate suppression and evidence.
- Applicant ID and Applicant Key are durable prefill targets, with normalised email as a secondary match check.
Gates you can see
- Green, Orange and Red decision paths.
- A three-event attendance gate, plus Board and Site Visit gates.
- Sequential onboarding that blocks payment before start and activation before confirmation.
Built for the people running it
The dashboard opens on a nine-applicant pipeline with status, owner, next step, gate result and exception queues, so a Chapter Manager or Membership Officer can orient before opening a record. The applicant profile groups the pipeline by status, with queues for each role.
QA evidence
Eleven checks pass, covering every decision path, each gate, the matching outcomes and the safety state. For production I recommend one prefilled Fillout link per applicant or reviewer that updates the intended Airtable record directly.