TLF-Contract-Claims-Insight-47.jpg

Severin Doctrine Applicability for Pass-Through Software Manufacturer Claims

While there are ways in which subcontractors may achieve privity of contract, they may not generally bring direct claims against the Government due to a lack of privity. Therefore, subcontractor claims against the Government are typically asserted by prime contractors as pass-through claims. However, prime contractors may only bring such pass-through claims if they meet the requirements of the Severin Doctrine. First articulated by the Court of Claims in 1943, the Severin Doctrine bars pass-through subcontractor claims unless the prime contractor itself remains liable to claims by the subcontractor. While the Severin Doctrine has evolved through its application to various pass-through claims scenarios, at its outset, it barred the assertion of pass-through claims unless the prime contractor either reimbursed the subcontractor due to the Government’s fault or was at least liable to make such a reimbursement in the future.

Based on the principles of sovereign acts immunity and privity of contract as applied to government contracts, the Severin Doctrine requires the prime contractor to have at least some demonstrable exposure to subcontractor liability. To prevent pass-through claims through this affirmative defense, the Government typically points to any provisions in the subcontract that tend to exculpate the prime contractor from liability to the subcontractor. When entering teaming arrangements, contractors should be aware that if the subcontract agreement contains a clause completely or specifically exonerating a prime contractor from liability to the subcontractor for pertinent damages, then the prime contractor may not assert a related pass-through claim against the Government. Prime contractors are similarly barred from asserting pass-through claims if the subcontract specifically extinguishes prime contractor liability upon the meeting of certain requirements, such as the subcontractor being granted additional time or the acceptance of final payment.

Notably, the Severin Doctrine does not bar pass-through claims if the subcontract is silent about the prime contractor’s liability to the subcontractor regarding the asserted damages. Similarly, the Severin Doctrine does not generally bar pass-through claims for equitable adjustment under the changes or differing site conditions clauses. Still, pass-through claims for equitable adjustment may be barred in situations where the prime and subcontractor have agreed to an iron-bound or full release of prime contractor liability under the subcontract. In situations where the subcontract releases the prime contractor of only certain types of liability, the adjudicative forum will determine the scope of the residual prime contractor liability based on the language of the release, the conduct of the parties, and if applicable, relevant extrinsic evidence.

In pass-through software manufacturer claims asserted by the software reseller as the prime contractor, the terms of the agreement between the reseller and the software manufacturer are reviewed for any specific or general release of liability language to determine the applicability of the Severin Doctrine. In such cases, the standard release of liability clauses for consequential damages incidental to the underlying reseller agreement, without more, will generally not be sufficient for the Government to meet its burden to invoke the Severin Doctrine to bar pass-through claims. This was demonstrated in a 2020 claim before the Civilian Board of Contract Appeals (CBCA), where a software reseller, as the prime contractor, brought a pass-through claim for a software manufacturer against the Department of Interior (DOI).

The pass-through claim alleged that the Government breached various commercial software licensing terms under a General Services Administration (GSA) Federal Supply Schedule (FSS) contract by over-deploying the commercial software in excess of the agreed-upon quantity of licenses. As a preliminary issue, the Government argued that the CBCA should dismiss the claim because it was barred through the application of the Severin Doctrine. As evidence of the applicability of the doctrine, the Government pointed to a release of consequential liability clause in the reseller agreement. The relevant clause stated that “neither party shall be liable to the other party for consequential, punitive, incidental or special damages, including but not limited to lost profits, even if such party has been apprised of the likelihood of such damages coming.” Besides pointing to this clause, the Government failed to present any other significant evidence to support its position on the applicability of the Severin Doctrine.

The CBCA was not swayed by the Government’s argument, ruling that the Severin Doctrine was not applicable in this instance. The CBCA reasoned that the clause at issue contemplated the release of the parties’ collateral liabilities incidental to the reseller agreement between them. It did not discharge the prime contractor’s liability to the software manufacturer relating to contractual disputes such as the breach of contract action forming the basis for the pass-through claim. Since the Government failed to prove that the software reseller prime contractor would not be independently liable to the software manufacturer for damages due to alleged Government actions in the pass-through claim, the Severin Doctrine was deemed inapplicable.

