OMB Opines on Section 3610
Governor Ritchie: Now, he's going to throw a big word at you: ‘unfunded mandate.’ If Washington lets the states do it, it's an unfunded mandate. But what he doesn't like is the federal government losing power. But I call it the ingenuity of the American people.
President Bartlet: Well, first of all, let’s clear up a couple of things. ‘Unfunded mandate’ is two words, not one big word.
An unfunded mandate is a statute or regulation that requires an entity to perform certain actions, with no money provided for fulfilling the requirements. Examples include the Clean Air Act, the Americans with Disabilities Act, and the No Child Left Behind Act. Each of those statutes requires action at the state or local level, without providing funding to support those actions.
And it looks like the CARES Act needs to be added to the list.
How can that be? Wasn’t the CARES Act supported by more than $340 billion in public funds?
Yes. Yes, it was.
The problem is that no appropriations were set aside for implementation of Section 3610 of the CARES Act, the section that authorizes the Federal government to reimburse contractors for “stand-by” or other paid leave time when employees cannot perform planned work. We’ve written about Section 3610 before. We expect we will again.
If you’re not hip to Section 3610, you may want to follow the link in the above paragraph, or perhaps find another article to bring you up to speed. We’re going to assume you’ve got the basics.
Since you’ve got the basics, you understand that contractors can submit invoices to receive reimbursement of their Section 3610 costs—but that contracting officers have discretion as to whether or not to pay those invoices. One important aspect of contracting officer decision-making involves funding. At the moment, any payments must come out of funds already appropriated for the contract’s SOW. In other words, the contracting officer has to decide which is more important: funding the work that was planned or funding the contractor employees’ stand-by time. It is fairly obvious that as the contractor employee’s stand-by time is funded, there is less money left to perform the work that was contracted-for.
Which is kind of a tough decision, isn’t it?
Until and unless Congress appropriates funding expressly earmarked for Section 3610 reimbursements, every contracting officer is going to have to wrestle with that choice. And—as we’ve written before—at the moment guidance from DoD and DCMA in particular is woefully short.
Meanwhile, on July 14, the Office of Management and Budget issued guidance in the form of Frequently Asked Questions (FAQs) to help agencies deal with some of the issues. Section 3610 issues are discussed on pages 10 through 17. There are 18 FAQs addressing aspects of contractor reimbursements under Section 3610. We are not going to repeat the relevant FAQs and associated answers here. You should go read it for yourself. However, here are some interesting quotes, for your information.
-
It is important to secure fully supported documentation from contractors regarding claimed reimbursement, including relief claimed and received, along with the financial and other documentation necessary to support their requests for reimbursement under Section 3610. … Agencies should secure the contractor's agreement to segregate and report the actual costs of the leave payments for each employee (i.e., actual cost for each employee's paid leave, including names of employees and number of leave hours). The agency should further advise that the government may audit the billed costs in order to ensure the accuracy and compliance with the law. Contractors are responsible for supporting their requests for reimbursement.
But for many contractors, it’s all speculation at this point. Their contracts are likely to have insufficient funding available for Section 3610 reimbursement and, even if they do have funds, as noted above the contracting officers are going to have to wrestle with some tough decisions regarding whether to pay contractors for doing the contracted work or paying contractors for not working.
Meanwhile, the Department of Defense is pressuring Congress for the necessary appropriations. And defense contractor executives are doing the same thing, according to reports. However, those same reports state that Republicans are “skeptical” about providing additional relief funding on top of the funding already provided.
We’ll have to wait and see where this goes. And while we wait, we’ll see what government contracting officers—and DCMA contracting officers in particular—decide to do when they start to receive contractor requests for reimbursement of Section 3610 costs.
DOD Issues More Guidance on COVID-19 Expenses
On July 6, 2020, the Dept. of Defense issued more guidance on treatment of COVID-19 related expenses incurred by its contractors. We have noted several prior pieces of DOD guidance on the subject; however, more recently we have been critical of the lack of clear guidance to DOD contracting officers. This latest piece of guidance does nothing to change our mind about the failings of DOD guidance.
Our fundamental problem with the current guidance memo (link above) is that it really doesn’t say much of anything that a contracting officer might find useful.
Sure, it addresses non-labor COVID-19 expenses, which is new and certainly of potential interest to many DOD contractors. Recalling that the CARES Act (especially Section 3610) and related guidance focused on contractor’s “stand-bye” labor costs, one might reasonably argue that guidance on non-labor costs was needed. Our problem is the memo doesn’t really add anything to the conversation that wasn’t already in the FAR.
Here’s a quick recap of the memo, quoting selectively:
-
DoD Contractors may have already incurred, and will likely continue to incur, delays and costs associated with their response to the COVID-19 pandemic. However, to date, no funds have been appropriated specifically for reimbursement of these costs.
-
DFARS Class Deviation 2020-O0013 – CARES Act Section 3610 Implementation, effective April 8, 2020, provides a means for affected contractors to request reimbursement of costs incurred for paid leave granted to their employees during the COVID-19 pandemic. Subject to the availability of funds, a contracting officer may modify contracts or other agreements to reimburse up to 40 hours per week of paid leave costs.
So far, that’s just a recap of history. There’s absolutely nothing new there. Let’s continue:
-
Contractors may face further unplanned costs due to COVID-19, such as those related to providing PPE to employees, additional cleaning of work areas, changes to work spaces to accommodate social distancing, and delays in delivering and/or receiving purchased materials. Where allowable and allocable, these costs may be recovered on cost-reimbursement and incentive contracts.
Yes. The FAR does permit contractors to be reimbursed for costs that are allowable and allocable to their flexibly priced contracts. Those costs don’t need to be COVID-19 related costs either; they can be any costs that are allowable and allocable. Why DOD felt the need to restate what was already true as if it were new policy guidance escapes us.
But let’s move on.
-
DoD contracts contain clauses to excuse performance delays not due to the contractor’s fault or negligence … In the event of delays caused by COVID-19, the contractor may be entitled to relief from contract delivery requirements. However, there is no statutory, regulatory, or contractual entitlement to an adjustment to contract price for schedule delays that are attributable to excusable delays. Unlike contractors performing under cost-type contracts, contractors under fixed-price contracts generally must bear the risk of cost increases, including those due to COVID-19 (e.g., costs associated with PPE, social distancing, and supplier delays and inefficiencies).
-
Contracting Officers are granted discretion, subject to the availability of funds, to modify contracts … to reflect changes to the Government’s needs as a result of COVID-19. Any resulting changes in contract price must be substantiated by the contractor and determined by the contracting officer to be required to perform the contract as modified, and must be driven exclusively by the change(s) directed by the Government.
Hold on. Let’s stop right there. What did the memo just say? Did it say contracting officers can modify FFP contracts for the cost impact of COVID-19 related expenses?
No. No, it didn’t. Read again.
The memo says that contracting officers are granted discretion to modify contracts to reflect changes to the government’s needs. It has nothing to do with the contractor’s needs. In fact the memo reinforces that notion with the statement that the changes “must be driven exclusively by the change(s) directed by the Government.” Exclusively.
So what does that mean? It means the memo is granting authority to contracting officers to make changes to FFP contracts under the changes clause, should the government’s needs have changed. You know what? That’s authority that was already given to contracting officers when they received their certificates of appointment. There is absolutely nothing new there.
The memo seems to hint that contracting officers are being given authority to make changes to FFP contract prices as the result of COVID-19. (Nudge, nudge. Wink, wink.) For example, it states “the costs that would be associated with such COVID-19 related, Government-directed change modifications may be above and beyond current available funding.” However, that weak hint is contradicted throughout the memo, including the following:
-
In making such modifications, Contracting Officers must be mindful that they are stewards of the public funds. They must only execute contract actions that result in fair and reasonable prices for the supplies or services provided and are determined to be in the best interests of the Government.
-
The costs that would be associated with such COVID-19 related, Government-directed change modifications may be above and beyond current available funding. In such cases, Contracting Officers may not direct a change or execute a modification that results in an increase to the contract price until and unless the Department receives additional appropriations.
Based on the express language of the memo, we strongly recommend that contractors not expect any changes to their FFP contract prices as the result of non-labor COVID-19 related costs. Their stand-bye labor costs, of course, may reimbursed (even under T&M or FFP contracts) pursuant to the CARES Act Section 3610; but even that price impact is subject to contracting officer discretion and the availability of funds.
And as we’ve already noted, contracting officers have received little if any guidance regarding the exercise of their discretion.
This memo continues that trend.
|
Updates of Potential Interest
A couple of quick updates of potential interest to readers.
First, the Prompt Payment Interest Rate for the second half of 2020 was published in the Federal Register on July 10, 2020. The current interest rate is now 1.125 percent per year. In accordance with the Prompt Payment Act, as implemented in FAR 32.907 and associated contract clauses—and as calculated in accordance with 5 CFR 1315—the government must pay an interest penalty automatically, without the need of a contractor request to do so, when it makes a late payment to the contractor. The current interest rate is a key component of that penalty calculation.
Note that circumstances in which the government is required to pay an interest penalty vary considerably and, before you go off demanding such a payment (if one was not made automatically), you definitely should read FAR 32.9 and the payment clause(s) in your contract.
Importantly, the Prompt Payment Interest Rate is not just used for calculating the interest penalty for late government payments to contractors. It is also used for calculating interest that accrues on a claim made under the Contract Disputes Act. That same interest rate is also used to calculate Facilities Capital Cost of Money factors for compliance with Cost Accounting Standards 414 and 417. Note that FAR 31.205-10 makes CAS 414 applicable to all contracts, even if otherwise exempt from CAS, should a contractor elect to propose and receive FCCOM on its contracts.
So it’s kind of a big deal, if you are one of the many contractors that use it. But 1.125% is not at all a high rate, and thus calculations that involve the Prompt Payment Act Interest Rate are going to be smaller than they have been historically.
Next, let’s talk about the TINA threshold. (Yes, we know it’s not called “TINA” anymore, but it will always be TINA to us.) Federal Acquisition Circular 2020-007, published in the Federal Register on July 2, 2020, included a Final Rule that implemented statutory changes made to the TINA Threshold by the FY 2018 National Defense Authorization Act (NDAA). FAR Case 2018-005 was opened “to increase the threshold for requesting certified cost or pricing data from $750,000 to $2 million for contracts entered into after June 30, 2018. The threshold for Cost Accounting Standards applicability is required by 41 U.S.C. 1502(b)(1)(B) to be the same threshold as the one for requesting certified cost or pricing data.”
Thus, the new threshold for obtaining certified cost or pricing data is now $2 million, as is the threshold at which CAS might be applied to a contract. (Note that CAS still contains a $7.5 million “trigger contract” value, so application of CAS to a contract is not automatic.)
When we say the TINA/CAS threshold is now $2 million, we should recognize that there have been Class Deviations that implemented the “new” threshold in place for months, because the policy makers got impatient waiting for the rule-makers to do their thing. We have several blog articles discussing whether or not a statutory change could (or must) trump the regulatory rules that implement it. We also lamented the slow pace of the regulatory rule-making.
But regardless of how long it took to get here, here we are.
However, we still have a problem with contracts awarded prior to June 30, 2018. It is likely that those contracts contain the “old” TINA threshold, which would apply to subcontractors under those prime contracts. That’s a problem, because now those contracts are out of alignment with the current thresholds. What can be done?
Well, according to the final rule—
Upon the request of a contractor that was required to submit certified cost or pricing data in connection with a prime contract entered into before July 1, 2018, the contracting officer shall modify the contract without requiring consideration to reflect a $2 million threshold for obtaining certified cost or pricing data from subcontractors.
In our view, any prime contractor that does not make that request is doing a disservice to itself. Further, if we were a subcontractor, we would immediately request that our subcontract be modified to use the new thresholds.
Why would we care?
According to the final rule, there are cost savings associated with the threshold change. According to the regulatory analysis, contractors stand to realize $589 million in cost savings (across the entire spectrum of government contractors), and the government stands to realize an additional $91 million in cost savings, from raising the thresholds. The cost savings come from having fewer contractors submit certified cost or pricing data and having fewer contractors subject to CAS. That’s a decent amount of savings. Makes us frustrated (once again) that the FAR Councils took their sweet time implementing this statutory change.
We should also note that even if a prime or subcontract were modified to implement the new thresholds, we don’t believe it would change history. Subcontractors that submitted certified cost or pricing data under the old threshold would still be subject to defective pricing allegations if it turns out their certified cost or pricing data was not accurate, complete, or current. Similarly, we think subcontracts that were CAS-covered under the old threshold still remain CAS-covered under the new threshold, even if they were valued at less than $2 million. It’s axiomatic that a contract modification does not impact CAS applicability; and we believe that rule still would hold true in this case.
Working Under an Implied-in-Fact Contract
Most of the people reading this blog work in the field of government contracting, in one capacity or another. Some of you are finance/accounting folks, some are contracting folks, some are buyers. Some are program managers. Some of you work for the government and some of you work for contractors. But the single thread that unites the majority of readers is that you all work with contracts—government contracts.
Accordingly, you are used to having a contract to deal with. Most of the time, there is a Request for Proposals (RFP) and a proposal in response to that RFP, and then there is a negotiation and award of a contract. An actual written-and-signed-in-blue-or-black-ink contract. There’s even a Uniform Contract Format that is used by the Federal government, just to make sure the standard contract follows a standard structure that the parties both understand.
But what happens if there is no contract?
What happens if there are two parties working together without a written agreement?
Can that even be a thing in government contracting?
Yes. Yes, it can.
It’s certainly not a best practice. Or even a recommended practice. In fact, we strongly advise against working without a written agreement.
We teach the acronym RTFC: “Read the Foolish Contract,” because so few actually do. But if you don’t have a written agreement then there’s nothing to read, so it’s supremely difficult to determine the contracting parties’ mutual rights and responsibilities. For example, how do you bill for services rendered without any sort of billing instructions? How do the parties know when the agreed-upon scope of work has been completed? (How do the parties even confirm what the agreed-upon scope of work actually is?) Working without a written agreement is, to put it mildly, a very poor practice that is likely to end in one or more disputes, and possibly in litigation.
Still, it happens. And it happened to one contractor named Network Documentation & Implementation, Inc. (NDI), who alleged it performed more than $2 million worth of services for the Defense Information Systems Agency (DISA) without a written agreement. Unsurprisingly, the parties found themselves before the Armed Services Board of Contract Appeals (ASBCA), with a dispute under contract number “000000-00-0-0000.”
Before the ASBCA was the government’s motion to dismiss. One of the bases for DISA’s motion to dismiss was that NDI failed to allege the elements of an “implied-in-fact” contract. To be clear, the Board can hear appeals involving implied-in-fact contracts. Because they can exist and are a thing in government contracting.
What are the elements of an “implied-in-fact” contract?
According to Judge Witwer, writing for the Board—
An implied-in-fact contract is ‘founded upon a meeting of the minds, which, although not embodied in an express contract, is inferred, as a fact, from conduct of the parties showing, in the light of the surrounding circumstances, their tacit understanding.’ The elements of an implied-in-fact contract are: ‘(1) mutuality of intent; (2) consideration; (3) an unambiguous offer and acceptance; and (4) ‘actual authority’ on the part of the government’s representative to bind the government in contract.’
(Internal citations omitted.)
The dispute involved additional services that NDI alleged were ordered by DISA’s Chief Information Officer for Operations. According to NDI, the CIO—who had negotiated prior contracts with which NDI has been involved and who thus had actual or apparent authority to bind the government—requested the NDI perform additional services under a “separate agreement” from the one in which it was currently operating as a subcontractor. According to the complaint, the CIO represented that DISA would compensate NDI for the additional work “at NDI’s standard hourly rates.”
Right there we have at least two problems.
-
Was NDI’s prime contractor aware that its customer had requested its subcontractor to provide additional services not associated with the prime contract? Seems awful close to a conflict of interest to us, but obviously we don’t have the subcontract in front of us.
-
What does the phrase “standard hourly rates” even mean? Was the CIO not aware that many contracts are competed and prices are set by contractors based on competitive pressures? Alternatively, what about negotiations? Has no contractor ever in the history of DISA ever offered lower hourly rates in order to secure the contract award? It seems to us that the DISA CIO would have understood those concepts, because (allegedly) he negotiated the prime contract under which NDI had been a subcontractor. So … what did he mean when he (allegedly) said to NDI that it would be compensated at its “standard hourly rates”?
Also, the use of the phrase “standard hourly rates” implies either a labor-hour or T&M contract. Okay. Not our favorite contract type, but okay. Now … what about travel expenses and other ODCs? Was DISA going to reimburse NDI for those non-labor expenses? If so, at what rates? Could NDI rent a limousine to transport its employees to and from the DISA site, and then bill DISA for the limo? If not, why not? What contract term would prevent it? Remember, there was no written agreement, just an alleged implied-in-fact contract.
No matter, because NDI “submitted a copy of its hourly rates” to DISA, which was allegedly reviewed and accepted.
However, one thing NDI did not do was submit any invoices to DISA as the work progressed. Because how could it? It had no contract to reference, no ACRNs to reference, no billing instructions to reference. There was nothing in DFAS’ payment systems that would let a billing clerk process payment, even if such a payment request somehow made its way to that clerk’s desk. Nope. NDI didn’t bill and the unbilled costs kept mounting up.
According to NDI, DISA promised to pay “in full” when the work had been completed. (As noted above, we wonder how the parties would know when the work had been completed, but let’s assume they would.)
After nearly two years, NDI allegedly completed its work and then submitted an invoice to DISA, an invoice that DISA did not pay.
Another five years passed. No, we don’t know why.
Nearly five years after submitting its invoice for services provided under its alleged implied-in-fact contract, NDI finally got around to filing a claim for $2.036 million. A DISA contracting officer quickly denied the claim and NDI appealed to the ASBCA. DISA moved to dismiss, arguing, among other things, that there was no agreement.
Judge Witwer denied the motion, writing –
To survive a motion to dismiss for failure to state a claim, the complaint must allege facts plausibly suggesting, not merely consistent with, a showing of entitlement to relief. Here, NDI alleges that a government official with implied actual authority represented that DISA would pay NDI’s costs in return for NDI’s provision of the additional artificial intelligence services. In particular, NDI alleges that Mr. Norwood, who had previously negotiated the terms of NDI’s subcontract on the TEIS II contract and who repeatedly authorized the issuance of Common Access Cards to NDI employees, stated that DISA would compensate NDI at its ‘standard hourly rates’ for the additional services. NDI relied on that promise and provided the requested services. The government accepted and benefited from NDI’s performance. These allegations describe the elements of an implied-in-fact contract. Thus, we reject DISA’s argument that the appeal must be dismissed because the complaint does not allege sufficient facts to suggest that an implied-in-fact contract was formed.
Because NDI has satisfied both the jurisdictional claim requirements of the CDA and the minimum pleading requirements for the pursuit of a claim before this Board, we deny the government’s motion to dismiss. Whether a contract was actually formed relates to the merits of the appeal and is not before us at this time
(Internal citations omitted.)
Let’s wrap this up with four last points.
If a contractor chooses to accept direction from a person who is not a government contracting officer, then there should be assurance that the individual providing direction has authority to bind the government.
If a contractor chooses to work without a written agreement, then there should be assurance that it will be paid for its services.
If a contractor chooses to work for years without being paid, then there should be assurances that it will be paid in full as soon as the work is completed.
If a contractor chooses to wait five years before asserting its right to payment via a claim, we think that contractor should not accept any more government contracts. If you aren’t getting paid and you think you are entitled to payment, you should file a claim quickly—certainly within a few months.
|