Truancy and Chronic Absenteeism Case Management Software: Running the Statutory Ladder Without Losing the File

Why attendance work breaks the moment it becomes a legal process

A student services director is sitting outside a courtroom with a manila folder. Inside is the evidence that the district did what the statute required before referring this family: the absences, the notices sent at each threshold, proof of delivery, the attendance conference that was offered and whether the parent attended, the interventions tried, and the outcome of each. The folder was assembled over two days from four sources. One notice is missing because it was sent from a campus that uses its own letter template. The conference happened but the only record is a line in a counselor's calendar. The county attorney will notice both.

This is the part of attendance work that no student information system was built for. PowerSchool, Infinite Campus and Skyward record that a student was marked absent in period four. They do not know that three unexcused absences trigger a first notice in your state, that a conference must be offered before a referral, that the referral is only accepted if the packet shows documented intervention, or that a family that moved between two of your campuses carries their absence count with them.

The money side is just as concrete. In states that fund districts on average daily attendance, every recovered day is revenue, and chronic absenteeism is separately reported as a school quality indicator under ESSA in most state accountability plans. So the same dataset is being asked to do two different jobs for two different audiences: recover funding and stay out of a finding, while also driving a legal escalation with due process attached. Most districts do the first job in a report and the second job in a shared drive.

Problem 1: your attendance codes do not mean what the statute means

Districts carry dozens of local attendance codes. Excused for illness, excused with a note, excused religious observance, school activity, in school suspension, out of school suspension, tardy, tardy over 30 minutes, partial day, unverified pending, and the code a campus invented in 2019 that nobody has audited since. The statute in your state counts a much smaller set of things, and the mapping between the two is a judgement call that currently lives in a workbook.

The conversion is not cosmetic. Secondary campuses take attendance by period, elementary campuses by day, and your statute may count days, half days or hours. Ohio moved habitual truancy to an hours based definition with an intervention plan on a fixed clock. California treats three unexcused absences or three tardies over thirty minutes as the trigger. Texas requires documented truancy prevention measures before a referral and sets its own count within a rolling window. Whatever your state does, the arithmetic that turns period level codes into statutory counts is the foundation of everything downstream, and if it is wrong, every notice you send is wrong.

What a custom build does: attendance code mapping becomes explicit configuration, versioned and dated, with a rules engine that computes statutory counts separately from the funding count and the chronic absenteeism count. Three numbers, three definitions, one source of truth, all recomputed nightly. When a campus changes a code retroactively, the affected students and any notices already generated surface for review rather than quietly diverging.

Problem 2: the notice ladder is a legal clock nobody is watching

Your statute prescribes a sequence: a first notice at one threshold, a second with different content, a required conference offer, then eligibility for referral to an attendance review board or the court. Each step has content requirements, sometimes language requirements, and sometimes a waiting period before the next step is valid. Miss a rung and the referral is rejected, which means months of a family's escalating absence with no legal traction.

Running this from a spreadsheet fails in a specific way. Somebody runs a report on Friday, filters for students over the threshold, mail merges letters and marks a column. The next Friday they do it again, and the students who crossed the threshold on Monday got a five day head start on a legal clock nobody was watching. Transfers between campuses reset the tracking because the new campus starts its own list.

What a custom build does: threshold crossing generates a case automatically the night it happens, with the correct notice queued, the delivery method chosen by your escalation policy, and the next step scheduled. Proof of delivery is captured, whether that is a mail log, an email receipt, an SMS confirmation or a signature from a home visit. The case follows the student across campuses inside the district. The attendance team's screen becomes a queue of what is due today rather than a report they interpret.

Problem 3: the intervention record has to survive scrutiny

Before a court will take a family, and before a school attendance review board will act, they want evidence that the district tried. Attendance conferences held or offered, plans agreed, home visits, transportation offered, health referrals for a student whose absences are asthma related, counselor contact, credit recovery arrangements. Most of that happens. Almost none of it is recorded in a form anyone else can read.

EveryDay Labs and Kinvolved both do useful work here and neither one is this. They are family engagement and analytics layers: absence prediction, nudge mailers, two way messaging, dashboards on chronic absenteeism trends. Districts get value from them. What they do not do is hold the legal case file, run the statutory ladder with proof, or produce a packet a county attorney will accept, because that was never their product.

