July 16, 2020 Public Contract Law Journal

Close Enough for Government Work: The Economic Utility of Teaming Agreement & the Issue of Enforceability

by Michael W. Mutek
Washington Monument

Washington Monument

Michael W. Mutek is general counsel, defense, for Aerojet Rocketdyne, at the company’s defense headquarters in Huntsville, Alabama. He is a past chair of the Public Contract Law Section and currently serves in the ABA’s House of Delegates as a Section delegate.

I.  Introduction

The phrase “close enough for government work” is generally believed to have originated during World War II.1 At that time, the phrase meant that a product met the highest standards of quality because the product would not be accepted by the U.S. military unless it met such exacting standards.2 Over time, popular culture began using the phrase in an ironic sense. Eventually, that ironic and sometimes disparaging usage of the phrase changed the common meaning from something that meets the highest standards to something that is just good enough to “get the job done.”3

The phrase’s evolution from an exacting standard to one that “gets the job done” is worth considering in the context of contractor team arrangements. Such arrangements combine complementary capabilities from different companies in order to satisfy government needs and are integral to contract pursuit strategies. They “get the job done,” but enforcement of such agreements is subject to state laws that have more exacting standards.4

A good starting point is the Federal Acquisition Regulation (FAR) because it recognizes the economic utility5 of team arrangements and provides a regulatory framework that supports such arrangements.6 Contractors also recognize the economic utility of team arrangements because for many years such arrangements have provided an effective means to join forces and become more competitive.7 The FAR does not mandate that an arrangement be memorialized in an enforceable teaming agreement, and there is no simple “bright-line” test to facilitate a federal government agency’s evaluation of enforceability.8

This is significant because team members collaborating to win a government contract can find themselves in a dispute that raises the issue whether their teaming agreement is enforceable.9 Thus, it is fair to ask whether a teaming agreement is “close enough for government work” — meaning that it is recognized as valid under the FAR — even though the agreement’s governing law could find the agreement unenforceable.

Stated differently, should the economic utility of a team arrangement —  one that helps teammates pursue a government contract and may provide the government with “the best combination of performance, cost, and delivery for the system or product being acquired” — be recognized as valid under   the FAR only if the team arrangement is memorialized in a teaming agreement that would be enforceable under its governing law?10 This standard for recognition — enforceability under the agreement’s governing law — would impose an exacting requirement similar to the original meaning of “close enough for government work.” Alternatively, should a teaming agreement clearly manifesting intent to cooperate and work together be recognized as a valid team arrangement under the FAR even if enforceability under state law is uncertain? This standard would reflect the current meaning of the phrase “close enough for government work” because the teaming agreement “gets the job done.”

II.  Team Arrangements & Government Contracts11

Through the FAR framework for recognition of  team  arrangements  and  the development of internal company policies and procedures that address collaboration with other companies as a business strategy, teaming has become woven into the fabric of government contract pursuit activities.12 In fact, teaming is so common that competitive procurements routinely involve team versus team competitions.13 An important aspect of such arrangements is that they can facilitate pre-award cooperation, which includes the development of competitive strategies by the prospective prime contractor and its prospective subcontractors.14 Team arrangements can be procompetitive, enabling the teammates to create a strong and credible proposal in a situation where the companies might not be able to compete successfully on their own.15

The “holy grail” sought in government contracting is competition.16 It is the cornerstone of the government’s acquisition policy.17 Team formation can be a critical aspect of a government contractor’s competitive strategy to win a contract, and contractors have used team arrangements as such a strategy for many years.18 A contractor team arrangement serves to bring together companies with complementary capabilities that share a common goal, which usually is to win a specific contract or related group of contracts.19 A benefit can be that the past performance and experience of an intended subcontractor can bolster a prime contractor’s competitive position and address gaps in the prime contractor’s performance capabilities.20

The potential benefits of teaming have been acknowledged by the Federal Trade Commission (FTC) and the U.S. Department of Justice (DoJ). These agencies have stated that to compete in today’s marketplace, companies that are actual or potential competitors might at times need to collaborate as teammates in pursuing a government contract.21

Collaboration can provide competitive benefits, but disputes can arise.22 If the dispute is not resolved and a party seeks to end the relationship, questions concerning the agreement’s enforceability could be raised. Should the government agency awarding the contract consider the impact of an actual or even a possible dispute between team members during the source selection process? Should an agency providing credit to the prime contractor because of a potential subcontractor’s past performance, resources, capabilities, and experience consider the enforceability of the teaming agreement that the parties execute? These are among the questions that this article will examine.

Disputes can arise either before or after award of a contract. If a dispute arises before award and the government becomes aware of it, the government can consider the dispute’s potential impact on performance when the government evaluates the team’s proposal and makes a source selection decision.23 The FAR permits exchanges between government evaluators and offerors, which can be used to flesh out the actual risks to contract performance created by such a dispute.24 However, this kind of evaluation and risk analysis is not possible when a teaming agreement dispute develops after the team has been selected for award.25

Another issue that the government and prime contractors must consider is the mandate for “present responsibility.” All contractors must possess present responsibility to perform a government contract.26  Further, there cannot be an award “unless the [C]ontracting [O]fficer makes an affirmative determination of responsibility,” and without “information clearly indicating that the prospective contractor is responsible, the [C]ontracting [O]fficer shall make a determination of nonresponsibility.”27

The government assessment of present responsibility during the source selection evaluation process includes a determination that the prime contractor possesses the necessary skills, equipment, and facilities to perform the contract.28 Although generally there is no privity of contract between the government and a subcontractor in the acquisition of goods or services sought by the government, the FAR does recognize the importance of subcontractors and reserves rights for the government in the FAR subpart on contractor team arrangements that permit it to require consent to subcontracts29 and “[h]old the prime contractor fully responsible for contract performance, regardless of any team arrangement between the prime contractor and its subcontractors.”30 Because the subcontractor may be the source of necessary skills, equipment, and facilities required in the performance of the contract being pursued, the potential prime contractor is required to assess the present responsibility of its proposed subcontractors.31 The potential prime contractor’s determination of its prospective subcontractor’s responsibility may affect the government’s determination of the prospective prime contractor’s responsibility.32 However, although the government considers the resources and experience of a subcontractor, an analysis of the teaming agreement’s enforceability is not part of that review.33

Furthermore, Contracting Officers are not equipped to perform this analysis.34 Any review of enforceability would require knowledge of relevant state law. The FAR provides Contracting Officers with guidance as to the use of team arrangements because team formation is a beneficial process that is often fundamental to government contract competition and performance; however, enforceability of teaming agreements is not mentioned in the FAR.35

This article proposes that the economic utility of team arrangements supports the treatment of such arrangements as valid under the FAR without a determination as to enforceability. However, an important caveat is that if the procuring agency becomes aware of an actual dispute between team members, it can determine during the source selection process whether the dispute poses an actual risk to the performance of the contract.36 This treatment of teaming agreements is based on recognition that team arrangements provide an economic benefit and “get the job done.”37 Also, this treatment recognizes the frequent and common use of teaming agreements in government contracting in order to bring together complementary capabilities.38 Finally, it avoids speculation over whether, under the relevant state law, there could be an issue with enforceability when there is no actual dispute posing a risk.39

Of course, the government does consider risk as part of its evaluation process. It can determine not to provide evaluation credit to the prime contractor for the past performance and experience of a subcontractor for several reasons, including the fact that a dispute exists.40 The government also could inquire as to alternative sources that the prime contractor could utilize if the proposed subcontractor is not available; in fact, a prime contractor might be prudent to proactively address this issue with the customer if a dispute arises with a teammate.41

The thesis of this article is that the FAR and the economic benefit derived from team arrangements support recognition of team arrangements without an assessment under the governing law that the agreement is enforceable. This article will examine the regulatory framework and the policy that support team arrangements, discuss the process of teaming, and argue that a Contracting Officer should not be forced to adjudicate enforceability, which would revolve around key issues of the parties’ intent to be bound and the specificity of terms contained in the agreement.

III.  Regulatory Framework & Policy

A. The FAR

The FAR prescribes the rules for contracting with the federal government and is the primary document governing federal contracting actions.42 Subpart 9.6 of the FAR takes up the issue of contractor team arrangements and defines the term “team arrangement” in a manner that addresses both horizontal and vertical teaming:43

“Contractor team arrangement” . . . means an arrangement in which — (1) [t]wo    or more companies form a partnership or joint venture to act as a potential prime contractor; or (2) [a] potential prime contractor agrees with one or more other companies to have them act as its subcontractors under a specified [g]overnment contract or acquisition program.44

The FAR expresses government policy on team arrangements:

The [g]overnment will recognize the integrity and validity of contractor team arrangements; provided, the arrangements are identified and company relationships are fully disclosed in an offer or, for arrangements entered into after submission of an offer, before the arrangement becomes effective. The [g]overnment will not normally require or encourage the dissolution of contractor team arrangements.45

Some of the key benefits of team arrangements are expressly recognized in the FAR, which states that “[c]ontractor team arrangements may be desirable from both a [g]overnment and industry standpoint in order to enable the companies involved to — (1) [c]omplement each other’s unique capabilities; and (2) [o]ffer the [g]overnment the best combination of performance, cost, and delivery for the system or product being acquired.”46

Prospective contractors seeking a contract award and government agencies evaluating proposals understand that team arrangements can be an important part of a prime contractor’s proposal and can impact the competitive source selection process. The government evaluates the proposing prime contractor’s team as part of its source selection process to determine which offeror has proposed “the best combination of performance, cost, and delivery for the system or product being acquired.”47 The agency’s consideration of a subcontractor’s capabilities is proper where the offeror is proposing performance as a team.48

It is important to note, however, that the term “teaming agreement” does not appear in FAR subpart 9.6, Contractor Team Arrangements.49 Further, there is no prescribed format in the FAR for a teaming agreement; in fact, there is no express requirement in the FAR that such an agreement be written.50 However, the government may ask to see evidence of the claimed team arrangement in order to provide it with an adequate assurance that a teaming commitment exists; and the request for proposal (RFP) or request for quote (RFQ) may expressly require evidence of the team arrangement.51

Even though a teaming agreement is entered into by private parties and does not include the government, the government is fulfilling an obligation, whether it is to support national security by buying a weapon system or to ensure general welfare by buying an information technology system for use by a civilian agency, when it issues a solicitation.52 The government maintains a strong interest in team arrangements formed to fulfill government needs. As a result, the government is a third-party beneficiary of team arrangements and of the teaming agreements that memorialize the commitments of the teaming partners pursuing the award of a government contract.53

