PolicyOMB M-24-10 and Federal AI governance
OMB Memorandum M-24-10 directs U.S. federal agencies to inventory AI use cases, conduct impact assessments, and appoint chief AI officers with quarterly reporting duties.
Verified for technical accuracy — Kodi C.
The Office of Management and Budget issued Memorandum M-24-10 on March 28, 2024, operationalizing Executive Order 14110 across federal agencies. The policy requires every CFO Act agency to designate a Chief Artificial Intelligence Officer, publish inventories of safety-impacting AI use cases, and implement minimum risk management practices by December 1, 2024. Agencies must also file quarterly reports on compliance progress and document waivers granted for national security or law-enforcement use.
Key directives
- Governance appointments. Agencies must confirm Chief AI Officers, AI governance boards, and AI setup leads to manage policy compliance and budget integration.
- AI use-case inventory. Safety-impacting and rights-impacting systems require documented assessments, independent evaluation, and public reporting that follows the AI Risk Management Framework.
- Testing and oversight. Agencies must implement real-world testing, incident response plans, and shutdown procedures before deploying safety-impacting AI, with annual reviews and Inspector General oversight.
Focus areas
- Gap analysis. Benchmark existing AI programs against M-24-10 timelines for inventories, assessments, and public transparency deliverables.
- Policy alignment. Update agency-specific AI strategies, privacy impact assessments, and procurement clauses to incorporate OMB risk controls and independent evaluation requirements.
- Reporting cadence. Establish quarterly reporting processes that capture compliance metrics, waivers, incident logs, and mitigation plans for submission to OMB and the public.
Program assurance
- Independent evaluation. Stand up external review panels or cross-functional teams that can certify pre-deployment testing and monitor ongoing AI system performance.
- Records management. Archive AI life-cycle documentation—training data lineage, evaluation artifacts, and incident tickets—to satisfy oversight and FOIA inquiries.
- Workforce readiness. Train acquisition, privacy, and mission owners on the memorandum's obligations, including waiver justification templates and shutdown decision criteria.
Cited sources
- OMB Memorandum M-24-10 — Advancing Governance, Innovation, and Risk Management for Agency Use of Artificial Intelligence
- OMB Fact Sheet — Governmentwide Policy to Advance Safe, Secure, and Responsible AI
This brief supporting federal programs with M-24-10 compliance playbooks that formalize AI inventories, external evaluations, and public reporting pipelines.
Regulatory backdrop
This development represents a significant milestone in the broader regulatory environment affecting policy initiatives globally. Organizations must understand not only the immediate requirements but also the interconnected policy frameworks that influence implementation strategies and compliance obligations.
The regulatory environment continues to evolve as policymakers balance innovation enablement with risk mitigation and stakeholder protection. This particular development reflects ongoing efforts to establish clear governance frameworks that support responsible adoption while maintaining appropriate safeguards against potential misuse or unintended consequences.
Stakeholders across multiple sectors should consider how this development intersects with existing compliance obligations under frameworks such as GDPR, CCPA, SOC 2, ISO 27001, and industry-specific regulations. The interconnected nature of modern regulatory requirements means that addressing one area often has implications for related compliance domains.
What to consider
Organizations seeking to align with these requirements should begin with a thorough gap analysis comparing current capabilities against the specified standards. This assessment should encompass technical infrastructure, organizational processes, personnel competencies, and governance mechanisms.
A phased implementation approach typically proves most effective, beginning with foundational elements before progressing to more advanced capabilities. Priority should be given to areas presenting the greatest risk exposure or compliance urgency, while building sustainable practices that can adapt to evolving requirements.
Key implementation factors include resource allocation, timeline management, stakeholder coordination, and change management. Organizations should establish clear governance structures to oversee implementation progress and ensure accountability across relevant business units and functional areas.
Technical implementation should follow security-by-design principles, incorporating appropriate controls from the outset rather than attempting to retrofit security measures after deployment. This approach typically reduces overall implementation costs while improving security posture and compliance outcomes.
Managing risk
Effective risk management requires systematic identification, assessment, and treatment of risks associated with this development. Organizations should use established frameworks such as NIST RMF, ISO 31000, or COBIT to structure their risk management approach.
Risk identification should consider technical vulnerabilities, operational disruptions, regulatory penalties, reputational impacts, and strategic implications. Each identified risk should be assessed for likelihood and potential impact, with appropriate risk treatment strategies developed for high-priority items.
Continuous monitoring capabilities are essential for detecting emerging risks and evaluating the effectiveness of implemented controls. Organizations should establish key risk indicators and reporting mechanisms that provide timely visibility into risk exposure across relevant domains.
Risk tolerance thresholds should be established at the organizational level, with clear escalation procedures for risks that exceed acceptable levels. This governance framework ensures appropriate oversight while enabling agile responses to changing risk conditions.
Roadmap to compliance
Developing a structured compliance roadmap helps organizations systematically address requirements while managing resource constraints and competing priorities. The roadmap should establish clear milestones, responsible parties, and success criteria for each compliance objective.
Near-term priorities typically focus on addressing imminent compliance deadlines and high-risk gaps. Medium-term initiatives build sustainable compliance capabilities through process improvements, technology investments, and workforce development. Long-term strategic planning ensures continued alignment as requirements evolve.
Documentation requirements should be addressed throughout the compliance journey, establishing evidence trails that demonstrate due diligence and support audit activities. Organizations should implement document management practices that ensure accessibility, version control, and appropriate retention.
Regular compliance assessments help organizations verify progress against roadmap objectives and identify areas requiring additional attention. These assessments should incorporate both internal reviews and independent third-party evaluations where appropriate.
Who is affected
This development affects multiple stakeholder groups, each with distinct interests, concerns, and information needs. Effective stakeholder management requires understanding these perspectives and developing appropriate engagement strategies.
Internal stakeholders including executive leadership, board members, operational teams, and employee populations require tailored communications that address their specific concerns and responsibilities. Clear role definitions and accountability structures support effective internal coordination.
External stakeholders such as customers, partners, regulators, and industry peers also have legitimate interests in organizational responses to this development. Transparent communication and demonstrated commitment to compliance build trust and support collaborative relationships.
Investor and analyst communities focus on governance, risk management, and compliance capabilities as indicators of organizational resilience and long-term value creation. Organizations should consider how their response to this development affects external perceptions and stakeholder confidence.
Infrastructure needs
Technology plays a critical enabling role in addressing the requirements associated with this development. Organizations should evaluate current technology capabilities against anticipated needs and develop enhancement plans where gaps exist.
Core technology considerations typically include data management systems, security infrastructure, monitoring and analytics platforms, and integration capabilities. Organizations should assess whether existing technology investments can be used or whether new capabilities are required.
Automation opportunities should be identified and prioritized based on efficiency gains, error reduction, and scalability benefits. Robotic process automation, artificial intelligence, and machine learning technologies may offer valuable capabilities for specific use cases.
Technology vendor relationships should be evaluated to ensure appropriate support for compliance requirements. Contractual provisions, service level agreements, and vendor security practices all merit attention as part of technology governance.
Emerging trends
The regulatory and policy environment continues to evolve rapidly, with several emerging trends likely to influence future developments in this area. Organizations should maintain awareness of these trends and build adaptive capabilities that support ongoing compliance.
Regulatory convergence across jurisdictions creates both challenges and opportunities for multinational organizations. While harmonization efforts reduce compliance complexity in some areas, divergent national approaches require careful planning in others.
Technology evolution continues to create new capabilities and new risks requiring regulatory attention. Organizations should anticipate that current requirements will be supplemented or modified as policymakers respond to technological changes and emerging best practices.
Industry collaboration through standards bodies, professional associations, and informal networks provides valuable opportunities for sharing implementation experiences and influencing policy development. Active engagement in these forums supports more effective compliance outcomes.
Continue in the Policy pillar
Return to the hub for curated research and deep-dive guides.
Latest guides
-
Policy Advocacy Roadmap
Coordinate cross-border policy advocacy aligned with EU Better Regulation, U.S. Administrative Procedure Act, Lobbying Disclosure rules, and Canadian transparency requirements.
-
AI Policy Implementation Guide
Coordinate governance, safety, and reporting programmes that meet EU Artificial Intelligence Act timelines and U.S. National AI Initiative Act mandates while sustaining product…
-
Export Controls and Sanctions Policy Guide
Integrate U.S. Export Control Reform Act, International Emergency Economic Powers Act, and EU Dual-Use Regulation requirements into trade compliance, engineering, and supplier…
Cited sources
- OMB Memorandum M-24-10 — Advancing Governance, Innovation, and Risk Management for Agency Use of Artificial Intelligence — whitehouse.gov
- OMB Issues Governmentwide Policy to Advance Safe, Secure, and Responsible AI — whitehouse.gov
- ISO 31000:2018 — Risk Management Guidelines — International Organization for Standardization
Comments
Community
We publish only high-quality, respectful contributions. Every submission is reviewed for clarity, sourcing, and safety before it appears here.
No approved comments yet. Add the first perspective.