Every child, one record, one screen.
The profile owns no data at all.
It composes what admissions, attendance, pastoral, inclusion and health already hold, under one permission model.
Faces, not numbers
Photograph, year group, age, admission number and status on every card, because staff recognise children by face.
Grouped as you need it
By year group, by key stage or not at all. Grid for recognition, list for volume work.
One search box
Name, guardian email, telephone or admission number. The four things a parent on the telephone can actually tell you.
Nothing is ever lost
Superseded records are retained as history rather than deleted, and purges are governed actions with reasons.
Faces, not reference numbers.
A photograph, year group, age, admission number and enrolment status on every card. Staff recognise children by face, so the record is built the way a teacher thinks rather than the way a database does. Grid for recognition, list for volume work, and enrolled, prospective and withdrawn as filters rather than separate screens.
- One search box answering to name, guardian email, telephone or admission number
- Grouping by year group, by key stage, or not at all
- Every superseded document and entry retained as history rather than deleted
The profile owns no data at all.
It composes what other departments already hold. Attendance comes from attendance, provision comes from inclusion, contacts come from admissions and behaviour comes from pastoral. That is why nothing on the screen can be out of date with the system it came from, and why nobody is asked to update the same fact twice.
Full functionality
Every workflow below is specified with its trigger, its actor, the screen it happens on, the step sequence, the permissions and the edge cases.
01The composed profile
One screen holds the child. Every panel on it is owned by the department that maintains it, and shown only to a person whose role, scope, clearance and purpose all permit it.
- Identity, photograph, year group, form, house and admission number.
- Attendance summary and trend, live from the register rather than from a nightly job.
- Behaviour, rewards and the last three contacts home.
- Provision, adjustments and examination arrangements where they apply.
02Guardians and family structure
- Multiple guardians with distinct parental responsibility, contact priority, and collection rights.
- Siblings linked across year groups, so a message to a family is one message.
- Separated families handled properly: who receives reports, who may collect, who must not be contacted.
- Emergency contacts, ranked, with the reason a rank exists.
03Pastoral care and behaviour
- Positive and negative events logged from the lesson, the corridor, the bus and the event.
- House points and rewards that a student can see the same day, because delayed recognition is not recognition.
- Escalation paths with named owners rather than a note asking somebody to keep an eye on it.
- Pattern detection across attendance, behaviour and attainment, surfaced to the pastoral lead rather than waiting for a report to be run.
04Inclusion and provision
- Provision plans, adjustments and review cycles attached to the child rather than to a folder.
- Adjustments follow the child into the register, the seating plan, the report and examination arrangements.
- Impact tracked against the provision, so review meetings argue about evidence rather than impressions.
- External agency involvement recorded with its own clearance level.
05Safeguarding
Safeguarding is a restricted class of data, not a module. A concern raised in a lesson, on a bus, at an event or by a parent enters the same protected record through whichever door it came in.
- Visible only to named clearance holders, with every read logged.
- Chronology assembled automatically, in order, with author and timestamp.
- Never deleted, never overwritten, and never exportable by role alone.
- Separate from behaviour, because conflating the two is how schools lose cases.
06Health and medical
- Allergies and conditions surfaced where they matter: the canteen scanner, the trip list, the cover sheet.
- Medication administration logged with two-person confirmation where policy requires it.
- Immunisation and medical documents with expiry tracking.
- Nurse and first aid visits recorded against the child and visible to the pastoral lead.
07Documents and history
- Every document, photograph and record entry that is replaced or withdrawn is retained as history rather than deleted.
- Administrative purges are a governed action with a reason, not a delete button.
- Full chronology per child, filterable by department and by author.
- Export is a separate permission from read, and it is logged.
08Transitions and leavers
- Year group rollover as a governed batch with a preview and a reversal path.
- Transfer certificates and leaver files generated from the record.
- Alumnus is a state of the same record, not a new one, so a leaver's history stays intact.
- Re-enrolment recognises a returning family rather than creating a duplicate.
More of the platform
A register a teacher finishes in forty seconds, with statutory reporting, absence follow-up and roll call already computed.
Curriculum design, timetable generation, gradebook, reporting and the cover engine that reads all three.
Recruitment, contracts, visas, leave, appraisal and CPD on the same record that grants the person their access.
See it running on real data.
A working demonstration on a live database, walked through by the people who built it. Forty minutes, no slide deck.