The Mountain Is Bigger Than It Looks: Why Regulated Programs Stall

Article 3 | Why Heavily Regulated Programs Stall

The first two articles in this series focused on why highly regulated CTE programs often struggle before they ever get off the ground. The first point was that these programs have to be built backward. In aviation, fire technology, public safety, advanced manufacturing, and other regulated technical fields, the regulatory requirements, funding model, delivery structure, and compliance obligations have to be understood before the curriculum is written. If those pieces are treated as details to figure out later, the program usually pays for it later.

The second point was that colleges often ask faculty to carry the wrong load. Faculty are essential to strong curriculum. They know the discipline. They understand what students need to learn. But too often, they are also expected to solve structural questions that are larger than curriculum: regulatory alignment, program architecture, funding eligibility, approval sequencing, high school pathways, transfer considerations, staffing models, facility needs, and implementation strategy. That is not a faculty problem. It is a design problem.

This article is about the next layer. Even if the program concept is strong, even if industry need is real, and even if the curriculum is well written, the program still has to move through the college’s approval process. That process has to be understood, tracked, and actively worked. It cannot just be entered and trusted to move on its own.

That’s what this article is about.

Every dean understands that colleges have local processes. That’s not the issue. The issue is the amount of time, attention, and coordination required to work that process when the program is new, technical, regulated, and tied to outside requirements. The broad rules may be familiar, but the actual path still has to be mapped. The forms matter. The software system matters. The committee calendar matters. The reviewers matter. The deadlines matter. The evidence standard matters. The unwritten expectations matter.

A dean may look at a new program and think, “We can do this in house. We have a faculty member who knows the subject.” And maybe they can. But the subject is only part of the mountain. The rest of the mountain is process, evidence, timing, governance, resources, compliance, outside approvals, and follow-through.

The State Rules Are the Floor, Not the Map

California community colleges operate within a statewide approval framework. The Chancellor’s Office Program and Course Approval Handbook lays out the broad criteria for programs and courses. Is the program appropriate to the mission? Is there a need? Does the curriculum meet standards? Are adequate resources available? Is the program compliant?

Those questions matter. But they don’t tell you how a proposal moves through your specific college.

They don’t tell you which committee needs to see the concept first. They don’t tell you whether the proposal needs to go through planning and budget before curriculum. They don’t tell you how long technical review takes. They don’t tell you when the curriculum committee stops accepting items for the next catalog. They don’t tell you whether a proposal returned for edits goes back one step or all the way to the author. They don’t tell you who is watching the approval system for comments.

That last point sounds small. It isn’t.

In some systems, one missed email or one unnoticed notification can stop a proposal cold. Not because anyone rejected it. Not because the program was weak. It just sits. A reviewer asks for clarification. The system sends a notification. The faculty author is teaching, grading, advising, attending meetings. The message gets missed. A deadline passes. The committee calendar moves on. Summer arrives. The next available approval window is months away.

A program can lose a semester that way. In some cases, a full year or longer. That’s the part people outside the process consistently underestimate. Approval delays are rarely dramatic. Nothing explodes. Nobody says no. The proposal simply doesn’t move. By the time everyone realizes it, the launch window is gone.

Approval Is a Sequence

Most people think of approval as an event. The program is written, courses are submitted, reviewed, and approved. That’s not how it works. Approval is a sequence, and the sequence has to be managed.

A proposal may move from faculty author to department chair, to dean, to technical review, to curriculum committee, to Academic Senate, to planning and budget, to College Council, to the board, to regional consortium review, to Chancellor’s Office submission — depending on the college and the type of program. The order matters. The timing matters. The documentation matters. The local culture matters.

Some colleges map this sequence clearly in a curriculum management system. Others spread the process across board policy, curriculum committee practice, Academic Senate expectations, planning documents, budget review, advisory committee documentation, regional consortium requirements, and Chancellor’s Office submission. Those aren’t good or bad differences. They’re simply differences that matter when someone is trying to move a program from idea to launch.

That’s what gets missed when a new program is treated only as a curriculum-writing project. In California, curriculum must be faculty-driven, and that is how it should be. Faculty bring the disciplinary expertise and academic judgment needed to build courses that actually serve students.

But that does not mean faculty should be left to carry the entire approval and launch process alone.

A faculty member may know exactly what students need to learn, but the program still needs someone working the pathway: tracking system notifications, anticipating review questions, coordinating documentation, watching deadlines, and making sure the proposal keeps moving. Even when faculty understand the process, they may not have the time, authority, or institutional position to chase every step.

That work has to be owned by someone. If it is not, the process owns the program.

The Approval Package Is Bigger Than the Curriculum

Curriculum is often mistaken for the program. Curriculum explains what will be taught. The approval package explains whether the college can responsibly approve, launch, sustain, and evaluate the program. Those are different questions.

