Growth is supposed to be good news. Your expanded learning program went from a handful of sites to district-wide. Enrollment doubled. The board’s happy. The state’s happy. But somewhere between year one and year three, the systems you stood up to run the program stopped keeping pace.
This isn’t unusual. California’s Expanded Learning Opportunities Program (ELOP) pushed districts to serve every TK–6 student whose family wanted a spot — and most districts built their operational infrastructure on the fly. Paper forms, spreadsheets, a platform someone found at a conference. It worked when you had five sites. It doesn’t work at ten.
Here are seven signs that your systems haven’t kept up with your program.
1. You can’t answer “how many kids are in the program right now?”
This is the most basic question a superintendent, board member, or site principal can ask. And in a surprising number of districts, there’s no real-time answer. Someone has to pull up a spreadsheet, check with site coordinators, or wait until the weekly report lands.
If you’re running an ELOP or ASES-funded program, you’re already required to track daily attendance for state reporting. Under EC §8483.7, ASES grantees must maintain accurate attendance records and make them available for audit. But “tracking attendance” and “knowing how many kids are in your program at 3:45 on a Tuesday” are two very different capabilities.
When you can’t answer the basic headcount question without delay, every downstream decision — staffing ratios, meal counts, safety protocols — runs on stale information.
2. Weekly reporting takes hours, not minutes
Here’s a pattern that shows up across growing districts: someone on the team starts every Monday at an unreasonable hour, downloading report after report, calculating ADA by site, copying numbers into a master spreadsheet, and assembling the weekly update before anyone else arrives.
If producing a single weekly snapshot requires pulling data from multiple systems and doing manual math, that’s not a reporting process. It’s a data reconstruction project. And it’s fragile — one person out sick, one tab accidentally deleted, and the whole thing breaks.
The CDE’s ELOP reporting requirements aren’t going away. Districts need attendance data, unduplicated pupil counts, and program metrics for annual submissions. A system that makes weekly internal reporting painful will make state reporting even worse.
3. Your attendance system and your SIS live in separate worlds
This is one of the most common — and most expensive — gaps. Your student information system (Aeries, PowerSchool, Infinite Campus) holds the authoritative student record: enrollment status, demographics, emergency contacts, authorized pickups. Your attendance platform holds check-in/check-out data. And the two don’t talk to each other.
The consequences compound fast. Staff manually re-enter parent contact information. Registration forms collect data that already exists in the SIS. When a parent updates an emergency contact with the school office, that change doesn’t flow to the afterschool program. At audit time, you’re reconciling two separate record sets.
CALPADS submissions for expanded learning require student-level data that aligns with your SIS records. If your attendance system isn’t syncing with your SIS, someone is manually bridging that gap — and every manual handoff is a place where data can drift.
4. Registration still lives on paper
Paper registration forms were fine when you had one site and a filing cabinet. They’re a liability at scale. Forms get lost. Handwriting gets misread. Staff spend hours typing parent information into spreadsheets. And there’s no easy way to manage waitlists across multiple sites when enrollment lives in a stack of paper in someone’s office.
Digital registration connected to your SIS eliminates the re-entry problem entirely. A parent provides their phone number or email, sees the programs their child is eligible for, selects one, and signs electronically. The student’s demographic data, contacts, and school enrollment are already there — pulled from the SIS, not re-typed from a form.
For districts managing ELOP waitlists — which can run into the hundreds at high-demand sites — paper-based enrollment makes it nearly impossible to demonstrate active waitlist management to oversight bodies.
5. Staffing decisions are reactive, not proactive
Growing programs need more staff. That’s obvious. What’s less obvious is how you deploy staff across sites when enrollment fluctuates, dismissal times vary, and ratios differ by grade band.
ASES requires a minimum 20:1 student-to-staff ratio per EC §8483.4. ELOP programs follow the same standard. But meeting that ratio isn’t just about having enough bodies — it’s about having the right people at the right sites at the right times.
Districts with real-time pickup and enrollment data can see that a 3:00 PM dismissal frees up staff at one site, and redirect those people to a school five minutes away that releases at 3:15. Without that visibility, staffing decisions happen after problems surface: a site runs short, a ratio gets blown, and someone scrambles to find a sub.
If your staffing model depends on site coordinators texting each other, you’ve outgrown your system.
6. Board members have to “just believe you”
At some point, your expanded learning program will face a board presentation. Enrollment numbers, attendance rates, waitlist movement, cost-per-student, ADA — board members want specifics. And if your data lives across disconnected spreadsheets that only one person knows how to assemble, you’re walking into that room with a credibility problem.
The shift from “trust me, we’re doing things” to “here are the numbers” matters beyond board meetings. CDE’s quality standards for expanded learning emphasize continuous quality improvement, and that requires data you can actually point to. Districts that can pull site-level enrollment, ADA, and program movement from a single dashboard don’t just report better — they make better decisions.
When your frontline staff can pull up data and brief leadership on what’s happening at their site, that’s a sign your systems are working. When only the director can produce a report, that’s a sign they’re not.
7. You’ve already switched vendors once — and the pain didn’t go away
This one stings. You recognized the spreadsheet problem, found a platform, onboarded the team, and eight months later realized you’d traded one set of problems for a different set. The new system produced reports, but they were just another export to copy-paste. No SIS integration. No real-time visibility. Just a slightly fancier spreadsheet.
A failed implementation isn’t a reason to give up on technology. It’s diagnostic information. It usually means one of three things:
- The system didn’t integrate with your SIS. Without that connection, you’re maintaining parallel records — which is the exact problem you were trying to solve.
- The system was built for a different use case. Childcare platforms, recreation software, and generic check-in tools don’t understand ASES/ELOP funding structures, CALPADS reporting, or California-specific compliance requirements.
- The vendor sold a product, not a partnership. Growing programs need a technology partner that understands your specific operational context — your braided funding, your vendor partnerships, your board reporting cadence — not just a login and a support ticket queue.
If the pain didn’t go away after switching, the problem wasn’t the specific vendor. It was the gap between what your program needs and what the system was designed to do.
What better looks like
None of these signs mean your program is failing. They mean your program grew faster than the infrastructure supporting it — which is actually a good problem to have, if you address it.
Better looks like:
- One source of truth that syncs nightly with your SIS, so student data is always current
- Real-time check-in/check-out visible across all sites, so you can answer the headcount question instantly
- Automated reporting that turns a Monday morning data reconstruction project into a two-minute dashboard pull
- Digital registration connected to SIS data, eliminating paper forms and manual re-entry
- Proactive staffing tools driven by enrollment and pickup data, not reactive texting
- Defensible board metrics that frontline staff can pull up and explain, not just the director
The operational demands of California’s expanded learning programs aren’t going to get simpler. ELOP funding under EC §46120 is ongoing, enrollment expectations are rising, and the state’s emphasis on accountability and data-driven improvement is only increasing. Your systems need to keep up.
Sources
- CDE: Expanded Learning Opportunities Program (ELOP)
- CDE: After School Education and Safety Program (ASES)
- CDE: ELOP FAQ
- CDE: Expanded Learning Reporting and Forms
- CDE: Quality Standards and CQI
- EC §8483.4 — ASES Staffing Ratios
- EC §8483.7 — ASES Attendance Records
- EC §46120 — Expanded Learning Opportunities Program
