7 Funding Red Flags That Trigger Anti-Deficiency Act Risk Before Award

Most contracting officers can recite the Anti-Deficiency Act in theory. They know the rules about bona fide need, fiscal year appropriations, and proper obligation. But theory rarely matches the chaos of real pre-award review.

The truth is, ADA violations don't announce themselves. They hide inside purchase request packages that look clean at first glance. They nestle into CLIN structures that seem routine. They appear in IGCE line items that no single reviewer questions because everyone assumes someone else checked.

By the time the problem surfaces—often months after award—the contracting officer owns the risk. It doesn't matter that the budget office miscoded the funds or the program office wrote a bad statement of work. The KO signed the document. The KO is accountable.

This article gives you a diagnostic framework you can use before you sign. These seven red flags represent the most common funding mismatches that survive legal and finance review because no one sees the full picture. Each one includes the specific document clues that should make you stop and ask questions. Think of it as pattern recognition, not rule memorization. Because in federal contracting, spotting the mismatch early is what separates a clean file from a compliance disaster.

Red Flag 1: Multi-Year CLIN Structure Funded with Single-Year Appropriations

This is one of the most common traps, especially in services contracting. The period of performance spans multiple fiscal years. The CLIN structure reflects that reality. But the funding citation points to a single fiscal year appropriation.

It looks logical on paper. The requiring activity wants continuity. The contract is structured to provide it. But if you're obligating fiscal year 2025 funds against work that runs into fiscal year 2026, you've created an obligation mismatch. The funds are locked to the year they were appropriated. The work isn't.

What to look for in the contract file:

• IGCE that phases labor or deliverables past the September 30 boundary
• Funding citation showing a single fiscal year even though the PoP crosses into the next
• CLIN descriptions that treat the entire period as one continuous effort without breaking obligations by fiscal year
• No documentation explaining how the work will be severed or how future-year funds will be added

Triage questions to ask before proceeding:

• Is the work severable by fiscal year, or does it need to be treated as a single undertaking?
• If severable, how will we structure the CLINs and funding to match each fiscal year's appropriation?
• If not severable, do we have the correct appropriation type that allows multi-year obligation?
• Has the budget office confirmed that future-year funds are programmed and available?

Red Flag 2: Services Requirement Spanning Fiscal Year Boundary Written as Nonseverable

Severability is one of those concepts everyone thinks they understand until they have to apply it. In general, services are severable if each period stands alone and delivers value without depending on what comes before or after. But the language in your Performance Work Statement can turn a theoretically severable service into a nonseverable problem.

If your PWS talks about a "final deliverable," an "integrated system," or a "single outcome" that takes months to complete, you're describing nonseverable work. That means the entire effort must be funded with the appropriation that matches the bona fide need. If the need arises in fiscal year 2026, you can't use fiscal year 2025 funds just because you're signing the contract in September.

What to look for in the contract file:

• PWS includes language like "culminating in," "final report," "system integration," or "end-to-end solution"
• Period of performance crosses September 30 but the contract is funded as if the work is severable
• CLIN structure uses incremental funding or splits obligations by fiscal year even though the work can't logically be divided
• No clear breakpoint where the government could terminate and still receive something useful

Triage questions to ask before proceeding:

• Can the government receive value from the work performed in fiscal year 2025 alone, even if the contract is terminated on September 30?
• Does the requiring activity need the entire scope to meet their mission, or can each phase stand independently?
• If the work is nonseverable, which fiscal year reflects the true bona fide need?
• Should we restructure the contract into separate awards or option periods to align with fiscal year appropriations?

Red Flag 3: Incrementally Funded Contract Type That Requires Full Funding at Award

Not all contract types are eligible for incremental funding. This sounds basic, but it's one of the most frequently violated rules in federal contracting. Contracting officers see FAR 52.232-22, assume it applies universally, and move forward with partial obligation on a contract type that legally requires full funding upfront.

Here's the distinction: incremental funding is generally permissible for cost-reimbursement contracts and some time-and-materials arrangements. It is not permissible for firm-fixed-price contracts where the government is buying a specific deliverable or outcome. If the contractor is on the hook to complete the work regardless of cost, the government must obligate the full amount at award. You can't incrementally fund a promise.

