Building the Pipeline Together: A Practical Guide for Employers and Educators

What employers and education programs each need from the other, what a working partnership looks like in practice, and how to tell in its first year whether yours is on track.

The short version

Employers that can't fill skilled roles and education programs whose students or participants need a path into work are trying to solve two halves of the same problem. A partnership between them works when each side brings specific information the other can act on, commits only what it can sustain, keeps the people moving through the pipeline at the center, and checks within a year whether it's running as intended.

Lauren McClain, Ph.D.

Lauren McClain, Ph.D.

Co-founder and workforce development consultant, Grantibly

· 14 min read

Key takeaways about employer and education partnerships

What this guide covers

Employers and education programs are working on the same workforce problem from opposite ends

An employer that can't fill skilled roles and an education program whose students or participants need a path into work are working on the same problem, each from its own end.

The employer knows what the work requires, how many people it expects to hire, and where new hires struggle. The program knows what it teaches, who is enrolled, when they finish, and how long it takes to change a course. Neither side can see the whole problem from where it sits, and neither can solve its half alone.

What the employer holds

Knowledge of how the work is done today, the roles it expects to fill, current equipment and software, and the supervisors and mentors who will train new people.

What the education program holds

The curriculum and the people who teach it, the students or participants and their circumstances, the academic calendar, and the approval process that governs any change to what is taught.

What neither holds alone

The experience of the people moving through the pipeline: how they found the program, what nearly kept them away, what happened in their placement, and why some of them left.

That's why this guide is written for both readers at once. An employer will find what an education partner needs in order to act, and an educator will find what an employer needs in order to stay involved. Both will find the part that is easiest to leave out: the students, participants, and new employees who move through the pipeline, whose experience shapes whether the arrangement produces anything at all.

The two sides are also expected to talk. Perkins V, the federal law that funds career and technical education, requires the school districts and colleges that receive its funding to assess whether their programs meet local needs and to update that assessment at least once every two years.

In that assessment, districts and colleges must consult, among others, the local workforce development board and "a range of local or regional businesses or industries." The same section says ongoing consultation may include employer input on curriculum, credentials, and "current technology and equipment," along with finding opportunities for work-based learning.

So an employer's call may be more welcome than it expects, and an educator asking employers for input is doing what the law already anticipates. What the law can't supply is what the two sides say to each other, which is what the rest of this guide is about.

An employer-education partnership can stall when each side brings a general request instead of a specific need

An employer-education partnership can stall when each side brings a general request, such as a complaint about graduates or an invitation to a committee, instead of a specific need the other side could act on.

"Your graduates aren't ready" is a reasonable place to start a conversation, but it rarely tells a program what to change. "Join our advisory committee" is a reasonable offer, but it rarely tells an employer what its time will accomplish. Both sides can leave the meeting with good intentions and nothing either one can use.

Each of these is a gap in information that one side holds and the other doesn't, which also makes each one something the two sides can address. We start from the problem rather than the program: before an organization invests in a solution, it needs to understand the problem it is actually trying to solve. For a partnership, that means both organizations understanding it, in the same terms, before either one builds anything.

The next two sections describe what each side can bring so the other can act. The section after that describes what the two can build together once they have.

We look at the larger system: How do education, training, employers, communities, and workforce systems interact?

Lauren McClain, Ph.D., Grantibly

What an employer needs to bring to an education partner is specific information about the work and time it can sustain

An employer starting a partnership with a college or school district needs to bring specific information about the work before anything else: the roles it has trouble filling, what the work involves, the skills a new hire needs on the first day, how many people it expects to hire, and roughly when. With that, a program can compare what it already teaches with what the work requires. Without it, the program can only guess.

The person to bring that information to is whoever runs the program that prepares people for the work. Titles vary, but a dean of workforce or continuing education, a program chair, or a school district's career and technical education director are common starting points. How do we start working with a local college or school district on our hiring needs? covers who to contact and what to ask in a first conversation.

Money is the contribution employers often think of first, and it may not be the one a program most needs. Real problems and projects from the workplace, access to current equipment, practitioners who speak to classes, site visits, mentors, work experience placements, honest input on curriculum, and a named person who answers email are hard for a program to find anywhere else.

