Two years ago, you sent one of your best surgical aides to the community college's surgical technology program. She finished, passed her certification exam, and took a job forty minutes away, at a hospital paying two dollars more an hour. You didn't pay for her training. You also have nothing to show for it.
That outcome isn't rare, and it isn't really about training quality. It's about what happens to the relationship between a hospital and the person it's developing, and who controls that relationship while the training is happening.
The outside path, honestly described
When a hospital sends an employee to an outside surgical tech or sterile processing program, that employee becomes a student on someone else's calendar. They compete for a limited number of seats, often at programs concentrated in urban areas far from the hospital itself, a supply problem we've covered in more depth elsewhere, sometimes waiting six months to a year for the next cohort to open. During the program, they usually aren't earning a wage tied to your hospital, and there's no formal agreement connecting their training back to you. Once they're certified, they're free. If a nearby system offers more money, nothing structurally holds them to the hospital that got them there.
None of this makes community colleges bad partners. Many hospitals rely on them well, and for plenty of roles they're the right answer. The problem shows up specifically when a hospital needs the people it develops to actually stay.
Why "better curriculum" isn't the fix
The instinct at this point is to look for a stronger program: better instructors, a bigger name. It's worth being direct about why that doesn't solve the underlying issue. Surgical technologists are certified through the same two national bodies, NCCT and NBSTSA, no matter who delivers the instruction. Sterile processing technicians go through HSPA, the field's dominant certifying body, with more than 40,000 members and certification holders. A community college program and an employer-run apprenticeship are both, in the end, preparing someone for the same national exam. If a claim about why one program is better would still be true with "the community college" swapped in for any other provider's name, it isn't describing a real advantage. It's describing a level playing field.
Norton Healthcare in Louisville ran into this directly. Despite an existing partnership with a local community college's surgical technology program, the health system still couldn't close its surgical tech shortage, so it built its own in-house apprentice program: six weeks of didactic training and simulation lab work, followed by a six-month OR preceptorship. Norton is a six-hospital system with its own clinical education staff to design and staff a build like that. Most rural hospitals don't have a training department to spare for a project like that, which is exactly the gap between wanting an in-house apprenticeship and being able to stand one up.
What actually changes when the apprenticeship is in-house
An employer-run apprenticeship changes three things, and none of them are about the coursework. The apprenticeship is registered with your hospital as the sponsor, and that's the legal structure that makes the rest possible:
- The hospital selects the candidate instead of accepting whoever enrolls.
- The apprentice is a paid employee of the hospital from day one, not a student paying, or not paying, somewhere else.
- The arrangement is a job, with wage progression and a direct stake for both sides in the outcome.
That's a very different starting point than a certificate with no employer attached to it.
That structure shows up in the numbers. According to the U.S. Department of Labor, registered apprenticeship completers nationally retain employment with their sponsoring employer at a 91% rate, with an average completion wage of roughly $50,000 a year. Those figures aren't healthcare-specific, and every hospital should ask how they play out in its own market, but they reflect what changes when training and employment are the same relationship instead of two separate ones.
What it takes to run this
You bring the candidates and the clinical floor to train them on. We bring the rest, already assembled, instead of something your hospital has to build from scratch:
- Sponsorship: We handle it, so the apprenticeship is registered and administered at the program level.
- Braided funding: We layer workforce dollars, such as CTE (career and technical education funds) and WIOA, together, so the cost to the hospital stays low when the funding stack clears.
- A curriculum partner: We bring in the partner who delivers the actual instruction.
- A compliance system: Craft Connect, where your staff log hours and progress, and pull the reports funders require.
Most rural hospitals don't have a team sitting idle to register programs, chase funding streams, vet curriculum partners, and build reporting. We're that team, already assembled.
What this means for your hospital
If your current pipeline runs through a community college, you don't necessarily need to walk away from it. What's worth asking is who actually controls the outcome once someone finishes: who chose them, who employed them while they trained, and what happens if a competitor calls the week they get certified. If the honest answer to that last one is "nothing we can do," the fix isn't a better program. It's the infrastructure behind it, built once so you don't have to build it yourself.
Tell us your highest-cost open role and the people you already have on staff who could grow into it. We'll come back with a draft pathway and a funding map, usually within a 30-minute conversation.
.webp)