{"resourceId":"maryland-doit-ai-transcription-governance-card-gemini-copilot-only-20261110","versions":[{"version":"external-cae271e231a4798197f30637bee0329e6e0fe56438c3fb268b7490b9aaaa8660","resource":{"id":"maryland-doit-ai-transcription-governance-card-gemini-copilot-only-20261110","title":"Maryland DoIT governance card: AI meeting transcripts are public records, all-party consent required, and only Gemini and Copilot are approved transcription tools","organization":"Maryland Department of Information Technology (DoIT)","sector":"State government IT","geography":"Maryland, United States","publishedAt":"Last revised August 7, 2025 (inspected November 10, 2026)","publicationDate":"2025-08-07","eventDate":null,"sourceName":"Maryland DoIT","sourceLabel":"State AI governance guidance","sourceUrl":"https://doit.maryland.gov/policies/ai/Pages/AI-governance-card-call-recording-transcription-tools.aspx","evidenceClass":"standards-guidance","outcomeClass":"cautionary","topics":["governance-procurement","data-security","knowledge-work"],"finding":"Maryland DoIT's AI governance card for call recording and transcription treats AI meeting transcripts and recordings as public records under the Maryland Public Information Act, requires consent from every participant under the state's two-party consent rule, bars recording confidential meetings, and requires human review of accuracy. It lists Gemini and Copilot as the only tools currently approved for meeting transcription in state agencies; any other software needs review by DoIT's AI Enablement team through the intake process. The card was last revised Aug. 7, 2025.","sledRelevance":"Why now: Anthropic announced Claude Meetings on Nov. 10, and Maryland DoIT has an open RFQ for Claude Enterprise licenses (posted Nov. 6; covered in the Nov. 9 edition). Under this card, a Maryland agency could not use Claude as a meeting transcriber until the AI Enablement team approves it, and outputs would be PIA-reachable public records requiring consent and retention. Other states with all-party consent rules and public-records laws face similar gates.","evidence":"Official state guidance with explicit rules, risk tiering and an approved-tools list; no outcome data.","architectureImplications":"Interpretation: approved transcription is tied to tools inside the state productivity suite; an AI meeting participant writing to claude.ai is a separate system that needs intake review and a retention path.","governanceImplications":"The card requires intake review for non-approved tools, PIA-aware retention, all-party consent and watermark preservation; Claude Meetings would need to satisfy each before use.","securityPrivacyImplications":"Prohibits recording confidential meetings and sensitive data (SSNs, passwords, health details, immigration status, children's data); notes HIPAA use requires a BAA-backed service.","caveats":"Guidance last revised Aug. 7, 2025; predates Claude Meetings and does not mention Claude. It is guidance agencies may adopt or tighten, not a statute. The approved-tools list may have changed without a page revision. Cross-tagged state-government: state agency guidance. Newly relevant because Claude Meetings was announced Nov. 10 and Maryland DoIT has an open Claude Enterprise license RFQ.","streamIds":["anthropic","state-government"],"roles":{"sales":"Frame this as the approval path, not a barrier. Maryland is buying Claude Enterprise licenses, but its transcription governance card names only Gemini and Copilot as approved and routes any other tool through AI Enablement review, with all-party consent and PIA retention rules. For Maryland agency CIOs, ask whether Claude Meetings is in scope of their purchase and who files the intake. Offer intake-package preparation. Do not suggest Claude Meetings is already approved for Maryland agencies.","engineering":"Engineering should map Claude Meetings against each card requirement: consent notice to all participants, no confidential meetings, retention per State schedules, preserved AI-generated labels, and human accuracy review. Outputs live in claude.ai rather than the state productivity suite, so retention and PIA search must be designed. Google Meet-only support may also conflict with the agency's platform. Proof of value should demonstrate a PIA export of a test meeting's AI notes.","delivery":"Delivery would prepare an AI intake submission covering use case, risk tier, data flows, consent workflow and retention, coordinated with the agency PIA officer. Dependencies are DoIT AI Enablement review and the outcome of the Claude Enterprise RFQ. Pilot only after written approval and only with non-confidential meetings. Risks include staff adopting the beta before approval and AI notes containing errors that become public records."},"roleDetails":{"sales":{"customerProblem":"Maryland agencies buying Claude Enterprise may expect Claude Meetings to be usable, but state guidance only approves Gemini and Copilot for transcription.","stakeholders":["Agency CIO","Agency PIA officer","DoIT AI Enablement team","Agency counsel"],"discoveryQuestions":["Does your Claude purchase include meeting features?","Has AI intake been filed for Claude transcription use?","What meeting platform do you use?","How would AI notes be retained for PIA requests?"],"valueHypothesis":"A prepared intake package could shorten the review path for a narrowly scoped Claude meeting-notes use case.","potentialEngagement":"Intake documentation support and a consent and retention workflow design for one agency.","unsupportedClaims":["That Claude is approved for Maryland transcription","That a license purchase satisfies AI intake","That AI notes are exempt from PIA"]},"engineering":{"fit":"Relevant to Maryland agencies and to states with similar consent and records rules.","architectureIntegration":"Approved tools are suite-embedded (Gemini, Copilot); Claude Meetings outputs stored in claude.ai.","prerequisites":["DoIT AI intake approval","PIA officer consultation","Records schedule mapping"],"constraints":["Guidance last revised Aug. 2025","All-party consent state","No confidential meetings"],"security":"Card prohibits sensitive data in recordings and requires secure storage; HIPAA use requires a BAA-backed service.","proofOfValue":["Demonstrate consent notice reaches all participants","Demonstrate PIA-ready export of AI notes","Measure transcription error rate on agency acronyms"]},"delivery":{"work":"Prepare and submit AI intake, then pilot only if approved.","dependencies":["DoIT AI Enablement review","Claude Enterprise RFQ award","Meeting platform compatibility"],"ownership":"Agency CIO with PIA officer; DoIT for approval.","skillsAdoption":"Hosts trained on consent language and watermark preservation.","governanceCheckpoints":["Intake approval","PIA officer sign-off","Post-pilot accuracy review"],"acceptanceCriteria":["Proposed: written approval before any production meeting","Proposed: consent captured for 100% of pilot meetings","Proposed: AI notes retrievable for a test PIA request within statutory timelines"],"risks":["Shadow use before approval","Erroneous notes as public records","Platform mismatch with Google Meet-only support"]}},"retrievedAt":"2026-11-11T04:21:09Z","enrichedAt":"2026-11-11T04:32:28Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Interpretation: guidance highlights transcription errors with accents, dialects and acronyms, so accessibility uses of AI notes still need human verification.","procurementImplications":"Interpretation: a Claude Enterprise purchase does not by itself approve Claude for transcription; buyers should plan AI intake review alongside procurement.","operatingModelImplications":"Agency IT leads must work with their PIA officer; DoIT's AI Enablement team gates new transcription tools.","sourceVerification":{"openedUrl":"https://doit.maryland.gov/policies/ai/Pages/AI-governance-card-call-recording-transcription-tools.aspx","referenceExcerpt":"If you would like to use a different software than Gemini and Copilot, the AI Enablement team will have to review the policies","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}