To bar a prime contractor’s pass-through software manufacturer or subcontractor suit against the Government pursuant to the Severin Doctrine, the Government must prove that the prime contractor is not liable to the software manufacturer or subcontractor for the costs alleged in the suit. Unless the terms of the subcontractor agreement expressly release the prime contractor from liability for the types of damages arising out of Government breach as alleged in the pass-through claim, the claim should not be barred by the Severin Doctrine. When establishing the terms of a software reseller agreement, the Government reseller prime contractor and the software manufacturer should be cognizant of the impact any general or specific release of liability clauses may have on the applicability of the Severin Doctrine. Any iron-clad or full release of liability clauses should be carefully reviewed as part of due diligence enquiries in entering teaming arrangements. When appropriate, contractors should include language that carves out an exception for liability due to Government breaches to preserve the software manufacturer or subcontractor's rights to assert pass-through claims against the Government.

This Federal Contract Claims Insight is provided as a general summary of the applicable law in the practice area and does not constitute legal advice. Contractors wishing to learn more are encouraged to consult the TILLIT LAW PLLC Client Portal or Contact Us to determine how the law would apply in a specific situation.

Related Insights

TLF-Contract-Claims-Insight-12.jpg

The U.S. Federal Government often utilizes federal supply schedule (FSS) contracts to purchase commercially available off-the-shelf software (COTS) software from reputable pre-vetted software vendors. These FSS contracts are administered by the General Services Administration (GSA), and they eliminate the need for lengthy open-market solicitations for common COTS software products. FSS contracts permit agencies to purchase COTS software products quickly and efficiently from pre-vetted software vendors using pricing that reflects volume discounts due to GSA’s government-wide purchasing leverage. Generally, the COTS software product manufacturer’s end-user licensing agreement (EULA) is incorporated into the procurement contract and dictates the Government’s use of the COTS software. The term “contractor” has been expressly defined in 41 U.S.C. § 7107(7) as a “party to a Federal Government contract other than the Federal Government.” Therefore, in COTS software product purchases, since the pre-vetted software vendor has the FSS contract with the Government, the COTS software product manufacturer is generally not considered a contractor in the traditional sense because it is not a party to the Government contract. Accordingly, since the CDA does not permit appeals by anyone who is not a party to a Government contract, COTS software product manufacturers are generally unable to bring contract claims against the Government under the CDA. However, subcontractors and certain third parties may achieve privity of contract with the Government under particular circumstances, which allows them to bring claims against the Federal Government under the CDA.

more
TLF-Federal-Procurement-Insight-12.jpg

The federal government generally procures software as commercial items. The terms and conditions governing the use of commercial software are contained in the end-user licensing agreement (EULA), which is generally incorporated into the government contract. Since the Federal Acquisition Regulation (FAR) does not provide standard licensing agreements for commercial software, manufacturers or resellers must negotiate the terms of use of such software when the EULA is incorporated into the contract. Depending on the contract, the EULA can be incorporated into an individual order or the master agreement of a government-wide acquisition vehicle, such as a Federal Supply Schedule (FSS) contract.

As relevant to government contracts, the U.S. federal government waives its sovereign immunity for liability arising from contract claims under the Contract Disputes Act (CDA). However, the government may use the Sovereign Acts Doctrine as an affirmative defense against contractor claims. Standard contract provisions within the software manufacturer’s EULA may occasionally conflict with federal laws, including the government’s rights as a sovereign. Contractors must, therefore, review their standard EULA terms and negotiate specific clauses with the software manufacturer, if necessary, before submitting them to the government for incorporation into a government contract. While contractors should review all provisions with sovereign immunity implications, they should pay especially close attention to the following standard clauses before the EULA is submitted to the government for incorporation into a federal contract.

more
TLF-Bid-Protest-Insight-13.jpg

