# OMB issues M-25-21 on federal AI use > The U.S. Office of Management and Budget issued Memorandum M-25-21, "Accelerating Federal Use of AI through Innovation, Governance, and Public Trust." The memorandum directs executive agencies to pursue AI adoption while maintaining safeguards for civil rights, civil liberties, and privacy. It rescinds and replaces M-24-10 and includes implementation requirements in an appendix for agency strategy, governance, risk management, and public transparency. Canonical: https://hypler.com/ai-news/omb-m-25-21-federal-ai-use-2025 Hypler publication: 2026-10-06 Hypler updated: 2026-10-10 Original source date: 2025-04-03 Byline: Hypler editorial team Source publisher: US Office of Management and Budget Editorial standard: https://hypler.com/ai-news#editorial-standard Article kind: source-briefing Category: Policy Tags: OMB, federal policy, AI governance, public trust ## Engineering relevance The memorandum connects federal AI adoption with agency governance. Product teams can use its operating themes to structure ownership, review, and evaluation, while determining applicable obligations for their own jurisdiction and context. ## What the primary source recorded OMB Memorandum M-25-21, dated April 3, 2025, directs covered executive-branch agencies to accelerate AI use while maintaining safeguards for civil rights, civil liberties, and privacy. It rescinds and replaces M-24-10, includes implementation guidance, and describes requirements for agency governance, risk management, transparency, and high-impact AI; it governs agency use rather than creating general public obligations. ## The interface and data contract behind the headline A covered-agency implementation register should map each applicable memorandum requirement to a system owner, use case, high-impact determination, evidence artifact, due date, and escalation path. Architecture documentation should separately identify the AI-enabled functionality rather than label every surrounding information system as AI. Procurement, privacy, civil-rights, and security responsibilities require their own accountable review paths. ## Tradeoffs and failure modes A vendor checklist can omit the agency's intended use and therefore miss the actual risk. An organization can also misclassify a high-impact workflow because it looks at the model rather than the decision supported. Public inventories become misleading when ownership, deployment state, or safeguards are stale. The memorandum itself does not replace other applicable policy or law. ## A bounded hypothetical implementation Hypothetical example: an agency explores an assistant that drafts benefit-case summaries. The register marks the workflow as potentially high impact, records that a staff member retains the final determination, and collects evaluation evidence by language and document quality. The pilot pauses when a required impact assessment is incomplete rather than treating the memo as a generic permission slip. ## Validation should test the system, not the slogan Test the inventory against active use cases, verify responsible-official assignments, and sample evidence for each high-impact determination. Exercise the discontinue-use process, incident reporting, and public transparency update. Legal and policy reviewers should confirm applicability and interpretive changes; engineering validation should prove that the implemented safeguards behave as the register says they do. ## SI direction requires evidence and authority boundaries The memorandum is federal executive-branch guidance, not a claim about Hypler or a certification for commercial systems. Its practical engineering value is the discipline of named owners, scoped use cases, measurable safeguards, and a credible path to stop use when evidence no longer supports it. ## Agency AI programs need accountable operating records Agency governance guidance needs to be read in its defined institutional scope. A private company can study its operating patterns without treating the memorandum as a universal rule for its own products. Keep the cited document, issue date and relevant use case with any analysis, and distinguish the source's requirements from the engineering controls proposed for a particular system. Where legal interpretation is required, supply implementation facts to the responsible reviewer rather than asking a model to decide applicability. Useful technical work makes the system easier to examine without representing that work as a federal compliance determination. An inventory should describe operational relationships, not merely collect names of model vendors. Identify the workflow owner, intended users, data classes, dependencies, output audience and any consequential action path. Connect that record to the application revision it describes. A feature can change from drafting assistance to a decision input without changing its visible name, so the inventory should be updated from delivery artifacts and reviewed for meaning by its accountable owner. This reduces the gap between a governance document and the software people actually use, while preserving distinctions among experiments, internal tools and public services. Oversight needs a practical intervention path. An operator must be able to pause a workflow, investigate a disputed result and determine whether a model change affected its behavior. A nominal approval step is weak if the reviewer cannot see the evidence or if the system proceeds when the decision is unavailable. Define what the workflow does when approval is denied, expires or cannot be obtained. Monitoring should include those outcomes instead of counting only completed requests. Preserve records that support investigation while limiting access to sensitive input data; governance should not become a reason to copy private material into unrestricted logs. A delivery review can inspect one use case from inventory through configuration, interface, evaluation and outcome evidence. Check whether the named owner and declared permission boundary still match the active implementation. Test a provider outage, an unavailable reviewer and a result requiring correction. Compare the final user-visible behavior with the documented operating procedure. Hypler can build the interfaces, adapters and evidence records needed for that review around an existing system. The work supports accountable operation and informed policy review, while the historical memorandum remains a source with its own date and scope rather than a badge attached to a commercial product. ## Original source - [US Office of Management and Budget](https://www.whitehouse.gov/wp-content/uploads/2025/02/M-25-21-Accelerating-Federal-Use-of-AI-through-Innovation-Governance-and-Public-Trust.pdf) ## Related links - [SI agent governance](/ai-agent-governance) - [Data integration engineering](/data-integration-engineering) - [Testing and observability](/wiki/testing-observability) ## Image provenance ### Primary image ![Generated editorial illustration. Federal AI governance illustrated with a memorandum, balanced scales and circuit drafting overlay; not an official document or event photograph.](https://hypler.com/assets/news/omb-m-25-21-federal-ai-use-2025.webp) generated illustration. Credit: Hypler / AI-generated editorial illustration. Hypler editorial asset; not vendor or event photography. - [Image source](https://hypler.com/ai-news/media.md) ### Supporting image ![Generated illustration of evidence records passing through a permission gate; not a compliance certification.](https://hypler.com/assets/news/policy-evidence.webp) generated illustration. Credit: Hypler / AI-generated editorial illustration. Hypler editorial asset; not vendor or event photography. - [Image source](https://hypler.com/ai-news/media.md) ## Reading boundary Historical source briefing with Hypler engineering analysis. Source details reflect the original publication date; implementation examples are hypothetical. Public reading grants no private access or execution authority.