The contributions an employer can make differ a great deal in what they ask of staff. Speaking to a class takes an hour, while hosting an intern takes months of a supervisor's attention. What can an employer actually contribute besides money? sorts them by that cost.

The larger contributions depend on the employees who make them. A mentor or host needs time set aside, some preparation, and support from their own supervisor, because mentoring added to a full workload tends to shrink to whatever time is left over. Programs and employers can share that load by building systems of support, so that no single mentor has to be everything to every student or participant.

Whether the staff time is worth it is a fair question. The answer depends on whether the employer hires regularly for roles a nearby program prepares people for, whether it can wait for results on an academic timeline, and whether it can keep its commitments after the first burst of interest. Is a school partnership worth the staff time it will cost us? works through that decision, including the smallest version worth trying.

A question for employers before investing in a pipeline

Instead of asking only "How do we recruit more workers?", ask: "Are there organizational conditions causing us to continually replace people we have already recruited and trained?"

If new employees are leaving, a partnership will increase how many people an employer brings in without changing why they go. Why do good employees keep leaving when we pay competitively? looks at what is often behind that.

What an education program needs to bring to an employer is an honest picture of what it teaches, who it serves, and how fast it can change

An education program working with employers needs to bring an honest picture of itself: what it teaches now, who its students or participants are, when they finish, and how long it takes to change a course or add a program. An employer that expects a new course next semester can lose patience when the change has to go through an approval process and wait for the academic calendar.

Explaining early how that process works, and what can happen sooner, keeps expectations realistic on both sides.

The second thing a program brings is better questions. When employers say graduates aren't ready, the useful response is to ask for specific situations: what a recent hire struggled with, what happened, how often it happens, and what a well-prepared new hire would have done instead.

Ask the frontline supervisors who work with graduates every day, and ask the graduates themselves, since the manager who attends meetings often hears about problems secondhand. Then sort what you hear by who is in a position to address it.

A skills gap

Something the program can teach and give students or participants practice in.

An equipment gap

Tools or software the program doesn't have, which an employer may be able to lend, donate, or let students use on site.

A supervision gap

How new hires are trained and supported on the job, which the employer controls.

Feedback is only valuable if the program is prepared to do something with it. Telling employers what was heard, what the program will change, and what it can't change is what keeps them willing to answer the next time they are asked. Employers keep saying our graduates aren’t ready. How do we find out what they actually need? walks through the questions and the sorting in detail.

Programs also make choices that depend on what employers know. Which certifications to build training around is one: a sound method starts from the jobs students or participants can realistically get in the region and works back to what those employers require, prefer, or recognize, as choosing the certifications to build training around explains.

Whether a short credential will help someone get hired is another such choice, and the independent evidence on whether micro-credentials help people get hired is thinner and more mixed than much of the marketing suggests. Local employers are part of the answer to both.

The relationship runs in both directions. Many colleges and training providers offer training for an employer's current employees, and a working relationship gives an employer an earlier look at the people entering its field. Upskilling your people through a college or training partner covers how that works, from who pays to who owns the curriculum.

A working employer-education partnership starts small, names who is responsible on each side, and decides early what it will look at

A working employer-education partnership can start small, with a responsible person named on each side and an early decision about what both will look at, and then grow from what they learn. One role the employer hires for regularly, one program that prepares people for it, and one or two contributions the employer can sustain for a term or a year are enough to learn from.

The steps below describe that shape, and they apply whether the partnership begins with a guest speaker or with work experience placements.

Apprenticeship is one form a partnership can take, and a highly structured one. The U.S. Department of Labor describes Registered Apprenticeship as a paid job with progressive wage increases, structured on-the-job learning with an experienced mentor, supplemental classroom education, and a portable, nationally recognized credential, and it encourages employers to build programs with "workforce organizations, educators, and others."

Whether to start an apprenticeship is a decision of its own, covered in Should we start an apprenticeship program?, and what a registered apprenticeship actually involves has its own page.

Internships, job shadowing, and site visits are smaller steps that let both sides learn how much mentoring the employer can sustain before committing to more. The companion guide on work-based learning goes further into how placements and mentoring are designed.