What a custom build does: interventions are typed records against the case with date, participants, outcome and attachments, entered by the person who did the work on a phone from a doorstep. The referral packet is generated, not assembled: a single document containing the absence history in statutory terms, every notice with delivery evidence, every conference, every intervention, and a signed cover from the attendance officer. Underneath it is an append only log, so nothing in the file can be back dated after a referral is challenged.

Problem 4: chronic absenteeism and truancy are two different jobs

Truancy is unexcused, legal and individual. Chronic absenteeism counts all absence, excused included, is usually defined as missing ten percent or more of enrolled days, and is a school level accountability number. A student with a chronic illness and perfect documentation is chronically absent and not truant. A student with eight unexcused days out of thirty is truant and may not yet be chronically absent. Districts that run one list conflate two problems and end up sending legal notices to families whose children have cancer.

What a custom build does: cohort tracking that is separate by design. Chronic absenteeism is tracked as a rate against enrolled days, computed continuously so a campus can see in November which students are on pace to be chronically absent by June rather than confirming it in the summer. Reason categories drive different playbooks: health, transportation, housing instability, caregiving responsibility, disengagement. The intervention a family needs is rarely a letter, and a system that only escalates legally is a system that will send the wrong response most of the time.

What a build has to include

• A versioned attendance code map producing three separate counts: funding, statutory truancy and chronic absenteeism.
• A rules engine for your state's thresholds, waiting periods and notice content, editable by your staff when the legislature moves.
• Automatic case creation with delivery evidence capture on every notice.
• Case continuity across campuses within the district, and a defined handling for students who withdraw and reenrol.
• Mobile intervention logging for home visits, because the alternative is a note typed three days later.
• Generated referral packets for the attendance review board and the court, in the format your county actually accepts.
• Family communication in home languages with two way response, and a preference for the channel the family answers on.
• An append only audit trail on the entire case.
• Reporting split by audience: your board, your state accountability submission, and your county.

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, a focused first release, meaning attendance code interpretation, threshold detection, automated notice generation with delivery evidence and a case queue, runs $55,000 to $110,000 and ships in 10 to 14 weeks. Adding intervention case files, referral packet generation, chronic absenteeism cohort tracking with reason categories and multilingual two way family messaging brings the total to $140,000 to $300,000 across 5 to 9 months.

What drives cost up in this category: the number of counties you refer into, because each court has its own accepted packet and its own liaison with opinions. Multilingual notice generation, since each language adds review workflow. Period based attendance at secondary campuses combined with a day or hour based statute, which is genuinely fiddly arithmetic. And any state that changed its truancy law recently, because you will need to run both the old and the new rule for a transition year.

What keeps cost down: leaving the student information system as the source of raw attendance and building the interpretation and case layer on top. Nobody in this project should be building an attendance taking screen.

When buying is the right answer

Buy if you are under roughly 5,000 students, or if your county effectively does not accept truancy referrals, which is true in more places than districts admit. In that case the legal ladder is theatre and your real problem is family engagement, so EveryDay Labs or Kinvolved plus your SIS reporting is honestly the better spend.

Build when two or more of these are true. You are above roughly 15,000 students. Your state funds you on average daily attendance, so recovered days are measurable revenue. You employ dedicated attendance officers or a court liaison, which means you already pay salaries to do manually what software should do. Your county attorney has rejected a referral packet for missing documentation. Or your board has asked for a chronic absenteeism number and two departments produced two different answers.

How to choose a developer for attendance and truancy systems

Ask them to explain, on a whiteboard, how they would compute a statutory truancy count from period level attendance codes at a high school where the statute counts days. If they wave at it, they have not done this. The answer should mention configurable code mapping, a conversion rule, and versioning so that a code change in March does not silently rewrite January.

Ask how a notice already sent is handled when the underlying attendance is corrected afterwards. The right answer is that the case is flagged for human review and the original notice remains in the record with its correction noted. A system that silently recalculates has destroyed your evidence.

Ask whether they have built anything that produces a document another agency has to accept. Court packets, review board files and state submissions are all this category, and a developer who has only built internal dashboards will underestimate it.

Ask about data retention and access control, since these files contain family circumstances that are sensitive well beyond ordinary education records. Then get code ownership in writing before kickoff: the repository, the cloud accounts, and the right to hire anyone else. At Digital Heroes the district owns all of it from the first commit, and a vendor who resists that is planning to be hard to replace.