What to look for in the contract file:

• Contract type is labeled FFP, firm-fixed-delivery, or fixed-price-level-of-effort
• Funding strategy relies on FAR 52.232-22 or references "incremental funding" in the contract provisions
• IGCE shows full contract value, but obligation at award is only partial
• No documentation from legal or finance confirming that incremental funding is permissible for this contract type

Triage questions to ask before proceeding:

• Does this contract type allow incremental funding under the FAR and fiscal law?
• Is the contractor being asked to deliver a fixed outcome, or is the government buying effort over time?
• If full funding is required, do we have access to the full amount now, or do we need to delay the award?
• Has legal reviewed and confirmed that our funding strategy matches the legal obligations created by this contract type?

Red Flag 4: Year-End Obligation Against Future Fiscal Year Need

September is the danger zone. Budgets are expiring. Program offices are scrambling to obligate funds before they disappear. And contracting officers are flooded with purchase requests that look urgent but don't pass the bona fide need test.

The rule is simple: you must obligate funds in the fiscal year the need arises. If the training doesn't happen until November, the need isn't bona fide to fiscal year 2025. If the conference is in January, you can't justify using September money. The timing of the contract award is irrelevant. What matters is when the government actually needs the service or supply.

Think of it like paying for a wedding venue. You can't use your 2025 household budget to pay for a reception happening in 2026 just because you want to lock in the price early. The expense belongs to the year it occurs.

What to look for in the contract file:

• PR submitted in August or September for work beginning in October or later
• Training dates, conference registrations, or event schedules that fall in the next fiscal year
• Justification memo that focuses on spending the money rather than explaining why the need exists now
• Period of performance start date that conveniently begins on October 1 or later with no work happening before then

Triage questions to ask before proceeding:

• When does the government actually need this service or supply?
• Is there a legitimate reason to obligate now, or is this purely a budget execution exercise?
• Can the requiring activity document a current-year need that justifies using current-year funds?
• If the need is genuinely in the next fiscal year, do we have authority to use the correct appropriation?

Red Flag 5: On-Call or As-Needed Services Under Incremental Funding

Vague requirements create vague compliance risks. When a statement of work describes services as "on-call," "as-needed," or "to be determined based on mission requirements," you're looking at a scope that may not satisfy the bona fide need rule. If the government doesn't know when or whether it will need the work, how can it justify obligating funds now?

This problem gets worse under incremental funding. The government is essentially reserving contractor capacity without a clear plan for how or when that capacity will be used. That's not how appropriations work. You can't obligate money just in case you might need something later.

What to look for in the contract file:

• PWS uses reactive or flexible language like "on-call," "standby," "as-needed," or "TBD based on mission priorities"
• No fixed schedule, phasing plan, or deliverable timeline
• Incremental funding approach with expiring appropriations but unclear when or whether the work will actually be tasked
• Services described in terms of contractor availability rather than specific government need

Triage questions to ask before proceeding:

• Does the government have a specific, current need for these services, or is this precautionary?
• Can the requiring activity define what work will be performed and when?
• If the services are truly on-call, should this be structured as an IDIQ or on-call contract with orders issued only when a bona fide need arises?
• Does the funding strategy align with how and when the work will actually be tasked?

Red Flag 6: O&M Funding Citation Supporting Multi-Year System Development or Capital Asset

Not all funding is created equal. Operations and Maintenance appropriations are designed for near-term needs. They're annual. They're meant to keep things running, not build things that last. When you see an O&M funding citation attached to a statement of work that involves system builds, software customization, infrastructure upgrades, or multi-year lifecycle support, you're looking at a mismatch.

The problem is that acquisitions often masquerade as services when they're really building something enduring. A contractor might be hired to "provide IT support," but the SOW includes developing custom applications that the government will use for years. That's not operations and maintenance. That's investment. And it requires the right kind of appropriation.

What to look for in the contract file:

• Funding cite labeled O&M but SOW describes system development, software builds, or infrastructure projects
• Deliverables include things the government will own, operate, or maintain beyond the period of performance
• Language around "lifecycle support," "enduring capability," "system integration," or "platform development"
• Work that creates something new rather than maintaining or operating something that already exists

Triage questions to ask before proceeding:

