The request arrives on Tuesday. The educational services office asks for the data from the recently closed period, with a ten-day deadline. And the reconstruction begins: a phone call to each location, three spreadsheets open together, sums that someone had already done and that you redo because you no longer remember where they came from.
The cost is not just time. It’s that two extractions of the same thing, done at different times, return different numbers, and you have no way of realizing it before delivery. Here you find the categories of data that entities most often request from a 0-6 service under contract or concession, where they are if the structure registers them well and in what form they come out.
When the request arrives, the reconstruction begins
The scene is repeated almost identically in nearly all structures. The coordinator writes to the locations to ask for the attendance counts, someone responds with a sheet, someone else with a photo of the paper register. The economic data is held by the administration, the personnel data is in a different folder, and the complete registries are in a third place. Reassembling everything means spending two days pasting columns.
The real problem is downstream. When the number comes from a manually calculated sum, that number is no longer verifiable: if the entity asks for clarification in November on a data delivered in September, you have to redo the work from scratch and hope it matches. And if it doesn’t match, you don’t know which of the two versions is the correct one, because neither has a traceable source behind it.
The categories that entities most often request
A necessary premise: there is no universally valid list. Requests vary from municipality to municipality, from call to call, and from agreement to agreement: what one entity considers essential, another never asks for. For this reason, here you won’t find obligations, but recurring data categories, that is, the types of information that are most frequently requested from a 0-6 service.
- Children's attendance: actual attendance by period, usually distinguished by section or location.
- Registry of enrolled children and family units: who attends, with identifying data next to the numbers.
- Economic data: billed fees, collected amounts, issued documents, any fees charged to the entity.
- Staff: employed personnel, service hours, shift coverage.
- Service structure: active locations, sections, capacity, opening hours.
- Supporting documentation: the actual documents, not just the summary.
Children's attendance: the daily register
This is the category that is almost always requested, and it is also the one that is most poorly reconstructed by hand, because attendance is a data point generated every day and lost every day. If educators only mark it in the section notebook, at the end of the year you have two hundred pages to count.
In Easy.School, cloud management software for 0-6 services used by over a thousand structures, the daily register can be exported to Excel and returns actual attendance by section and period. It’s the difference between the number of enrolled children and the number of those who actually attended: two data points that entities often keep separate and that can easily be confused manually. The file is already divided by section, so if the request comes with a detail different from what you expected, you don’t start over: you filter.
Registries: numbers with names next to them
Many requests are not satisfied with the total. They want to know who was there: list of enrolled children, personal data, family unit composition, date of entry and any withdrawal. If attendance is in one place and registries in another, this is the point where the work doubles.
Reports are also built from child and family forms, so they include personal data along with the numbers, without manual cross-referencing. There are annual reports for a snapshot of the period and individual child reports for when the entity requests details on a specific position. And if the request concerns information that no standard field provides, the registries accept custom fields for child, family, and staff: you add it once, fill it out during the year, and then extract it like everything else.
Fees, invoices, and cost centers
The economic part is where numbers that don’t add up cause the most damage, because an incorrect total in a summary already delivered to the entity is difficult to correct later. It’s essential that the summary comes from the same documents you issued, not from a parallel table.
There is an Excel export built on the format of the Revenue Agency, with the addressee and child complete with tax code, taxable amount, VAT, and total. It can be filtered by section, child, product, payment method, and document type: five levers that cover almost all the forms in which a request can arrive. When the entity wants documents and not the summary, there is a mass download of accounting documents. And to understand how a figure is distributed, cost centers are assigned to the invoice and also to each line: this way the detail exists already at the moment of issuance, not reconstructed in December.
Staff: shifts, attendance, and documents
For staff, the questions are generally three: who was on duty, for how many hours, with what qualifications. These are three data points that live in different places and that almost always are recomposed manually.
Daily, weekly, and personal shifts can be printed in PDF with the calendar, and this is the form closest to what an entity expects when asking for service coverage. The staff attendance records entries, exits, and justifications approved by the coordinator, so the total hours are not an estimate but the sum of verifiable lines. The staff documents are on each individual’s profile, with visibility by role: when the qualifications of an educator are needed, you know where they are without searching in a shared folder.
Multiple locations, and the form in which you deliver
If you manage multiple locations, half the effort is in putting back together what is generated separately. In Easy.School, locations are unlimited and each has its own settings: the data is already attributed to the correct location, so the entity's request is fulfilled by filtering, not by calling.
Regarding the form, a simple rule applies: Excel when the entity needs to reprocess the numbers, PDF when it needs to file a document. What really changes the day, however, is being able to look at the export before delivering it: you open the file, check the lines, verify that the totals match what you expect. And if a number turns out to be different from a previous extraction, there is a log of actions on the database tables: you can see what has been modified and when, instead of guessing which version to deliver.
In summary
Requests from entities vary from municipality to municipality, but the data categories repeat: attendance, registries, economic data, staff, service structure. If the structure registers them well throughout the year, the report is not a reconstruction but an extraction: daily register in Excel for attendance, child and family forms for registries, filterable accounting export for the economic part, shifts and staff attendance for coverage.
The work shifts from recalculating sums to checking them before delivery, and this also changes the quality of what you deliver. Want to see how this data is extracted in your structure? Try Easy.School for free.