B.  Deference to Agency Discretion

Courts generally defer to an agency in the conduct of the agency’s responsibilities, including the agency’s interpretation of its own regulations.54 In Chevron U.S.A. Inc. v. Natural Resources Defense Council, Inc., the Supreme Court addressed the question of deference and stated that, if an agency reasonably interprets a statute in promulgating and interpreting its regulations, courts should generally defer to the agency’s interpretation.55 This has become known as “Chevron deference.”56 In Chevron, the Supreme Court provided a two-part test that examines whether Congress has directly spoken to the precise regulatory question at issue and, if not, whether the agency’s interpretation is consistent with the purposes of the statute pursuant to which the regulation was promulgated.57 Where “the statute ‘is silent or ambiguous with respect to the specific issue,’” the tribunal “must sustain the [a]gency’s interpretation if it is ‘based on a permissible construction’ of the Act.”58

Over the years, FAR provisions have been upheld under Chevron on the ground that Congress has not spoken directly to the precise question at issue, and the Supreme Court has extended the Chevron doctrine to agencies’ interpretations of their own regulations.59 The result is a strong presumption in favor of the validity of agency action, so long as the agency’s interpretation of its statutory authority is reasonable. Although this deference is not without criticism,60 without Chevron, agencies would act in the shadow of far greater uncertainty about whether federal courts will  obliterate  their  handiwork. In that world, courts would exercise far greater authority over the meaning of federal law — and, by implication, far greater control over the scope and substance of federal policy in virtually every significant field of regulatory activity.61 Chevron’s importance is attested to by the fact that it is arguably the most cited case in modern public law.62

As a result, contracting agencies possess discretion in determining whether to recognize a team arrangement; and the courts — and the GAO — would be understandably reluctant to second-guess a Contracting Officer’s decision or substitute its own judgment, provided that a rational basis supports the decision to recognize or not recognize the validity of a team arrangement.63

C.  State Law Is Not Binding on the Agency Examining a Team Arrangement During Pre-Award Evaluation.

As noted above, FAR subpart 9.6 addresses team arrangements but does not discuss enforceability of teaming agreements and does not mention the term “teaming agreement.” An agency will examine and may consider subcontractor capabilities when reviewing a potential prime contractor’s proposal. If an offeror is not successful in obtaining the award of a desired contract, issues including the evaluation of the winning contractor’s team arrangements are examined and a challenge in the form of a bid protest can be filed.64

Considering the value of team arrangements to a competitive proposal, it is not surprising that the enforceability of a teaming agreement under state law has been raised in the protest scenario. Thus, for example, in AllWorld Language Consultants, Inc., the protester alleged that the awardee’s teaming agreement was unenforceable under Virginia law and that the agency “unreasonably found that [the awardee] had provided evidence of a ‘binding agreement’ . . . as required by the RFQ.”65  The GAO stated in a footnote that   “the protester does not establish why GSA was bound by Virginia state law in interpreting the RFQ requirement for evidence of a binding commitment.”66

IV.  The Contracting Officer Is Not in a Position to Adjudicate Enforceability

Contracting Officers are not in a position to adjudicate the enforceability of a teaming agreement under state laws. This is because the investigation that would be required to determine the intent of the parties and the specificity of the material terms that the parties intend to include in their post-award arrangement would be too fact-intensive.

A teaming agreement is a generally deemed to be a “preliminary agreement” (i.e., an agreement that contemplates later execution of a more definitive agreement).67 More specifically, the teammates usually plan to execute a subcontract that will supersede their teaming agreement if the team’s proposal is successful.68 The questions examined to determine agreement enforceability generally are (1) whether the parties intend to enter into a binding contractual relationship, and, assuming that the parties intend to do so, (2) whether “sufficiently objective criteria” exist whereby a court can determine the terms.69 An issue can be the lack of specificity in the teaming agreement, which renders the agreement a mere “agreement to agree.”70 Typically, a mere “agreement to agree” is unenforceable.71

The clearer the intent of the parties to be bound, and the more definite  and specific the agreement’s terms, the more likely a court will hold the teaming agreement to be an enforceable contract and not an unenforceable agreement to agree.72 However, because team arrangements may be formed and collaborative proposal efforts begun months before an agency has published a final Statement of Work (SoW), the parties would have to be clairvoyant to determine exactly what the final SoW will look like — and accordingly how they should allocate workshare, and negotiate price, warranties, or other terms of their arrangement. This may be possible in some contracts, for example contracts for the purchase of commercial or off-the-shelf products. However, determination of the scope and details or a final SoW is difficult in situations where development is involved or where customer needs are evolving.73

Any expectation that a definitive and final SoW can be ascertained early in the process also ignores certain realities of government contracting, including the fact that the SoW can and often does change and that the final negotiated contract between the prime contractor and the government customer may differ from that contemplated when the government first issued its RFP. Throughout a competition, the stakeholders to a team arrangement — the prime contractor seeking the award, the subcontractor(s) seeking subcontract(s), and the government evaluating the team’s proposal to obtain a needed product or service — anticipate that the team will work together and that the subcontractor(s) will participate in the performance of the contract. But the precise parameters of the arrangement must often await changes in the RFP, definitization of the SoW, negotiation of the proposals, agreement on price, and award of a contract.74 These realities that can change the scope of the potential contract and its subcontracts create fertile ground  for  disputes, and those disputes could end up implicating issues of enforceability of the teaming agreement.75 However, the economic benefits of establishing team arrangements to compete for government contracts — the establishment of     a competitive team between the prime and subcontractor(s) and the provision of a competitive offering for the government — justify recognition of the team arrangement in the absence of an existing dispute that jeopardizes the arrangement and future contract performance.

What follows is not an exhaustive survey of all cases that have addressed disputes between teaming partners. Instead, this review of several key cases is presented in order to indicate the difficulty that exists in determining whether a teaming agreement would be found to be enforceable under its governing law. The purpose of this review is to show that it would be impractical for a Contracting Officer to be required to examine a teaming agreement in order to determine the enforceability of the agreement.

A.   Intent

The vast majority of team arrangements are performed without a dispute. The parties in this marriage of convenience share the mutual goal of winning the contract. The issues that may arise usually are resolved through negotiation.76 If a dispute occurs, the parties may utilize the “disputes” provision of their teaming agreement.

The “disputes” provision may provide for dispute resolution through negotiation, and it is not uncommon for a teaming agreement to provide for escalation of the dispute’s negotiation upward through senior management ranks of the companies in the hope that the parties can resolve the matter.77 If the dispute is not resolved, the “governing law” provision kicks in, and the venue may be prescribed.

The party alleging breach of the teaming agreement will need to establish the existence of an enforceable agreement.78 A lack of enforceability may be raised as a defense by the party alleged to have breached the agreement.79 If enforceability is raised, the first issue to be addressed by a court may be intent.80 

A court examining the intent of the parties to the teaming agreement must balance interests. It does not want to require performance of contractual obligations when the intent of the parties was not to be bound until the execution of a definitive subcontract, but the court also seeks to enforce intent to be bound by the teaming agreement.81 For example, a prospective subcontractor may be denied its anticipated work. This aggrieved subcontractor scenario is a good starting point to discuss enforceability. This scenario — where the intended subcontractor expends time, money, and effort to help the prime contractor achieve a contract award and may have given up other opportunities only to be denied its intended work — may be referred to as “being left at the altar.”82 This type of dispute could arise after evaluation of the proposal that includes the subcontractor’s past performance and prior experience by the source selection team.83 In “left at the altar” cases, there may be some element of a lack of good faith in that the subcontractor contributed to the prime contractor’s success in winning the award of the pursued contract.84

This scenario is also a good starting point because Air Technology Corp. v. General Electric Co., the case generally accepted as the first reported team arrangement decision, is a “left at the altar” case.85 This 1964 case presented the situation where the parties entered into an oral agreement and agreed that they would be a “team member” in the prime contractor’s proposal to the Air Force.86 The Massachusetts Supreme Judicial Court, affirming the decision of a master based upon its own review of the record, found, “[the prime contractor] sought [the subcontractor]’s aid in obtaining and carrying out a prime contract for” the Air Force.87 The bargain was that, in return for the subcontractor’s support, the prime contractor undertook to issue a subcontract for specified work that would allow the subcontractor a “reasonable opportunity to recover its costs plus a fair profit.”88

The Air Technology court examined intent and rejected the prime contractor’s argument that “its obligation to [the subcontractor] was at most to negotiate a subcontract and that such an obligation is too uncertain to be enforceable,” and held that, “[w]hatever uncertainty may have existed about the subcontract does not preclude recovery by [the subcontractor].”89 In affirming the enforceability of the contract, the court held, “[t]he use of the term ‘team member’ leads us to infer that the parties intended a contractual association in some form of joint undertaking.”90

Another “left at the altar” decision resulted in a Virginia court finding “specific performance not only appropriate, but necessary,” because the clear intention of the parties was that the intended subcontractor would receive  the work.91 In EG&G, Inc. v. Cube Corp., the court rejected the notion that the teaming agreement was merely an agreement to agree, finding instead that    it was a binding and enforceable contract because, among other reasons, the parties began performance prior to the breakdown of negotiations over the subcontract.92 In this case, specific performance was possible because the court examined the intent of the parties, which was that the subcontractor will be performing “certain functional areas as a subcontractor.”93

In another “left at the altar” teaming decision, the U.S. Court of Appeals for the Third Circuit held that a teaming agreement, which provided that    the subcontractor would assist the prime contractor in preparing its bid, was enforceable because of the intent of the parties.94 In that case, ATACS Corp. v. Trans World Communications, Inc. (ATACS), the customer was Greece, and it sought bids to manufacture communications shelters for its army.95 ATACS, the intended subcontractor, and Trans World, the intended prime contractor, worked together and the team submitted the lowest bid.96 The arrangement fell apart when Trans World revealed that it had been soliciting other proposals from other companies for the subcontract and used pricing information from other companies to request that ATACS lower its price.97

Then, after Trans World selected another company as its subcontractor, ATACS brought an action asserting, among other things, breach of contract.98 With respect to intent to be bound, the court noted that “[t]he record contains numerous correspondences by both parties clearly indicating their ‘inten[t]  to team.’”99 In addition, Trans World represented in its proposal to the customer that ATACS “constituted part of the ‘team’ that would undertake the project.”100 The representation was a factor in determining the agreement’s enforceability.101

