Limitation of Funds vs Limitation of Cost: Which FAR Clause Applies to You?

Every contracting officer has been there. You're building a contract package, and you reach the funding clause section. You see two options that sound almost identical: Limitation of Funds and Limitation of Cost. Both seem to do the same thing—protect the government from spending more than it has available. So you pick one, move on, and hope you got it right.

But here's the problem: getting this wrong doesn't just create paperwork headaches. It can trigger Anti-Deficiency Act violations, payment disputes, contractor claims, and mission failures. The confusion isn't because these clauses are poorly written. It's because they sound similar but apply to completely different contract scenarios.

This article walks you through a decision-tree framework to determine which clause applies based on your contract type, funding scenario, and risk allocation. By the end, you'll understand not just what each clause says, but when and why to use it.

What Each Clause Actually Does

Before you can choose between Limitation of Funds and Limitation of Cost, you need to understand what each clause is designed to accomplish. They share a common goal—limiting government financial liability—but they operate in fundamentally different contracting environments.

Limitation of Funds (LOF) Overview

Limitation of Funds is used in fixed-price contracts that are funded incrementally. Think of a multi-year services contract where Congress appropriates money one year at a time, but the contract spans three years. You can't obligate funds you don't have yet, so you fund the contract in chunks.

Under LOF, the government's obligation is limited to the amount currently on the contract. The contractor assumes the cost risk for performance within that obligated amount. If the money runs out before the work is done, the contractor must stop work unless the government adds more funds through a contract modification.

This clause is triggered by appropriations constraints, not cost growth. It's about when funds become available, not whether the work will cost more than expected.

Limitation of Cost (LOC) Overview

Limitation of Cost is used in cost-reimbursement contracts. These are contracts where the government agrees to reimburse the contractor for allowable costs, plus a fee. The total cost isn't known upfront because the work involves uncertainty—think research and development or prototype testing.

Under LOC, the government's reimbursement is limited to the estimated cost stated in the contract. The contractor assumes minimal cost risk but has strict notification duties. If the contractor realizes the work will cost more than the estimate, they must notify the contracting officer and provide a revised estimate.

This clause is triggered by cost growth or uncertainty about final cost. It's not about when funds are available—it's about whether the original cost estimate will hold.

Why the Names Sound Similar But the Applications Are Not

Both clauses protect the government from exceeding available funds. Both require the contractor to notify the government when thresholds are approaching. Both create a point where the contractor may need to stop work if additional funding isn't provided.

But here's the critical difference: Limitation of Funds is about incremental funding strategy in a fixed-price environment. Limitation of Cost is about cost uncertainty in a cost-reimbursement environment. One is a budgeting tool. The other is a cost control mechanism.

The Decision Tree: Which Clause Do You Need?

Choosing the right clause starts with three diagnostic questions. Think of this like a flowchart you can walk through during acquisition planning or contract modification drafting.

Start with Contract Type

Is this a fixed-price contract? If yes, you're likely in Limitation of Funds territory. Fixed-price contracts transfer cost risk to the contractor. The contractor agrees to deliver for a set price, regardless of their actual costs. LOF aligns with this structure by limiting government obligation to the funds currently on contract.

Is this a cost-reimbursement contract? If yes, you're likely in Limitation of Cost territory. Cost-reimbursement contracts keep cost risk with the government. The government agrees to reimburse allowable costs up to an estimated ceiling. LOC aligns with this structure by capping reimbursement at the estimated cost and requiring contractor notification if costs will exceed that estimate.

Hybrid or time-and-materials contracts require additional analysis, which we'll address in the scenarios section.

Funding Strategy Question

Are you incrementally funding due to budget constraints or multi-year appropriations? This points toward LOF. For example, if you have a three-year contract but only received one year of funding from Congress, you'll fund incrementally as each year's appropriation becomes available. The clause protects the government from obligating funds it doesn't yet have.

Are you estimating cost with built-in uncertainty or allowance for growth? This points toward LOC. For example, if you're contracting for prototype development and you estimate it will cost two million dollars but you're not certain, you need a mechanism to address cost growth. The clause requires the contractor to alert you if costs are tracking higher than expected.

Risk Allocation Question

Does the contractor bear full cost risk for performance? If yes, this is a fixed-price structure, and LOF is appropriate if you're funding incrementally. The contractor agreed to perform for the fixed price. LOF simply limits how much of that price the government has obligated at any given time.

Does the government bear cost risk and reimburse actuals? If yes, this is a cost-type structure, and LOC is appropriate. The government is on the hook for actual allowable costs, so LOC creates a ceiling and notification requirement to prevent runaway costs.

Common Misapplications and Why They Happen

Understanding the theory is one thing. But in practice, acquisition professionals frequently apply the wrong clause. Here are the most common errors and why they occur.

Using Limitation of Funds on a Cost-Reimbursement Contract

