School admissions and enrollment, without the paper chase
Between an application and the first day there are references, reports, birth certificates, medical and consent forms, deposits and contracts to collect. We build a workflow that checks each application for missing items, reminds families, books assessments and interviews, tracks offers and acceptances and collects enrollment forms, then hands a clean record to your SIS or MIS. Admissions staff decide every offer. A typical build costs $1,000 to $2,500 and takes about four to five weeks.
The problem
Why admissions season turns into a paper chase
Admissions teams spend weeks each year chasing documents: school reports, references, proof of address, medical forms and signed contracts. Families send them by email, upload some and post others, and staff keep track in a spreadsheet.
Offer season is the hardest. Deadlines for acceptance, deposits and forms all fall together, and a missed reply can mean a place held for someone who has gone elsewhere, or a family who never heard back.
What we build
What our school admissions automation includes
Application checklist
Each application checked against the items your process requires, with what is missing listed per family.
Document reminders
Polite reminders with a secure upload link, then a task for admissions staff.
Assessment and interview booking
Families pick from available slots, with reminders and staff calendars updated.
Offer and acceptance tracking
Offers, acceptance deadlines and deposits tracked, with reminders before deadlines and a list of who has not replied.
Enrollment forms
Medical, consent and contact forms sent after acceptance and chased before the start date.
Handover to SIS or MIS
A clean new-student record prepared for your SIS or MIS through its supported route, or a tidy file for staff to import.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Application received
A new application starts the checklist.
-
02
Automated
Missing items chased
Families get reminders with an upload link until items arrive.
-
03
Automated
Assessments booked
Families book slots and get reminders.
-
04
Staff review
Admissions reviews
Staff check documents and prepare the file for decision.
-
05
Head of school or programme lead decides
Offer decision
Who is offered a place, and any bursary or support, is decided by the head and admissions panel.
How it behaves
How the admissions and enrollment workflow behaves
What families see
- A clear list of what is still needed
- A secure link to upload from a phone
- Reminders before deadlines and booking links for assessments
What admissions staff see
- A checklist per application with missing items
- Offer and acceptance deadlines in one view
- Enrollment forms complete before the start date
What the automation does
- Checks applications for missing items
- Sends reminders and books slots
- Never scores, ranks or decides on applicants
Edge cases and fallbacks
- Family uploads the wrong document
- Flagged for staff; the item stays open.
- Separated parents both apply
- Both contacts recorded and flagged for staff to confirm arrangements.
- Acceptance deadline passes
- Admissions is alerted; nothing is withdrawn automatically.
- Upload tool or n8n outage
- Families can still email documents and staff are alerted.
Architecture
Admissions and enrollment workflow at a glance.
- Input
- Logic and services
- Output
- Data
- People
How it flows
- 1 A new application starts a checklist of the documents your process requires.
- 2 Families get reminders and a secure upload link; uploads are filed against the application.
- 3 Admissions staff review complete files, and the panel decides offers.
- 4 After acceptance, enrollment forms are collected and a clean record goes to the SIS or MIS.
Project planner
How the project runs, phase by phase.
Admissions documents, offers & enrollment project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Application process, required documents, deadlines, SIS or MIS and storage.
-
02
Design
2 to 3 days
Checklist, reminder timing, upload rules, offer tracking and handover format.
-
03
Build
About 2 weeks
Checklist, uploads, booking, offer tracking, enrollment forms and handover.
-
04
Shadow run
About 1 week
Checklists built for live applications while staff chase as usual.
-
05
Launch
1 to 2 days
Switch on, ideally before the main application deadline.
-
06
Support
Ongoing
Changes for the next intake and new forms.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Process, documents, deadlines and handover.
$200 – $400
-
Build
Checklist, uploads, booking, offers and forms.
$500 – $1,300
-
Integrations
CRM, storage, calendar and SIS handover.
$150 – $400
-
Testing and shadow run
Live applications compared with staff tracking.
$100 – $250
-
Launch and training
Switch-on and admissions walkthrough.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Writing new students straight into some SIS platforms needs an approved route; if so, we quote it separately. Form, storage and n8n costs are billed to you directly.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Form and storage tools: Your form provider and Microsoft 365 or Google Workspace plans.
- n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
US: FERPA once a student enrolls
FERPA applies to institutions receiving funds from Department of Education programs. Outside providers handling education records must be under the school's direct control for their use and maintenance.
Source: www.govinfo.govEU AI Act: no AI admissions decisions
AI systems used to determine access or admission to education are listed as high-risk in Annex III, so our workflows never score or rank applicants.
Source: artificialintelligenceact.euUK: children's data
UK GDPR Article 8 sets 13 as the age at which a child can consent to online services; below that, a parent consents, so admissions forms are completed by parents.
Source: www.legislation.gov.ukFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Admissions documents, offers & enrollment questions, answered.
It is a workflow on top of the tools you have: forms, CRM, storage and SIS. If you already use admissions software, we connect to it and add the chasing and tracking it lacks.
Never. It checks documents are present and keeps deadlines visible. The admissions panel and head decide offers, and AI is not used to score or rank applicants.
Yes, through a secure link that accepts photos and PDFs and files each item against the application.
State school admissions often run through local authority or district systems. We can automate the school-side admin around them, such as tours, forms and enrollment, where those systems allow.
Through Wonde or OneRoster where your setup supports it, your SIS import, or a clean file for staff to import. We confirm the route before quoting.
Applications complete by the deadline, time spent chasing documents, offers answered on time and enrollment forms complete before the first day.
Free 20-minute call
Want this for your schools & training?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for schools & training
All servicesEducation CRM & enquiry pipeline
Every family or learner enquiry from web, phone, open days and social in one education CRM, with tour bookings, polite follow-ups and a weekly view of enquiries, visits and applications by source.
From $1,000 · About 4 weeks Details
AI assistant for parents & learners
An AI assistant on your website and help inbox that answers term dates, fees, uniform, transport, course and policy questions from your approved information, in several languages, and passes anything personal or sensitive to staff.
From $2,500 · About 5 to 8 weeks Details
Attendance alerts & parent communications
Same-day absence messages to parents from your MIS or SIS, replies logged for the attendance officer, trip and payment reminders, and routine notices sent in each family's preferred language and channel.
From $1,000 · About 4 weeks Details