ATACS summarized the issue of intent, stating, “[i]t is by now hornbook law that ‘the test for enforceability of an agreement is whether both parties have manifested an intention to be bound by its terms and whether the terms are sufficiently definite to be specifically enforced.’”102 The ATACS court said:

With teaming agreements, courts are particularly sensitive to what the parties intended in agreeing to “team” — that is, searching for sufficiently definite terms for enforcement other than the simple promise to enter into a subcontract at a later date — and whether that teaming agreement was intended to bind the parties during the various stages of government contract procurement.103

The court also cited the Uniform Commercial Code for the proposition that “[a]n agreement for sale which is otherwise sufficiently definite . . . to be a con- tract is not made invalid by the fact that it leaves particulars of performance to be specified by one [of ] the parties.”104

A more recent Florida U.S. District Court decision, Premier Gaming Trailers LLC v. Luna Diversified Enterprises, Inc., addressed a partner “left at the altar” without a subcontract.105 The prime contractor used its partner’s bid information in the proposal that it submitted to the Army.106 Then, it terminated the relationship after receiving an Army prime contract in order to find a less expensive supplier.107 The district court ordered the prime contractor to pay damages and costs to its partner due to the failure to recognize their unwritten agreement.108 This court focused on the use of the teammate’s information as an indication of intent and the fact that the teammate was part of the winning proposal.109

The Delaware Court of Chancery applied a similar objective approach in interpreting a memorandum of agreement (MOA), another form of preliminary agreement, often similar in terms to a traditional teaming agreement, in accordance with industry customs.110 The court, in denying the motion to dismiss, found the facts pled supported that an enforceable agreement could exist.111 In examining intent to be bound, the court said, “Delaware adheres to the ‘objective’ theory of contracts: a contract’s construction should be that which would be understood by an objective, reasonable third party.”112 The court noted that it “looks for allegations suggesting an objective manifestation of intent to be bound by the MOA.”113 The court found that “a rough skeleton of definite obligations exists in the MOA upon which prior course of dealings and industry custom could, by reasonable inference, add sufficient flesh to justify enforcement of the resulting form.”114

Review of cases that have examined teaming agreements illustrates that intent is relatively simple to ascertain when compared to specificity of terms.115 That may be because disputed teaming agreements are those where there has been great reliance upon and considerable activity in furtherance of the parties’ pursuit of a contract award. The activities of the parties may illustrate “an objective manifestation of intent to be bound” by the teaming agreement.116 The second question addresses the specificity of terms and this requirement to find an enforceable teaming agreement is not as simple to meet, as discussed below.

B.  Specificity of Terms

The more difficult issue faced by a contractor seeking to enforce a teaming agreement is proving that the terms of the agreement are specific enough to warrant enforceability. Virginia courts have garnered attention in teaming agreement disputes. Virginia is a key area for government agencies and is home to many government contractors who use Virginia as governing law for teaming agreements.117 As a result, several teaming agreement disputes have used Virginia law, which has of late exhibited a strong focus on the specificity of the teaming agreement’s material terms.118 As noted above, specificity may be difficult to achieve in the pre-award environment where a teaming agreement is executed.

In W.J. Schafer Associates, Inc. v. Cordant, Inc., the Virginia Supreme Court held that the teaming agreement at issue was unenforceable on the ground that the teaming agreement was “too vague and indefinite to be enforced.”119 The court found that the agreement showed that the parties knew that the required items made by the subcontractor (called “digitizers”) might not be available for use if the contract were awarded.120 The court also noted that the teaming agreement stated that the prime contractor 

“shall make a determination, through consultations with [the subcontractor], on  the probability of [the digitizer’s] availability by contract award” and that, “[i]f sufficient and satisfactory progress has not been made in order to make the [digitizer] available by contract award, [the prime contractor] reserves the right, in its sole discretion, to pursue a replacement product.”121

As a result, the court found that, by its express terms, the teaming agreement “was not an enforceable contract for the sale of digitizers.”122

In the EG&G “left at the altar” case mentioned earlier, the court issued an injunction compelling specific performance.123 The court’s decision demonstrated that Virginia courts will uphold a bargain that creates an enforceable right under Virginia law, whether called a teaming agreement or something else, and found that the teaming agreement was enforceable.124 In that case, the joint NASA and Navy solicitation sought bids “for the procurement of operations and maintenance support services” at one of NASA’s flight facilities, and the procurement was a small business set-aside.125 Under the teaming agreement, EG&G was to assist Cube in preparing its bid, and Cube would award EG&G a subcontract.126 Cube was awarded the contract but, after performing under a letter subcontract, the teammates were unable to reach agreement regarding the specific terms of the subcontract.127 Then, Cube sent EG&G a letter stating that, because the parties had reached an impasse, the relationship would end, and EG&G brought an action for specific performance of the teaming agreement.128 The court held that the teaming agreement was sufficiently definite.129

The EG&G court distinguished the facts faced by the Schafer court and stressed that the teaming agreement contained an obligation to subcontract, which was lacking in Schafer.130 The EG&G teaming agreement was binding because it specifically said that, if Cube were awarded the contract as prime contractor, “EG&G would be a subcontractor.”131 The EG&G counsel involved in this litigation felt that this “would be” language was “the icing on the cake,” and it was in addition to the fact that the agreement included specific terms including a defined work scope.132

The ATACS case, discussed in the section on intent, was decided at a time when no Pennsylvania case had addressed teaming agreement enforceability.133 The defendant prime contractor argued that “Pennsylvania law would not recognize such an arrangement without a finalized subcontract because of the absence of an essential term.”134 In ATACS, the particular essential term asserted by the defendant was the price of plaintiff’s subcontract, and the defendant emphasized that the parties never reached a final agreement on price, which, defendant argued, “must prove fatal to contract formation.”135 The court noted that “[t]he fact that the parties never finalized an implementing subcontract is usually not fatal to enforcing the teaming agreement on its own” and said that “Pennsylvania courts have long since recognized that ‘the paramount goal of contractual interpretation is to ascertain and give effect to the intent of the parties.’”136

The court went on to say, “Indeed, the omission of an essential term in a contract, such as price, does not vitiate contract formation if the parties otherwise manifested their mutual assent to the agreement and the terms of that agreement are sufficiently definite.”137  The court said that it would “look to: (1) whether both parties manifested an intention to be bound by the teaming agreement; and (2) whether the terms of that agreement are sufficiently definite.”138 The court found that “[a]fter a thorough review of the relevant correspondences,” the lower court “concluded that the plaintiffs established sufficiently definite terms of the teaming arrangement,” and the court of appeals affirmed.139 The court went further and stated that an agreement can contain open terms that will be addressed in the future even if the open terms are essential and clear intent to be bound is evident.140

Cyberlock Consulting, Inc. v. Information Experts, Inc. is a Virginia decision that has received much attention and has been debated by government contracting practitioners because its mandate for specificity in teaming agreements may be difficult to achieve.141 Another concern is that the decision may ignore certain realities of the government contracting industry.142 For example, in many situations, it may be impossible to achieve such specificity before contractor selection and prime contract award.

However, Cyberlock does not necessarily lead to the death of teaming. That is because the parties in this case had shown the court what they could achieve in a teaming agreement between them.143 The teaming agreement in dispute was the parties’ second teaming agreement.144 Their first teaming agreement had achieved — the court noted — the actual negotiation of a subcontract.145 The court said that “one of the attachments to the First Teaming Agreement, Exhibit D to that agreement, was the specific subcontract which the parties intended to enter into upon the award of the prime contract.”146

Cyberlock claimed that it was owed a subcontract from Information Experts, Inc. (IE), the prime contractor, as a result of the second teaming agreement.147 This second teaming agreement was entered into to bid on a contract issued by the Office of Personnel Management (OPM); the teaming agreement contained a merger or integration clause, which stated that the agreement “constitute[d] the entire agreement of the parties hereto and supersedes all prior and contemporaneous representations, proposals, discussions, and communications, whether oral or in writing.”148

The second teaming agreement included a statement of work indicating that, in the event of an award of a prime contract, IE would perform fifty-one percent of the work and Cyberlock would perform forty-nine percent.149 The important nuance in this case was, as the court pointed out in the very beginning of the decision, the first teaming agreement between the parties included as an attachment the subcontract the parties intended to and did execute upon contract award, but the second teaming agreement said that its terms were subject to termination upon the “failure of the parties to reach agreement on a subcontract after a reasonable period of good faith negotiations.”150

OPM awarded the prime contract to IE and, after a month of negotiations on the terms of the subcontract resulted in no agreement, IE terminated negotiations.151 The court noted that, while the agreement did contain language indicating the parties planned to enter into a subcontract in the event IE was awarded the OPM contract, the parties never negotiated or agreed to a specific subcontract for the second teaming agreement (as they had for the first).152 The court held the agreement read as a whole indicated that the teaming agreement language set forth a framework for the subcontract negotiation.153 One way to read this case is that the lack of specificity in the second teaming agreement indicated a lack of intent given the first agreement’s inclusion of a negotiated subcontract.

A post-Cyberlock decision of the Virginia Supreme Court involved a small business set-aside, and the court noted that the negotiations for a contract with the Defense Threat Reduction Agency did not result in an agreement.154 Two subcontractors then alleged breach of the teaming agreement and the non-disclosure agreement (NDA) with the prime contractor.155 In Navar, Inc. v. Federal Business Council, the Virginia Supreme Court emphasized the lack of evidence presented at the trial court, which had found for the aggrieved subcontractors.156 The Virginia Supreme Court noted that the subcontractors “did not present any evidence to support their argument beyond arguing that they were entitled to a full [forty-nine percent] workshare because the [t]eaming [a]greement stated Navar would ‘receive, at a minimum, [fifty-one per- cent] of the labor hours and labor dollars.’”157 The court also noted that this figure may simply reflect attention to the applicable regulatory requirement158 that the prime contractor “perform at least [fifty] percent of the cost of the contract incurred for personnel with its own employees.”159 Further, and in what could be an important statement, the court pointed out that the subcontractors “did not present any expert evidence to support their argument that the standard in the industry was that subcontractors were guaranteed [forty-nine percent] of the work share. The evidence showed email exchanges mentioning workshare percentages, but no written documents were produced regarding any actual agreement governing the workshare split.”160

The Navar court found essential terms lacking and found no basis for determining damages, such as testimony from an expert witness.161 Essential terms that were lacking in this case appear to be specific work share instead of a percentage and a means of determining damages in the event of a breach.162

