Use It or Lose It Is How You Accidentally Break Fiscal Law

Every September, Contracting Officers across the federal government face the same ritual: program offices appear with expiring funds, urgent requirements, and a hard deadline of midnight on September 30. The message is clear—obligate the money or lose it. So contracts get signed, modifications get processed, and obligations get recorded. On October 1, it feels like success. The funding was saved. The program office is happy. The resource manager checks the box.

But months later, someone opens the contract file. Maybe it's an audit. Maybe it's a file review. Maybe it's a modification that doesn't add up. And suddenly, the obligation that looked clean in September starts to unravel. There's no documented bona fide need determination. The severability analysis is missing or backward. The contract structure doesn't match the fiscal logic. The Contracting Officer who signed the document is now the one who has to explain why the obligation was lawful in the first place.

This article is not about avoiding year-end spending. It's about recognizing that the pressure to obligate quickly often inverts the correct decision-making sequence. It skips the documentation that proves an obligation was lawful and leaves the Contracting Officer holding a file that cannot survive scrutiny. The good news is that there's a simple framework you can use under time pressure to ensure your file is defensible from the start—and it's faster than cleaning up the mess later.

The Real Risk Is Not Losing the Money—It's Obligating It Wrong

The phrase "use it or lose it" drives behavior across the federal government. It creates urgency, focuses attention, and moves dollars out the door before the fiscal year expires. But it also creates a dangerous inversion: organizational incentive to spend becomes the driver of the decision, and the legal justification for spending becomes an afterthought.

Here's the structural problem. Program offices and resource managers are measured by execution rates and funding absorption. Their job is to make sure money gets obligated before it expires. The Contracting Officer's job is different. The KO must ensure that every obligation is supported by a lawful need, proper contract structure, and appropriate fiscal year alignment. These two roles are not always in conflict, but when time pressure enters the equation, they often are.

The Anti-Deficiency Act violation does not occur on October 1 when the funding expires. It occurs the moment an obligation is recorded without a lawful basis—even if that moment is September 29 and the contract looks perfectly fine in the system. The violation is latent. It sits in the file, invisible, until someone asks the question the file cannot answer: why was this obligation lawful?

And when that question gets asked, the Contracting Officer is the one who must answer it. Program offices move on to the next fiscal year. Resource managers close out their books. The KO owns the file. That ownership is not symbolic. It is legal, professional, and personal.

What "Obligate Now, Figure It Out Later" Actually Produces

Rushed year-end obligations tend to fail in three predictable ways. None of these failures are visible on the day the contract is signed. They only surface later when someone looks closely at the file or when the contract needs to be modified.

Failure Mode 1: Bona Fide Need Is Assumed, Not Documented. The requirement appears in September, and everyone assumes the need arose in the current fiscal year because the fiscal year is ending. But assumption is not documentation. A lawful obligation requires a record showing that the need arose during the period when the funds were available. If that record does not exist, the obligation cannot be defended. It does not matter that the need might have been real. What matters is whether the file can prove it.

Failure Mode 2: Severability Determination Is Skipped or Misapplied. Severability determines whether a requirement must be fully funded upfront or whether it can be incrementally funded across fiscal years. When time is short, this determination often gets skipped entirely, or it gets applied backward. The result is incremental funding on nonseverable requirements, which violates the bona fide needs rule, or full funding on severable requirements, which wastes flexibility and creates downstream complications.

Failure Mode 3: Contract Structure Does Not Align With Fiscal Logic. The contract period of performance gets stretched or compressed to fit available funding rather than actual need timing. The modification adds scope that doesn't match the documented requirement. The fiscal year alignment is arbitrary. These mismatches are invisible when the obligation is recorded, but they become glaring when the contract is modified or when someone maps the performance period back to the original need determination.

Think of it like building a house on a foundation you never inspected. The house might stand for months. But when the ground shifts or someone looks underneath, the cracks appear. By then, you're not fixing a foundation—you're explaining why the house is sinking.

The Correct Sequence—Need, Severability, Funding Approach, Obligation

There is a correct sequence for obligation decisions. It does not take longer than the rushed version. It just requires discipline about what gets documented and when. If you follow this sequence, your file will be defensible from the start, and you will not have to reconstruct logic months later under scrutiny.

Step 1: Document the Bona Fide Need and the Period When That Need Arises. Before anything else, write down why the requirement exists and when the need arose. This does not need to be a legal treatise. It needs to be a clear statement: "We need X service because Y situation exists, and that situation arose on Z date." If you cannot write that sentence, you do not have a documented need.

Step 2: Determine Whether the Requirement Is Severable or Nonseverable. Severability is about the nature of performance, not the nature of funding. Ask yourself: is this requirement naturally divisible into separate parts that can be accepted and used independently, or does it produce a single end result that has no value until complete? Recurring services like maintenance or support are typically severable. Discrete deliverables like studies or construction are typically nonseverable. Document your determination in one sentence.

Step 3: Select the Contract Type and Funding Method That Matches the Severability Determination. If the requirement is severable, you can use incremental funding and align each fiscal year's funding with that fiscal year's performance. If the requirement is nonseverable, you must fully fund it with the fiscal year funds available when the need arose. The funding method is not a choice—it is a consequence of the severability determination.

