eurobanks/iStock/Getty Images Plus
North Carolina has been preparing for Workforce Pell since November 2025. Staff from the governor’s office, the Department of Commerce and higher education agencies have been working alongside a national consulting firm to map the state’s programs against the new federal eligibility criteria. After months of that work, the president of the North Carolina Community College System offered a candid preliminary assessment: Roughly 4 percent of the state’s short-term credential programs are expected to qualify. He described himself as “a little bit underwhelmed.”
North Carolina is not an outlier. The Department of Education’s own impact assessment, embedded in the proposed rule for the program published in March, estimates that while more than half of undergraduate certificate programs in certain fields (skilled trades, business, law/protective services and STEM) are expected to pass the required value-added earnings test, fewer than 5 percent of programs in consumer and public services fields will. Lindsey Reichlin Cruse, director of research at the National Skills Coalition, has said plainly that this will not be a “huge sea change” when the “clock strikes midnight in July.” Public comments on the proposed rule closed April 8—but the structural questions this piece raises will not be resolved through that process, because they are embedded in the statute itself.
This is not a rollout problem. It is a design problem. Understanding the difference matters both for calibrating what July 2026 will actually deliver and for deciding what to do with the momentum this program has generated.
To understand how the design problem arose, it helps to understand the legislative vehicle that carried Workforce Pell into law. Congress passed the One Big Beautiful Bill Act through a process called budget reconciliation, which allows the Senate to advance legislation with 51 votes rather than the 60 typically required. The trade-off is that reconciliation comes with strict rules: A nonpartisan Senate official known as the parliamentarian reviews every provision and removes anything deemed a policy change rather than a direct budgetary measure. Those rulings are effectively final. The program that reached the president’s desk was not the program Congress drafted. It was the program that survived.
The original political logic was internally coherent. The House committee report on the 2023 Bipartisan Workforce Pell Act stated the design rationale directly: Because programs would face more accountability requirements than any other Title IV program, lawmakers could justify opening Workforce Pell to all short-term providers, including for-profit colleges and nonaccredited institutions. High guardrails—completion and job-placement rates of at least 70 percent combined with the test of value-added earnings—were the currency that purchased broad access. The two halves were designed as a single bargain.
The parliamentarian broke the bargain in half. The provision allowing nonaccredited providers was ruled a policy change rather than a budgetary one and was struck. Senators reinserted the program without it. Critically, the ruling did not change the accountability requirements. It changed the universe of institutions required to meet them—and that is where the program came apart. What remained were accountability requirements designed for a broad universe, now imposed on a narrow one.
Furthermore, the implementation funding—$160 million over five years in the original stand-alone legislation—does not appear in the final statute. The Department of Education’s own Federal Register notice acknowledged that the July 1implementation date was, as a practical matter, a “temporal impossibility.”
None of this reflects a failure of intention. Reconciliation is a known constraint, and the advocates who worked toward this program for more than a decade had limited control over the vehicle it ultimately traveled through. But the program we are now asking states, governors, institutions and regulators to mobilize for is not the program that a decade of advocacy produced. The two are not the same, and the field will be better served by understanding the difference than by treating the gap as a temporary implementation challenge.
The operational consequences are visible throughout the approval chain. The eligibility process requires governors to consult with state workforce boards to certify program alignment with high-skill, high-wage or in-demand occupations, after which the secretary of education conducts a federal review. That architecture assumes states have outcome data to support those certifications. Most don’t. Research on noncredit program outcomes across eight states found that none of them have complete data on whether graduates went on to pursue or complete further credentials—which is itself a statutory eligibility requirement. Additionally, the typical noncredit occupational training program in most states runs between 15 and 100 clock hours, well below the 150-hour statutory floor, meaning programs that might otherwise qualify will need to be restructured before they can even apply.
Some will argue that narrow eligibility is a feature rather than a flaw—that only the best programs should qualify and the accountability requirements are working as designed. That argument would be more persuasive if the programs best positioned to pass at launch were also those most in need of federal support to reach underserved students. In practice, the programs most likely to clear the earnings test are concentrated in fields that already produce strong labor market outcomes, not necessarily the programs (or the students) the original policy was designed to serve.
The moment, however, does not have to be wasted. Three things are worth pursuing seriously regardless of what July produces.
The first is state data infrastructure. The approval process forces states to confront a gap they have long deferred: Systematic outcome tracking for short-term and noncredit programs does not exist in most states. States that use Workforce Pell implementation as the occasion to build real outcome data systems will emerge with something durable—infrastructure that will serve them through whatever the next federal iteration of Workforce Pell looks like, independent of how many programs qualify in year one.
The second is credentials of value. The value-added earnings framework and the requirement that credentials be stackable are, taken on their merits, the right standards for any short-term program seeking public investment. Very few programs will pass them initially. But asking whether programs meet those standards even informally, even for programs that will not pursue Workforce Pell eligibility—is a useful auditing tool. States and institutions that ask what it would take to qualify will end up with a sharper picture of where their programs are actually delivering economic value and where they are not.
The third is portability and articulation. The requirement that programs prepare students to pursue further credentials, and that credits be accepted toward those credentials, points in the right direction independent of this program. States and institutions that use the compliance process to build real articulation agreements and credit-recognition pathways will have something lasting. Portability is worth pursuing on its own terms. Workforce Pell gives it a deadline and a framework, even if only a fraction of programs ultimately qualify under it.
The concept behind Workforce Pell—federal investment in short-term programs that lead to real jobs and real wages—has genuine merit and a decade of bipartisan support behind it. What arrived in July 2025 is a constrained iteration of that concept, shaped less by deliberate design than by the limits of the legislative vehicle that carried it. The guardrails that create the current narrowness point the way toward what a future version needs to solve: restoration of implementation funding, state data infrastructure in place and provider eligibility determined through a proper authorization process rather than a parliamentarian’s ruling.
The field has spent months asking how to implement what it has. The more useful question now is what it wants to have built by the time the next version arrives—and whether it uses this one to get there.
