The trip, the evening, the building work
A project is anything the school runs that has a date, a budget, people attached and something to do before it: a trip, a parent evening, a fundraiser, a repair.
Participants, costs, consent forms, the checklist and the photo album all hang off the same record, so the trip that happened in March can still be answered for in June. Tasks can link to any record in the system — a family, a class, a bus, an application — so "chase this" has a place to live.
For the office
What a secretary, a bursar or a head of year can do with it.
- Trips, events, parent evenings, fundraisers and building work
- Who is going, what it costs against the budget, and what is still to do
- Consent collected as a form, before the day
- Photo albums visible only to the families whose children were there
- Parent evening booking, with slots parents choose themselves
For whoever has to approve it
Where the data sits, who can read it, and what it connects to.
- A task can point at any record type through one table, so a new kind is a line rather than a migration
- Album visibility is derived from participation, not from a list someone maintains
Questions we are asked
- Can parents book their own parent-evening slot?
- Yes, within the window you open, and the teacher's list fills itself in.
- Are trip costs billed automatically?
- Yes — a charge per participating child, on their family's ledger, with the discount rules applied.
See it with your own school's data
Sixty days free, no card up front — or open a ready-made demo school and click around it first.