The 72-Hour Transcript
Everyone wanted AI meeting transcripts, and everyone feared them, the wrong details and the permanent discoverable record. The fix was to make the transcript delete itself in 72 hours, and to make downloading it the act that assigned responsibility, under company policy, for finalizing the record.
The facts behind Delete It by Default: a real meeting-transcript policy, and the two mechanisms that carried it.
What happened
AI meeting transcripts were wanted and feared for two tangled reasons: accuracy (a misheard number or “not” becomes a confident, wrong sentence) and retention (an imperfect transcript that sticks around forever is a permanent, discoverable record). At a company I worked with, we governed the tool rather than banning it, with two mechanisms.
- Auto-delete at 72 hours. Every AI transcript deleted itself on a timer unless someone acted, so an ephemeral draft could not harden into a permanent record. One hard exception, wired in from the start: a legal hold or a required regulated record always overrode the deletion and stopped the clock.
- Downloading assigns responsibility. The moment a person downloaded a transcript, that person owned the accuracy, cleaning, verification, and finalization into real minutes, under company policy. An internal accountability rule that named who was answerable, not a change to the legal nature of the information.
What it produced
The two mechanisms need each other. Auto-delete alone loses useful notes and drives screenshot-hoarding; an ownership rule alone leaves a swamp of half-verified transcripts nobody owns. Together, the record does not exist unless a named person reached out and took it, and the taking is the acceptance of responsibility. Attention was expanded during the meeting; accountability stayed intact after it.
Underneath sat a quieter decision: the tool was chosen by data tier. For confidential meetings, we used the tool that could restrict auto-sharing of the transcript to just the meeting owner; for the rest, either tool was fine. The AI feature was picked by the sensitivity of the data in the room, not by the incumbent vendor, which is the Permission pillar in one decision.
The conditions that made it work
- Enforced, not announced. The auto-delete was configured in the system on a timer; a rule people must remember to follow is a hope, not a mechanism.
- The number is a legal question. The 72 hours never overrides a duty to preserve (FRCP 37(e)) or an affirmative retention requirement; it was set with legal and records, not by convenience.
- Ownership only holds if the owner does the work. Downloading has to be followed by real cleaning and verification, or you have relabeled an unverified transcript as “minutes.”
The argument for governing AI output this way is in Delete It by Default.
How this was measured. This is a firsthand account of a policy design and its rationale from a single organization; its effects are described qualitatively, not measured, and the specifics are an operating example, not legal advice.
Cheers,
-Titus
Get it in your inbox.
New Issues, FAQs, and Case Studies as they go out. Each one names something, explains something, or hands you something you can use on Monday. Subscribe, and I will send each as it goes out.
Prefer the tool you already think in? Here is how to read it in your chatbot.