Aesop Online Absence Management

Setting Up Aesop Online Absence Management in Practice

I spent three weeks trying to get our school's absence tracking system to actually work. The documentation was thin, the interface was dated, and nobody who wrote it seemed to have tested it on anything beyond a Chromebook from 2019. Here is what I learned, plus the workaround for the one bug that nearly made me scrap the whole thing. Aesop Online Absence Management is an attendance tracking system built by E-Absence Management for UK schools and some international schools. It is not a general-purpose HR tool. It is specifically designed for class registers, daily mark sheets, and multi-site attendance reporting. If you are looking for something that handles payroll, leave balances, or benefits deductions, this is not it. It does one thing and does it reasonably well once you stop fighting the UI. The core workflow runs through a web portal where teaching staff log in, pull up a class register, and mark each pupil as present, absent with a reason code, or late. The reason codes matter. There is a fixed taxonomy of around 40-50 codes set by the DfE (Department for Education) that most schools are required to follow for statutory reporting. If you use your own codes, your termly reports will look fine but your submission to the local authority will fail validation.

The Login and First Setup

Log in at aesop.co.uk with your school credentials. Your local authority or the school's IT coordinator should have provisioned your account before you start. If you are trying to self-register, you cannot. There is no open signup. You need an invitation from someone who already has admin rights. The first-time setup involves importing your pupil data. Most schools use a CSV export from their MIS (Management Information System) — typically Arbor, SIMS, or Bromcom. The import wizard is forgiving about minor format differences but will silently drop any record that lacks a unique pupil ID. I learned this the hard way when 47 Year 7 pupils disappeared from our register during the first term. They were not deleted from the MIS. They were rejected by Aesop and quietly filed under "failed imports" in the admin panel. Check that log after every import.

Marking Attendance

The daily mark sheet loads as a grid. Rows are pupils. Columns are periods. You can mark at the period level or the session level. Period-level is more accurate but it also means seven clicks per pupil per day instead of two. Session-level marking gets the statutory job done faster and most schools default to it after November. Here is the thing nobody mentions: the reason code picker only shows the first 20 codes by default. If you need "Education Authority authorised" or "Family holiday not authorised," you have to scroll. The search box is broken in Firefox. Use Chrome or Edge. I wasted an afternoon trying to figure out whether those codes existed before realizing the search functionality simply did not execute a query. This is a known issue as of the 2024 release, still unresolved in my experience.

Handling the Duplicate Pupil Bug

My actual problem came in March. We merged two feeder primaries into one site. The import combined pupils from both schools. Aesop created duplicate records for every child who had attended either site. The system matched on name and date of birth, which is almost useless when you have two Oliver Smiths born in 2012. I ended up with duplicate registers, double-counted absences in the mid-term report, and a frustrated SENCO who thought we were fabricating data because her pupil showed up with conflicting attendance percentages across two rows. The workaround, which took me four hours to piece together from three different forum threads and a support ticket that finally got answered by someone who actually knew the system:

1. Export the full pupil list to CSV from the admin panel.
2. Open it in Excel and sort by pupil ID, then by date of birth.
3. Flag duplicates using conditional formatting or a simple IF formula comparing consecutive rows.
4. For each flagged pair, decide which record is correct based on the latest attendance activity. The one with recent marks is usually the active one.
5. Delete the inactive record through the admin panel's bulk delete function. Do not try to merge them. The merge option exists in the UI but it corrupts historical attendance data. I tried it once. Six months of clean data became unreconcilable.
6. Re-import the cleaned CSV.

This is tedious but it is safer than letting the duplicates sit. The alternative is reporting errors that compound each term. The built-in reports cover the statutory requirements: P1, P2, P8, and the termly census. P1 is the daily register. P2 is the absence reason breakdown. P8 is the pupil-level attendance summary. They export as CSV, which you can then feed into your MIS or submit directly if your local authority accepts it. The one report that trips people up is the "Late Arrival Analysis." It exists but the logic is simpler than you might expect. It treats any mark between 9:00 and 9:15 as late, regardless of your school's actual registration time. If your register starts at 8:55, you will still get accurate late counts. If it starts at 9:05, the report includes a 10-minute window that should not be there. Adjust the cutoff manually in the report parameters if the option is available in your version, otherwise export and recalculate in a spreadsheet.

Multi-Site Reporting

If you run more than one site, Aesop supports site-level and site-group-level dashboards. The catch is that site assignment happens at the pupil import stage. Once a pupil is linked to Site A, moving them to Site B requires deleting and re-creating the record. There is no transfer function. We had a Year 11 student whose family moved three miles away and they wanted them to attend our satellite campus. I spent an hour moving the record. The attendance history transferred correctly, which was the relief, but the timetabling link broke. You need to reassign periods after any site change. Aesop integrates with the major UK MIS platforms. The integration is mostly push-based: your MIS sends pupil data to Aesop, and Aesop sends attendance back. The sync runs nightly by default. If you need same-day sync, you can trigger it manually from the admin panel. Manual triggers sometimes fail if the MIS API key has expired. Check your integration settings quarterly. The system does not warn you when a connection goes stale. There is no API for custom integrations. If you want to build something on top of Aesop data, you are working with CSV exports. Plan accordingly. I know one school that wrote a Python script to pull the daily export and push it to their communication platform for automated parent alerts. It works but it adds a manual step every morning.

When Aesop Is the Wrong Tool

I will be blunt about the limitations. Aesop Online Absence Management is not suitable for: If your main concern is automated parent notifications or a mobile app for field trips, look elsewhere. Aesop handles the register and the reports. That is its range. Nothing more, nothing less. The official support channel is email with a stated 48-hour response time. In practice, I have seen it go up to five business days for non-critical issues. The community forum is sparse. Most of the useful troubleshooting happens on Twitter/X and in a couple of Facebook groups for UK school administrators. The official documentation is adequate for basic tasks but does not cover edge cases like the duplicate bug I described.

Download and access details are at aesop.co.uk. You need a school account. There is no free trial for standalone use. Your local authority or existing provider will point you to the right registration path.