A complete program package has to explain why the program is needed, how it aligns with the college mission, what student population it serves, what labor market evidence supports it, what external standards apply, what facilities and equipment are required, who can teach it, how students will move through it, what outcomes will be measured, how much it will cost, what revenue or FTES it may generate, what existing programs may be affected, and what implementation plan will carry the program from approval to launch.

In highly regulated CTE programs, it becomes more complicated still. The college may also have to account for external regulatory agencies, industry certifications, mandated training standards, safety requirements, instructor qualifications, specialized equipment, off-site facilities, student eligibility requirements, and documentation that has to be maintained after the program launches.

There’s also the problem of overlapping approval systems. A program may need to satisfy local curriculum policy, Chancellor’s Office expectations, accreditation standards, external industry or regulatory requirements, and funding-related requirements simultaneously. If the program will serve VA students, veterans education approval requirements may affect how the program is structured, documented, and offered. If students need access to federal financial aid, the program has to be designed in a way that supports those requirements as well. Those layers don’t replace the local process. They sit on top of it.

That’s where regulated programs become especially unforgiving. A college can approve a program locally, but if it doesn’t also meet the external requirements tied to the field, the credential may not do what students were promised it would do. In some programs, the local certificate is only valuable because it leads to an external certification, exam eligibility, licensure pathway, or employer-recognized qualification. If that outside standard is missed, the graduation document may be technically complete but practically worthless to the student holding it.

Emerging Technology Makes the Evidence Problem Harder

The labor market piece is especially challenging in emerging technology fields. Most approval processes expect labor market data — and they should. Colleges shouldn’t build programs on hype or one exciting conversation. Students deserve programs that connect to real opportunities.

But labor market data is historical. It tells us what has already existed long enough to be measured. That creates a real problem when the workforce need is new.

Imagine a company builds a major technical facility near a college. The hiring need is real. The training requirements are real. Maybe the industry even requires specialized regulated training before workers can enter the facility. But on paper, the labor market data may show little or nothing. The occupation may not map cleanly to an existing job code. Standard reports may lag behind the employer’s expansion by years. The data may say there is no need at the exact moment the need is becoming obvious to everyone on the ground.

That doesn’t mean the need isn’t real. It means the standard data is incomplete. And that gap has to be filled carefully — not ignored, and not papered over with optimism.

A strong proposal has to acknowledge the limitation honestly. It has to explain why historical data doesn’t fully capture the emerging demand, and supplement it with real-world evidence: employer commitments, hiring projections, facility expansion documentation, advisory committee input, job postings, industry studies, employer letters, regulatory requirements, and economic development data. That takes time, conversations, and the knowledge of what kind of evidence a college can reasonably rely on.

The absence of clean labor market data doesn’t remove the need to prove demand. It makes the proposal harder to build. That’s one of the places where emerging technology programs are easiest to underestimate.

The Process Is Not the Enemy

It’s tempting to look at all of this and call it bureaucracy.

The approval process exists because colleges are making real commitments. They’re committing public resources, faculty time, facilities, and equipment. They’re putting a program in the catalog. They’re telling students a pathway exists through institutional marketing and recruiting campaigns. They’re telling employers that graduates will be prepared. In regulated fields, they may also be telling an outside agency that the program meets a required standard.

Those commitments shouldn’t be made casually.

I’ve watched programs lose a full year not because anyone rejected them, but because the right questions came too late. That’s not bureaucracy failing. That’s planning arriving after the commitment was already made. By the time someone asks about facilities, the curriculum is already written. By the time someone asks about faculty availability, the launch date is already assumed. By the time someone asks about compliance, the program already has momentum.

That’s when planning becomes rework. And rework is expensive — not always dramatically. Sometimes it’s a missed grant timeline. Sometimes it’s faculty revising courses that shouldn’t have been written yet. Sometimes it’s another catalog year lost. Sometimes it’s an industry partner who quietly loses confidence. Sometimes it’s students who could have been served, still waiting.

The Mountain Is Bigger Than It Looks

This is the thing a dean needs to see before assigning a new regulated CTE program to one faculty member and assuming the work is covered.

Writing curriculum is one climb. Getting the program approved locally is another. Proving need is another. Aligning with Chancellor’s Office expectations is another. Meeting accreditation standards is another. Building the delivery model is another. Finding qualified instructors is another. Securing facilities and equipment is another. Mapping the student process is another. Managing the approval timeline is another. And these aren’t all separate climbs, they usually should be done together, in sequence and parallel.

In highly regulated programs, there are more climbs layered on top of those. VA education benefits bring their own approval structure. Federal financial aid requires the program to be built in a way that supports student eligibility. External certifications, licenses, and regulated workforce credentials mean the outside agency’s requirements have to be mapped over the local and state process from the beginning.

None of those systems care that the others are complicated. They all still have to be satisfied.

That’s what makes these programs genuinely difficult. The dean has to look beyond whether the college has the subject-matter expertise to write curriculum and ask a harder question: do we have the time, capacity, and coordination structure to work this process all the way through while still meeting our other commitments?