• Is the contractor maintaining an existing capability, or building something new?
• Will the deliverable be used beyond the current fiscal year?
• Does the nature of the work require procurement or R&D appropriations instead of O&M?
• Has the budget office confirmed that the appropriation type matches the legal character of the work?

Red Flag 7: Continuing Resolution Constraints Ignored in Procurement Timeline

When Congress doesn't pass a budget on time, agencies operate under a Continuing Resolution. CRs keep the lights on, but they come with restrictions. One of the biggest is the prohibition on new starts—programs, projects, or activities that weren't funded in the prior fiscal year.

Contracting officers often assume that if funds are available, they can proceed. But if the requirement qualifies as a new start and no exemption has been granted, the award violates the CR. The tricky part is that "new start" isn't always obvious. It depends on whether the work is a continuation of prior efforts or something fundamentally new.

What to look for in the contract file:

• Procurement action initiated or award planned during a CR period
• No documentation confirming that the requirement is exempt from new start restrictions
• Work that differs significantly in scope, purpose, or structure from prior-year contracts
• No evidence that legal or budget office reviewed CR compliance before moving forward

Triage questions to ask before proceeding:

• Is the government currently operating under a CR?
• Does this requirement qualify as a new start, or is it a continuation of prior-year work?
• Has legal or the budget office confirmed that we can proceed, or do we need to wait for a full-year appropriation?
• Is there documentation in the file demonstrating CR compliance and any applicable exemptions?

Practical Application: Pre-Award Triage Workflow

Red flags are only useful if you have a system for catching them. Here's a simple workflow you can build into your pre-award review process. It's designed to take less than ten minutes for routine actions, but it forces you to look at the contract file as a whole rather than reviewing each document in isolation.

Step 1: Map the key elements side by side

Pull up four things: the funding citation, the contract type, the period of performance, and the PWS or SOW. Look at them together. Do they tell the same story? If the funding is annual but the PoP spans two fiscal years, you've got a mismatch. If the contract type is FFP but the funding line says "incremental," something's wrong.

Step 2: Check the dates

Look at when the need arises versus when the funds expire. If the PR was submitted in September but the work starts in November, ask why. If the funding is from fiscal year 2025 but the IGCE phases work into fiscal year 2026, stop and escalate.

Step 3: Read the PWS for severability clues

Scan for words like "final," "integrated," "system," "culminating," or "end-to-end." If the work sounds like one continuous effort, it probably is. If it crosses a fiscal year boundary, you need to verify that the funding approach matches the legal reality.

Step 4: Verify appropriation type matches the work

If the funding cite says O&M but the SOW describes building or developing something, escalate. If the work creates an enduring capability, O&M probably isn't the right pot of money.

Step 5: Escalate when in doubt

If any of the red flags appear and you can't resolve them with a quick conversation, escalate to legal, the budget office, or the requiring activity. Document the question in the contract file. Don't assume someone else checked. The signature is yours.

Step 6: Document your analysis

Even if everything checks out, add a short memo or email to the file explaining what you reviewed and why you concluded there was no ADA risk. If the issue ever comes up later, you'll have evidence that you conducted due diligence.

Why This Matters

Most Anti-Deficiency Act violations aren't caught until after the money is spent. By that point, the options for fixing the problem are limited and painful. Funds may need to be returned. Contracts may need to be restructured or terminated. And the contracting officer is left explaining how the violation happened on their watch.

The unfair part is that KOs often inherit the risk. The program office writes a bad requirement. The budget office miscodes the funding. The requiring activity pushes a year-end spend plan that doesn't pass the bona fide need test. But when the contract is signed, the KO owns it.

Pattern recognition is your best defense. You don't need to become a fiscal law expert. You just need to spot the mismatches before they become obligations. These seven red flags represent the most common traps—scenarios where the documents look procedurally fine but don't align when you examine them together.

This checklist gives you a repeatable framework. Use it during end-of-year crunch when the pressure to execute is highest. Use it when you're reviewing an unfamiliar contract type or working with a new requiring activity. Use it anytime the documents feel slightly off but you can't immediately articulate why.

Because in federal contracting, your job isn't just to get the award out the door. It's to get it out correctly. And that starts with knowing what to look for before you sign.