How Brighton Park Neighborhood Council keeps a family’s whole history in one place
Challenge
Programs take applications on paper, over email and through whatever form was built for the season — so a family that has been through three programs has a history spread across three spreadsheets and somebody’s inbox. Answering “what have we already asked these people for?” meant asking around.
Solution
One object per program, with the fields the intake form asks for, and the form feeding it directly. Email is written next to the record rather than in a separate tab, sequences chase the documents that are still missing, and files go out as links instead of attachments.
Results
Every application arrives as a record, with the file and the email thread attached to it.
A family’s programs, forms and messages read as one history rather than four.
Follow-up is a sequence that stops on its own when somebody replies.
Brighton Park Neighborhood Council runs programs that the same families come back to — a young person in an after-school program this year is in a summer one next year, and their household has probably filled in a form for something else besides. The work is relational, and the record-keeping was not.
The problem was never the forms
Each program could get a form built for it in an afternoon. What it could not get was a place where the answers accumulated: the form filled a sheet, the sheet went in a folder, and the next program started its own. Nobody had decided this — it is just what happens when the tool ends at the submission.
So the questions that mattered were the ones nobody could answer quickly:
- Has this family already given us this document?
- Which programs has this young person been through?
- Who was the last person here to email them, and what did they say?
An object per program, and one record per person
The setup is deliberately plain. Each program is an object with the fields its intake form asks for, and the form writes straight into it — no export step, so there is no version of the data that is a week behind. A person who applies to a second program is linked to the record that already exists rather than typed in again.
That is the whole trick, and it is not a clever one: the history is only readable if the second application knows about the first.
Following up without a mail merge
Chasing a missing document used to be a spreadsheet, a filter, and an afternoon. It is now a sequence: a first message, a wait, a reminder, and an exit the moment somebody replies — so a family who answers on day one does not get the day-four nudge. Staff write from beside the record, with the family's own answers on screen, which is what stops the reminders reading like a mailshot.
Files that go out without an account
Signed forms, program calendars, letters for a school — these leave as a link rather than as an attachment, and the comments come back onto the record they belong to. The person opening it does not make an account to read a PDF, which for the families this work serves is the difference between a document being read and a document being ignored.