# Checklist: buying AI under OMB M-25-22, from scoping the purchase to contract closeout

Fourteen steps that follow OMB Memorandum M-25-22 through the acquisition lifecycle, each labeled as a requirement, a memo recommendation or our suggestion: scope, high-impact determination, solicitation terms on data and lock-in, pre-award testing, monitoring and closeout.

Checklist · Cross-sector · Economics & Procurement. Published November 14, 2026. Last reviewed November 14, 2026.

## One memo for buying AI across federal agencies

OMB issued Memorandum M-25-22, *Driving Efficient Acquisition of Artificial Intelligence in Government*, on April 3, 2025. It rescinds and replaces M-24-18 and works alongside M-25-21, the companion memo on federal AI use [1]. It applies to the agencies defined in 44 U.S.C. 3502(1), with some requirements limited to Chief Financial Officers Act agencies, and does not apply to elements of the Intelligence Community or to AI acquired as a component of a National Security System [1]. It covers contracts awarded under solicitations issued on or after the date 180 days after the memo was issued, and options to renew or extend exercised after that date [1]. As checked on November 14, 2026, OMB’s memoranda page still lists M-25-22 among the 2025 memoranda, and no later entry is titled as rescinding or replacing it [3].

## How to read the steps

The steps follow the memo’s acquisition lifecycle: identifying requirements, market research and planning, solicitation, selection and award, contract administration and closeout [1]. Each step is labeled. **Requirement** means the memo says agencies must do it; **Memo recommendation** means it says should, or encourages; **Our suggestion** goes beyond the memo. The owner under each step is a typical role; the memo names only a few, such as the Senior Agency Official for Privacy [1].

One conflict inside the memo affects timing. Its text gives agencies 270 days from issuance to update internal acquisition procedures, while its consolidated table of required actions lists 200 days for adding the process on data ownership and intellectual property rights to those updates, and does not list the 270-day item [1]. The memo does not reconcile the two figures, and this page reports both. The steps are written as checks to run for each new purchase.

Companies that sell AI to agencies can read the same steps as a preview of the terms they are likely to see. This page explains the memo; it is not legal advice.