Employers and educators won't always want the same things from a partnership. An employer may want candidates soon, while a program wants a stable relationship that shapes its curriculum over several years. When the two sides see the problem differently, the conversation itself may need help, and How do I get partners with different priorities on the same page? covers how that is done.

Students and participants are the people a pipeline is built for, so their experience belongs in the partnership's design

Students and participants are the people a pipeline is built for, and their experience is the part of an employer-education partnership most easily left out. An employer and an educator can agree on roles, curriculum, and placements and still lose people at every stage, because many of the reasons people enter, stay in, or leave a career path sit outside anything the partnership discussed.

Choosing a career path is rarely one clear decision. It's shaped by what students have been exposed to, whether they have seen someone doing the work, the people around them, practical conditions such as cost and schedules, and how they see themselves and who they think they could become.

Employers can help with that exposure directly, by letting students meet the people who do the work before they have to decide. How do students actually end up choosing a career path? looks at those influences and at reaching students who have never met anyone in the field.

Before enrollment

Students who have never seen anyone do the work may not treat the field as an option at all.

During the program

Work schedules, cost, the timing of financial aid, transportation, and childcare can make finishing hard to sustain. See why students start a program and don’t finish.

In the placement

A mentor with no time, work that is trivial or unsupported, and unclear expectations can push interns and apprentices out. See why interns and apprentices aren’t sticking.

After the hire

New employees who don't feel supported, or don't see a way to grow, may leave, and the pipeline then replaces them.

Angelika Gulbis's work on student persistence makes a point that applies at every one of those stages. Persistence is better seen as a capacity that can be built than as a fixed trait. Many students face real barriers, such as financial pressure, competing responsibilities, and environments where they don't feel they belong, and institutions are responsible for addressing them.

Support shouldn't mean rescue, though, and that holds for employers hosting placements as much as for schools. The aim is high expectations paired with meaningful support, so that students or participants build the ability to work through the next challenge themselves.

Which reasons apply in a given partnership can't be assumed. The people who left, the people who stayed, and the mentors who worked with them can each describe part of what happened, and asking them in a way that lets them answer candidly is how a partnership finds out.

Evidence from those conversations also helps settle a common question. A program whose seats fill but whose students leave before finishing gains little from recruiting more people into the same conditions, and Should we spend our effort recruiting more students or keeping the ones we have? shows how to tell from records a program already keeps.

Employers and educators can tell within a year whether a partnership is on track by checking how it runs before judging its outcomes

Employers and educators can tell within a year whether their partnership is on track, even though the outcomes they care about most, such as hires who stay and advance, can take several years to appear. In the first year, the more useful question is whether the partnership is running as the two sides intended, because outcomes are hard to interpret without knowing what students or participants received.

Commitments

Did each side do what it agreed to?

Compare the visits, talks, placements, and curriculum conversations that happened with what was planned, and note what got in the way.

Participation

Who took part, and who didn't?

Look at which students or participants met employers, applied for placements, started, and stayed, and whether some groups are missing.

Experience

What did participants and mentors say?

Ask students or participants about their placements, and ask mentors and supervisors whether they had the time and preparation the role needed.

Response

Did anything change because of what was learned?

Check whether the program adjusted what it teaches or the employer adjusted how it supervises, and whether each side heard back from the other.

Numbers and conversations do different work here. Records can show that one group finishes less often, or that several people leave a placement at the same point. The people involved can help explain why. Used together, they give both sides a much more complete picture than a completion rate alone. So instead of asking only whether the partnership worked, we would ask what worked, for whom, under what conditions, and what evidence supports that conclusion.

Two cautions keep that look honest. A rise in hires from the program doesn't by itself show that the partnership produced it, since the labor market, the program, and the students are all changing at once. And a disappointing first year doesn't automatically mean the idea was wrong, because the partnership may not have been carried out as planned, or participants may not have received enough of it.

Designing that kind of look, including whom to ask, what to ask, and how to protect people's ability to answer candidly, is work an evaluator does with you. How do we know whether our work-based learning program is working? describes what it covers for a work-based learning program.

The Grantibly perspective

Lauren's perspective

Grantibly's workforce development expertise has primarily developed through the education and training side of the workforce ecosystem. We have evaluated federally and privately funded programs designed to prepare people for high-demand careers, including programs in advanced manufacturing, cybersecurity, technical education, apprenticeships, and other career pathways.

