If you’re trying to grow work-based learning (WBL) in a school or district, you’ve probably felt this already: the ambition makes sense, but the execution gets messy fast. Students need more relevant learning. Employers want stronger talent pathways. Communities want better connections between school and work. Most people don’t need convincing that high-quality work-based learning matters.
But too often, schools try to grow work-based learning while coordination sits with a small number of people, sometimes just one. Educators find themselves supporting students, communicating with employers, managing paperwork, and trying to maintain quality, on top of everything else they already carry.
When that’s the situation, the instinct is understandable: we need more people. More staff equals more capacity. But here’s what 25 years of building work-based learning ecosystems at GPS Ed has taught us: simply hiring more people will not necessarily get you to more or better work-based learning. The real opportunity is to look deeper at the systems underpinning this work.
Capacity Is People, Process, and Technology—Not Just Headcount
Work-based learning capacity is not just a staffing issue. It’s a systems issue. And that distinction changes everything about how you approach it. True capacity in work-based learning is built across three interconnected dimensions:
- People: The right roles with clear ownership, shared responsibility across partners, and leadership aligned around a common vision. This is where most districts start, and where too many stop.
- Process: Documented, repeatable workflows for employer outreach, student placement, communication, compliance, and quality review. Without strong processes, even the most dedicated staff can’t always hold programs together.
- Technology: Tools and systems that reduce administrative burden, support data collection, and free up staff to focus on the relationship-building and student support work that only humans can do.
When one of these dimensions is weak, the others buckle under the pressure. We can hire more people. But if the underlying processes and technology are fragile, we’re just asking more people to hold more things together by hand. (Read the second post in this series on personal heroics in WBL to learn more.)
Here’s a simple example. An employer comes in to speak with students. Everyone leaves feeling good about it. But if there’s no process to capture what students took away, no clear follow-up, and no next step attached to that experience, the value stays mostly anecdotal.
Now compare that to the same moment with one small systems change: students complete a quick exit ticket. A few identify a real interest in that pathway. The school now knows who to connect to what. The employer hears that their time mattered. The next step is clear. That’s not a complete redesign. That’s a light-touch process improvement that makes the experience more meaningful and more repeatable.
The Right First Step Is an Assessment, Not an Expansion
If your team is stretched, the most powerful next move usually is not to do more. It is to assess your system. This assessment doesn’t have to be overly complex; there are a few simple questions to get you started:
- Where is your work-based learning infrastructure strong? Where is it fragile?
- What’s documented and repeatable? What’s still informal?
- Who owns what? Where is coordination falling back on one person?
- What support, in people, process, or technology, is missing?
That kind of honest assessment is the foundation of real capacity. And it’s where every durable work-based learning system starts.
If you’d like to go deeper in understanding your capacity across people, processes, and technology, take our Make School Work Readiness Survey™ in our Resources and Tools section.
This post is the first in our three-part series on work-based learning capacity. Next, read Is Your Work-Based Learning Program Running on Heroics? and How to Build Work-Based Learning Capacity That Actually Lasts.
Written By

Stephanie Loeck
Vice President of Strategic Development


