Federal contractors know the drill: sign a fixed-price contract, sharpen your pencil, pray inflation behaves, and keep a stress ball within arm’s reach. But what happens when the government adds new wage-and-leave obligations midstream and your labor costs jump for reasons no one priced into the original deal? According to a major Civilian Board of Contract Appeals decision, contractors are not always stuck eating those costs like a sad desk salad.
That is the big takeaway from the CBCA’s ruling involving Great Lakes Educational Loan Services and Nelnet Servicing. In plain English, the Board said contractors performing federal work may be entitled to recover added labor costs caused by wage and paid-leave mandates when their contracts include the right Federal Acquisition Regulation clauses. For contractors, contract managers, pricing teams, and in-house counsel, that is a very useful sentence to tape to a monitor.
This case matters because it pushes back on a common government-contract myth: that a fixed-price contract automatically means every later cost increase belongs to the contractor forever, amen. The reality is more nuanced. Fixed-price contracts do shift substantial risk, but they can still contain clauses that reopen pricing when specific legal or labor-cost triggers occur. The CBCA’s decision is a reminder that contract language still runs the show.
What the CBCA Actually Decided
The dispute centered on Department of Education loan-servicing contracts performed by Great Lakes and Nelnet. These were fixed-price contracts, but they were also contracts with labor-related FAR clauses built in. After federal wage and leave requirements were incorporated into the contracts, the contractors sought reimbursement for their increased labor costs.
The CBCA agreed on the core entitlement issue. It held that the contractors could pursue reimbursement for increased costs tied to the federal contractor minimum wage mandate and, at least for Nelnet, increased paid sick leave costs as well. The Board rejected the agency’s effort to treat the fixed-price nature of the contracts as an all-purpose force field against price adjustment.
That point is crucial. The ruling does not mean every contractor can recover every labor increase under every contract. It means a contractor may recover when the contract itself includes clauses that authorize that recovery and when the contractor can tie its added costs to the legal mandate rather than to ordinary business drift, inflation, or wishful accounting.
The Facts Behind the Fight
The underlying contracts dated back years, but in June 2023 the Department of Education modified the contracts to incorporate the federal contractor minimum wage clause and the paid sick leave clause. Once those requirements became part of the deal, the contractors submitted claims for the added costs of compliance. Nelnet’s claim reportedly exceeded $5 million, while Great Lakes sought roughly $197,128.
Those numbers did not appear out of thin air wearing fake glasses. They reflected what happens when legal wage floors move upward after pricing has already been set. For labor-heavy service contracts, even small hourly increases can ripple through payroll, taxes, benefits, and workforce planning. Add paid sick leave obligations on top, and the total can become material fast.
The contracting officer denied the claims, and the dispute went to the CBCA. What followed was a highly practical decision about how labor-law clauses, price-adjustment clauses, and fixed-price contracts interact in the real world.
Why the Board Rejected the Agency’s Main Arguments
1. A Fixed-Price Contract Is Not a Brick Wall
The agency leaned on the classic argument: this is fixed-price work, so the contractor bears the risk of cost increases. That idea is not wrong as far as it goes. The problem was that it did not go far enough. Fixed-price contracts can still allow price revisions when the contract includes clauses that expressly authorize equitable adjustments or other revisions under stated circumstances.
In other words, “fixed-price” is not magic. It is a contract type, not a universal ban on later price relief. If a contract includes a clause that says the price can move when a wage determination or legal labor requirement changes, then the price can move. That is not contract heresy. That is contract reading.
2. The Economic Price Adjustment Clause Did Not Swallow Everything Else
The Education Department also argued that the contracts’ economic price adjustment structure already accounted for labor-cost movement, so the contractors should not get additional reimbursement. The Board was not persuaded. Reading the contract as a whole, it concluded that the economic price adjustment language and the labor-law price-adjustment language served different functions.
That distinction matters. An EPA clause often addresses general market or labor fluctuations that the parties identify in advance. A clause tied to a new wage mandate, by contrast, is aimed at a specific legal trigger. One is about anticipated commercial movement; the other is about compliance with a later-imposed rule. The CBCA treated those as separate lanes, not duplicate parking spots.
3. The “No Contingency” Warranty Did Not Kill the Claim
Another agency argument focused on the warranty language in the wage clause stating that the contract price does not include contingencies for future increases already covered by the clause. The government tried to turn that warranty into a trap door. The Board instead read it sensibly.
The point of the warranty, the CBCA explained, is to prevent double recovery. A contractor cannot pad its original price to anticipate a later adjustment and then come back for the same money again. Fair enough. But that is different from saying the contractor must absorb a later legal cost increase that the clause itself says can support a price adjustment. The warranty blocks double-counting, not legitimate recovery.
4. Paid Sick Leave Costs Were More Complicated, Not Impossible
The paid sick leave piece had an extra twist. FAR 52.222-62 imposes the paid leave obligation, but it does not contain the same neat, self-contained reimbursement mechanism that appears in the minimum wage clause. Even so, the Board concluded Nelnet could still pursue recovery, reasoning that another clause in the contract, such as the wage-adjustment clause or the Changes clause, could supply the path.
That part of the ruling is especially important because it shows the Board was not reading the contract with blinders on. It looked at the agreement as a functioning whole. If one clause created the obligation and another clause provided the pricing pathway, that combination could still support recovery. Federal contract interpretation, at its best, is less “gotcha” and more “how does this deal actually work?”
The FAR Clauses Doing the Heavy Lifting
For anyone tracking this issue, several clauses deserve a gold star and maybe a vacation day. First is FAR 52.222-55, the clause implementing the Executive Order 14026 minimum wage regime for covered federal contractors. That clause expressly contemplates price adjustments for increased labor costs tied to an updated E.O. minimum wage.
Next is FAR 52.222-43, the Service Contract Labor Standards price-adjustment clause for multiple-year and option contracts. That clause is designed to adjust contract prices to reflect actual increases or decreases in applicable wages and fringe benefits, along with certain associated payroll costs. It is not a blank check, but it is real relief when properly triggered and properly documented.
Then there is FAR 52.222-62, the paid sick leave clause under Executive Order 13706. By itself, it is more about compliance than reimbursement. But the CBCA’s reasoning suggests contractors should never stop at the first clause they see. Sometimes the entitlement clause and the money clause are cousins, not twins.
Why This Still Matters After the Revocation of EO 14026
Here is where the timeline gets spicy. Executive Order 14026, which had raised the federal contractor minimum wage, was later revoked in 2025, and the Department of Labor has said it is no longer enforcing that order. So why should contractors still care about a case built around it?
Because contract disputes do not evaporate just because the policy weather changed. The CBCA decision still matters for at least three reasons. First, it addresses claims arising from contract periods when the mandate was in force and incorporated. Second, it reinforces broader principles about interpreting wage-related FAR clauses in fixed-price contracts. Third, it offers a roadmap for future disputes involving other labor mandates, wage determinations, or legally required benefit changes.
Think of the case as bigger than one executive order. It is about the allocation of risk when the government changes the labor rules after award and the contract already contains clauses that speak to that exact problem.
What Federal Contractors Should Do Next
Smart contractors should treat this ruling as both an opportunity and a warning. The opportunity is obvious: if the contract includes adjustment language, recovery may be available. The warning is just as obvious: entitlement without proof is just a very expensive opinion.
Contractors should start with a close clause review. Do not assume a fixed-price label ends the analysis. Check whether the contract includes labor standards clauses, minimum wage clauses, sick leave clauses, Changes clauses, or economic price adjustment provisions. Then read how those clauses interact. The CBCA did exactly that, and contractors should too.
Next comes documentation. Recovery claims need evidence showing the increase was caused by the legal mandate, not by an unrelated pay raise, retention problem, recruiting scramble, or internal compensation strategy. Payroll records, labor mapping, modified wage tables, accrual calculations, and contemporaneous notices to the contracting officer all matter. A shrug and a spreadsheet with mysterious tabs named “final_final_v7” will not do.
Contractors should also watch the limits of recovery. These clauses often allow direct labor increases and certain related taxes or insurance impacts, but not every layer of indirect cost, overhead, or profit. Overreaching can weaken a good claim faster than a bad coffee machine weakens morale.
Practical Examples of How This Plays Out
Imagine a federal call-center contractor with a large hourly workforce. A new wage mandate raises the minimum rate for covered workers. The contract includes the relevant FAR clause. The contractor updates pay, absorbs higher payroll tax costs, and tracks the delta by employee and contract period. That contractor may have a strong reimbursement argument.
Now imagine a different contractor that gives a broad discretionary raise to improve retention, then tries to pin the whole increase on a federal mandate. That is a much tougher road. The clause is not there to subsidize every compensation decision. It is there to address actual increases required by law or regulation as incorporated into the contract.
The same principle applies to paid sick leave. If the contractor can show additional leave-related payroll burdens flowed from a newly incorporated federal requirement, the claim has structure. If the figures are blended with unrelated HR changes and unsupported assumptions, the claim starts to wobble.
Contractor Experiences: What This Looks Like in Real Life
In real contractor operations, wage-mandate costs rarely arrive with cinematic music and a neatly labeled invoice. They show up in payroll reviews, subcontractor calls, revised labor models, and uncomfortable meetings where operations says, “We can comply,” finance says, “At what cost?” and legal says, “Please stop improvising in email.” That is why the CBCA ruling feels so relevant to people who actually live inside federal contracts.
A common experience goes like this: a contractor wins a service contract on a fixed-price basis after carefully modeling labor assumptions, expected attrition, training costs, and compliance overhead. Months or years later, a new wage floor or leave rule is incorporated through an option exercise or modification. Overnight, the contractor is not merely managing inflation. It is managing a legal requirement. Supervisors must update schedules. HR must revise policies. Payroll must change coding. Subcontractors need flow-down instructions. The issue stops being academic very quickly.
Another recurring experience is the internal debate over whether to submit a claim at all. Many contractors hesitate because they worry that asking for money will damage the customer relationship. That hesitation is understandable, but it can also become expensive. The more disciplined approach is to treat reimbursement as a contract-administration issue, not a personal insult. If the contract includes a mechanism for adjustment, using it is not bad manners. It is the point of having the clause in the first place.
There is also the documentation challenge. In theory, proving increased wage costs sounds simple. In practice, it can feel like reconstructing a parade from confetti. Which employees were working on or in connection with the contract? What was the before-and-after pay rate? Which cost increases were legally required, and which were business choices? Did payroll taxes rise in step? Were leave accruals tracked consistently? Contractors that maintain clean labor mapping and contract-specific records usually have a far easier time than those trying to reverse-engineer the answer after a denial lands.
Subcontractor management creates another layer of real-world friction. Prime contractors may be liable for performance while relying on subs that face the same wage and leave obligations. If the prime does not collect timely cost support, the reimbursement file can turn into a scavenger hunt. That is why experienced contractors build notice, backup, and audit-ready recordkeeping into their subcontract administration rather than waiting for a dispute to teach the lesson the hard way.
Perhaps the most relatable experience is the simple frustration of being told a cost increase is “just part of fixed-price risk” when the contract itself contains a clause saying otherwise. The CBCA decision resonates because it recognizes how these contracts actually operate. Yes, contractors bear risk. No, that does not mean the government gets to ignore price-adjustment language when a later mandate increases performance costs. For teams living through these changes, the ruling reads less like a revolution and more like a long-overdue reality check.
Final Thoughts
The CBCA’s message is straightforward: when a federal contract includes the right labor-related adjustment clauses, contractors may recover increased costs caused by wage and leave mandates, even on fixed-price work. That does not eliminate risk, and it does not guarantee payment. But it does confirm that the government cannot wave the words “fixed price” like a magic wand and make the rest of the contract disappear.
For contractors, the lesson is part legal, part operational, and part survival strategy. Read the clauses. Track the costs. Separate mandated increases from ordinary business decisions. Submit clean, well-supported claims. And when someone says fixed-price means “too bad, so sad,” feel free to answer with the most powerful phrase in government contracts: “Let’s read the clause again.”
