SectionUpdated April 16, 2026

    FAR 12.212Computer software.

    Plain-English Summary

    FAR 12.212 explains how the Government acquires commercial computer software and commercial computer software documentation, and it sets the default rule that these items should be bought under the vendor’s customary public license terms so long as those terms are consistent with Federal law and meet the Government’s needs. It also limits what contracting officers and agencies may demand from offerors and contractors: they generally may not require technical information that is not normally provided to the public, and they generally may not require the contractor to give the Government broader rights in the software or documentation than the parties agree to in the license. The section further states that the Government’s rights are limited to the rights stated in the license included in any contract addendum, which makes the license text a controlling part of the deal. In practice, this section is about preserving commercial market terms for software purchases while ensuring the Government gets the rights it actually needs and that those rights are clearly documented. It is closely tied to FAR 27.405-3, which provides additional guidance on negotiating software license agreements.

    Key Rules

    Use customary public licenses

    Commercial computer software and documentation must be acquired under the licenses customarily offered to the public, as long as those licenses are consistent with Federal law and satisfy the Government’s needs. This means the Government generally accepts the vendor’s standard commercial licensing model rather than imposing unique government-only terms.

    No special technical data demands

    Offerors and contractors generally cannot be required to provide technical information about commercial software or documentation that is not customarily made available to the public. The rule protects proprietary commercial information from being turned over simply because the buyer is the Government.

    No forced transfer of rights

    Offerors and contractors generally cannot be required to give the Government rights to use, modify, reproduce, release, perform, display, or disclose commercial software or documentation unless the parties mutually agree. Any broader rights must be negotiated, not unilaterally imposed.

    Government rights follow the license

    For commercial computer software and documentation, the Government has only the rights specified in the license contained in any contract addendum. The license language is therefore critical and should be reviewed carefully before award or acceptance.

    License must meet Federal law

    Even though customary public licenses are the default, they are acceptable only to the extent they are consistent with Federal law. If a license term conflicts with law or fails to satisfy the Government’s actual needs, it cannot simply be accepted as written.

    See negotiation guidance

    FAR 12.212 directs users to FAR 27.405-3 for additional guidance on negotiating commercial software license agreements. That cross-reference signals that license review and negotiation are expected parts of the acquisition process when standard terms are not sufficient.

    Responsibilities

    Contracting Officer

    Review the vendor’s commercial software license and any addendum to ensure the Government receives only the rights needed and that the terms are consistent with Federal law. The contracting officer should avoid requiring noncustomary technical information or broader rights unless they are actually negotiated and documented.

    Agency/Requirement Owner

    Define the Government’s actual operational and legal needs for the software, including any required rights to use, copy, modify, or disclose. The agency should identify early whether the vendor’s standard license is sufficient or whether special terms must be negotiated.

    Offeror/Contractor

    Provide commercial software and documentation under customary public license terms and disclose the license terms that will govern the Government’s use. The contractor generally does not have to provide nonpublic technical information or grant extra rights unless it agrees to do so.

    Legal/Policy Support Staff

    Evaluate whether proposed license terms are consistent with Federal law and whether any restrictions conflict with procurement policy or mission needs. They should help resolve issues involving ownership, use rights, confidentiality, and disclosure limits.

    Government User/Program Office

    Use the software only within the rights granted by the license and ensure the contract file reflects the applicable license terms. The program office should not assume it has broader rights than those expressly stated.

    Practical Implications

    1

    The license is often the most important document in the transaction, so contracting teams should read it as carefully as the contract itself. If the license is attached in an addendum, those terms control the Government’s rights.

    2

    A common pitfall is assuming the Government automatically gets unlimited rights because it is a federal buyer. For commercial software, the default is usually the vendor’s standard license, not government-purpose or unlimited rights.

    3

    Another frequent issue is failing to confirm whether the license conflicts with Federal law or mission needs. Terms about audit rights, indemnification, venue, automatic renewals, data collection, or restrictions on copying and disclosure may need review.

    4

    Contractors should not be pressured to hand over source code, internal technical data, or broader usage rights unless those items are actually needed and negotiated. If the Government needs more than the standard license provides, that should be addressed up front.

    5

    Because FAR 12.212 points to FAR 27.405-3, acquisition teams should treat software licensing as a negotiation and documentation issue, not just a pricing issue. Clear documentation helps avoid disputes over what the Government may do with the software after award.

    Official Regulatory Text

    (a) Commercial computer software or commercial computer software documentation shall be acquired under licenses customarily provided to the public to the extent such licenses are consistent with Federal law and otherwise satisfy the Government’s needs. Generally, offerors and contractors shall not be required to- (1) Furnish technical information related to commercial computer software or commercial computer software documentation that is not customarily provided to the public; or (2) Relinquish to, or otherwise provide, the Government rights to use, modify, reproduce, release, perform, display, or disclose commercial computer software or commercial computer software documentation except as mutually agreed to by the parties. (b) With regard to commercial computer software and commercial computer software documentation, the Government shall have only those rights specified in the license contained in any addendum to the contract. For additional guidance regarding the use and negotiation of license agreements for commercial computer software, see 27.405-3 .