Earn-and-learn is easy to support in principle. Most colleges, employers, intermediaries, and workforce organizations already understand why combining work and learning matters. The harder part is making that model work across institutions that were built to operate separately.
That is where many pathways start to slow down.
That framing is also reflected in the Achieve Podcast conversation with Mallory Palisch, but the point matters well beyond one conversation: earn-and-learn pathways usually struggle when institutions share a goal but not a working system.
Not because the idea is weak. Not because the curriculum is wrong. Not because employers are uninterested. Programs get harder to run when each partner is tracking a different part of the learner experience in a different place, with different rules, timelines, and definitions of progress.
A pathway may look aligned on paper. In practice, it can still feel fragmented.
Everyone agrees on the promise. Few systems support the practice.
This is the hidden challenge in a lot of work-based pathways.
Education teams are usually managing courses, academic progress, credit, and student records. Employers are managing hiring, scheduling, supervision, and performance. Workforce organizations may be tracking eligibility, funding, support services, and outcomes. Each part makes sense on its own. The problem shows up when the learner moves across all of them.
One partner tracks coursework. Another tracks job status. Someone else tracks hours, competencies, or mentor approvals. Then someone has to pull the story back together later.
That is not just a reporting issue. It changes how the pathway feels to operate.
When systems stay disconnected, small hand-offs become recurring friction points. A mentor approval is late. A college cannot easily see what happened on the job. An employer cannot tell whether the learner is hitting academic milestones. A workforce team has to chase updates before it can report outcomes. None of these problems sound dramatic on their own. Together, they make a good program harder to sustain.
Why good programs still feel fragile
A lot of earn-and-learn pathways look strong in a pilot.
The curriculum is sound. The employer is engaged. The college is willing to adapt. The early cohort is motivated. But once the model grows beyond a small group, the operational cracks start to widen.
You begin to see the same patterns repeatedly:
- duplicate data entry across partners
- uneven visibility into learner progress
- delayed approvals or missing documentation
- unclear ownership of milestones
- reporting that feels disconnected from actual program quality
This is one reason strong programs can still feel fragile. Too much of the coordination depends on manual effort.
That broader challenge is not imaginary. The Education Commission of the States has pointed to the need for stronger education-to-workforce data alignment, and EDC has highlighted how weak work-based learning data systems limit visibility and improvement. The issue is not that institutions do not care. It is that the infrastructure usually lags behind the model.
Credit for work is not an add-on. It is part of the pathway logic.
This is where many institutions still get stuck.
If a learner is doing meaningful work, but that work does not count toward academic progress in a clear and credible way, the pathway becomes harder to complete. It can also become harder to explain.
That matters in a higher-ed environment where college costs remain substantial. If the learner still has to pay for a full traditional structure while also carrying major work responsibilities, the pathway starts to lose the practical advantage that made earn-and-learn compelling in the first place.
This is not just about convenience. It is about design.
A true earn-and-learn pathway has to connect work, learning, and progress in a way that feels coherent to the person moving through it. If work experience, academic progress, and workforce outcomes all live in separate systems, the learner ends up carrying the burden of integration.
That is usually where momentum gets lost.
Shared data is really shared program design
When people hear “shared data,” they often assume this is mainly a software problem. It is not. It is a program design problem first.
Shared data forces shared decisions.
It means partners have to agree on what counts as progress. They have to align on competencies, milestones, mentor feedback, attendance, work experience, and outcomes. They have to decide what evidence matters and who is responsible for it.
That is why the operational layer matters so much. The goal is not to collect more information for its own sake. The goal is to create one usable picture of learner progress that colleges, employers, and workforce organizations can all act on.
When that happens, better things become possible. Credit for work becomes easier to manage. Reporting becomes a byproduct of program design instead of a separate burden. Employers can see whether the pathway is building the talent they actually need. Colleges can see how work and academics connect instead of treating them as parallel tracks.
That connective layer is also where Craft Education fits. Craft is an apprenticeship data management platform built to help programs manage training, work-based learning, and reporting in one place. When a pathway is moving from promising pilot to repeatable model, that kind of shared infrastructure becomes much more important.
Conclusion
If you are building or scaling one of these pathways, the work is not just launching a program. It is designing the hand-offs so they hold together over time.
That means defining what work should count, naming the milestones that matter across partners, deciding who owns each data point, and making sure learner progress does not have to be reconstructed later from disconnected records.
Most programs do not need more theory. They need better coordination.
That is the real scaling challenge in earn-and-learn: not getting people to believe in the model, but building the infrastructure that helps the model stay coherent as it grows.
.webp)