This case may illustrate the difficulty that exists for a disgruntled teammate to adequately prove damages and may provide a reason to consider the issue of damages in teaming agreements. In essence, addressing damages in the teaming agreement could serve as a sort of prenuptial agreement if there is a break-up. One basis of damages that may be ascertainable is the amount of bid and proposal expense incurred to support the pursuit of the contract. This would represent actual damages and merely compensates the aggrieved team member for the actual expense incurred. Expectation damages, such as lost profits, would be difficult to prove given the uncertainties of future contract performance.163 The issue of damages would not, however, be relevant were a Contracting Officer to seek to examine the enforceability of a teaming agreement. The Contracting Officer would focus on sufficient specificity to deem the teaming agreement enforceable.164

The Navar case, rather than Cyberlock, was used by the Virginia Supreme Court in the more recent case, CGI Federal Inc. v. FCi Federal, Inc., where the court affirmed the lower court’s action setting aside a jury verdict for twelve million dollars in damages arising out of breach of contract and fraudulent inducement claims.165 The court said this teaming agreement did not create an enforceable obligation to enter into a subcontract because language expressly conditioned the subcontract on future events and negotiations.166

Although rarer than an intended subcontractor being left at the altar, teaming agreement disputes have also arisen in situations where a planned subcontractor leaves the team and the prime contractor seeks to keep the planned subcontractor on the team, perhaps as a result of shared proprietary or competitive information. A case from Virginia presented that situation. In this case, A-T Solutions, the prime contractor, sought to keep R3, the intended subcontractor, from becoming a member of a competing team.167 That case, which was a bench decision on a motion for a preliminary injunction, interjects the twist of a cancelled solicitation.168

After signing the teaming agreement, both companies commenced their collaboration but on July 17, 2015, the government cancelled the solicitation “to allow for a reassessment of the mission requirements and revisions.”169 A revised solicitation was issued on December 10, 2015, and bids were due January 11, 2016.170 However, the intended subcontractor told A-T Solutions that the teaming agreement ceased to be valid as a result of the July solicitation cancellation.171

A-T Solutions then sought to prevent its teammate from competing against it and brought suit, arguing that it was entitled to specific performance compelling R3 to team with A-T Solutions for the program.172 R3 argued that  there was no enforceable contract.173 Ruling from the bench on A-T Solutions’ motion, apparently the day after proposal submission closed, the judge rejected A-T Solutions’ request.174

These decisions show that a review of enforceability examines intent and the specific terms in the teaming agreement considering the surrounding actions of the parties in the effort to determine whether the agreement will be deemed enforceable. This process is not simple and not the type of water into which a Contracting Officer should attempt to wade during the evaluation of a proposal.

C.  Oral Teaming Agreements

The FAR does not specify a requirement that a teaming agreement be in writing, although the RFP may require evidence of a teaming agreement.175 Oral teaming agreements exist although they are not as common as in the past.176 Air Technology Corp. v. General Electric Co., the first reported teaming agreement case, discussed earlier, involved an oral teaming agreement.177

Other oral teaming agreements have been the subject of disputes. For example, in 2000, the Ninth Circuit considered the enforceability of an oral agreement to enter into a teaming agreement.178 The hopeful subcontractor, Cable & Computer Technology, Inc. (CCT), engaged in negotiations with Lockheed Martin Corp. (Lockheed) over the terms of a teaming agreement, but never executed the agreement.179 On the one hand, Lockheed claimed that no contract existed, explaining “that all the parties did was to try, unsuccessfully, to work out a ‘teaming agreement,’ which [the Boeing Company (Boeing)] required to be submitted as part of the bid.”180 CCT, on the other hand, claimed that it had a teaming agreement with Lockheed.181

Lockheed decided to keep the work in-house and worked with an affiliate, instead of CCT, who then sued to enforce the terms of the draft teaming agreement.182 The district court found for Lockheed, but the Ninth Circuit disagreed, stating that the district court’s analysis “avoid[ed] the question of whether there was an oral contract” to execute a teaming agreement.183 The circuit court found that CCT had provided “significant, probative evidence” that CCT and Lockheed had orally agreed to team.184 Agreeing that “[n]o naked agreement to agree constitutes a contract,” the court nevertheless went on to say that “CCT offered in evidence to the district court . . . an exchange of promises, supported by consideration, to be a team with [Lockheed] and  as a team submit a bid to Boeing.”185 The court explained that, “[u]nlike an agreement to agree, an agreement to use best efforts to achieve a common objective is a closed, discrete, and actionable proposition. As might be expected, the law of California is no different from this statement by Judge Becker of what is the law of other American jurisdictions.”186

The district court reduced the damages, and Lockheed appealed “the damages approved by the district court, arguing that CCT is no more than a disappointed bidder and should recover no more than the expenses incurred in its reliance.”187 The Ninth Circuit held:

The defendants in their present brief attack the jury-awarded [punitive damages] of $25,735,000 against each of the two Lockheed subsidiaries, characterizing them as “gigantic” and out of line with other punitive awards in California. But the district court has already reduced the [punitive damages award] to $12.8 million against Sanders and the same amount against Owego.188

The Ninth Circuit said that the punitive damages were deserved and affirmed the judgment of the district court.189

The cases examined in this section of the article reveal the challenges that exist in determining teaming agreement enforceability. They support the proposition that this determination is not an activity that a Contracting Officer should engage in during a source selection.

V.  Bid Protests Challenging Team Arrangement Recognition

Disappointed competitors have challenged the award of a contract on the basis that the winning team included a teaming agreement that would be deemed unenforceable.190 The contract awardee’s teammate may have provided in the source-selection evaluation what were deemed essential capabilities as well as favorable past performance.191

It has been established that an agency’s consideration of a subcontractor’s capabilities is proper where the offeror is proposing performance as a team.192 However, as stated earlier, FAR subpart 9.6 does not address enforceability of the team arrangement and does not prescribe a specific type of teaming agreement.193 In addition, a predicate to the examination of the enforceability issue should be the existence of a dispute; otherwise, the enforceability issue is not ripe for adjudication.

GAO bid-protest decisions state that the agency has discretion in evaluating team arrangement issues in protests.194 In one protest, Rohmann Services, Inc., the protester alleged improper evaluation of an unsigned teaming agreement.195 The GAO denied that challenge and found that the RFP did not require submission or evaluation196 of teaming agreements.197

In another protest, the protester alleged that the agency improperly considered the experience and past performance of teaming partners “because of the vague and/ or limited roles that these entities would have in performing the awarded contract.”198 Again, this protest was denied by the GAO, which found that the Contracting Officer reasonably concluded that the teaming partner would perform the total effort promised, and that “its role would include — but not be limited to — the specific tasks set forth in the teaming agreement.”199

In a different protest, Beretta USA Corp., a protester challenged its exclusion from consideration based on lack of information in its teaming agreements in a situation where the RFP required the agency to “determine the commitments with key suppliers and how each offeror has sourced or will source said key suppliers.”200 The GAO denied the protest, finding the deficiency assigned by the agency was rational where the teaming agreements lacked information to permit the evaluation of the teammate’s ability to meet its delivery schedules.201 The GAO noted that “the agency did not ignore the teaming agreements but expressly found that the agreement between [the awardee] and its ammunition supplier did not provide a ‘level of commitment to verify delivery.’”202

Another protest, AllWorld Language Consultants, Inc., raised the issue of teaming agreement enforceability under Virginia law, the governing law for the teaming agreement at issue.203 The protester alleged that the agency could not consider the capabilities of a teaming partner since the awardee did not have a “binding agreement” with its teaming partner.204  That was because the teaming agreement said that “the [p]rime [c]ontractor intends to award a subcontract to the [s]ubcontract[or].”205 Declining to examine state law principles on teaming agreements, the GAO accepted the Contracting Officer’s statement that the proposal reflected a “binding commitment.” 206 Although it can be argued that “binding commitment” is ambiguous, the GAO’s decision examined the intent of the parties, and no dispute between the teammates was identified in this decision.207

Furthermore, in a different protest, Mission Services, Inc., the GAO examined a situation where the RFP required the provision of fully executed copies of entire teaming agreements.208 The RFP defined an “enforceable agreement” as:

A written and signed agreement (by both parties) that details that all parties have agreed to a business relationship for this procurement. This document must be clear that both parties have defined and agreed to the extent of the relationship to include the type or types of work the subcontractors/ partners shall perform and what areas of the base [indefinite-delivery, indefinite-quantity contract statement of work] they will cover. The agreement shall be specific in nature.209

Notably, in this protest decision the GAO did not define enforceability by reference to a determination of enforceability under state law, but looked to indicia of intent to be bound and to the specificity of the agreement as required  in the RFP.210 The GAO noted that the provision of teaming agreements that meet the RFP’s definition of enforceable agreement resulted in favorable consideration in accordance with the RFP.211

VI.  Alternatives to Traditional Teaming Agreements & Issues Posed

State law generally requires clear intent and specificity of material terms to find a teaming agreement enforceable.212 Despite this requirement, some companies, when faced with a tight competition schedule and a need to create a team, have utilized certain alternatives to traditional teaming agreements.213 Generally, such alternatives are simpler and quicker to negotiate, important points when competition for a contract commences. These alternatives are being used even though the use of such agreements may translate to enforceability issues.

The reality is that companies, particularly companies that frequently work together, may choose to rely more on the strength of their relationships and adequate due diligence in the selection of teammates and less on the terms of the written agreement to keep the team together. Teaming agreements take time to negotiate, and time is precious in the heat of a competition.

In informal discussions with business and proposal managers of defense contractors, the top three concerns with regard to team arrangements consistently were: (1) Will this teammate improve my probability of winning and give the customer a strong offering?; (2) Can the companies work well together?; and (3) Are there any issues with this teammate that could impair the team’s selection for the contract award? Enforceability of the teaming agreement did not make the list. Simply put, these managers expect the mutual goal to win the contract to be sufficient to keep the team together and do not anticipate a dispute that would cause the team to break up.

As a result, it is not surprising that alternatives are being used, even though some alternatives may be less likely to be enforceable because they lack the specificity of terms that enforceability demands. One rationale for such alter- native agreements is that there should be evidence manifesting the intent to work together but, in some cases, it is not possible to address material terms. For example, when an indefinite delivery indefinite quantity contract award is sought, the goal is to win the contract that would enable the team to seek later task or delivery orders. There may be no actual work that comes with the initial award.

