Term-time admin that does not take a term to finish
Enrolment, consent, device provisioning and parent communication all peak in the same fortnight. Flomation takes the repeatable parts, so a small team can absorb the peak without hiring for it.
- Best for
- Schools, trusts, colleges and universities
- Deployment
- Cloud or self-hosted
- Forms
- Mobile, accessible, no login needed
Everything happens at once, every year
The work is predictable and seasonal, which is exactly the shape of problem that automation is good at and that manual process handles worst.
- The same fortnight brings enrolment, consent, accounts, devices and timetables together.
- The same details are collected three times, on three different forms, by three different people.
- Parents and students expect to do it on a phone, in the evening, without an account.
- There is no automation budget and no team to spend it, so tools have to be free to start.
- Safeguarding and data protection expectations apply just as firmly to the admin.
Collect it once, use it everywhere
One good form at the front, feeding a flow that updates everything behind it, replaces most of the retyping the season generates.
Forms that work on a phone
Multi-page, conditional, accessible forms that need no login, can take a payment, and can be answered in English or Welsh from the same link.
Accounts and devices in order
Create the accounts, groups and licences a new student or member of staff needs, in sequence, and remove them again when they leave.
Chasing that chases itself
Send the reminder, then the follow-up, then the escalation, and stop the moment the form is completed, without anyone maintaining a list.
Where schools and trusts usually start
The seasonal work, automated once, reused every year.
- 01Enrolment and consentOne form collects the details and the consents, validates them as they are entered, and files them where they need to be.
- 02Student and staff accountsProvision directory accounts, email, groups and licences from the enrolment data rather than from a second spreadsheet.
- 03Trips, payments and permissionsTake the permission and the payment together, and give the trip organiser a live list rather than a folder of replies.
- 04Returns and reportingAssemble recurring returns from the systems that already hold the data, on the schedule the deadline demands.
The practical questions
Usually asked by the one person who looks after IT as part of another job.
- Start free, and stay free while the volumes are small.
- Self-host if your data protection position calls for it, or use the cloud if it does not.
- Forms need no account, which keeps parents out of a password reset queue.
- Every run is recorded, so a question about a submission has an answer.
See it built
Worked examples, with the flow and the outcome laid out end to end.
Build it once, run it every September
The enrolment flow you build this year is the one you run next year, and the year after, without rebuilding the spreadsheet each time.
Get started