Education Administration /Document processing live app field guide · 9 min

Enrolment Document Sorter

Brings enrolment processing from around 25 minutes per applicant to about 4.

docproc · sandbox · read-only

Open

FIG. 1

The live product. Open it to step through the full flow — every output is shown for a person to approve before anything happens.

How it would work

Reads the incoming enrolment packet, extracts the key fields from each document, checks them against the enrolment checklist, and surfaces the result — verified or flagged — for the enrolment officer to approve before any record is created.

Input 01

The enrolment packet

The bundle of documents a family submits at enrolment — birth certificate or proof of age, proof of residential address, Australian Immunisation Register (AIR) statement, and the signed enrolment application form. Year transfers also include the most recent school report.

Agent 02

Reads, extracts, checks

Reads each document in the packet, extracts the required fields — student name, date of birth, address, parent/guardian, immunisation status — with source attribution for each, and checks them against the school's enrolment checklist, surfacing any mismatch or missing item.

Output 03

A verdict, for the officer to act on

A checklist result — verified or flagged — with every extracted field and its source document laid out for the enrolment officer to review, correct if needed, and approve before any student record is created in the SMS.

Where it works well

It does the reading and checking on every packet, in full, and shows where each field came from.

At a school of 400–600 students the enrolment intake period produces dozens of packets in a short window — the AI processes each one in seconds and queues the result for the officer to confirm.
Best for the enrolment officer or school office manager handling a regular intake: Prep enrolments, mid-year transfers, year-level transitions.
The time recaptured goes back into the family conversation — explaining the school, answering questions, completing the welcome process — not into document reading.

The slow, invisible part of enrolment processing is not the decision — it is reading each document in the packet, pulling out five or six fields, and checking them against the checklist one by one. Done by hand it takes 15–25 minutes per applicant; it is the task most likely to get rushed when a family is waiting at the counter.

Where it works badly

It is confidently incomplete when the packet is incomplete — and a clean checklist result can mask a missing document.

Weak where documents are photocopied badly, handwritten in small print, or photographed at an angle — extraction confidence drops and the field needs the officer's eye.
The AIR statement check reads what the statement says; it cannot contact Medicare to verify the record is still current as of today.

The honest test

If you cannot say, right now, whether your school accepts a screenshot as proof of address or requires a full utility bill — this tool applies the checklist you give it, not the one in your head.

Submit a packet where the proof of address is a screenshot of a bank app that shows only a suburb, and the tool may extract an address — but it cannot confirm the address is current or that the document meets the school's standard. That is the trap.

What it doesn't do — and shouldn't

It reads and checks the documents. The enrolment officer creates the record. That boundary is deliberate.

WHAT IT DOES

Extracts each required field with the source document it was read from

Checks each field against the school's enrolment checklist and flags mismatches

Surfaces immunisation status as flagged when the AIR statement is not current

WHAT IT WON’T

Create or update the student record in the SMS

Verify documents with an external registry (Medicare, Births Deaths and Marriages)

Decide whether to accept an enrolment or exercise the school's discretion on placement

In Victoria, a government school's obligation to enrol children within its designated neighbourhood zone — and its discretion on out-of-zone applications — sits with the principal under the Education and Training Reform Act 2006. Immunisation requirements for school enrolment are set by state public health legislation, and non-compliance has specific follow-up obligations. The enrolment officer stays on the decision because the consequence — an incorrect record, a missed immunisation flag, an out-of-zone dispute — lands on the school, not the tool.

What your data has to look like

Legible documents in a consistent format, and a checklist the school has agreed and written down.

Typical readiness

across orgs we see, before the first job

Enrolment packets as digital files

Needs shaping

A written enrolment checklist the tool can check against

Needs shaping

Legible document scans

Usual weak point

A consistent enrolment form with named fields

Usual weak point

An SMS that can receive the extracted data

Needs shaping

The real first job

The checklist itself is usually the weak point — held in the office manager's head, applied differently by different staff, never written down as a formal document standard. Making the enrolment requirements explicit, agreed, and written is usually the real first job — larger and more valuable than the extraction layer on top. Once the checklist is fixed and the scanning standard is set, every packet after that is faster and right by default.

Right fit if…

Your school processes a regular intake of enrolment packets — Prep, transfers, year-level transitions

Families submit documents digitally, or you have a scanner at the counter

Your enrolment checklist is written down and consistently applied

Your enrolment officer spends 15–25 minutes per packet on document reading and checking

Walk away if…

Families hand in paper only and you have no way to digitise at point of receipt

Your enrolment requirements change frequently or vary by year level without a written standard

Most of your enrolments are complex discretionary decisions with no checklist to run against

You need a tool that creates the SMS record or contacts external registries for you

Open questions

The worried-buyer questions, answered straight

It can miss a mismatch if the document is unclear — which is exactly why nothing is written to the SMS on its say-so. It extracts each field, records which document it came from, and flags any mismatch or low-confidence read before the result reaches the enrolment officer. The officer reviews the checklist result, checks any flagged item, and approves before a record is created. The tool surfaces the extraction; the person stands behind it.

Partly, and the quality of the scan is the main variable. It works best when documents are clear digital PDFs or properly scanned — a phone photo taken at an angle, or a faded photocopy of a birth certificate, reduces extraction confidence and the officer needs to check the field by hand. Setting a minimum scanning standard at point of receipt — and telling families what format is accepted — is usually the first practical change, and it pays off on every packet after.

No. It removes the reading and the cross-checking — the 15–25 minutes per packet of pulling fields out of documents and running through the checklist — so the enrolment officer spends their time on the judgement: talking to the family, handling out-of-zone queries, managing the waiting list, and making the discretionary calls the principal delegates to them. The enrolment decision is still theirs. The time it frees goes back into the family-facing work.

The AIR statement needs to be the current issue from the Australian Immunisation Register. For primary school enrolment, a current Immunisation History Statement from the AIR must be provided — though unlike early childhood services, a child may still be enrolled even if the statement shows vaccinations are not up to date; the statement is required so the school can identify unvaccinated children during a disease outbreak. Requirements vary by state, year level, and service type, so the officer confirms the statement date and applies the school’s obligations before approving.

A child’s date of birth, address, and immunisation status are sensitive personal information protected under the applicable privacy legislation — for Victorian government schools, that is the Privacy and Data Protection Act 2014 (Vic), not the federal Privacy Act 1988 (which does not cover state government schools). Any deployment runs against your school’s own systems and data handling — the documents do not go to a shared pool. We scope where the data sits, who can see it, and how long it is retained as part of the build. The demo runs on entirely fabricated student records.

It flags when the AIR statement shows immunisations are not up to date and surfaces it for the enrolment officer to act on — it does not apply the state-specific rules about catch-up schedules, medical exemptions, or the circumstances under which a school must still enrol. Those rules differ by state and change periodically; the officer applies them. The tool raises the flag; the person makes the call.

What it takes to build

3–4 weeks · 4 phases

Reused from template~65%

Bespoke to this skin~35%

stack · Claude · document-extraction pipeline · review UI

What it would cost

Fixed scope, fixed price, fixed dates.

Bite-sized first piece

One contained change, low risk

Pilot build

Most builds land here

Embedded support

Scale on proof

Considering this for your school?

The honest place to start is a bite-sized first piece — one contained change, low risk. Tell us where the enrolment intake hurts; we'll play it back, scope it, and show you what's possible.

Book a call How we work