One record per student, not one per department

A parent rings on Wednesday and asks why their child was marked absent on Tuesday afternoon.

In most schools, answering that properly means opening the register, then the timetable to see which period it was, then the notes to see whether anyone logged a reason, then the message thread in case a parent already told somebody. Four places, and the answer is only trustworthy if all four agree.

They usually do agree. That is not the point. The point is that you cannot know they agree without checking, and the checking is the work.

Why schools end up here

Nobody chooses this. It accumulates.

Attendance starts in a register because attendance has always been in a register. Marks go in a spreadsheet because the person who set up marking preferred spreadsheets. Safeguarding notes end up somewhere restricted because they should be restricted. Parent messages live in whichever app the parents already use, which in this region is usually WhatsApp.

Each of those decisions was correct on the day it was made. The cost only appears later, at the join, and the join is where nobody is responsible.

This is also why adding another tool rarely helps. A better attendance app still leaves you reconciling attendance against everything else. Most schools running three disconnected systems, an information system, a safeguarding tool and something for HR, are not badly organised. They bought three sensible things.

What changes with one record

When attendance, assessment, notes and contact details hang off the same student, the four-file question becomes one screen. That is the entire benefit, and it is worth stating plainly rather than dressing up.

A few specific things follow from it.

Attendance is marked period by period, so "absent on Tuesday" resolves to a period and a subject rather than to a day. A pattern like repeated Monday lateness across consecutive weeks is visible without anyone building a report to look for it.

Reporting runs as a cycle with separate deadlines for teachers and senior leadership, and you can see who has actually finished rather than emailing to ask.

The whole academic year sits on one calendar, August to July, rather than one calendar per department. The daily bulletin goes to everyone from the same place, which is the unglamorous half of coordination and the half that usually happens in a group chat.

None of that is clever. It is what stops being hard when there is one record instead of several.

The part that is genuinely a trade-off

Moving to one record means the records have to be right, and they are not right today. Nobody's are.

Two students with slightly different spellings of the same name, a leaver who was never marked as a leaver, three years of marks in a format that made sense to whoever built it. All of that surfaces during import, and it surfaces as your problem even though it was not caused by the software you are moving to. Any vendor who tells you the migration is effortless has either not looked at your data or is not the one who will be doing it.

We would rather do that work with you than hand over a template and wish you luck. Tell us what your current export looks like, without student names or other personal data, and we will explain the usual mapping questions before you commit to anything.

What First IMS actually is

Eleven modules on one student record. Attendance, assessment, reporting, NEST safeguarding, timetable, yearly calendar, HR, invoicing, reception, seating plans and the dashboard a teacher opens first. Enable only the modules your school uses, so each role sees a focused workspace. Module availability depends on the selected plan.

Published First IMS rates are shown on the pricing page rather than quoted after a call.

There is no AI in it today, and when there is, it will be on the record and it will not involve pasting your student list into somebody else's chatbot.