Chapter 18: Data Systems and Operational Workflows

The Manual Burden Districts Face Today

Without purpose-built AR tracking tools, most districts are managing attendance recovery with improvised workflows.

Here’s what that looks like in practice: Site coordinators track AR attendance on paper rosters. Weekly, they enter the data into spreadsheets. Monthly, they email those spreadsheets to the district office. A data tech consolidates multi-site data, cross-references student IDs against SIS enrollment, runs grade-level minute-to-day conversions, checks running totals against the 10-day cap and absence limits, generates PADC and CALPADS reports, and files backup documentation for audit.

Administrators report this workflow consuming several hours per week across the district. Over a 40-week school year, that adds up fast — and it doesn’t account for error correction, audit prep, or troubleshooting when something breaks.

Why Manual Tracking Doesn’t Scale

Manual processes work for small pilots. They break at scale.

Error propagation. Data passes through multiple hands — site coordinator to spreadsheet to email to district tech to SIS to PADC/CALPADS. Each transfer introduces error risk. A single student ID typo creates mismatch errors. A missed email means incomplete data. A formula error in one spreadsheet cascades downstream.

Delayed visibility. If site-level data reaches the district office monthly, nobody sees AR accumulation, cap proximity, or eligibility issues in real time. By the time you discover a student exceeded the 10-day cap, weeks of recent AR hours may not count. Too late to adjust.

Audit vulnerability. Paper rosters get lost. Spreadsheets lack audit trails showing when data was entered or by whom. If an auditor asks whether a student earned 8 AR days, can you produce contemporaneous documentation proving attendance on those dates under certificated supervision? Reconstructing documentation months later is expensive and unreliable.

Staff turnover. When the one person who understands the spreadsheet formulas leaves, institutional knowledge walks out with them. New staff reverse-engineer processes and discover gaps they can’t explain.

What Automated Tracking Should Handle

Whether you’re using purpose-built AR software or configuring SIS modules, your system should handle five things:

1. Eligibility identification. Sync daily with SIS to pull current absence data, flag students who cross your threshold (say, 10 absences), and alert site staff about newly eligible students.

2. Real-time AR accumulation. As students attend sessions, hours accumulate automatically. The system calculates grade-appropriate minute-to-day conversions. Running totals stay visible to teachers, coordinators, and administrators.

3. Cap enforcement. The system prevents claiming beyond the 10-day cap. It warns when students approach limits — at 8 recovered days, flag “only 2 days of capacity remaining.” It cross-references absences so recovered days can’t exceed total absences.

4. Reporting integration. Export PADC-formatted data. Generate CALPADS Field 13.24 submissions. Produce audit-ready documentation on demand.

5. Role-based access. Teachers see their students, mark attendance, and view AR progress. Site coordinators see all students at their site and run local reports. District administrators see all sites and monitor program-wide performance. Data staff extract reports for PADC and CALPADS.

Real-Time vs. Retrospective Tracking

Real-time tracking means data enters at the point of service. Teachers mark AR attendance during or right after sessions, and accumulation calculates instantly. Errors get caught the same day. If a student stops attending, the coordinator knows right away.

Retrospective tracking means data is entered days or weeks after sessions — often at month-end when staff compile paper records. Errors hide until someone reconciles. Documentation gaps grow harder to fix with time.

Real-time tracking requires digital tools accessible during AR sessions — tablets, laptops, or phones. Retrospective tracking works with paper but sacrifices timeliness and accuracy. If your district is serious about recovering AR revenue, invest in real-time tools. The administrative time you save pays for itself quickly.

Building Views for Different Audiences

Different people need different views of the same AR data.

Teachers need a simple check-in roster (who’s here?), student-level progress (how many AR days has this student recovered?), and session planning tools.

Site coordinators and APs need participation metrics (enrollment numbers, attendance rate), individual student tracking (who’s approaching caps, who stopped coming), and intervention flags (who needs follow-up outreach).

Cabinet and district leadership need the big picture — total ADA recovered district-wide, cost per recovered day, revenue impact. They want trend data (month-over-month participation, site comparisons) and compliance status (are we on track for clean PADC/CALPADS submissions?).

One data source feeding role-based views beats maintaining separate spreadsheets for each audience.

SIS Integration: The Critical Connection

AR data doesn’t exist in isolation. It needs to connect to:

• SIS absence data — to enforce the “recovered days can’t exceed absences” rule
• SIS enrollment data — to confirm enrollment, identify grade levels, map students to correct schools
• CALPADS reporting — so recovered days flow into Field 13.24 in the STAS file
• PADC reporting — so recovered days are included in fiscal apportionment

Three integration approaches, from tightest to loosest:

1. Direct SIS integration — AR tracking lives as a module within your SIS or as a tightly coupled add-on. Data flows automatically.
2. API-based connections — standalone AR software reads and writes data through your SIS API. Near-real-time, but requires API configuration and maintenance.
3. File-based imports/exports — AR system generates files that your CALPADS coordinator imports manually. Simplest to set up, but introduces lag and manual steps.

The tighter the integration, the less manual work and the fewer errors. Pick the approach your district can actually support and maintain.