Step 4: Obligate Only After Steps 1 Through 3 Are Documented in the File. Obligation is the last step, not the first. Once the need is documented, the severability is determined, and the contract structure matches the fiscal logic, obligation becomes a mechanical act. The file tells the story. The obligation simply records it.

This sequence does not slow execution. It prevents rework, protects the Contracting Officer, and ensures the file can answer the only question that matters: why was this obligation lawful?

How to Recognize When You're Being Pressured Into a Bad Obligation

Time pressure is real. Deadlines are real. But pressure does not eliminate legal risk—it amplifies it. Here are five diagnostic questions you can ask in real time to determine whether you are about to create a defensible obligation or a latent violation.

• Is the requirement being packaged to fit the available funding, or is the funding matching the actual need?
• Is there a written bona fide need determination in the file, or is it assumed because the fiscal year is ending?
• Does the contract period of performance match the need period, or was it chosen to absorb expiring funds?
• Is incremental funding being used because the requirement is severable, or because full funding is unavailable?
• Can you explain the severability determination in one sentence, or would you need to look it up after the fact?

If the answer to any of these questions makes you uncomfortable, stop. Do not obligate until you can answer each question clearly and document the answer in the file. The discomfort you feel in September is a fraction of the discomfort you will feel in March when the file is opened and you cannot defend what you signed.

Practical Example—Same Requirement, Two Approaches

Let's walk through a scenario that plays out every September in federal agencies. A program office has $200,000 in expiring funds. They want to lock in a service contract for IT support. The clock is ticking. The Contracting Officer has two options.

Approach A: High Risk. The KO modifies an existing contract to add six months of IT support starting October 1, using the $200,000 in expiring funds. The modification is processed on September 28. The obligation is recorded before midnight on September 30. The file contains the modification, the signed document, and the funding certification. What the file does not contain is a bona fide need determination explaining why the need arose before the fiscal year ended, a severability analysis, or any justification for why six months of support aligns with the funding source. On October 1, the obligation looks clean. Six months later, when the program office asks to extend the contract, someone reviews the file and realizes the original obligation cannot be defended. The need was not documented, the severability was not analyzed, and the performance period was arbitrary.

Approach B: Defensible. The KO starts by documenting the bona fide need. The current IT support contract ends December 31. The program office requires continuation of support without a gap, and that need exists now, in the current fiscal year. The KO determines the requirement is severable because IT support is a recurring service that can be accepted and used in distinct monthly increments. The KO structures the contract to align fiscal year funds with fiscal year performance: the $200,000 in current-year funds will cover October 1 through December 31, and future fiscal year funds will cover January onward. The obligation is recorded on September 29. The file contains the bona fide need statement, the severability determination, and the contract structure justification. On October 1, the obligation looks clean. Six months later, when the program office asks to extend the contract, the file tells a complete story and the modification is straightforward.

Both approaches meet the September 30 deadline. Both obligate the same amount of money. But only one survives scrutiny. The difference is not speed. It is sequence.

What to Do When the Pressure Is Real and the Clock Is Running

Sometimes the pressure is not theoretical. You have hours, not days. The program office is insistent. The resource manager is anxious. The expectation is clear: move the money now. Here is what you do.

Acknowledge the pressure, but refuse to obligate without minimum documentation. You do not need a perfect file. You need a defensible file. That means three things must be in writing before you sign: a bona fide need statement, a severability determination, and a contract structure justification. These do not need to be lengthy. They need to be clear.

Use a simple checklist. Before you obligate, confirm that you can answer these questions in writing: Why does this need exist? When did it arise? Is the requirement severable or nonseverable? Does the contract period of performance match the need period? Does the funding method match the severability determination? If you can answer those questions in the file, you can obligate. If you cannot, you cannot.

If documentation cannot be completed in time, it is better to lose the funding than to create Anti-Deficiency Act exposure. This is not a popular position. It may feel obstructionist. But the risk of a fiscal law violation is not shared equally. The program office and the resource manager move on. You own the file. You own the justification. You own the consequences.

You are not obstructionist for requiring documentation. You are managing legal risk the program office does not own. Here is language you can use: "I understand the urgency, and I want to help. I cannot obligate without documenting the bona fide need and the severability determination. If we can get those two things in writing, I can process this today. If we cannot, I need you to understand that I am not the obstacle—the missing documentation is."

Why This Matters

Year-end spending pressure is not a planning failure. It is a structural risk created by incentive misalignment. Organizations are rewarded for spending money before it expires. Contracting Officers are accountable for ensuring that spending is lawful. Those two incentives do not always align, and when they do not, the Contracting Officer absorbs the risk.

The framework in this article does not eliminate time pressure. It gives you a decision-making sequence you can execute under pressure without creating latent violations. Obligation timing becomes the output of sound fiscal logic, not the driver of a shortcut. The file becomes defensible from the start, not reconstructed under scrutiny.

This approach protects you, the program office, and the agency. It ensures that every obligation can answer the only question that matters: why was this lawful? And it positions proper documentation as what it actually is—faster and safer than cleanup after the fact.

The file must be able to answer why the obligation was lawful, not just when it was recorded. If you remember that principle in September, you will not have to explain its absence in March.