This is one of the most common mistakes. It happens when someone copies a prior contract package without reading the clauses carefully. The problem is that LOF contradicts the fundamental structure of a cost-reimbursement contract.

In a cost-reimbursement contract, the government reimburses allowable costs. There's no fixed price to fund incrementally. Using LOF creates confusion about when the contractor should stop work and how invoices should be paid. It also fails to impose the proper notification requirements that come with cost growth under LOC.

Using Limitation of Cost on a Fixed-Price Contract

This error inappropriately shifts cost risk back to the government. In a fixed-price contract, the contractor is responsible for managing their costs. If their costs go up, that's their problem—not the government's. Including LOC suggests the government will entertain revised cost estimates and potentially increase funding, which conflicts with the nature of firm-fixed-price performance.

This mistake often stems from template fatigue. Someone used a cost-type contract template for a fixed-price requirement and didn't scrub out the cost-type clauses.

Failing to Include Either Clause When Required

Sometimes the problem isn't choosing the wrong clause—it's forgetting to include one at all. If you're incrementally funding a fixed-price contract and you omit LOF, you create ambiguity about the government's obligation. The contractor may assume the full contract price is obligated, leading to disputes when funds are exhausted.

If you're awarding a cost-plus contract and you omit LOC, you have no cost ceiling and no formal notification requirement. The contractor could theoretically incur unlimited costs, and the government would be obligated to reimburse them. This is exactly the scenario the Anti-Deficiency Act is designed to prevent.

Contractor and Government Obligations Under Each Clause

The practical difference between these clauses becomes clear when you look at what each party must do when thresholds are reached.

Limitation of Funds Obligations

The contractor must notify the contracting officer when a specified percentage of the obligated funds have been expended. This is typically set at seventy-five percent, but the contract can specify a different threshold. The purpose of this notice is to give the government time to process a funding modification before the money runs out.

The contractor must stop work when the obligated funds are exhausted unless the government modifies the contract to add more funds. This is a hard stop. The contractor is not entitled to reimbursement for costs incurred beyond the obligated amount, even if the work was necessary to complete performance.

The government must decide whether to add funds or accept reduced scope. If more funds become available, the contracting officer modifies the contract to increase the obligated amount, and work resumes. If funds aren't available, the contract may be terminated or the scope adjusted.

Limitation of Cost Obligations

The contractor must notify the contracting officer whenever they have reason to believe the total cost will exceed the estimated cost in the contract. This typically happens when costs reach seventy-five percent of the estimate, but the obligation is ongoing—if the contractor sees cost growth coming, they must alert the government immediately.

The contractor must provide a revised cost estimate along with their notice. The government needs this information to decide whether to increase funding, terminate the contract, or direct the contractor to stop work.

The government must decide whether to fund the additional cost or terminate. If the government agrees to the higher cost, the contracting officer modifies the contract to increase the estimated cost. If not, the contractor is directed to stop work or the contract is terminated.

Here's a key difference: under LOC, the contractor may continue work at their own risk if the government does not increase funding. In practice, contractors rarely do this because they know they won't be reimbursed. But the clause technically allows it, whereas LOF imposes a mandatory stop-work when funds are exhausted.

Key Differences in Stop-Work Authority

Think of LOF as a light switch: when the obligated funds run out, the switch flips off. Work stops. No gray area. Think of LOC as a thermostat: the contractor monitors the temperature (cost), warns the government when it's getting too hot, and adjusts behavior based on the government's response. The contractor has more discretion, but also more responsibility to communicate.

Real-World Scenarios and Applications

Abstract explanations only go so far. Here are three scenarios that show how these clauses work in practice.

Scenario 1: Multi-Year Fixed-Price IT Services Contract Funded Incrementally

You're awarding a three-year contract for help desk support services. The total contract value is three million dollars—one million per year. Congress has appropriated funds for Year 1, but Years 2 and 3 depend on future appropriations. You structure the contract as firm-fixed-price with annual option periods and include a Limitation of Funds clause.

At award, you obligate one million dollars. The contractor begins performance. Midway through Year 1, they notify you that they've expended seventy-five percent of the obligated funds. You confirm that Year 2 funding has been appropriated, and you modify the contract to add the second million dollars. Work continues without interruption.

But suppose Year 2 funding is delayed. The contractor hits the one million dollar obligation and must stop work. Your help desk goes dark until the funding arrives and you can modify the contract. This is exactly what LOF is designed to do—prevent the contractor from continuing work when the government doesn't have the legal authority to obligate additional funds yet.

Scenario 2: Cost-Plus-Fixed-Fee Research and Development Contract

You're awarding a cost-plus-fixed-fee contract for prototype development. Based on the contractor's proposal, you estimate the cost at two million dollars, plus a fixed fee of one hundred thousand dollars. You include a Limitation of Cost clause that sets the estimated cost at two million dollars.

Six months into performance, the contractor discovers that a key material is more expensive than anticipated. They project total costs will reach two point three million dollars. They notify you immediately and provide a revised estimate. You review the justification, determine the cost growth is reasonable, and modify the contract to increase the estimated cost to two point three million dollars.

