Chapter 7: The Intersection with Attendance Recovery Programs

Two Programs, Two Purposes, One Operational Reality

If your district runs Attendance Recovery alongside expanded learning, you already know these programs share infrastructure. Same afterschool hours, same buildings, often the same certificated teachers. Both require daily attendance tracking, and both feed CALPADS.

That overlap is an advantage — but only if you’re precise about which program is which, what each one reports, and where the statutory lines fall.

Three Statutory Programs, Not Two

Before we go further, a critical distinction. Districts sometimes talk about “Saturday School” and “Attendance Recovery” interchangeably. They’re not the same thing. There are actually three separate programs that touch absence-related instruction, each with its own Ed Code authority:

Expanded Learning Programs (ELO-P, ASES, 21st CCLC):

Authority: Various — Education Code §§8482-8484.65 (ASES), §46120 (ELO-P)
Purpose: Enrichment, homework support, extended learning
Funding: State grants through CDE Expanded Learning Division
Students: Voluntary, open to eligible students regardless of absence history
CALPADS reporting: LEAP file (Field 26.07 – ELP Days)
What you track: Days of participation

Attendance Recovery (EC §46211):

Authority: Education Code §46211
Purpose: Recover lost ADA funding by providing supplemental instruction to students with absences
Funding: Not grant-funded — the benefit is recovered ADA apportionment
Students: Voluntary, but targeted to students whose absences represent lost funding
CALPADS reporting: STAS file (Field 13.24 – AR Days) + PADC
What you track: Instructional minutes, converted to recovered ADA days

Saturday School (EC §37223):

Authority: Education Code §37223
Purpose: Provide additional instructional time on Saturdays as an alternative to other absence interventions
Funding: ADA apportionment for Saturday attendance
Students: Students assigned or offered Saturday instruction
CALPADS reporting: Reported through regular attendance channels, not the STAS AR fields
What you track: Attendance on designated Saturday instructional days

The key point: Saturday School and AR operate under different statutes with different rules. AR has a 10-day cap per student, requires certificated teacher supervision, and reports through Field 13.24. Saturday School doesn’t share those constraints or that reporting path.

In most districts, Ed Services Directors oversee all three. That’s fine — but the data systems, compliance documentation, and CALPADS reporting for each must stay separate. Don’t let operational convenience blur statutory boundaries.

Tracking Time in Both ELP and AR

A student can participate in both ELP and AR. Many districts design it that way — enrichment for everyone, with AR funding recovery available for students who have absences. But the two programs track time differently, and your systems need to handle both.

Consider a 5th-grader attending your afterschool program from 3:00–5:30 PM, four days a week. Her schedule:

Homework help and tutoring: 30 minutes
STEM enrichment: 90 minutes
Physical activity and snacks: 30 minutes

ELP side (LEAP file): She attended on four days. Field 26.07 gets 4 days of ELP participation. Simple — she was there, she gets credit.

AR side (STAS file) — only if she has absences to recover: The homework help (30 minutes) and STEM enrichment (90 minutes) both count as AR instructional time because they’re standards-aligned and supervised by a certificated teacher. Physical activity and snacks don’t count. That’s 120 qualifying minutes per session.

Here’s where the accumulation model matters. AR minutes don’t convert to partial days session by session. They accumulate across sessions. Over four sessions, she banks 480 qualifying minutes. At the grades 4–12 threshold of 240 minutes per day, that’s 2 full AR days for the week. (If she’d attended only three sessions — 360 minutes — that’s still 1 full AR day, with 120 minutes carrying forward.)

Your systems need to track two separate things:

Did the student attend the afterschool program? (yes/no) → feeds LEAP file
How many AR-qualifying instructional minutes did she accumulate? (running total) → feeds STAS file

Avoiding Double-Counting and Data Conflicts

CALPADS validation catches logical impossibilities. Three examples of what triggers errors:

Field 13.24 exceeds 10. A student shows 12 AR days — but the cap is 10 per year. Your system should enforce this ceiling before the data reaches CALPADS.

AR days exceed total absences. A student shows 8 AR days in STAS but only 6 absences in the SIS. You can’t recover funding for more days than the student missed. Another cap your system needs to enforce.

Impossible program overlap. LEAP shows a student in both ASES and ELO-P on the same dates at different sites. That’s physically impossible.

To prevent these, build three rules into your data flow:

Cap enforcement — Field 13.24 can’t exceed 10, and can’t exceed total absences
Program conflict checks — flag students showing simultaneous participation in programs at different sites
AR/ELP reconciliation — if a student earned AR days through an afterschool program, the LEAP and STAS records should reflect consistent dates

At any real scale — hundreds of students across multiple programs — this reconciliation has to be automated. Manual cross-checking between LEAP and STAS files won’t hold up.

Integration vs. Separation: A Strategic Call

Districts handle the AR/ELP relationship in two ways.

Separation means AR runs as its own program — different scheduling, different enrollment, different tracking. This is simpler for compliance. There’s less risk of blurred data between programs. But it’s operationally expensive: you’re duplicating infrastructure, staff time, and family communication.

Integration means your existing afterschool programs serve both purposes. Students get enrichment, and those with absences also accumulate AR minutes during the same sessions. One enrollment process, one data system, one set of staff. More efficient, but the compliance tracking is harder.

For most districts, integration is the better path — if you already have the right pieces in place. The districts in the strongest position are those whose afterschool programs already use certificated teachers delivering standards-aligned curriculum. For them, AR integration isn’t a new program. It’s an additional data layer on top of what they’re already doing.

Which approach fits depends on your district:

Staffing: If your afterschool programs already use certificated teachers, integration is straightforward. If you rely primarily on classified staff and community partners, you’ll need to add certificated oversight specifically for AR — which may argue for a separate track.
Student population: If chronic absenteeism is high among your afterschool participants, integration captures real revenue. If most of your afterschool students have strong attendance, the AR funding recovery won’t justify the added tracking burden.
Systems capability: Can your data systems distinguish AR-qualifying minutes from general ELP participation within the same session? If yes, integrate. If not, you either need to upgrade your systems or keep programs separate.

Whatever you choose, make it deliberate. Don’t let it happen by accident through ad hoc practices nobody documented.

Documentation: The Audit Reality

When a single session counts for both ELP and AR, the documentation bar goes up.

For ELP alone, you need daily attendance rosters, enrollment forms with parent signatures, and evidence that activities align with grant requirements. That’s standard program administration.

AR adds another layer: time logs showing instructional minutes delivered, teacher certification records, lesson plans or curriculum documentation proving academic alignment, and student-level records confirming AR days didn’t exceed caps or total absences.

The difference is stark. Tracking “Student X attended afterschool on March 15” is routine. Tracking “Student X attended afterschool on March 15 for 150 total minutes, of which 110 minutes qualified for AR under supervision of Teacher Y (valid multiple-subject credential), delivering instruction aligned to 5th-grade math standards per lesson plan Z” — that’s a different level of documentation.

If you’re running integrated programs, your systems need to produce both levels of documentation from the same session data. Getting this right upfront saves you from scrambling during an audit.