iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Competitors can work together on open technology standards when the work advances interoperability, but they must not use project discussions to coordinate how their businesses compete. Keep company-specific commercial information out of the room, follow a transparent and balanced process, and treat a participant’s concern about a discussion as a reason to pause and change course—not as a formality.
Why open technology work can raise antitrust concerns
Shared technical standards can make products and services work together and make it easier for customers to choose among competing implementations. The Federal Trade Commission (FTC) recognizes that competitor collaboration can produce these benefits. It also warns that collaboration can create antitrust risks when competitors stop making independent decisions or use joint market power to restrict competition.
The legal question depends on what participants do, why they do it, and how it affects competition—not simply on whether a meeting is labeled a standards project. Under the FTC’s explanation of U.S. antitrust law, price fixing, bid rigging, and market division are per se unlawful. Other forms of collaboration may require a fact-specific assessment of their purpose and competitive effects, including any business justification.
This article concerns U.S. federal law. Other jurisdictions may apply different rules, and participants should consult their own antitrust counsel about particular facts.
#1 Best Overall
What competitors should keep out of project discussions
W3C’s participant policy gives a concrete example of how a standards organization may set boundaries. For W3C activities, it tells participants: “Do not discuss (even in jest) or exchange non-public information.” Its policy identifies categories of company-level information that participants should not discuss or agree on, including:
- Prices, bids, costs, and pricing plans.
- Market shares, customers, territories, and customer or supplier terms.
- Marketing plans, production, output, capacity, and product distribution.
- Wages, benefits, and other employment terms.
- Agreements to reduce competition, including boycotts or excluding a person or organization from W3C activities or a market.
W3C also cautions against exchanging non-public information about product design. Its policy recognizes a limited technical context for design discussion when necessary to achieve interoperability, create benchmarks or tests, or define standards. That is not a general permission to discuss company roadmaps or commercial plans: keep the conversation focused on what the technical work requires, and ask counsel if the boundary is unclear.
Rank #2
How to distinguish technical work from commercial coordination
No single label—such as “technical,” “public,” or “standards-related”—makes a discussion lawful. The subject, information shared, participants, and practical effect all matter. These contrasts are useful prompts for keeping a meeting focused, not legal safe harbors.
Recommended Free Tools
| Project discussion | More appropriate focus | Potential warning sign |
|---|---|---|
| Interoperability requirements | Define the interface or behavior implementations need to support. | Using the discussion to align participants’ product timing, market strategy, or commercial terms. |
| Benchmarks and tests | Set objective methods for testing whether implementations meet a technical standard. | Sharing non-public company costs, output, or plans under cover of test planning. |
| Product design | Discuss design details only to the extent needed for interoperability, benchmarks, tests, or standards work, consistent with the applicable project policy. | Comparing confidential roadmaps, features, or distribution plans that are not necessary to the technical task. |
| Market conditions | Keep the agenda on the technical work rather than competitors’ commercial choices. | Discussing or agreeing on prices, bids, customers, territories, wages, output, or exclusion of a rival. |
Information being public does not, by itself, establish that an agreement or discussion is lawful. Likewise, the fact that participants are competitors does not make every technical exchange unlawful. When a topic appears to move from technical standard-setting toward commercial coordination, stop and seek guidance rather than trying to resolve the legal question informally in the meeting.
What to do if a meeting turns toward a prohibited topic
W3C’s policy provides a practical response for W3C activities. Participants can adapt the same basic sequence to the rules and reporting channels of another project:
- Raise the concern promptly. Tell the chair that the discussion may involve non-public or competitively sensitive information.
- Ask to change topics. Redirect the group to the agenda item’s technical question, or pause the discussion.
- Leave if the discussion continues. W3C says to leave when the chair does not change the topic.
- Report the issue through the project’s channel. W3C directs participants to inform a W3C Team member. For another organization, use its designated compliance or reporting process.
- Consult your own counsel. Do not assume that silence, a disclaimer, or a project chair’s approval resolves the legal risk.
Which project safeguards help—and what they do not do
Open, balanced, and documented procedures can support sound participation. W3C points to its Patent Policy, membership structure, and Process Document; the process includes prepared agendas, following those agendas, accurate minutes, public review, and consensus-seeking deliberation. For participants evaluating a project, useful governance questions include:
- Are agendas shared in advance and followed during meetings?
- Are minutes accurate enough to record the work and any concerns raised?
- Can affected participants review proposals through an open process?
- Are decision-making, balance of interests, and appeals procedures clear?
- Are intellectual-property disclosures and licensing handled under an established policy?
These safeguards can help limit opportunities for improper coordination and support broad participation. They do not guarantee that every discussion, agreement, or project decision complies with antitrust law, and W3C expressly says its policy is not legal advice or definitive protection from liability. Its rules apply to W3C activities; they are not a universal template for every technology project.
What the National Cooperative Research and Production Act does—and does not cover
The National Cooperative Research and Production Act (NCRPA) addresses qualifying joint ventures and standards-development activity. The Department of Justice (DOJ) explains that the Act clarifies application of the rule-of-reason standard to covered activity and may allow a prevailing entity to recover attorneys’ fees.
Best Value
- Open Source, Programmer, Developer, Software Engineer, Code, DevOps, Computer, Software, Scrum, Python, Linux, Stack Overflow, Java, Dotnet, Docker, Terraform, Kubernetes, Deploy
- Salt, Puppet, Chef, Container, AWS, Azure, Cloud, Coding, Programming, Geek, Funny, Tech, Technical, Compile, Compilation, Science, Bug, Debug
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
The possible limitation of monetary damages to actual damages rather than treble damages is conditional. DOJ says it follows notification to both DOJ and the FTC and the subsequent publication of a notice in the Federal Register. It is not automatic protection for every open-source effort, standards project, or participant. The Act’s definition of a standards-development organization includes requirements such as openness, balance of interests, due process, an appeals process, and consensus; whether a particular organization or activity qualifies depends on the statute and the facts.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What changed in federal collaboration guidance
The DOJ and FTC withdrew their 2000 Antitrust Guidelines for Collaborations Among Competitors in December 2024. In a release dated February 23, 2026, DOJ said the agencies had launched an inquiry into possible additional guidance on competitor collaborations. The release described a request for comments due April 24, 2026, covering subjects including joint licensing, conditional dealing, algorithmic pricing, data sharing, and labor collaborations.
That release documents the inquiry and comment deadline; it does not establish whether replacement guidance was later issued. Check current DOJ and FTC materials before relying on a statement about the agencies’ latest guidance. The withdrawal of the 2000 document also does not mean that competitor collaboration is unregulated: the underlying antitrust laws and fact-specific analysis still matter.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A practical review before joining or continuing a project
Before participating—or when assessing a concern—work through these questions with counsel where appropriate:
- What is the work? Is it technical standardization or interoperability, or does it also involve commercial coordination?
- Who is participating? Are participants actual or potential competitors in a relevant area of business?
- What information is being shared? Is it technical and appropriate to the task, or non-public and company-specific, such as prices, costs, customers, output, or labor terms?
- How is the project governed? Are participation, decisions, documentation, review, and appeals open and balanced?
- How are intellectual-property rights handled? Is there a clear policy for disclosure and licensing?
- Does anyone rely on NCRPA notification? Confirm whether notification to both agencies and Federal Register publication occurred, and whether the entity and activity qualify.
These questions organize the issues raised by FTC, DOJ, and W3C materials; they are not a substitute for legal advice. If a live discussion approaches a sensitive topic, use the project’s objection and reporting process and consult your own antitrust counsel.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