Moraph’s teams help organizations with work like this. [See our solutions](https://www.moraph.com/solutions).

## The checklist

1. **Decide whether the purchase is covered AI: an AI system or service, or a product where AI is integrated into an agency process, and not a common commercial product with AI embedded.** (Contracting officer with the program office) Memo recommendation. The memo’s scope uses the Advancing American AI Act definition, which excludes common commercial products with embedded AI, such as a word processor or map navigation system. In deciding whether a product falls within that exception, the memo says agencies should assess whether the product is widely available to the public for commercial use and whether AI is embedded in a product with substantial non-AI purposes [1].
2. **Record the date the solicitation was issued and whether any exclusion applies, such as AI acquired as a component of a National Security System, research, incidental contractor use of AI, or assessments of AI that is the target of an enforcement action.** (Contracting officer) Our suggestion, based on the memo’s scope. The memo applies to contracts awarded under solicitations issued on or after the date 180 days after its issuance and to options exercised after that date, and lists the uses it does not govern [1]. Recording these facts, and keeping a register of which contracts and options fall on each side of that line, is our suggestion.
3. **Convene the agency’s cross-functional team for the purchase and draw up an initial list of risks, including risks to the nine principles for AI use in Executive Order 13960.** (Program manager) Requirement. Agencies must update procedures so officials can convene a cross-functional team, and that team must identify potential risks to the agency’s implementation of the nine principles in Executive Order 13960. That the team should help create an initial list of potential risks is a memo recommendation. The memo’s examples of members include acquisition, IT, cybersecurity, privacy, civil rights, budget, data and legal staff [1].
4. **Identify the reasonably foreseeable use cases and make an initial determination of whether the system is likely to host a high-impact AI use case.** (Program manager with the Chief AI Officer’s office) Requirement, to the greatest extent practicable. High-impact AI has the meaning in M-25-21. M-25-22 summarizes it as AI whose output serves as the primary basis for decisions or actions with legal, material, binding or significant effect on matters including rights, access to services, safety, critical infrastructure or strategic assets [1]; M-25-21 itself says a principal basis [2].
5. **Run market research that includes new entrants, and ask for demonstrations in conditions close to the agency’s real operating environment, noting any sign of vendor lock-in.** (Contracting officer with the technical lead) Memo recommendation. Agencies should conduct thorough market research, seek novel capabilities from new entrants when appropriate, and, where practicable, seek demonstrations and tests that reflect agency networks; this phase should also identify obstacles to long-term cost-effectiveness from lock-in [1].
6. **Write the requirement in performance terms: a statement of objectives or performance work statement, a quality assurance surveillance plan, and incentives tied to measurable outcomes.** (Contracting officer) Memo recommendation. Agencies are strongly encouraged to use performance-based techniques, and, when determining whether to include performance-based incentives, must carefully consider whether the metrics are tied to business and mission outcomes and can measure baseline performance [1].
7. **In the solicitation, disclose whether the planned use is or may become high-impact, and tell vendors what transparency and documentation they must provide.** (Contracting officer) Requirement. When practicable, agencies must disclose in solicitations whether a planned use is or may become high-impact; for systems with potential or expected high-impact uses, agencies must inform vendors of the documentation needed to comply with M-25-21, for example enough descriptive information to complete the AI impact assessment [1]. M-25-21 requires an AI impact assessment before any high-impact use case is deployed [2].
8. **Put data, intellectual property and lock-in terms in the solicitation: who owns what, how agency data may be handled and retained, a permanent bar on training public or commercial models on non-public agency data without consent, and portability and knowledge-transfer requirements.** (Contracting officer with agency counsel) Requirement for IP and data terms: agencies must include appropriate terms on IP rights and lawful use of government data, consistent with their agency process. The memo says that process should address, among other things, ensuring contracts permanently prohibit using non-public agency inputs and outputs to further train publicly or commercially available AI, absent explicit agency consent, which makes that point a memo recommendation. Memo recommendation for lock-in provisions in the solicitation, such as knowledge transfer, data and model portability, clear licensing and pricing transparency; in the contract itself, vendor lock-in protections are among the terms agencies must include [1].
9. **Bring in the Senior Agency Official for Privacy early whenever the AI will handle personally identifiable information, including during pre-solicitation planning.** (Senior Agency Official for Privacy) Requirement. Consistent with OMB Circular A-130, agencies shall set policies and contract terms that ensure privacy compliance, and shall ensure the Senior Agency Official for Privacy has early and ongoing involvement, including when defining requirements [1].
10. **Decide whether the solicitation should require the vendor to disclose any use of AI in performing the contract.** (Contracting officer) Requirement to decide. The memo says agencies must be cognizant of the risks of unsolicited AI use by vendors and determine whether circumstances merit a disclosure provision [1].
11. **Before award, test the proposed AI solutions where practicable, and re-check proposals for new AI risks and for problems meeting M-25-21.** (Technical evaluation panel) Requirement, to the greatest extent practicable, for testing; memo recommendation for a test environment on agency networks and for re-evaluating risks before selection [1].
12. **Include contract terms for ongoing testing and monitoring: evaluation on data the agency defines, vendor access and time for independent evaluation, documented vendor test procedures, and compliance with the M-25-21 minimum practices for high-impact uses.** (Contracting officer) Requirement. The memo lists these terms as ones agencies must include, says the agency’s evaluation data should not be accessible to the vendor, and says contracts must not prohibit agencies from internally disclosing how the vendor tests or the results [1]. M-25-21’s minimum practices include pre-deployment testing, an impact assessment, ongoing monitoring and human oversight [2]. Vendor performance standards, rollback and notice of new AI features are memo recommendations [1].
13. **After award, obtain an authorization to operate before deployment, monitor performance and emerging risks, review value for money at intervals, and set criteria for retiring the system.** (Contracting officer’s representative with the authorizing official) Requirement for the authorization to operate, under OMB Circular A-130 and FISMA policies, and for contract oversight that identifies risks to privacy, civil rights and civil liberties. Memo recommendation for periodic value evaluations and sunset criteria [1].
14. **When the agency decides not to extend the contract, agree with the vendor on the format and usability of data and derived products, and plan any transfers before access ends.** (Contracting officer) Memo recommendation. Agencies should work with the vendor to implement terms on continuing rights and access to data and derived products as soon as the decision not to extend is made [1]. Starting that plan at award rather than at closeout is our suggestion.

## Sources

1. Office of Management and Budget. M-25-22, Driving Efficient Acquisition of Artificial Intelligence in Government (April 3, 2025). <https://www.whitehouse.gov/wp-content/uploads/2025/02/M-25-22-Driving-Efficient-Acquisition-of-Artificial-Intelligence-in-Government.pdf> Checked November 14, 2026.
2. Office of Management and Budget. M-25-21, Accelerating Federal Use of AI through Innovation, Governance, and Public Trust (April 3, 2025). <https://www.whitehouse.gov/wp-content/uploads/2025/02/M-25-21-Accelerating-Federal-Use-of-AI-through-Innovation-Governance-and-Public-Trust.pdf> Checked November 14, 2026.
3. Office of Management and Budget. Memoranda (OMB guidance index). <https://www.whitehouse.gov/omb/information-resources/guidance/memoranda/> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-omb-m-25-22-federal-ai-acquisition-contract-terms>
Publisher: Moraph Insights