That work has given us a close-up view of the entire education-to-workforce pipeline: how people are recruited into career pathways, what helps them persist, where they encounter barriers, how employers and educators work together, and what happens when the systems intended to support workers do, or do not, work as intended.

We do not approach workforce challenges as an HR problem alone. We approach them as a people, data, and systems problem.

Our role is not to walk into a partnership assuming we already know what is wrong or what each side should do about it. Our role is to help find out. We would rather help employers and educators understand what the evidence shows, and what it does not, than make unsupported promises about what a partnership will return.

Workforce development does not end when someone gets hired. Getting people through the door is only part of the challenge. And whatever a partnership learns shouldn't end up in a report that sits on a shelf. It should lead to priorities, conversations, decisions, and action.

What building a workforce pipeline together comes down to

An employer and an education program each hold half of a workforce problem. The employer knows the work, and the program knows its students or participants and the calendar it runs on.

A partnership starts to work when each side brings specific information instead of a general request, commits only what it can sustain, and pays attention to the people moving through the pipeline at every stage, from the first time they hear about a field to their first year on the job.

None of that has to start large. One role, one program, one or two contributions, and an agreement about what to look at in the first year are enough to begin. What the two sides find out in that year tells them which commitments to keep, which to change, and whether a larger partnership is worth the time it would take.

More questions about employer and education partnerships

Should an employer or an education program make the first move in a partnership?

Either an employer or an education program can make the first move in a partnership, and the side with the clearer need is often the one to call. An employer that hires repeatedly for a role can contact the program that prepares people for it. A program that receives federal career and technical education funding already has to consult local businesses, so it has its own reason to reach out. Arriving with something specific matters more than who calls first.

Does an employer-education partnership need a formal agreement?

An employer-education partnership doesn't need a formal agreement to start, since a guest speaker or a site visit can be arranged by email. A written agreement becomes worth having once the partnership involves placements, shared equipment, customized training, or curriculum one side helped build, because those raise questions about supervision, cost, and who owns what. A registered apprenticeship has its own written requirements, covered in the Insight Library's page on what a registered apprenticeship involves.

Is an employer advisory committee the same as an employer-education partnership?

An employer advisory committee can be one part of an employer-education partnership, but it's rarely the whole of one. A committee can give a program useful input on what it teaches. Its members are often managers who hear about new hires' struggles secondhand, though, and a meeting seldom leaves time for the follow-up questions that make a complaint specific. Frontline supervisors, graduates, mentors, and placements add what a committee meeting can't.

Can a small employer take part in a partnership with a college or school district?

A small employer can take part in a partnership with a college or school district by starting with one contribution it can sustain, such as a site visit, a guest speaker, or input on one course. Hosting placements takes more supervisor time, so it may come later. A need described by several employers in the same field can carry more weight with a program than one employer's request, so joining with others who hire for similar work can help.

Will a partnership with a college or school district fix our employee turnover?

A partnership with a college or school district is unlikely to fix employee turnover on its own, because it changes how people arrive rather than what happens after they do. If new employees are leaving, the useful first step is finding out where people are leaving, for whom, and why. A partnership works best alongside that look at what happens once new hires start.

Who can help when an employer and an education program want different things from a partnership?

When an employer and an education program want different things from a partnership, a facilitator from outside both organizations can help them agree on the problem, set priorities, and decide on next steps. At Grantibly, our Insight-to-Action Facilitation does this for partners with competing perspectives, and our Data-to-Action Roadmap helps when the two sides aren't yet sure what kind of support they need.

Related guides

Related reading in the Insight Library

Lauren McClain, Ph.D.

Lauren McClain, Ph.D.

Lauren McClain, Ph.D. is a co-founder of Grantibly and a workforce development consultant who develops the workforce through evaluation, training, facilitation, and strategic planning. A sociologist and former faculty member at Savannah State University and Western Kentucky University, she taught more than 50 social research methods courses, mentored more than 21 thesis and dissertation committees, and served on three Institutional Review Boards. Her work helps organizations use evidence to understand what is happening, decide what to do next, and do MORE good.

grantibly.com

Tell us what you're trying to understand

Schedule a consult Meet Lauren and Angelika