From the Anthropic edition of November 10, 2026
Maryland DoIT governance card: AI meeting transcripts are public records, all-party consent required, and only Gemini and Copilot are approved transcription tools
Maryland Department of Information Technology (DoIT) · State government IT · Maryland, United States
- Publisher
- Maryland DoIT
- Original publication
- Last revised August 7, 2025 (inspected November 10, 2026)
- Source retrieved
- 2026-11-11
What happened
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.
Why it matters
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 and measured results
Official state guidance with explicit rules, risk tiering and an approved-tools list; no outcome data.
Limitations and uncertainty
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.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-11; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- 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
- Discovery questions
- 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?
- Value hypothesis
- A prepared intake package could shorten the review path for a narrowly scoped Claude meeting-notes use case.
- Potential engagement
- Intake documentation support and a consent and retention workflow design for one agency.
- Unsupported claims
- That Claude is approved for Maryland transcription
- That a license purchase satisfies AI intake
- That AI notes are exempt from PIA
Pre-sales engineering
Role takeaway
- Fit
- Relevant to Maryland agencies and to states with similar consent and records rules.
- Architecture and integration
- 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.
- Proof of value
- Demonstrate consent notice reaches all participants
- Demonstrate PIA-ready export of AI notes
- Measure transcription error rate on agency acronyms
Delivery
Role takeaway
- 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.
- Skills and adoption
- Hosts trained on consent language and watermark preservation.
- Governance checkpoints
- Intake approval
- PIA officer sign-off
- Post-pilot accuracy review
- Acceptance criteria
- 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
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
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.
Governance
Who approves, reviews and stays accountable for outcomes?
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.
Security and privacy
What data, permissions and controls need testing?
Prohibits recording confidential meetings and sensitive data (SSNs, passwords, health details, immigration status, children's data); notes HIPAA use requires a BAA-backed service.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Guidance highlights transcription errors with accents, dialects and acronyms, so accessibility uses of AI notes still need human verification.
Procurement
What should contracts, pricing and exit terms secure?
A Claude Enterprise purchase does not by itself approve Claude for transcription; buyers should plan AI intake review alongside procurement.
Operating model
Which teams own the service once it runs?
Agency IT leads must work with their PIA officer; DoIT's AI Enablement team gates new transcription tools.
Publication history
- 2026-11-10Anthropic · Issue 1210 resources
Stable resource ID: maryland-doit-ai-transcription-governance-card-gemini-copilot-only-20261110