Now suppose the contractor didn't notify you. They quietly continued work, incurring two point three million dollars in costs. When they submit their final invoice, you refuse to pay the additional three hundred thousand dollars because they violated the notification requirement in the LOC clause. The contractor files a claim. This scenario shows why the notification duty is so critical in cost-reimbursement contracts.

Scenario 3: Time-and-Materials Contract with Not-to-Exceed Ceiling

Time-and-materials contracts occupy a middle ground. The contractor is paid for hours worked at specified labor rates, plus materials at cost. There's no fixed price for total performance, but there's also no open-ended cost reimbursement. Most T&M contracts include a not-to-exceed (NTE) ceiling.

If you're incrementally funding a T&M contract due to appropriations timing, you may include LOF-style language. The contractor bills for hours and materials, but the government's obligation is limited to the amount currently funded on the contract. When funds run low, the contractor notifies you, and you add more funding if it's available.

But if the T&M contract has a single NTE ceiling and is fully funded at award, you typically don't need LOF or LOC. The NTE ceiling itself limits government obligation. The key question is whether you're funding incrementally (LOF logic) or managing cost uncertainty (LOC logic). T&M contracts can require either, depending on the funding strategy.

How to Diagnose This During Acquisition Planning

The best time to get this right is before you issue the solicitation. Here are the questions you should ask during pre-award planning.

Questions to Ask During Pre-Award Planning

• What contract type are we using? Fixed-price, cost-reimbursement, or hybrid?
• Will this contract be incrementally funded? If yes, why—because of appropriations timing or because of cost uncertainty?
• Are we funding incrementally due to the structure of appropriations, or because we're unsure what the final cost will be?
• What cost risk does the contractor assume under this structure? Full risk (fixed-price) or minimal risk (cost-reimbursement)?
• If the contractor's costs increase, who is responsible—the contractor or the government?

These questions map directly to the decision tree. Answer them honestly, and the right clause becomes obvious.

Template Review Red Flags

Templates are useful, but they're dangerous if used blindly. Here are red flags that should trigger a closer look.

• The previous contract used LOF—does that make sense for this requirement, or was that contract structured differently?
• The boilerplate contract package includes LOC—is this actually a cost-type contract, or are we using a fixed-price structure?
• You're preparing a contract modification to add funding—does the existing clause align with how you're adding funds and why?
• The contract type changed from the previous version, but the funding clauses stayed the same—did anyone update them?

If you see any of these red flags, stop and apply the decision tree before moving forward.

What Happens When You Get It Wrong

The consequences of using the wrong clause aren't just theoretical. They create real legal, financial, and operational problems.

Anti-Deficiency Act Concerns

The Anti-Deficiency Act prohibits federal employees from obligating funds in excess of available appropriations. If you use the wrong clause and the contractor continues work beyond the funds legally available, you may have violated the Act. Violations can result in personal liability for the contracting officer, including fines and administrative action.

This typically happens when a cost-reimbursement contract lacks an LOC clause, or when an incrementally funded fixed-price contract lacks an LOF clause. The contractor assumes they can continue work, costs exceed available funds, and the government has obligated more than it has authority to spend.

Contractor Payment Disputes

Contractors perform work based on their understanding of the contract terms. If the contract includes the wrong clause, the contractor may believe they will be reimbursed for costs that the government later refuses to pay. This leads to claims, disputes, and sometimes litigation.

For example, a contractor working under a fixed-price contract with an LOC clause may interpret that as permission to seek additional reimbursement if their costs grow. When the government denies the request because the contract is fixed-price, the contractor argues the clause created an ambiguity. The government may ultimately prevail, but only after months of dispute resolution.

Contract Performance Failures

Misapplied clauses create confusion about when the contractor should stop work. If the contractor stops too early because they misunderstood their obligations, the government program is disrupted. If the contractor continues too long because the clause was unclear, the government faces a funding crisis.

Either way, mission suffers. A miscommunication about a funding clause can ground an aircraft fleet, delay a construction project, or halt critical research. These aren't administrative inconveniences—they're operational failures that stem from poor contract drafting.

Why This Matters

Limitation of Funds and Limitation of Cost aren't just regulatory puzzles to solve. They're strategic tools that align contract structure with funding reality. Choosing the right clause requires understanding contract type, funding strategy, and risk allocation—not just copying prior examples or guessing based on clause names.

When you understand the logic behind each clause, you can apply it in real time during acquisition planning, contract award, or modification drafting. You stop relying on templates and start making informed decisions. You reduce the risk of Anti-Deficiency Act violations, payment disputes, and performance failures.

Most importantly, you create contracts that both parties understand. The contractor knows when to notify the government, when to stop work, and what financial risk they assume. The government knows when it must add funding, when it can refuse, and how to protect itself from cost overruns. That clarity protects everyone and keeps the mission moving forward.