Buried in a spreadsheet of answers to a $50 billion Army solicitation sat a six word rule: "No teaming is permitted on MAPS."
On August 11, GAO ruled the Army could not do that.
The decision is worth your time even if you were never going to bid on MAPS, because the reasoning has nothing to do with MAPS. GAO said so itself: whether an agency can force small businesses to pick one way of joining forces, or bar teaming entirely, is a question "of widespread interest to the procurement community that has not been decided previously."
That phrase matters. This was the first time anyone had answered it.
What the Army did
The Marketplace for the Acquisition of Professional Services, MAPS, is the Army's plan to fold two existing contract vehicles, RS3 and ITES-3S, into one multiple award IDIQ. Five technical domains, from foundational IT to research and development. A $50 billion ceiling, a five year base ordering period with a five year option, and a minimum guarantee of $100 per contract.
Worth noting for anyone tracking the rewrite of the procurement rules: the Army issued MAPS under Revolutionary FAR Overhaul part 15 procedures, adopted through a Defense Department class deviation in March. This is one of the first significant protest decisions to come out of a solicitation run on the new rulebook.
MAPS is not a set-aside. The Army planned 70 awards in each domain, split 30 large businesses, 25 small businesses, and 15 commercial sector vendors, for up to 350 awards total. Small businesses were competing for reserved slots inside a mixed field.
And they were told they had to do it alone. Across three separate answers in the solicitation's question and answer file, the Army said "Offerors shall not propose subcontractors for this Solicitation," "No teaming is permitted on MAPS," and "CTAs [contractor teaming arrangements] are not permitted."
Intelligence Consulting Enterprise Solutions, a small business in Alexandria, Virginia, challenged the terms of the solicitation before proposals were due. It raised four primary challenges. GAO denied three of them: the numbering of the solicitation and how amendments were posted, the bar on using classified contracts as past performance references, and the claim that the Army's answers were too thin to let offerors compete intelligently.
The fourth one landed.
Why GAO ruled the way it did
The relevant law is short. Under 15 U.S.C. 644(e)(4)(A), when an agency issues a solicitation for a bundled or consolidated contract:
"a small business concern that provides for use of a particular team of subcontractors or a joint venture of small business concerns may submit an offer for the performance of the contract."
The Army read the word "or" as its own choice to make. Two options exist, teams or joint ventures, so the agency picks one and offerors live with it. After ICES filed, the Army amended MAPS to expressly allow joint ventures, then defended the position that permitting one formation and barring the other was within its discretion.
GAO agreed there was a choice in that sentence. It disagreed about whose choice it was:
"The Army is correct that section 644(e)(4)(A) creates a discretionary choice about which of the two types of formations to use, the Army is wrong about with whom the discretion lies."
Read the sentence again and the reason is plain. The subject is "a small business concern." The verb is "may submit." Congress gave the choice to the company writing the proposal, not the agency writing the solicitation.
GAO went further and read the provision against the purpose of the statute. The Small Business Act directs agencies consolidating requirements to do it in a way that gives small businesses real opportunities to participate. An agency reading that cuts the number of ways a small business can assemble a competitive offer, GAO held, "has the effect of reducing, rather than maximizing, the opportunity for small business concerns to compete."
GAO recommended the Army amend the solicitation to allow small business teams alongside joint ventures, reopen it for revised proposals, and reimburse ICES for the cost of the protest.
The two ways to bid as a group
FAR 9.601 recognizes two structures, and the difference between them is the difference between a contract and a company.
A teaming arrangement means you bid as the prime and the other firms sign on as your first tier subcontractors. Nothing new gets created. It is an agreement between existing companies about who does what if you win.
A joint venture means a separate entity submits the offer. Under 13 CFR 125.8, each member has to be small under the size standard for the contract's NAICS code, or fit one of the exceptions to affiliation. Where two small businesses form a JV between themselves, the agreement "need not be in any specific form or contain any specific conditions." Where the JV pairs an SBA approved mentor with its protégé, the requirements get long: the small business has to be the managing venturer, a named employee of that small business has to be the Responsible Manager, the small business has to own at least 51 percent of the entity, profits have to track the work performed, and the JV needs its own bank account requiring every partner's signature.
Teaming is lighter to stand up. A joint venture takes more paperwork and more commitment. Both are legitimate, and the point of the ICES decision is that on a consolidated buy, the agency does not get to take one of them off your table.
The rule that makes teaming worth doing
The regulation at the center of this case is the most useful paragraph in the whole subject for a company that has not won much yet, and almost nobody outside protest lawyers can quote it.
13 CFR 125.2(g) reads:
"When an offer of a small business prime contractor includes a proposed team of small business subcontractors and specifically identifies the first-tier subcontractor(s) in the proposal, the head of the agency must consider the capabilities, past performance, and experience of each first tier subcontractor that is part of the team as the capabilities, past performance, and experience of the small business prime contractor if the capabilities, past performance, and experience of the small business prime does not independently demonstrate capabilities and past performance necessary for award."
Read that slowly, because it is doing a lot of work.
"Must consider." Not may. When the conditions are met, the agency has no choice.
"As the capabilities, past performance, and experience of the small business prime contractor." Not as a side note or a plus factor. Your teammate's record counts as yours.
"Specifically identifies the first-tier subcontractor(s) in the proposal." This is the condition people miss. A handshake does not trigger it. You have to name your team in the proposal.
"If the small business prime does not independently demonstrate capabilities and past performance necessary for award." The rule is a floor for companies that cannot clear the bar alone. If your own record is already strong enough, the agency evaluates you on it.
That last clause is the honest limit on this provision, and it is also the point. This rule exists for exactly the company that has the people and the plan but not yet the contract history. SBA wrote it in 2020 to implement amendments to the Small Business Act, and by SBA's own account the evaluation it requires is mandatory both for bundled or consolidated contracts and for multiple award contracts above an agency's substantial bundling threshold.
This is the regulatory answer to the oldest trap in this business: you need past performance to win work, and you need work to build past performance. If you are early and thin on references, that is an argument for teaming, not an argument for waiting. We have written before about building past performance as a new contractor, and naming a strong first-tier team belongs at the top of that list.
Joint ventures get parallel treatment. Under 13 CFR 125.8(e), when a JV bids a set-aside, the agency "must consider work done and qualifications held individually by each partner to the joint venture as well as any work done by the joint venture itself previously."
One caution on scope. GAO decided this case on consolidation, and expressly declined to reach whether MAPS was also a bundled or substantially bundled buy. As the decision puts it, all bundling is a form of consolidation, but not all consolidation is bundling. If you are trying to work out whether these protections reach a specific solicitation, that distinction is where the analysis starts, not the dollar value alone.
What teaming does not let you do
Two limits are worth knowing before you build a team, and both of them point the same direction. These apply to set-aside work, which MAPS is not, but they will shape most of the teaming decisions you actually make.
You still have to do the work. Under 13 CFR 125.6, a small business holding a set-aside services contract above the simplified acquisition threshold cannot pay more than 50 percent of what the government pays it to firms that are not similarly situated.
"Similarly situated" is the whole ballgame. 13 CFR 125.1 defines it as a subcontractor holding the same small business program status as the prime, and small for the NAICS code assigned to its subcontract. On a HUBZone contract, a certified HUBZone sub. On an 8(a) contract, a certified 8(a) participant. On a plain small business set-aside, any small business.
Here is why that matters more than the 50 percent number: work you pass to a similarly situated teammate does not count against the limitation. Team with firms holding the status you hold, and the subcontracting limit stops being the thing that constrains your design.
The real risk sits on the other side. Under 13 CFR 121.103(h), if a subcontractor that is not similarly situated performs the primary and vital requirements of the contract, or you are unusually reliant on that subcontractor, SBA can find an ostensible subcontractor and your firm becomes ineligible for the award. The same regulation is explicit that using a subcontractor's experience and past performance to strengthen your offer is fine on its own. The problem is never borrowing the record. It is handing over the work.
Small business to small business teaming avoids most of this by construction. Teaming where a large firm does the heavy lifting is where companies get into trouble.
What to do with this on your next bid
Read the Q&A, not just the solicitation. The Army's ban did not appear in the body of the RFP. It lived in three answers buried in a question and answer file, in a procurement that drew more than 2,500 pre-proposal questions. Restrictions live in amendments and answers, and they carry real weight.
Do not assume a later amendment wiped the Q&A. MAPS amendments carried an order of precedence clause saying the amendment "supersedes and replaces all prior amendments, historical drafts, and Government-provided Questions and Answers." ICES read that as voiding every answer. GAO disagreed, and the reasoning is worth keeping: such a clause only rescinds answers that actually conflict with the final solicitation text. Answers that sit comfortably alongside it still apply. That cuts both ways. A helpful answer may survive an amendment, and so may a restrictive one.
Know the deadline, because it is brutal. Under 4 CFR 21.2, a protest challenging the terms of a solicitation has to be filed before the time set for receipt of initial proposals. Not ten days after award. Not once you see who won. If you spot a restriction you believe is unlawful and you submit a proposal anyway, the argument is gone, however right you were. ICES filed before proposals were due, which is the only reason this decision exists.
Ask before you assume. Not every limit on teaming is unlawful. The ICES holding rests on a consolidated procurement and the specific language covering them. A restriction on a small, standalone buy is a different question.
Build the team before the solicitation drops. A teaming agreement negotiated in the week a proposal is due is a bad agreement. Decide who you would bid with, and on what, while nothing is on the street.
The takeaway
GAO did not create a new right here. It enforced one that has been sitting in the Small Business Act the whole time, against an agency that read it backwards on a $50 billion buy.
That is worth sitting with. The Army is not a careless customer, and this language went out in a solicitation anyway. Which means the useful question is not whether the government will protect your ability to compete as a team. It is whether you know the rule well enough to notice when a solicitation quietly takes it away.
If you are weighing whether to bid alone, team, or joint venture on a contract that is bigger than what you have won before, talk to an advisor. That decision is usually made too late and too fast, and it is the one that most often decides the outcome.