What EPPs Need Beyond Accreditation Software

Educator preparation providers already know how to manage evidence.

They collect candidate artifacts, track field placements, document supervisor feedback, and prepare for accreditation, licensure, and institutional review. That work matters because accreditation depends on evidence of candidate learning, clinical practice, and program quality. CAEP standards center on clinical partnerships and practice, including shared responsibility for clinical preparation, clinical educators, and clinical experiences.

Accreditation, portfolio, and field placement tools were built for that job: organizing evidence, assessing candidate work, managing placements, and supporting licensure progress.

But work-based learning, especially a registered teacher apprenticeship, adds a different operating requirement.

For an EPP, a Registered Apprenticeship Program is not simply another placement or residency format. It is a structured workforce pathway validated by the U.S. Department of Labor or a State Apprenticeship Agency. Apprentices receive paid work experience, mentorship, classroom instruction, progressive wage increases, and a portable credential. Federal apprenticeship standards also require sponsor responsibility, on-the-job learning, related instruction, performance evaluation, progress records, and a progressively increasing wage schedule.

That is where EPP teams start to feel the gap between accreditation evidence and pathway operations.

What accreditation software is designed to do well

Accreditation software is usually built around the institution and its evidence requirements.

It helps an EPP answer questions like: Can we show that candidates are meeting standards? Can we collect evidence across coursework and clinical practice? Can supervising teachers and faculty assess candidate work? Can we prepare documentation for review?

Those are serious jobs. Apprenticeship does not make them less important.

In a traditional teacher preparation workflow, a placement system may show where a candidate is assigned, which supervising teacher or mentor is involved, what the candidate submitted, and whether evaluations are complete. Portfolio and assessment systems may help the institution collect artifacts, score rubrics, and report learning outcomes.

For accreditation, that is often the point: organize the evidence and make program quality easier to prove.

The issue is not that accreditation software is unnecessary. The issue is that registered teacher apprenticeship asks the system to support a broader work-based learning pathway.

What registered teacher apprenticeship adds to EPP operations

A registered teacher apprenticeship has to connect candidate learning, district work, wages, and evidence-ready records.

That means an EPP may need visibility into on-the-job learning or on-the-job training hours, Related Technical Instruction (RTI), mentor teacher or supervisor sign-offs, competency progress, wage progression, sponsor responsibilities, and state or federal reporting. RAPIDS, the Registered Apprenticeship Partners Information Database System, is used in many states as the case management platform for apprentices, occupations, job openings, and related program information.

The U.S. Department of Labor’s RAPIDS documentation shows the broader data model. RAPIDS captures program-level information such as occupations, wage scales, related technical instruction, program dates, completion data, and points of contact. It also captures apprentice-level data, including occupation, wage information, apprenticeship dates, completion data, and certificates.

That is more than most EPPs need for a traditional field placement or clinical experience.

An EPP may show that a candidate completed a placement. But can the program also show how many apprenticeship hours were completed, whether RTI is on track, which competencies were verified, which partner needs the next update, and what evidence the sponsor needs?

That is a different job.

Where the gap shows up for EPP teams

The gap usually becomes visible after launch.

At the beginning, the model may look straightforward. The EPP has courses. The district has teacher apprentices. Mentor teachers are assigned. The pathway is approved.

Then the day-to-day work begins.

Someone has to reconcile hours from one place, coursework from another, mentor feedback from a third, and wage or employment information from somewhere else. Staff start using spreadsheets to connect what the systems do not. Missing approvals become normal. Reports take longer than expected. Data has to be cleaned before anyone can use it.

This is not just hypothetical. Education, apprenticeship, operations research found that active education work-based learning programs, including teacher apprenticeships, often rely on manual transcription, paper-based tracking, spreadsheets, email, shared drives, and disconnected systems to coordinate across districts, EPPs, state apprenticeship agencies, intermediaries, and other partners. The same research identified granular tracking, wage progression, mentor feedback, reporting, and cross-partner coordination as major post-launch burdens.

The problem is not always a lack of data. Often, the data exists somewhere.

It is just scattered across systems that were never designed to work together for apprenticeship.

Why “we already track placements” is not the same as apprenticeship tracking

Field placement tracking and apprenticeship tracking overlap, but they are not the same.

A placement system can help an EPP manage assignments, supervising teachers, observations, evaluations, and fieldwork documentation. That is valuable. But apprenticeship management has to answer broader operational questions.

Is the teacher apprentice accumulating the required on-the-job learning hours? Is RTI complete or still in progress? Are mentor teachers or supervisors verifying competencies on time? Can the sponsor see what they need? Is the EPP maintaining records for state, federal, funder, or accreditation reporting? Are wage or employment milestones clear to the partners responsible for them?

Those questions matter because teacher apprenticeship is not only an academic experience. It is also a regulated work-based learning model.

Federal apprenticeship standards recognize time-based, competency-based, and hybrid approaches, but each still requires defined on-the-job learning, related instruction, evaluation, wage progression, and progress records.

When EPPs treat teacher apprenticeship as a variation of field placement, they can underestimate the operational load of running the pathway over time.

What EPPs should ask before relying on an existing system

Before assuming an accreditation or portfolio system can support apprenticeship, EPP leaders should ask:

• Can the system track on-the-job learning hours in a way that is easy to review and report?
• Can it connect RTI progress with workplace progress?
• Can mentor teachers, districts, sponsors, and program administrators each see what they need?
• Can it maintain apprenticeship records without weeks of manual cleanup?
• Can it make competency progress visible across partners?
• Can it help the EPP and district partner work from the same source of truth?

If the answer is “not really,” the program may need more than an accreditation tool.

It may need an apprenticeship-ready data layer.

What EPPs need from an apprenticeship-ready platform

The right platform does not replace every tool an EPP already uses. The LMS, SIS, accreditation workflow, portfolio process, and district partner systems still have jobs to do.

The pain starts when no system owns the work-based learning operating record: who is in the pathway, which hours have been logged, which competencies have been evaluated, which mentor teachers or supervisors have signed off, and what leaders can report without rebuilding everything from spreadsheets.

That is the layer EPPs need: a shared place to manage work-based learning progress across candidates, mentor teachers, districts, sponsors, and program administrators.

Craft Connect helps EPPs manage the day-to-day work-based learning data that becomes hardest to coordinate manually in registered teacher apprenticeship programs. It gives programs four practical ways to turn apprenticeship activity into a clearer operating record:

• Track candidate progress across the pathway. Programs can manage fieldwork, clinical experience hours, on-the-job learning, and RTI visibility in one shared environment.
• Capture evidence as candidates learn on the job. Mentor teachers and supervisors can provide sign-offs, rubric-aligned feedback, and competency updates without pushing the whole burden back onto the EPP team.
• Give each education partner the right view. Institutions, mentor teachers, districts, candidates, and program administrators can work from role-based visibility instead of disconnected spreadsheets.
• Make reporting easier to prepare. Programs can maintain records for USDOL, WIOA, state requirements, accreditation, and program oversight while the pathway runs.

That is the practical promise: Craft Connect gives EPPs and district partners shared visibility into the work-based learning activity happening between systems.

Accreditation software can help prove program quality. Craft Connect helps EPPs manage the work-based learning data behind that quality: the hours, approvals, competencies, partners, and records that make teacher apprenticeship easier to run well.

EPPs that understand the difference will be better prepared to build teacher apprenticeship programs that are not only approved, but sustainable.