That means being honest about what the launch will require. Someone has to track the approval pathway, monitor system notifications, manage committee deadlines, close evidence gaps, coordinate funding and accreditation requirements, verify external compliance, and keep the program aligned with the credential or certification students are being promised.

A strong faculty member can write strong curriculum. A capable dean can support the work. A college can have excellent internal people. But highly regulated CTE programs require sustained coordination across multiple systems, and that work does not happen automatically.

That is not a criticism. It is a capacity question. Before the college commits to launch, someone has to determine whether the institution has the bandwidth to carry the work properly — or whether additional support is needed to keep the program moving without pulling attention away from everything else the college is already responsible for.

This Is A Capacity Decision

The answer is not to skip the process. The answer is to resource it honestly and build for it earlier.

Before curriculum is written, someone needs to map the approval pathway. Before the proposal enters governance, someone needs to know what evidence is required. Before industry partners say they need workers, someone needs to help them understand what documentation the college needs from them. Before a program is described to students, someone needs to map how students will enter, progress, complete, and qualify for the intended outcome. Before a launch date is discussed, someone needs to know whether the curriculum, faculty, facilities, equipment, budget, compliance requirements, financial aid implications, veterans education requirements, accreditation expectations, and evidence of need can actually line up.

That takes focus. It takes sustained attention. It takes someone who is not just generally supportive of the program, but specifically responsible for keeping the structure, evidence, approvals, and implementation pieces moving together.

This is where the dean has to make an honest resource decision. If the college has the internal capacity to do that work, then it needs to be clearly assigned, protected, and tracked. If the college does not have that capacity, then the risk is not that the work will disappear. The risk is that it will be absorbed in fragments by people who are already carrying full-time responsibilities.

That is when things get missed. Not because people are careless, but because no one has enough uninterrupted focus to own the whole launch. A faculty member writes curriculum. A dean answers the most urgent questions. A committee reviewer catches one issue. An industry partner provides informal support. Someone assumes the labor market evidence will be handled later. Someone assumes compliance has already been checked. Someone assumes the proposal is still moving because it was submitted.

That is not a launch strategy. That is drift.

When the work happens early and is properly resourced, everything downstream gets easier. Faculty can focus on building strong courses. Deans can make better decisions. Curriculum committees can review a complete proposal. Industry partners understand their role. Students get a pathway that actually functions. The college also avoids discovering structural problems after the program has already been committed to a shape it may not be able to hold.

The point is not that every college needs outside help for every program. The point is that highly regulated CTE programs require a level of coordination that has to be acknowledged up front. Someone has to own the pathway, the evidence, the compliance alignment, and the timeline. If that work is not assigned and resourced, the program may still move forward, but it will move forward with unnecessary risk.

The Pattern

The pattern is that highly regulated CTE programs are treated as curriculum projects when they’re really system-design projects. They require someone who understands the state framework, the local process, the evidence standard, the regulatory environment, the funding model, the delivery structure, the outside approval requirements, and the implementation plan — and who can hold all of that together before the program is too far down the path to change course.

If you only understand the statewide rules, you may miss the local process. If you only understand the local process, you may miss the external regulatory requirements. If you only write curriculum, you may miss the architecture. If you rely only on historical labor market data, you may miss the emerging workforce need developing right across the street. If you only get the program through local approval, you may still miss the requirement that makes the student eligible for the certification, benefit, or employment outcome the program was supposed to deliver.

That’s how strong ideas stall. Not because the idea was wrong. Because the program wasn’t ready for the process it entered.

Closing

Highly regulated CTE programs do not usually fail to launch because nobody cared. They stall, get rebuilt, or quietly disappear because the work was under-scoped at the beginning.

The approval pathway was not fully mapped. The evidence package was incomplete. The curriculum moved faster than the structure. The compliance requirements were understood too late. The external certification pathway was assumed instead of verified. And sometimes, yes — one missed notification was enough to push the program into the next cycle.

None of that is inevitable, and none of it means a college cannot do this work in house. Many colleges can, especially when they have experienced curriculum leadership, available administrative capacity, strong faculty engagement, clear industry partners, and someone specifically assigned to manage the process from concept through launch.

The key is being honest about whether that capacity exists for this specific program, at this specific moment, with everything else already on the college’s plate. If the answer is yes, the work still has to be clearly owned, protected, and tracked. If the answer is no, the risk is that the work gets absorbed in pieces by people who are already carrying full-time responsibilities.

That is where I start every engagement: with the question of what this specific college needs to see in order to approve, launch, sustain, fund, and evaluate the program while still meeting the outside requirements that make the credential valuable to students.

Not with curriculum. Not with a course list. With the full picture of what it is actually going to take.

If you are working on a regulated program right now, the first question may not be whether the idea is good. It may be whether the launch has been properly resourced, whether the pathway has been mapped, and whether someone has the focus to keep all of the moving pieces aligned.

BlueSky Workforce works alongside community colleges to develop, document, and move workforce programs through approval, with particular focus on highly technical and regulated fields where the external compliance environment adds layers that standard curriculum development was never designed to carry.