The attendance register is filled out in the morning, amidst jackets to hang and families in a hurry. It serves to know who is here today, how many enrolled children are in the section, and whether the numerical ratio holds. Then six months pass, and someone asks for an account of a Tuesday in February.
It could be an entity verifying the declared data for a contribution, a family contesting the fee for a month, or an insurance company wanting to know what time a child left. There, the register stops being an organizational tool and becomes the account of a day. This article explains what a record must contain for that account to hold.
Filled out today, read in six months
The difference between a register that serves and one that does not is not visible on the day it is filled out. It is seen on the day it is reread. A sheet with a tick next to the name answers only one question: that child was present. It does not say what time they arrived, who accompanied them, who wrote that tick, or when. If the question that comes months later is more precise than that, the sheet is not enough.
A necessary premise: here we are not talking about legal evaluations. What documents are required in your region, with what preservation and for how long, is a matter to verify with your consultant and the regional school office. What follows is the practical plan: what makes a record readable, coherent, and defensible when someone examines it.
What a single record must contain
The point is not the total for the day; it is the individual event. Each entry, each exit, and each absence should carry four pieces of information. In Easy.School, each of these is a field of the record, not a note in the margin.
- The exact time. Not the time slot, not "morning". The precise time of entry or exit is what allows answering questions about actual attendance time, extensions, and meal counts.
- The companion. Who brought the child and, above all, who picked them up. This is the data that is most often missing and the one that is most needed when the question concerns an exit.
- The method of detection. Knowing whether that data was entered manually by an educator, read from a QR code, typed with a PIN by a family member, or generated by automation changes how the record is read. A time recorded by QR code at entry and one transcribed from memory in the afternoon do not carry the same weight, and it is right that they be distinguished.
- The motivation, when there is one. This applies to absences, but also to early exits and late entries.
Four fields per record may seem like a lot. They are not if the system collects them while people do what they would do anyway: the teacher marks the arrival, the family member scans the QR code or enters the PIN, and the automation handles the rest.
Absence is not a blank space
In fragile registers, absence is an unfilled box. But an empty box is ambiguous: it can mean that the child was not there, or that no one recorded anything. These are two very different things, and months later, no one will be able to distinguish them.
An absence recorded as such, with its motivation and the indication of who communicated it, is data. A blank space is not. For this reason, it is advisable that communication comes from the family: from the Easy Family app, the family member reports the absence for a single day or for a period, and that report enters the register already complete, without passing through a hurriedly read message and transcribed later.
Inconsistencies that weaken everything else
A register loses credibility not for the missing data, but for the impossible data. An exit without a corresponding entry. An exit time earlier than the entry time. A presence marked on a day that also shows as an absence. A record with a future date, entered by mistake while adjusting the month. Just one of these lines is enough for the reader to start doubting all the others.
The difference is made by the moment the inconsistency is intercepted. If it emerges six months later, it is a problem to explain. If the system blocks it while you are writing, it does not exist. Easy.School prevents impossible combinations: no exit without an open entry, exit time always subsequent to entry time, no presences on a day already marked as absent, no records with a future date, and no records with a time earlier than another already present on the same day. These are checks that are not noticeable: their effect is that certain lines never make it into the register.
Correcting an error without rewriting history
Errors happen. An educator marks the exit of the wrong child, a time ends up with an hour discrepancy, an absence needs to be moved by a day. The problem is not the error: it is how it is corrected.
The correction that erases and rewrites leaves a clean register but without memory: whoever reads it later sees the final result, without knowing if that data was born that way or was modified three months later. The tracked correction, on the other hand, shows that there was an intervention — and it is precisely this that makes the register more solid, not weaker. A register that admits its corrections is more credible than one that seems perfect.
On a practical level, two things are needed. The first: changes to the database tables are recorded in an action log, so there is a trace of what has been touched. The second: bulk operations must be cleanly reversible. When you bulk register the attendances of a section, that operation receives a unique code that identifies it; if you notice an error, you retrieve the operation from that code and modify it, instead of hunting line by line hoping not to forget one.
The staff register also tells that day
When the question concerns a specific day, it almost never stops at the children. The next question is who was working. The educator-child ratio, the coverage of a section during an outing, the presence of the coordinator in the facility: these are information that lives in the staff register and must be read together with that of the attendance.
The same logic applies: entries and exits with the time, and the justifications — holidays, illness, customizable permits according to the rules of the facility — with the approval of the coordinator. An approved permit is complete data; a permit communicated verbally and remembered by two people differently is not.
In what form is it delivered to those who ask
A register that lives only within the management system is not deliverable: sooner or later it needs to be extracted and handed to someone, and at that moment three things matter: the perimeter, the format, and the readability.
The perimeter is the part that is most often mistaken. Those verifying ask for a period, a section, or a single child: delivering the entire year of the whole complex is not collaborating more, it is making the work unreadable and showing data that no one asked for. Easy.School reports are already exported delimited — by section, by period, or by single child — and this is also the correct way to handle data concerning minors.
The format depends on who is reading. PDF is useful when the document needs to be attached and should not be manipulated. Excel and CSV are useful when someone on the other side needs to do calculations, cross-checks, or controls on many lines. For the single day, there is the daily register report in Excel format, which solves the most frequent request: "send us the register for February 14th".
Before exporting, always ask what period the request refers to and in what form the document is needed: two minutes of questions avoid three subsequent extractions.
In summary
A useful attendance register months later contains, for each event, the time, the companion, the method of detection, and the motivation; treats absence as data and not as a void; does not host impossible lines because the system blocks them from the start; keeps track of corrections instead of hiding them; and allows extraction in the perimeter and format that are needed. To understand what obligations apply to your structure, consult with your advisor and the regional school office: what you can do right away is ensure that the data is there and is coherent.
Do you want to keep the attendance register in order without adding work to your days? Try Easy.School for free.