Benefits gained through use of the alternatives to traditional teaming agreements include the ability to provide written evidence of the arrangement to the government customer in the proposal in addition to being simpler and easier to negotiate, which saves time and money. At the same time, often alternatives are not exclusive and workshare is not guaranteed. For the potential subcontractor, that may be a significant downside.

These alternatives come in various forms including an enhanced non- disclosure agreement (NDA) that addresses a specific opportunity that the team seeks to pursue. Sometimes referred to as an “NDA on steroids,” this form of alternative teaming agreement can be useful with commercial companies that lack experience in government contracting.214 Such an agreement may facilitate the commercial company’s willingness to support the proposal effort. Another variation is sometimes called a “bidding agreement” and is an agreement that the supplier will support the prime contractor with information useful in the proposal and that the supplier intends to submit a price proposal.

An alternative that does require considerable effort but could be useful if several proposals are contemplated is the development of a blanket or master purchase agreement that authorizes the release and fulfillment of purchase or task orders by the prime contractor to the supplier. This provides evidence  of an established relationship and avoids the material terms issue because the terms, including price, are negotiated as part of the master purchase agreement and would be applicable to the several proposals.

VII.  Conclusion

Team arrangements are common in government contracts. Although the FAR addresses the government’s recognition of contractor team arrangements as well as the economic utility of such arrangements, a teaming agreement’s enforceability looks to the law of its governing state. This interplay may raise the question whether there can be a valid team arrangement under the FAR if, in the event of a dispute, the teaming agreement used by the parties could be deemed unenforceable. The answer should be that a team arrangement should be treated as valid manifestation of the team members’ intention to collaborate and perform the contract if awarded. This would be the case under the FAR, despite potential unenforceability under the teaming agreement’s governing law. Treatment of a teaming agreement is an issue of agency discretion, which should be given deference if the determination has a rational basis.

The FAR neither mandates a specific type of agreement to be used by contractors to combine their capabilities in pursuit of a government contract nor addresses the enforceability of teaming agreements. In fact, the FAR does not require a written teaming agreement. However, the government can inquire into the arrangement to satisfy itself that the parties intend to work together and that they possess the requisite responsibility requirements prescribed in the FAR to perform the government contract.215 The federal government is not bound by state law. Furthermore, the government is not in a position to adjudicate enforceability. As the cases indicate, the examination of intent and specificity does not involve a simple “bright line” test, but an examination that may include review of the parties’ “surrounding actions.” This is not a simple determination.

The actual existence of a dispute before the award of the contract presents a scenario that could reasonably raise concerns about the availability of the subcontractor to perform the contract. This uncertainty could impact contract performance. Such a situation could be considered as a risk in the source selection evaluation. However, enforceability generally should not be an issue unless there is evidence of a dispute that is ripe for adjudication. In the absence of an actual dispute, a teaming agreement reflecting the parties’ intent to be bound in a team arrangement should be deemed “close enough for government work.”