The Competition in Contracting Act (CICA) mandates the use of procurement procedures enabling full and open competition in federal acquisition. Agencies may not place task or delivery orders that fall outside the scope of the underlying blanket purchase agreement (BPA) or indefinite delivery indefinite quantity (IDIQ) contract as such requirements are subject to full and open competition under CICA. In such protests, the protestors generally challenge the award against the master contract by alleging that the task or delivery order improperly exceeded the scope of the underlying master contract. The adjudicative forum must then decide whether material differences in scope exist between the order at issue and the relevant underlying master contract.

In B-412821, the Government Accountability Office (GAO) sustained such a bid protest challenging the issuance of an out-of-scope sole-source delivery order under a Government Services Administration (GSA) Federal Supply Schedule (FSS) Blanket Purchase Agreement (BPA). The protest involved the acquisition of Microsoft e-mail products for the Internal Revenue Service (IRS). The BPA was issued in 2013 for maintenance and software assurance services for the IRS’s existing inventory of Microsoft products and services for a period of three years. The BPA included a complete schedule of the Microsoft product licenses owned by the IRS and their quantities. Under the BPA, the IRS was expressly permitted to upgrade and use the latest version of each Microsoft product during the term of the BPA if it so chose. Additionally, if Microsoft products owned by the IRS became unsupported by the manufacturer, the IRS retained the right to convert its licenses to comparable, supported products at no cost. In other words, by utilizing this BPA, the IRS intended to keep its portfolio of Microsoft licenses up to date with the latest versions.

more
Expanded Protestor Standing for Potential Subcontractors under Percipient.jpg

Government agencies are required to acquire and use commercially available products and services to the maximum extent practicable. In the implementation of 10 U.S.C. § 3453, government agencies are required to ensure that prime and subcontractors at all levels incorporate commercially available products and services as components of items supplied to the government. Under the Tucker Act, 28 U.S.C. § 1491(b)(1), interested parties are permitted to file suit in the Court of Federal Claims (COFC) challenging (1) a solicitation issued by a federal agency, (2) an award or a proposed award of a contract, or (3) any alleged violation of statute or regulation in connection with a procurement or a proposed procurement. The Federal Acquisition Streamlining Act (FASA) of 1994 contains a “task order bar” that removes from Tucker Act coverage any protests in connection with the issuance or proposed issuance of task or delivery orders that are below the monetary threshold of $25M for defense procurements and $10M for non-defense procurements.

On June 7, 2024, in Percipient.AI v. U.S. (23-1970), the Court of Appeals for the Federal Circuit (CAFC) addressed the interplay of these statutes to carve out a new rule conferring standing upon manufacturers of commercially available products and services to bring a protest alleging harm to their direct economic interests due to the government’s violation of 10 U.S.C. § 3453 – when their product or service has a substantial chance of meeting the government’s needs, either partially or completely, and when they take care not to directly or indirectly challenge the solicitation, contract award, or proposed contract award. The decision may be of particular interest to commercial software manufacturers that produce software in emerging sectors that satisfy at least some of the government’s solicited requirements in large-value procurements. In Percipient.AI, the National Geospatial-Intelligence Agency (NGA) issued the “SAFFIRE” solicitation contemplating a single award Indefinite Delivery, Indefinite Quantity (IDIQ) contract to sustain and improve its processes for obtaining and storing visual intelligence data and integrating those capabilities with a form of user-facing artificial intelligence (AI) called computer vision (CV). The NGA simultaneously solicited Task Order 1 of the IDIQ, which, in pertinent part, directed the contractor to develop and deliver the CV suite of systems. While the protestor produced commercial software that could meet the government’s CV system requirements, it could not meet the storage component of the contract. Therefore, in reliance on the government’s and the eventual awardee’s anticipated compliance with 10 U.S.C. § 3453, the protestor chose not to bid for or protest the SAFFIRE solicitation or the eventual contract award to a large systems integrator.

more

Severin Doctrine Applicability for Pass-Through Software Manufacturer Claims

TILLIT LAW Federal Contract Claims Insights