Automating Recurring Registrations: What Can and Cannot Be Done

It’s 1 PM on any Wednesday. In the section, there are twenty-five children, almost all already on their cots, and the educator opens the tablet to record naptime. She records it once. Then again. Then again, twenty-five times, for a data point that has been the same since September.

A significant portion of daily registrations is predictable. Not all, fortunately: exceptions exist, and it is on those that it is worth spending attention. But the base — naptime, lunch on fixed days, recurring Thursday activities — repeats with a regularity that software can absorb. Let’s see how automations are set up in Easy.School, which registrations make sense to automate, which are better left manual, and what automations do not do.

What is an automation, in practice

An automation in Easy.School is a programmed rule that records attendance, meals, activities, and naptimes for one or more sections, based on the day of the week and the time slot. It is not a reminder and it is not a draft to be confirmed: when the rule triggers, the registration enters the logbook and the registers exactly like a registration made manually by an educator.

This equivalence has two consequences. The first is convenient: a second archive to check does not arise, there are no "automatic" data separate from "real" data. The second requires attention: if the rule is set up incorrectly, the wrong data enters the registers with the same naturalness as the correct one. Automations are configured once and then remain there to work, which is why the initial half-hour of setup should be well spent.

How to set up a rule

Every rule is born by answering four questions:

• What does it record — an attendance, a meal, an activity, or a naptime: the items that make up the logbook, the aggregated view of attendance, lunch, snack, naptime, needs, activities, and daily averages.
• On which sections — one section, some, or all those in the complex. The naptime for infants follows different hours than that for older children: two distinct rules describe reality better than a generic rule.
• On which days — the rule attaches to the days of the week. Monday's lunch may be different from Friday's, and garden activities may only exist on Tuesdays and Thursdays.
• In which time slot — the time tells the system when that registration makes sense: it is the parameter that distinguishes morning snack from afternoon snack.

Once saved, the rule remains active until you modify it: it does not need to be reconfirmed at the beginning of the week nor recreated after holidays. The right moment to review it is when something really changes — a new schedule, a section that splits, a different menu.

Registrations that make sense to automate

The criterion is simple: automate what is true for almost all children in the section, almost every day, and that when it is not true, it stands out immediately.

• The afternoon naptime. This is the clearest case: in many sections, it is a structural fact of the day, with the same time slot from September to June. Those who do not sleep are a visible exception, which can be corrected in a few seconds.
• The lunch on fixed days. If the menu follows a stable rotation and the section always eats at the same time, the registration is repetitive by definition.
• The recurring activity. Activities are recorded by group: the activity is chosen from the structure's catalog, which is configurable, and the children who participated are indicated. If there is always psychomotricity on Wednesdays and always reading on Fridays, the rule prepares the registration and the educator only needs to remove those who were not present that day.
• The snack. Same logic as lunch: fixed time, almost total participation, few exceptions.

Registrations that are better to continue doing manually

There are data that lose value the moment they stop being observed. Automating them does not save time: it only produces lines that no one will read with confidence.

• The needs. The change, the potty, the terms that each structure personalizes according to its own language: these are punctual registrations, tied to a specific moment. No time rule can invent them.
• The notes and media of the day. The sentence about this morning's play or the photo from the workshop are what the family looks for when opening the Easy Family app. No rule can write them in place of those who were there.
• The unplanned activities. The outing, the visit, the improvised transfer because it was raining: these are individual events, recorded when they happen.
• The attendance in structures with very variable hours. If part-time, extended hours, and alternating day frequencies coexist in the same section, attendance is the data most exposed to error and is what families look at first.

What automations do not do

Here it is necessary to be clear, because this is where wrong expectations arise. An automation does not verify in place of the educator. It records what you told it to record, on the day and at the time you indicated, without knowing what really happened in the section.

In particular: it does not know that a child is home with a fever today, it does not notice that three children did not sleep at all, it does not distinguish who tasted two spoonfuls from who ate everything, it does not record that Thursday's activity was skipped because a colleague was absent. It does not manage days outside the ordinary: parties, outings, closures, assemblies. And it does not produce what makes the logbook interesting for a family, namely the observed detail.

From here a simple hygiene rule: before a special day, suspend the involved rules or plan to correct them afterward. Every registration remains modifiable and there is a log of actions on the database tables, so who changed what is always reconstructible. Correction is not a patch: it is a normal part of the flow.

When it is better not to automate at all

There are periods and situations where a rule costs more than it yields:

• During acclimatization. In September, the schedules are provisional, children stay for half an hour or two hours, and there is not yet a typical day to describe.
• In a newly opened or reorganized section. First, observe how it really works, then write the rule. The opposite leads to rules that describe intentions, not reality.
• With a newly formed work group. If the educators are still getting familiar with the Easy Staff app, it is better for them to learn to register manually from the section first: correcting an automation that has not been understood is more difficult than entering data from scratch.
• When exceptions are the majority. If every day you correct half of the generated registrations, either the rule is poorly written or that data is not automatable. In both cases, it is deactivated.

The work changes form: from entering to correcting

The real effect of automations is not "less work": it is different work. Previously, the educator entered twenty-five identical naptimes and then, if she had time left, added a note about who did not sleep. Now she opens the logbook, finds the twenty-five naptimes already there, and uses the time she needs on the three exceptions of the day.

This is a change in posture that should be explicitly communicated to the work group; otherwise, automation is experienced as external control or, worse, as a permission not to look. The correct message is another: the system takes care of the repetitive part, you take care of the part that requires observation. Verification remains a daily gesture, just much shorter: a check on the logbook at the end of the morning and one at the end of the afternoon, from the tablet, while being in the section.

For the coordinator, the advantage comes downstream: the registers remain continuously filled even on difficult days, and the export in PDF, Excel, or CSV at the end of the month does not start from an archive full of gaps.

In summary

Automations are programmed rules that record attendance, meals, activities, and naptimes by section, day, and time slot: they are configured once and remain. Automate what truly repeats — naptime, meals at fixed times, weekly activities — and leave manual what arises from observation: needs, notes, media, individual events. No rule verifies in place of those in the section, and in unstable phases like acclimatization, it is more honest not to use them at all. What they return is not an automatic day: it is the time that today ends up in repeated compilation.

Do you want to see how they work with the rhythms of your structure? Try Easy.School for free.