In practice, the vast majority of team arrangements are held together by mutual interest and the parties usually satisfy themselves through due diligence that they can work together to achieve their mutual goal. Such arrangements often are a key component of a government contractor’s competitive strategy and have been used in government contracting for a long time. A very small percentage of teaming agreements generate significant issues that require a review of enforceability. As a result, team arrangements are likely to continue to be an important tool for contractors seeking the award of a government contract despite enforceability concerns.

  1. See Close Enough for Government Work, Wiktionary (Oct. 15, 2019), https://en.wiktionary.org/wiki/close_enough_for_government_work [https://perma.cc/F5BD-Q39F]; see also Jonah Goldberg, “Good Enough for Government Work,” Nat’l Rev. (June 9, 2008), https://www.nationalreview.com/corner/good-enough-government-work-jonah-goldberg-2/ [https://perma.cc/52JZ-YT6K].
  2. See Steve Kelman, Good Enough for Government Work?, Fed. Computer Wk.: The Lectern (Jan. 2, 2018, 11:44 AM), https://fcw.com/blogs/lectern/2018/01/good-enough-for-government-work-kelman.aspx [https://perma.cc/P2WU-ZYU4].
  3. See Barry Popik, “Close Enough for Government Work” (“Good Enough for Government Work”), Big Apple (May 30, 2010), https://www.barrypopik.com/index.php/new_york_city/entry/close_enough_for_government_work_good_enough_for_government_work [https://perma.cc/AU5Q-LUL2].
  4. See Michael W. Mutek, Contractor Team Arrangements—Competitive Solution or Legal Liability: The Deskbook for Drafting Teaming Agreements 77 (2006).
  5. Economic utility is the “[a]bility of a good or service to satisfy one or more needs or wants of a consumer.” Economic Utility, Bus. Dictionary, http://www.businessdictionary.com/definition /economic-utility.html [https://perma.cc/G7VY-RCGZ] (last visited Feb. 14, 2020).
  6. See FAR 9.602.
  7. See Robert G. Hanseman & Catharine Kidd, Enforceability of Teaming Agreements, 46 Procurement Law. 18, 18 (2010).
  8. The issue of enforceability is not addressed in the FAR. See generally FAR 9.6. However, the importance of teaming agreement enforceability has increased, and is evident in the study of decisions rendered on teaming agreement enforceability, which include numerous advisories and other articles that report on the decisions and provide advice to government contractors. See, e.g., Antonio R. Franco, Teaming Agreements: Are They Necessary or Not Worth the Effort?, Piliero Mazza (Jan. 10, 2019), https://www.pilieromazza.com/teaming-agreements-are-they-necessary-or-not-worth-the-effort [https://perma.cc/XPJ5-77J6]; Dan Johnson, How Enforceable Are Teaming Agreements?, Nat’l Def. (Sept. 28, 2018), https://www.nationaldefensemagazine.org/articles/2018/9/28/how-enforceable-are-teaming-agreements [https://perma.cc/AJW5-MFYW]; Paul R. Hurst & Kendall R. Enyard, Virginia Supreme Court Puts Contractor Teaming Agreements on Life Support, Steptoe & Johnson LLP (July 17, 2018), https://www.steptoe.com/en/news-publications/contractor-teaming-agreements-on-life-support.html [https://perma.cc/EP4Y-PK6U]; J. Patrick McMahon, Do You Intend Your Teaming Agreement to Be Binding and Enforceable?, McMahon, Welch & Learned, PLLC (Mar. 9, 2018), https://www.mwllegal.com/do-you-intend-your-teaming-agreement-to-be-binding-and-enforceable [https://perma.cc/9L7P-9XE9]; James Y. Boland, Don’t Get Left at the Altar: Mere “Agreements to Agree” Are Not Enforceable, Venable LLP (Aug. 17, 2016), https://www.venable.com/insights/publications/2016/08/dont-get-left-at-the-altar-mere-agreements-to-agre [https://perma.cc/3NMP-KRTN]; Michael W. Mutek & Thomas P. Barletta, Teaming Is Not Dead—But Contractors Must Heed Decisions on Enforceability, Steptoe & Johnson LLP (Feb. 4, 2016), https://www.steptoe.com/en/news-publications/teaming-is-not-dead-but-contractors-must-heed-decisions-on-enforceability.html [https://perma.cc/T82Y-LV9G].
  9. See, e.g., Cyberlock Consulting, Inc. v. Info. Experts, Inc., 939 F. Supp. 2d 572, 577 (E.D. Va. 2013), aff’d, 549 F. App’x 211, 212 (4th Cir. 2014). For example, in Cyberlock Consulting, Inc. v. Information Experts, Inc., the court found that the agreement in dispute was merely one to negotiate an undefined scope of work, which rendered the agreement unenforceable. See Cyberlock, 939 F. Supp. 2d at 582. This opinion is among those that have generated controversy and concern because of the requirement for considerable specificity in the teaming agreement. See, e.g., Madalyn A. Murtha, The Enforceability of Teaming Agreements in Government Contracting and Its Effect on Agreement Formation, 49 Procurement Law. 22, 22, 27 (2014). Such specificity may be difficult to achieve in a pre-award setting. This represents the exacting standard discussed in this article.
  10. FAR 9.602(a)(2).
  11. This article focuses on traditional prime contractor and subcontractor team arrangements, and does not address General Services Administration (GSA) Schedule Contractor Team Arrangements (CTA), which constitute arrangements where “two or more GSA Schedule contractors team together to provide a total solution to meet a customer’s needs.” Contractor Team Arrangements, U.S. Gen. Servs. Admin. (last updated June 4, 2019), https://www.gsa.gov/buying-selling/purchasing-programs/gsa-schedules/schedule-features/contractor-team-arrangements [https://perma.cc/4SHX-XZ53]. Pursuant to a GSA Schedule CTA, the teaming contractors seek to complement each other’s schedule capabilities and join forces in order to “compete for orders for which they may not qualify independently.” Id. “GSA encourages the use of CTAs to meet buyer’s requirements,” and FAR 9.6, Contractor Team Arrangements, does not apply to GSA Schedules team arrangements. Id. In addition, this article does not cover small business set-asides under the Small Business Administration (SBA) rules contained in title 13 of the Code of Federal Regulations. It is noteworthy that the U.S. Government sets aside roughly twenty-three percent of its annual procurement dollars for the procurement of goods and services from small businesses. See Small Business Procurement, U.S. Small Bus. Admin., https://www.sba.gov/partners/contracting-officials/small-business-procurement [https://perma.cc/DSZ8-94L9] (last visited Feb. 15, 2020). Companies competing for small business set-asides through team arrangements must follow the SBA rules. See 13 C.F.R. § 125.2(e)(5)(ii) (2019); Reginald M. Jones & Douglas P. Hibshman, Limitations on Teaming Arrangements in Small Business Set-Asides, 45 Procurement Law. 3, 3 (2010).
  12. See Brent E. Newton, Note, The Legal Effect of Government Contractor Teaming Agreements: A Proposal for Determining Liability and Assessing Damages in Event of Breach, 91 Colum. L. Rev. 1990, 1990 (1991).
  13. See, e.g., Aaron Mehta, Boeing Wants Government to Force Northrop to Partner on ICBM Replacement, Def. News (Sept. 17, 2019), https://www.defensenews.com/digital-show-dailies/air-force-association/2019/09/17/boeing-calls-for-government-intervention-on-icbm-replacement-fight [https://perma.cc/7CTX-5SC3] (explaining that Boeing wants the government to force Northrop Grumman to partner on an ICBM replacement program).
  14. Cf. Mutek, supra note 4, at 4.
  15. See Contractor Team Arrangements, supra note 11.
  16. See 41 U.S.C. § 3301(a)(1) (2012).
  17. See FAR 6.101(a) – (b) (stating “contracting officers shall promote and provide for full and open competition in soliciting offers and awarding [g]overnment contracts” and “shall provide for full and open competition through use of the competitive procedure(s) contained in this subpart that are best suited to the circumstances of the contract action and consistent with the need to fulfill the [g]overnment’s requirements efficiently”).
  18. See James F. Killian & Roy C. Fazio, Creating and Enforcing Teaming Agreements, 25 Construction Law. 5, 9 (2005).
  19. See id. at 5.
  20. Cf. Analytic Scis. Corp., B-259013, 95-1 CPD ¶ 122, at 4 (Comp. Gen. Feb. 28, 1995) (finding consideration of a potential subcontractor’s capabilities is proper when the prime is proposing the subcontractor as part of its team).
  21. See Fed. Trade Comm’n & U.S. Dep’t of Justice, Antitrust Guidelines for Collaborations Among Competitors 1 (2000), https://www.ftc.gov/system/files/documents/public_statements/300481/000407ftcdojguidelines.pdf [https://perma.cc/VRM8-WUPT] (stating that the teams may be procompetitive but noting that “[n]evertheless, a perception that antitrust laws are skeptical about agreements among actual or potential competitors may deter the development of procompetitive collaborations”).
  22. Note that not all teaming agreement disputes will involve enforceability. This article addresses those that do. In many cases, both parties intend that the teaming agreement be treated as a binding, enforceable agreement, and a dispute over some detail may be addressed under the teaming agreement, which often includes an internal escalation procedure involving senior management of the teammates to resolve issues that may arise in the course of working together under the teaming agreement.
  23. See FAR 15.305(a).
  24. See FAR 15.102(a), (c), 15.306(a)(1)–(2).
  25. See generally FAR 15.305–15.306 (providing for only pre-award evaluation).
  26. See FAR 9.100 (prescribing “policies, standards, and procedures for determining whether prospective contractors and subcontractors are responsible”); FAR 9.103(a) (requiring “[p]urchases . . . be made from, and contracts . . . be awarded to, responsible prospective contractors only”).
  27. FAR 9.103(b).
  28. See FAR 9.104-1(e)–(f).
  29. See FAR 9.604(a).
  30. See FAR 9.604(e).
  31. See FAR 9.104-4(a).
  32. See id.
  33. See FAR 9.104-1(a), (e), (f).
  34. See FAR 2.101 (“‘Contracting [O]fficer’ means a person with the authority to enter into, administer, and/or terminate contracts and make related determinations and findings. The term includes certain authorized representatives of the [C]ontracting [O]fficer acting within the limits of their authority as delegated by the [C]ontracting [O]fficer.”). A Contracting Officer is free to consult with legal counsel on team arrangement issues or any other issues relevant to the source selection. See FAR 1.602-2(c).
  35. See generally FAR 9.6.
  36. In an actual dispute that is ripe for adjudication during proposal evaluation, the government has discretion to consider the dispute as a risk in the source selection process. See FAR 15.305(a). A dispute that arises after award can impact performance, but the prime contractor is responsible for performance of the entire contract, and the contract’s terms addresses performance issues. See generally FAR 33.213(a) (providing for an obligation to continue performance pending resolution of a dispute). Performance problems relating to teammates and suppliers can become part of a prime contractor’s negative past performance record. See FAR 9.104-1(c); FAR 9.104-4(a). A contractor with a history of team arrangement disputes could, even in the absence of an issue on a current teaming agreement for the opportunity at hand, raise a concern and be considered by the agency in conducting its source selection. See FAR 15.304(c).
  37. See FAR 9.602(a)(2).
  38. See U.S. Dep’t of Def., Office of Small Bus. Programs, Guidebook for Facilitating Small Business Team Arrangements 10 (2007), https://www.lrp.usace.army.mil/Portals/72/docs/SmallBusiness/Teaming.pdf [https://perma.cc/3V54-YUMJ].
  39. A separate question is whether courts, when examining a dispute under a teaming agreement, should recognize and consider the economic utility of team arrangements as well as the difficulty in ascertaining before final contract award the precise scope of the contract being pursued, which could impact the ability to negotiate with specificity material terms in the teaming agreement.
  40. See FAR 15.001, 15.305(a).
  41. See Steptoe & Johnson LLP, Kendall Enyard, et al., The Government Contractor Teaming Agreement Toolkit 47 (2018), https://www.steptoe.com/images/content/1/7/v2/177171/Government-Contractor-Teaming-Agreement-Toolkit-2018.pdf [https://perma.cc/T2HK-7AAL].
  42. See FAR 1.101.
  43. Vertical team arrangements, which provide for a prime contractor-subcontractor relationship, represent the more common of the two types. See Enyard, et al., supra note 41, at 15, 17.
  44. FAR 9.601. The government has recognized teaming agreements for many years. See U.S. Dep’t of Def., 41 Def. Procurement Circular 3-4 (1966); ASPR 4-117(b) (1976).
  45. FAR 9.603.
  46. FAR 9.602(a).
  47. Id.
  48. See Analytic Scis. Corp., B-259013, 95-1 CPD ¶ 122, at 4 (Comp. Gen. Feb. 28, 1995).
  49. See generally FAR 9.6.
  50. See generally id. Oral teaming agreements are less common today because many contractors have developed policies and procedures for collaboration with other companies as an aspect of corporate governance. Often such corporate policies require early identification of a teaming opportunity and the preparation of a business case for the arrangement, which includes an assessment of the teammate and its role. See Newton, supra note 12, at 1997–98. This is referred to as due diligence, and includes an evaluation of the risks, including possible antitrust issues. See Mutek, supra note 4, at 16. Also, the parties generally enter into a nondisclosure agreement (NDA) to facilitate the exchange of information. See Douglas E. Perry & Louis D. Victorino, Practical Tips & Considerations for Subcontract Negotiations: A Subcontractor’s Perspective, Briefing Papers Collection 1, 7 (2003). Finally, companies have developed and used standard forms of teaming agreements and NDAs to facilitate collaboration. See Murtha, supra note 9, at 27. Standard forms lack specificity to the immediate pursuit and can make enforcement problematic. See, e.g., Sample Teaming Agreement, Slippery Rock U. Gov’t Contracting Assistance Ctr. (Aug. 31, 2017), https://www.sru.edu/Documents/offices/GCAC/SAMPLE_Teaming_Agreement.pdf [https://perma.cc/Z8XS-DX6C].
  51. Customer requests for evidence of the team arrangement may be one factor that has contributed to greater discipline in executing a written agreement. Such an agreement often uses the prime contractor’s standard teaming agreement form although there may be some tailoring of the terms, particularly as related to the scope of work; however, the scope of work may be notional because a teaming agreement may be created before the final scope of the prime contract is known. The final scope may not be known until the award decision by the customer and negotiation of the definitive contract with the prime contractor.
  52. See Enyard, et al., supra note 41, at 2, 30.
  53. The Ninth Circuit, in one teaming agreement case involving two major contractors, noted:
    McDonnell correctly points out that this case differs from the usual commercial dispute in that the absent party, the [g]overnment, is involved with the agreements at issue, even though it is not a party to them. The [g]overnment prompted the parties to enter the teaming agreements and, due to its extensive involvement in the military procurement arena, exerts a tremendous influence on them.
    Northrop Corp. v. McDonnell Douglas Corp., 705 F.2d 1030, 1044 (9th Cir. 1983).
  54. This deference is also seen in protests where the Government Accountability Office (GAO) has noted that, “[i]n reviewing a protest of an agency’s proposal evaluation, it is not our role to reevaluate proposals. Rather, we will consider only whether the evaluation was reasonable and consistent with the terms of the solicitation and applicable procurement statutes and regulations.” Metson Marine Servs., Inc., B299705, 2007 CPD ¶ 159, at 5 (Comp. Gen. July 20, 2007) (citations committed).
  55. See Chevron U.S.A. Inc. v. Nat. Res. Def. Council, Inc., 467 U.S. 837, 844 (1984).
  56. See Chevron Deference, Black’s Law Dictionary (11th ed. 2019).
  57. See Chevron U.S.A. Inc., 467 U.S. at 842–43.
  58. Barnhart v. Walton, 535 U.S. 212, 218 (2002) (quoting Chevron U.S.A. Inc., 467 U.S. at 843).
  59. See, e.g., Brownlee v. Dyncorp, 349 F.3d 1343, 1354 (Fed. Cir. 2003) (“The FAR regulations are the very type of regulations that the Supreme Court in Chevron and later cases has held should be afforded deference.”); see also Auer v. Robbins, 519 U.S. 452, 461 (1997).
  60. One criticism is that Chevron opens the door to judicial abdication. See, e.g., Joseph Postell & Paul J. Larkin, Jr., Not Above the Law: Ending the Misguided Chevron–Auer Deference Regime, Heritage Found. 4 (Sept. 7, 2018), https://www.heritage.org/courts/report/not-above-the-law-ending-the-misguided-chevron-auer-deference-regime [https://perma.cc/ZD4A-LC3G].
  61. See generally Richard W. Murphy, A “New” Counter-Marbury: Reconciling Skidmore Deference and Agency Interpretive Freedom, 56 Admin. L. Rev. 1, 35 (2004) (“[W]ithout Chevron’s help, the agency would be stuck with the Court’s construction.”).
  62. See Peter M. Shane & Christopher J. Walker, Chevron at 30: Looking Back and Looking Forward, 83 Fordham L. Rev. 475, 475 (2014).
  63. Contracting agencies and Contracting Officers have broad discretion to determine their needs and the best way to meet them. See Crewzers Fire Crew Transp., Inc., B-402530 et al., 2010 CPD ¶ 117, at 3 (Comp. Gen. May 17, 2010); USA Fabrics, Inc., B-295737 et al., 2005 CPD ¶ 82, at 4–5 (Comp. Gen. Apr. 19, 2005).
  64. See generally FAR 33.103–33.104. The FAR defines protest:
    [A] written objection by an interested party to any of the following:
    (1) A solicitation or other request by an agency for offers for a contract for the procurement of property or services.
    (2) The cancellation of the solicitation or other request.
    (3) An award or proposed award of the contract.
    (4) A termination or cancellation of an award of the contract, if the written objection contains an allegation that the termination or cancellation is based in whole or in part on improprieties concerning the award of the contract.
    FAR 33.101.
  65. AllWorld Language Consultants, Inc., B-414244 et al., 2017 CPD ¶ 111, at 3, 6 n.4 (Comp. Gen. Apr. 3, 2017).
  66. Id. at 6 n.4.
  67. See ATACS Corp. v. Trans World Commc’ns, Inc., 155 F.3d 659, 666 (3d Cir. 1998); Newton, supra note 12, at 2013.
  68. See ATACS Corp., 155 F.3d at 666. An alternative could be a joint venture agreement. See FAR 9.601(1).
  69. ATACS Corp., 155 F.3d at 666. A jurisdiction encountering a teaming agreement for the first time often examines its precedent on preliminary agreements. See id.
  70. See, e.g., W.J. Schafer Assocs., Inc. v. Cordant, Inc., 493 S.E.2d 512, 515 (Va. 1997).
  71. See id.; Dumas v. First Fed. Sav. & Loan Ass’n, 654 F.2d 359, 360–61 (5th Cir. 1981) (noting that agreement in which terms and conditions are left to future negotiations expressly contingent upon “mutually acceptable” terms must be treated as “agreement to seek to agree in the future”).
  72. Compare ATACS Corp., 155 F.3d at 664, 668 (affirming the district court ruling that agreement to “negotiate in good faith the final subcontract prices” was enforceable), with Cyberlock Consulting, Inc. v. Info. Experts, Inc., 939 F. Supp. 2d 572, 580 (E.D. Va. 2013) (finding that “the post-prime contract award obligations in the [s]econd [t]eaming [a]greement are unambiguous and constitute an unenforceable agreement to agree.”). In Cyberlock, the parties had a first teaming agreement that included a subcontract; however, the second teaming agreement, which was the subject of the dispute, did not. See Cyberlock Consulting, Inc., 939 F. Supp. 2d at 575–76.
  73. See Cable & Comput. Tech., Inc., ASBCA No. 47420 et al., 03-1 BCA ¶ 32,237, at 159,406.
  74. See generally FAR 9.602(c) (recognizing the team arrangement is generally formed before submitting an offer).
  75. See Murtha, supra note 9, at 22.
  76. See Mutek, supra note 4, at 77, 79.
  77. See id. at 79. The expectation is that if the initial parties attempting to resolve the issue are too close to the issue and unable to resolve it, there could be benefit through the upward movement of the dispute into more senior management ranks.
  78. See Allen & Co. v. Occidental Petroleum Corp., 382 F. Supp. 1052, 1055 (S.D.N.Y. 1974).
  79. See, e.g., ATACS Corp. v. Trans World Commc’ns, Inc., 155 F.3d 659, 665 (3d Cir. 1998).
  80. See, e.g., id. at 665–66.
  81. See Adjustrite Sys., Inc. v. GAB Bus. Servs., Inc., 145 F.3d 543, 548 (2d Cir. 1998); Browning Jeffries, Preliminary Negotiations or Binding Obligations? A Framework for Determining the Intent of the Parties, 48 Gonz. L. Rev. 1, 2–3 (2012).
  82. See Boland, supra note 8.
  83. The author has observed that, early in the teaming process, a prime contractor’s business development (BD) function often is the primary function selecting teaming partners; in fact, it is common for government contractors to have the BD function responsible for the company’s team arrangement policy, although approval of a desired team arrangement usually involves several other functions as well. Even though the teaming partner is identified by BD, there may be a transition to the prime contractor’s supply chain (formerly called the purchasing function) when the prime contractor is selected for the award of the pursued government contract. Then, the supply chain function supersedes the teaming agreement with a subcontract and manages the relationship with the subcontractor from that point forward. In the author’s experience, the transition of teammate management from BD to supply chain is a point where disagreements can arise. That is because BD is focused on assembling a team to capture the contract and supply chain is focused on the negotiation and administration of the subcontract including the control of costs. For example, the supply chain function may examine whether another company could be less expensive and may seek to compete the subcontract or even examine if the company’s own resources could perform the work. This transition appears to have been where the dispute arose in Air Tech. Corp. v. Gen. Elec. Co., 199 N.E.2d 538, 541, 543, 545-46 (Mass.: 1964), and the author has been involved in or observed other disputes that arose when the relationship transitioned from BD management during the contract pursuit stage to supply chain administration of the relationship after award of the contract to the prime contractor.
  84. See, e.g., EGamp;G, Inc. v. Cube Corp., 63 Va. Cir. 634, 649 (Va. Cir. Ct. 2002).
  85. See Air Tech. Corp., 199 N.E.2d at 545.
  86. See id.
  87. Id. at 546.
  88. See id. at 547.
  89. Id. at 548.
  90. Id. at 546. One reason that this case remains an interesting examination of a teaming agreement is the fact that the court referred this matter to a master and stated that it drew its “own conclusions from the master’s very complete subsidiary findings.” See id. The master findings examined the surrounding circumstances and conduct of the parties to determine the intent of the parties and found:
    What the parties intended is indicated by GE’s subsequent conduct e.g. (1) listing AT in the letter of interest as a subcontractor, “team member,” and the only potential source of the EM sensor; (2) designating . . . AT’s personnel as “the only individuals . . . having program responsibility in the EM sensor field”; (3) Hynes’s statements that showing AT as a second tier subcontractor was a “mistake,” and that it was GE’s “intention . . . that AT would receive a sole source procurement for the EM sensor”; (4) treating Dr. Clapp, Dr. Hillger, and AT’s DASA contract as team assets in the proposal presentation; (5) GE’s early treatment . . . of AT’s EM sensor material as entitled to protection from Dresser; (6) GE’s assistance in and use of Dr. Clapp’s research in the summer of 1961; and (7) the absence of any GE suggestion to AT prior to December, 1961, that in the EM sensor work Dresser or other companies, and (above all) GE, were to compete with AT.
    Id. at 546 n.12.
  91. See EG&G, Inc. v. Cube Corp., 63 Va. Cir. 634, 655, 657 (2002).
  92. See id. at 648, 650.
  93. See id. at 652.
  94. See ATACS Corp. v. Trans World Commc’ns, Inc., 155 F.3d 659, 668 (3d Cir. 1998).
  95. See id. at 662.
  96. See id. at 662–63.
  97. See id. at 663–64.
  98. See id. at 664.
  99. Id. at 668.
  100. Id.
  101. See id.
  102. Id. at 665 (citation omitted).
  103. Id. at 667 (citations omitted).
  104. See id. at 666–67 (quoting U.C.C § 2-311(1) (Am. Law. Inst. & Unif. Law Comm’n 2012)).
  105. See Premier Gaming Trailers LLC v. Luna Diversified Enters., Inc., No. 8:16–cv–3378–T–33TGW, 2017 WL 735458, at *1–2 (M.D. Fla. Feb. 24, 2017). This was a default judgement in favor of Premier Gaming Trailers LLC (Premier Gaming) because Luna Diversified Enterprises, Inc. failed to file a response. See id. at *1, 3. The default judgment was subsequently vacated. See Premier Gaming Trailers LLC v. Luna Diversified Enters., Inc., No. 8:16–cv–3378–T–33TGW, 2017 WL 1251585, at *2 (M.D. Fla. Apr. 5, 2017). Then, Premier Gaming’s motion for a new trial was denied. See Premier Gaming Trailers LLC v. Luna Diversified Enters., Inc., No. 8:16–cv–3378–T–33TGW, 2018 WL 4145885, at *1, 4 (M.D. Fla. Aug. 30, 2018).
  106. See Premier Gaming Trailers LLC, 2017 WL 735458, at *1.
  107. See id. at *2.
  108. See id. at *3.
  109. See id. at *1.
  110. See BAE Sys. Info. & Elec. Sys. Integration, Inc. v. Lockheed Martin Corp., No. 3099-VCN, at 3, 9 (Del. Ch. Feb. 3, 2009), https://www.potteranderson.com/media/experience/492_BAE_20v_20Lockheed_20Martin.pdf [https://perma.cc/KN52-XR4X].
  111. See id. at 18.
  112. Id. at 9.
  113. Id.
  114. Id. at 15.
  115. Compare ATACS Corp. v. Trans World Commc’ns, Inc., 155 F.3d 659, 668 (3d Cir. 1998), with W.J. Schafer Assocs., Inc. v. Cordant, Inc., 493 S.E.2d 512, 515 (Va. 1997).
  116. See BAE Sys., No. 3099-VCN, at 9–10.
  117. See Jack Rephan, Teaming Agreements in Virginia: Are They Enforceable?, Pender & Coward Blog: Opinions & Observations (Jan. 12, 2016), https://www.pendercoward.com/resources/blog-opinions-and-observations/teaming-agreements-in-virginia-are-they-enforceable-january-2016 [https://perma.cc/E6RF-ZNH4] (discussing developments in Virginia law governing teaming agreements).
  118. See, e.g., Cyberlock Consulting, Inc. v. Info. Experts, Inc., 549 F. App’x 211, 212 (4th Cir. 2014); CGI Fed. Inc. v. FCI Fed., Inc., 814 S.E.2d 183, 188 (Va. 2018); W.J. Schafer Assocs., Inc., 493 S.E.2d at 515; EG&G, Inc. v. Cube Corp., 63 Va. Cir. 634, 645–46 (2002). See generally Paul W. Mengel III, The Climb to Enforce Your Teaming Agreement in Virginia Has Gotten Steeper, Piliero Mazza Blog (Oct. 25, 2018), https://www.pilieromazza.com/the-climb-to-enforce-your-teaming-agreement-in-virginia-has-gotten-steeper [https://perma.cc/8HJB-92ZF] (discussing several disputes that used Virginia law). In contracts law, a material term in a contract is a term or provision that concerns significant issues, “such as subject matter, price, payment, quantity, quality, duration, or the work to be done.” Material Term, Black’s Law Dictionary (11th ed. 2019).
  119. See W.J. Schafer Assocs., Inc., 493 S.E.2d at 515–16.
  120. See id. at 515.
  121. Id.
  122. Id.
  123. See EG&G, Inc., 63 Va. Cir. at 658.
  124. See id. at 649–50.
  125. Id. at 635.
  126. See id. at 636.
  127. Id. at 639, 641–43.
  128. See id. at 643.
  129. See id. at 657.
  130. See id. at 647–48.
  131. Id. at 649.
  132. Interview with Stuart Young, Vice President & Gen. Counsel, EG&G, Inc., and David Metzger, Partner, Holland & Knight (Nov. 8, 2019).
  133. See ATACS Corp. v. Trans World Commc’ns, Inc., 155 F.3d 659, 667 (3d Cir. 1998).
  134. Id.
  135. See id. at 665.
  136. Id. at 667 (citation omitted).
  137. Id. (citations omitted).
  138. Id.
  139. Id. at 668.
  140. See id. at 667.
  141. See Robert H. Koehler, Teaming Agreements: The Proverbial “Wolf in Sheep’s Clothing,” Briefing Papers Collection 1, 2 (2014). See generally Cyberlock Consulting, Inc. v. Info. Experts, Inc., 939 F. Supp. 2d 572 (E.D. Va. 2013).
  142. See, e.g., Mengel, supra note 118.
  143. See Cyberlock Consulting, Inc., 939 F. Supp. 2d at 581.
  144. See id. at 578.
  145. See id. at 574–75.
  146. Id. at 574. The court also stated:
    Accordingly, Section 7 of the First Teaming Agreement stated that “[i]f, during the period of this Agreement, a prime contract is awarded to [IE] as a result of the proposal, [IE] will, within five (5) business days from the date of award of the Task Order by the Government to [IE], enter into the subcontract attached to this Agreement as Exhibit D with [Cyberlock], subject only to the limitations in Paragraph 8.” . . . . The First Teaming Agreement provided for a number of occurrences under which the agreement would terminate, none of which was the failure of the parties to successfully negotiate a subcontract.
    Id. (citations omitted).
  147. See id. at 578.
  148. See id. at 575 (citation omitted).
  149. See id.
  150. See id. at 575–76.
  151. See id. at 576.
  152. See id. at 575–76.
  153. See id. at 581.
  154. See Navar, Inc. v. Fed. Bus. Council, 784 S.E.2d 296, 297, 300 (Va. 2016).
  155. See id. at 298.
  156. See id. at 298–99.
  157. Id. at 300.
  158. See 13 C.F.R. § 125.6(a)(1) (2019).
  159. Navar, Inc., 784 S.E.2d at 300.
  160. Id.
  161. See id.
  162. See id. A review of teaming agreement cases does not provide a clear checklist of what are the essential terms that, if addressed, will ensure enforceability. Instead, cases note, “omission of an essential term in a contract, such as price, does not vitiate contract formation if the parties otherwise manifested their mutual assent to the agreement and the terms of that agreement are sufficiently definite.” ATACS Corp. v. Trans World Commc’ns, Inc., 155 F.3d 659, 667 (3d Cir. 1998) (citations omitted). “Although not all of the terms need to be fixed before a contract will be binding, some courts suggest that the failure to spell out customary terms evidences a lack of intent to be bound.” Jeffries, supra note 81, at 30 (citations omitted).
  163. See Newton, supra note 12, at 2037–40.
  164. See W.J. Schafer Assocs., Inc. v. Cordant, Inc., 493 S.E.2d 512, 515 (Va. 1997).
  165. See CGI Fed. Inc. v. FCI Fed., Inc., 814 S.E.2d 183, 185, 190 (Va. 2018).
  166. See id. at 190.
  167. See Complaint at 9, ex. 1, A-T Sols., Inc. v. R3 Strategic Support Grp., Inc., No. 3:16-CV-00007-JAG (E.D. Va. Jan. 5, 2016), ECF No. 1 [hereinafter A-T Solutions Complaint].
  168. See id. at 4; Transcript of Record at 143, A-T Sols., Inc. v. R3 Strategic Support Grp., Inc., No. 3:16-cv-00007-JAG (E.D. Va. Jan 12, 2016), ECF No. 20 [hereinafter A-T Solutions Transcript].
  169. See A-T Solutions Complaint, supra note 167, at 4.
  170. See id.
  171. See id.
  172. See id. at 9.
  173. See Memorandum in Opposition to Motion for Preliminary Injunction at 8, A-T Sols., Inc. v. R3 Strategic Support Grp., Inc., No. 3:16-CV-00007-JAG (E.D. Va. Jan. 10, 2016), ECF No. 14.
  174. See A-T Solutions Transcript, supra note 168, at 143. A-T Solutions was represented by Billy B. Ruhling, II of DiMuroGinsberg, P.C. See A-T Solutions Complaint, supra note 167, at 10. During a telephone interview, Mr. Ruhling stated that the judge weighed factors going both ways. Telephone Interview with Billy B. Ruhling, Attorney, DiMuroGinsburg, P.C. (Sept. 24, 2019). Equities favored A-T Solutions in that, as noted by the court, R3 could have and should have advised AT Solutions earlier of R3’s intent to abandon the team and go elsewhere. A-T Solutions Transcript, supra note 168, at 142. However, R3 benefited from the strict view in Virginia of teaming agreements and treatment of teaming agreements as unenforceable agreements to agree in the absence of a high degree of specificity of terms. See id. at 78–79.
  175. See generally FAR 9.6.
  176. Teaming practices have evolved in several ways. Oral agreements are rare today but were common in the past, particularly between parties that frequently joined forces via a teaming agreement. Also, in the past, the common teaming agreements’ exhibit that addresses the expected scope of work for the subcontractor more frequently was simply a “TBD,” which reflected the fact that the final SoW was not known, and the parties were used to dealing with this uncertainty. See Newton, supra note 12, at 2025–26. Rarely is that the case today; however, specificity often is difficult before the definitization of the prime contract.
  177. See Air Tech. Corp. v. Gen. Elec. Co., 199 N.E.2d 538, 541 (Mass. 1964).
  178. See Cable & Comput. Tech. Inc. v. Lockheed Sanders, Inc., 214 F.3d 1030, 1040 (9th Cir. 2000).
  179. See id. at 1033–34.
  180. Id. at 1033.
  181. See id.
  182. See id.
  183. See id. at 1033–34.
  184. See Cable & Comput. Tech. Inc. v. Lockheed Sanders, Inc., 214 F.3d 1030, 1035 (9th Cir. 2000).
  185. Id.
  186. Id. (citations omitted).
  187. See Cable & Comput. Tech. Inc. v. Lockheed Sanders Inc., 52 F. App’x 20, 22 (9th Cir. 2002).
  188. Id. at 23.
  189. See id.
  190. See, e.g., AllWorld Language Consultants, Inc., B-414244 et al., 2017 CPD ¶ 111, at 3 (Comp. Gen. Apr. 3, 2017).
  191. See, e.g., Metro Mach. Corp., B-297879.2, 2006 CPD ¶ 80, at 5 (Comp. Gen. May. 3, 2006).
  192. See Analytic Scis. Corp., B-259013, 95-1 CPD ¶ 122, at 4 (Comp. Gen. Feb. 28, 1995).
  193. See generally FAR 9.6.
  194. See AllWorld Language Consultants, Inc., 2017 CPD ¶ 111, at 5; see also Nextgen Consulting, Inc., B-413104.4, 2016 CPD ¶ 334, at 5 (Comp. Gen. Nov. 16, 2016).
  195. See Rohmann Servs., Inc., B-405171 et al., 2011 CPD ¶ 177, at 3, 4, 4 n.2 (Comp. Gen. Sept. 8, 2011).
  196. This may beg the question whether the government could state that an enforceable teaming agreement is a requirement and, if so, that raises the related question of how prospective contractors reasonably would be required to fulfill that requirement. One obvious option is the provision of a legal opinion on the subject of the teaming agreement’s enforceability. The provision to the government of a legal opinion on an agreement between two private parties has precedent. The FAR states:
    41 U.S.C. [§] 6305 prohibits transfer of [g]overnment contracts from the contractor to a third party. The [g]overnment may, when in its interest, recognize a third party as the successor in interest to a [g]overnment contract when the third party’s interest in the contract arises out of the transfer of- (1) [a]ll the contractor’s assets; or (2) [t]he entire portion of the assets involved in performing the contract.
    FAR 42.1204(a). When a contractor asks that the government recognize a successor in interest, “the contractor shall submit to the responsible contracting officer” a number of required items, including an “opinion of legal counsel for the transferor and transferee stating that the transfer was properly effected under applicable law and the effective date of transfer.” FAR 42.1204(f)(5). One issue noted by the author is that agency procedures and requirements for the content of the legal opinion associated with a novation vary. That could also be an issue with opinions related to teaming agreement enforceability. Another issue would be the time and expense associated with such opinions. A prime contractor can have several teammates. Finally, the government can recognize the intended contributions of a planned subcontractor to the performance of the contract even in the absence of a teaming agreement.
  197. See Rohmann Servs., Inc., 2011 CPD ¶ 177, at 7.
  198. See Star Contract Servs., LLC, B-409424, 2014 CPD ¶ 133, at 3 (Comp. Gen. Apr. 23, 2014).
  199. See id. at 5, 8.
  200. See Beretta USA Corp., B-406376.2 et al., 2013 CPD ¶ 186, at 4–5 (Comp. Gen. July 12, 2013).
  201. See id. at 6, 14.
  202. Id. at 6 (citation omitted).
  203. See AllWorld Language Consultants, Inc., B-414244 et al., 2017 CPD ¶ 111, at 6 n.4 (Comp. Gen. Apr. 3, 2017).
  204. See id. at 3.
  205. Id. at 5.
  206. See id. at 6 n.4 (“Although the agreement states it is governed by the laws of Virginia, the protester does not establish why GSA was bound by Virginia state law in interpreting the RFQ requirement for evidence of a binding commitment.”).
  207. See id. at 4, 7.
  208. See Mission Servs., Inc., B-415136.3 et al., 2018 CPD ¶ 222, at 3 (Comp. Gen. May 22, 2018).
  209. Id.
  210. See id. at 12–13.
  211. See id. at 13.
  212. See, e.g., ATACS Corp. v. Trans World Commc’ns, Inc., 155 F.3d 659, 666 (3d Cir. 1998) (noting Pennsylvania law looks to whether there is intent to be bound and sufficiently definite terms).
  213. See generally Newton, supra note 12, at 2015–16 (discussing possible alternatives to teaming agreements).
  214. See generally Michael W. Mutek, Senior Counsel, Steptoe & Johnson LLP, Address at the National Contract Management Association’s 57th Annual March Workshop: Teaming Agreements: Competitive Discriminator or Legal Liability, at 62 (Mar. 7, 2018), http://www.ncmaboston.org/presentations/ [https://perma.cc/4JRS-C6MX].
  215. See generally FAR 9.103(a)–(b).