District residency programs don't have a data problem because they're poorly managed. They have a data problem because they sit at the intersection of two institutional systems — K-12 district operations and EPP accreditation requirements — that were built completely independently of each other.
Neither system was designed for what a district residency program actually does. And no amount of effort on the operational side can fix a structural problem.
This post is for the coordinators and program managers running district-based residency programs who are spending a significant portion of their time managing data infrastructure that should be invisible. The problem is real, it's widespread, and it has a name.
A Model That's Growing — And a Data Problem That's Growing With It
Teacher residencies are gaining significant traction as a high-quality preparation pathway. According to the Learning Policy Institute's 2025 analysis, 23 states, including the District of Columbia, had created or supported teacher residency programs in state-level policy as of 2024. The National Center for Teacher Residencies reports its broader community — spanning both its Network and Residency Design Academy — covered 30 states in 2024–25 and partnered with over 650 districts and charter schools.
That growth is well-earned. Residency-prepared teachers retain at higher rates, fill shortage areas at higher rates, and report stronger preparation than fast-track alternatives. The model works. The data infrastructure supporting it, in most programs, does not.
System 1 — What the District's Tools Track (And What They Don't)
District HR systems, student information systems, and payroll platforms were built for district operations. They track headcount, assignment location, compensation, attendance, and employment status. They do this well.
What they do not track: clinical practice competencies. Observation records. Evaluator sign-offs. Candidate milestone progression. Hours logged against state certification minimums. InTASC standards alignment.
A teacher resident exists in the district's HR system as an employee — a paraprofessional, a stipend recipient, or a contracted worker, depending on the program model. That record contains everything the district needs operationally. It contains almost nothing that an EPP needs for CAEP Standard 2, which requires clinical partnerships and practice to be documented with structured evidence of candidate development.
The two records — the district's employment record and the EPP's candidate record — describe the same person. They almost never talk to each other.
System 2 — What EPP Reporting Requires (And Why District Data Doesn't Map)
State EPP reporting requirements and accreditation frameworks were designed for university-based programs. The data fields, reporting structures, and evidence categories reflect how a college or university operates a teacher preparation program — not how a school district does.
CAEP's Quality Assurance System standard requires relevant, verifiable, representative, cumulative, and actionable data. Title II federal reporting requires program-completer data organized by preparation route, certification area, and outcome metrics. Both frameworks assume a single institutional operator with a unified candidate database and standardized documentation processes.
District residency programs don't operate that way. Candidates are simultaneously district employees and EPP candidates. Mentor teachers are district staff, not university supervisors. Placements are determined by district staffing needs, not program convenience. The data structures on each side don't align, and the translation work falls on the coordinator every reporting cycle.
System 3 — The Unofficial System That Fills the Gap
Because neither the district's tools nor the EPP reporting framework covers everything, most district residency programs develop a third system: the coordinator's own collection of spreadsheets, shared drives, tracking documents, and manual workarounds. This unofficial system exists because it has to. It's the only place where all the data actually lives together.
It works — until it doesn't.
The coordinator who built it leaves. The shared drive reorganizes. The spreadsheet formula breaks. The accreditation reviewer requests candidate-level clinical practice data organized by cohort and placement site, but the unofficial system was never designed to produce that output cleanly.
The Learning Policy Institute's 2025 research on successful teacher residencies identifies well-developed data practices as a key factor in program sustainability and in demonstrating outcomes to funders and policymakers. Programs without a structured data infrastructure struggle to make the case for continued investment — regardless of how strong their actual outcomes are.
Why This Problem Is Harder Than It Looks
The structural mismatch isn't solved by choosing better tools from either the district or EPP side. The district won't rebuild its HR system for a residency program. The university's EPP platform wasn't designed for district-based employer workflows. Both sides have legitimate tools for their own contexts. Neither covers the intersection.
The programs that solve this problem stop trying to bridge two incompatible systems and instead adopt a purpose-built layer designed specifically for the intersection — one that tracks what the district needs operationally and what the EPP needs for accreditation, without forcing either side to restructure. That's precisely what Craft is built to do: manage the full candidate lifecycle across the LEA-EPP partnership, with role-based access for district staff and structured reporting that satisfies accreditation requirements without manual translation.
Name the Problem Before You Can Fix It
District residency coordinators are often excellent at their jobs. The data problem they face isn't a sign of poor execution — it's a sign of operating at the intersection of two systems that weren't designed to work together.
The first step is recognizing that the problem is structural. The solution has to match that diagnosis.
.webp)