Your SIS is your system of record. Attendly is your system of action.
That line is how Attendly positions the product. It is also how I decide what we ship.
I am not trying to replace your SIS. We read from it. The sync is read-only and one-way. It runs multiple times a day. It is not real-time. We do not write back. The school day stays where it already lives.
What we build is the next step after that record exists.
The chart is not the file
Districts already have dashboards. Chronic absence is on the Dashboard. Period attendance is in the SIS. Boards can see a red cell from across the room.
The work that stalls is smaller than that.
Who checked this pupil into expanded learning at 2:40. Which authorized adult picked them up. Which hours were ELO-P, and which hours were Attendance Recovery, on the same campus. Which absence those Recovery hours attach to. Whether the adult in that Recovery room was a certificated employee of the LEA, in ratio, with minutes that add to a day.
Education Code 46211 does not ask for a heatmap. It asks for a recovered day that can be sampled. CDE wants Recovery on its own register. Section HZ is a sampling script for that register.
A dashboard can tell you the district has a chronic absence problem. PACE and Attendance Works already counted 1,143,668 chronically absent California students in 2024-25. You did not need us to chart that number again.
You needed a way to take the next action on one pupil without opening four spreadsheets.
Action is assignment, check-in, and a packet
I keep the product on three verbs.
Assign. A recovered day has to attach to an eligible absence. CDE is blunt about that. A chart of “make-up hours” that never names the Wednesday it offsets is not ADA.
Check in. Expanded learning is not period attendance. CALPADS Flash 305 wants a participation day on the LEAP file, including a signed form with zero days. The afternoon still needs a time and a site. I already wrote the longer version of that split in Our SIS Already Tracks This.
Pack. Section DZ will ask whether you offered ELO-P and whether the hours added to nine. Section HZ will ask whether the Recovery teacher, the ratio, and the assigned absence sit in one place. The ELO-P audit checklist is that packet for expanded learning. The Attendance Recovery hub is that packet for ADA.
None of those verbs is a widget that glows when the rate moves.
How we work, versus what you log into
Internally, Attendly runs on AI. Drafts, research, the boring glue that used to wait on a queue. That is how the company moves.
The product is not that. We do not ship “AI attendance.” We do not ask a model to mark a pupil present. We do not treat a generated summary as the register Section HZ will open.
If a clerk cannot see the absence, the hours, the adult, and the ratio without translation, we built the wrong thing.
That is a product rule, not a slogan on a sales deck.
What I will not build next
I will not build a second SIS.
I will not build a dashboard whose only job is to restate what DataQuest already published.
I will not blur ELO-P minutes and Recovery minutes because they share a cafeteria. CDE already said a pupil is in one of those programs in a given stretch, not both.
I will keep building the workflow that takes a roster from the SIS and turns it into a check-in, a recovered day, or an audit folder a partner can hand over without rewriting the year in April.
If that is the leak in your district, let’s talk. Sit with the team that builds the next step, not another chart of the empty seats.
Where Attendly fits
Let's talk
If this is the leak in your district, sit down with the team that builds the workflow.
Let's talk
