Sometimes you may find yourself running late. It happens to the best of us for a multitude of reasons. But what happens to federal contractors when they are running late in performing under a contract and there is “no reasonable likelihood” of timely performance?
Unfortunately for contractors in this position, as illustrated by a recent Civilian Board of Contract Appeals (CBCA) decision, the result may be a default termination.
Federal contractors not so infrequently find themselves in a position where they are unable to complete performance of a contract by the agreed-upon deadline. So, what happens when the delay is neither party’s fault, but the government denies extension of the period of performance or provides inadequate extensions?
In IAP Worldwide Services, Inc. (ASBCA Nos. 59397, 59398, and 59399), the Armed Services Board of Contract Appeals found under the legal theory of “constructive acceleration” that the U.S. Army Corps of Engineers was liable for extra costs incurred by IAP due to the Corps insistence of timely contract delivery despite excusable delays.
A contractor’s performance of extra work outside the scope of the contract may go uncompensated if a contractor does not receive appropriate authorization in accordance with the contractual terms.
A Court of Federal Claims decision reinforced that a contractor should only perform work required under the terms of the federal contract or directed by an authorized government agent in accordance with the contractual terms. And importantly, a Contracting Officer’s Representative isn’t always authorized to order additional work–even if that person acts as though he or she has such authority.
They say that two things in life are guaranteed – death and taxes – and status as a federal contractor may not exempt one from the latter, according to a recent Armed Services Board of Contract Appeals decision.
In Presentation Products, Inc. dba Spinitar, ASBCA No. 61066 (2017), the ASBCA held the contractor was liable to pay a state tax, and the government had no duty to reimburse the contractor. The problem arose from the fact that the contractor did not incorporate state tax costs into its proposed price, despite being required to pay the taxes under the terms of the contract and applicable state law.
To federal construction contractors, the true legwork may seem to begin only after the government has accepted a proposal and performance has begun. However, a recent Armed Services Board of Contract Appeals decision reinforces that federal construction contractors’ work often should begin long before contract award.
In Zafer Construction Company, ASBCA No. 56769 (2017), the ASBCA rejected a construction contractor’s allegations of unilateral mistake, unconscionability, and differing site conditions (among other claims for additional costs). The problem? The contractor did not attend a government scheduled site visit, conduct an independent site visit, review technical drawings, submit any inquiries during the proposal stage, or otherwise take reasonable steps necessary to better ascertain the nature of the work prior to submitting a multimillion dollar proposal on a complex project.
The government’s use of specifications within a contract carries an implied warranty that the specifications are free from errors. When a contractor is misled by the erroneous specifications, the contractor may seek recovery through an equitable adjustment to the contract. But what happens when the government seeks services through a requirements contract and is simply negligent in estimating its needs?
A recent Federal Circuit decision, Agility Defense & Government Services, Inc., v. United States, No. 16-1068 (Fed. Cir. 2017) finds that a contractor may be able to recover damages in such instances under a negligent estimate theory.
An agency may modify a contract without running afoul of the Competition in Contracting Act, so long as the the modification is deemed “in scope.” An “out of scope” modification, on the other hand, is improper–and may be protested at GAO.
In a recent bid protest decision, GAO denied a protest challenging an agency’s modification of a contract where the modification was within scope and of a nature that competitors could have reasonably anticipated at the time of award. In its decision, GAO explained the difference between an in scope and out of scope modification, including the factors GAO will use to determine whether the modification is permissible.