{"resourceId":"ai-acquisition-lessons","versions":[{"version":"legacy/2026-08-27/ai-acquisition-lessons","resource":{"id":"ai-acquisition-lessons","title":"AI acquisition reviews rarely capture reusable lessons","organization":"U.S. Government Accountability Office","sector":"Public procurement","geography":"United States","publishedAt":"April 13, 2026","sourceName":"AI Acquisitions: Agencies Should Collect and Apply Lessons Learned","sourceLabel":"GAO-26-107859","sourceUrl":"https://files.gao.gov/reports/GAO-26-107859/index.html","evidenceClass":"government-audit","outcomeClass":"cautionary","topics":["infrastructure","data-security","governance-procurement","operating-model"],"finding":"GAO examined 13 AI acquisitions at four federal agencies and found that procurement processes did not systematically preserve lessons for future buyers.","sledRelevance":"SLED buyers face similar risks when contracts omit evaluation data, performance thresholds, portability, audit access, or an exit path.","evidence":"Four agencies lacked systematic lessons-learned requirements, missing reusable learning on data rights, testing, regional model accuracy, and discontinued solutions. All four concurred with GAO’s recommendations.","architectureImplications":"Require pre-award test plans, integration boundaries, portability, performance acceptance criteria, observability, and a documented exit architecture.","governanceImplications":"Use AI-specific solicitation clauses and a shared lessons repository; assign procurement, legal, data, and technical owners to acceptance and renewal decisions.","securityPrivacyImplications":"Contract for audit access, incident duties, data use and deletion, model-change notice, subcontractor controls, and security testing evidence.","caveats":"The sample is federal and limited to 13 acquisitions; local procurement statutes and market conditions vary."}},{"version":"enrichment/2026-09-05T02:33:27.019Z/ai-acquisition-lessons","resource":{"id":"ai-acquisition-lessons","title":"AI acquisition reviews rarely capture reusable lessons","organization":"U.S. Government Accountability Office","sector":"Public procurement","geography":"United States","publishedAt":"April 13, 2026","publicationDate":"2026-04-13","eventDate":null,"sourceName":"AI Acquisitions: Agencies Should Collect and Apply Lessons Learned","sourceLabel":"GAO-26-107859","sourceUrl":"https://files.gao.gov/reports/GAO-26-107859/index.html","evidenceClass":"government-audit","outcomeClass":"cautionary","topics":["infrastructure","data-security","governance-procurement","operating-model"],"finding":"GAO examined 13 AI acquisitions at four federal agencies and found that procurement processes did not systematically preserve lessons for future buyers.","sledRelevance":"SLED buyers face similar risks when contracts omit evaluation data, performance thresholds, portability, audit access, or an exit path.","evidence":"Four agencies lacked systematic lessons-learned requirements, missing reusable learning on data rights, testing, regional model accuracy, and discontinued solutions. All four concurred with GAO’s recommendations.","architectureImplications":"Require pre-award test plans, integration boundaries, portability, performance acceptance criteria, observability, and a documented exit architecture.","governanceImplications":"Use AI-specific solicitation clauses and a shared lessons repository; assign procurement, legal, data, and technical owners to acceptance and renewal decisions.","securityPrivacyImplications":"Contract for audit access, incident duties, data use and deletion, model-change notice, subcontractor controls, and security testing evidence.","caveats":"The sample is federal and limited to 13 acquisitions; local procurement statutes and market conditions vary.","streamIds":["state-government","local-government","campus-operations","k12"],"roles":{"sales":"Interpretation — Customer problem: AI buyers can repeat avoidable contract and testing mistakes when prior procurement lessons disappear. Stakeholders: procurement, legal, program sponsors, data owners, enterprise architecture, and security. Discovery: where are evaluation results and failed purchases recorded; which rights cover customer data; and how are regional accuracy and exit needs tested? Value hypothesis: reusable acquisition evidence may improve requirements and reduce poorly understood acceptance risks. Potential engagement: review selected past acquisitions and build the next solicitation's evaluation and exit criteria. The audit's 13 acquisitions identify concrete questions about testing, data rights, and discontinued solutions. Unsupported claims: this limited federal sample does not establish failure rates or financial benefit for SLED buyers, whose statutes and markets differ.","engineering":"Interpretation — Fit: apply the findings at requirements and pre-award evaluation for a defined AI use case. Architecture and integration: specify system boundaries, data exchange, monitoring, performance acceptance, portability, and an executable exit route. Prerequisites: representative permitted test data, regional use conditions, ownership of expected answers, and procurement/legal agreement on enforceable evidence. Constraints: a supplier demonstration may omit local data or integration conditions; discontinued components can defeat an undocumented exit plan. Security: require audit access, incident duties, data-use/deletion terms, model-change notices, and subcontractor controls. Proposed proof: exercise representative customer scenarios, failure handling, data export and deletion, and record results against agreed requirements before selection or acceptance.","delivery":"Interpretation — Work: capture acquisition lessons, convert them into contract and test requirements, and retain evidence through acceptance, renewal, and exit. Dependencies: procurement schedules, legal review, vendor cooperation, and access to technical findings from prior projects. Ownership: procurement maintains the shared record; technical and program owners validate performance; legal/data owners resolve rights and deletion obligations. Skills and adoption: teach buyers to distinguish supplier assurances from demonstrated evidence and make lessons easy to reuse. Governance checkpoints: solicitation approval, acceptance, renewal, and discontinuation review. Proposed acceptance: each agreed contract threshold has test evidence, unresolved gaps have accountable remediation, and export/exit steps are documented and exercised where feasible. Risks include generic clauses, inaccessible lessons, and criteria that cannot be enforced under local procurement rules."},"retrievedAt":null,"enrichedAt":"2026-09-05T02:33:27.019Z","enrichmentBasis":"archived evidence"}}]}