A Released Meeting Recording Points to the Wrong Retention Schedule: Correct the Disposal Clock

Stop the disposal path when a released recording appears under a schedule that belongs to another artifact. The immediate job is to establish which service governs the recording. Then establish the item's policy and trigger date.

A recording can have related files with different retention treatment. Google says Meet recordings are governed by Drive retention rules by default, unless dedicated Meet retention is enabled. Google also says copies downloaded and uploaded to Drive are subject to Drive retention rules. Google Workspace updated that guidance on October 23, 2026.

• Pause deletion and any scheduled disposition action for the identified recording.
• Preserve the recording hash and immutable item ID. Preserve the storage location and owner. Also preserve the release event and observed schedule or policy ID.
• Confirm the authoritative service binding and policy scope before changing a clock.

Which retention schedule governs the released recording?

The governing schedule is the rule that applies to the specific recording in its authoritative service and location, subject to any applicable hold. It is not automatically the schedule displayed beside a related transcript, chat, exported copy, or case attachment.

For Google Workspace, Meet retention can be managed separately only after dedicated Meet retention is activated. Without that setting, Meet recordings are retained under Drive rules. Google warns that incorrectly configured retention rules can allow immediate and irreversible cleanup, so validate the target rule on a small scope before broad changes.

For Microsoft 365, policy scope and artifact location also matter. Microsoft says Teams meeting recordings and transcripts from user chats require a retention policy that includes the organizer's OneDrive account. A Teams message policy does not automatically cover files used with Teams.

How do you prove the authoritative binding?

Build the reassociation ledger from system evidence, not labels copied into a release note. Capture the recording hash first. Then retrieve the item metadata and storage location. Retrieve the policy assignment and rule scope, along with the trigger event and any hold reference.

Compare the observed schedule with the rule that actually reaches the original recording. If the item was copied or otherwise placed elsewhere, including through an export or upload, create a separate ledger row for each derivative. A derivative can have a different location and policy path.

Google states that default retention rules apply only where a custom rule or hold does not apply. Its retention guidance also says holds take priority over retention rules. Microsoft similarly distinguishes policies that apply at a container level from retention labels that apply at an item level.

• Check the original recording before checking release packages or exported copies.
• Verify whether a custom rule, default rule, label, or hold applies.
• Record the rule's retention period and its start event exactly as configured.
• Ask the policy owner to approve the authoritative binding when the evidence conflicts.

Which clocks must be recalculated after reassociation?

Recalculate each deadline from the authoritative rule's configured trigger. Google identifies creation date and modification date as possible retention starts for Drive and Meet, depending on configuration. Move-to-trash date and a Drive label date field can also be possible retention starts. Do not reuse the previous schedule's trigger date without verifying it.

The corrected deletion date is only one output. Recalculate the legal-hold status and access-review date. Also recalculate the derivative review date and disposition-review date where used, plus any release or destruction workflow deadline tied to the old assignment.

Keep the old and corrected clocks side by side in the ledger. That makes the change reviewable and exposes whether an old deadline is earlier than the corrected one.

• Authoritative trigger date and retention period
• Corrected deletion or disposition eligibility date
• Active legal-hold status and hold-release dependency
• Access and sharing review deadline for the released recording
• Derivative inventory and review deadline for every derivative

What changes when a legal hold applies?

A legal hold blocks ordinary disposal while it remains applicable. Google says holds take priority over retention rules and that data becomes subject to applicable rules immediately after a hold is removed. Do not recalculate a hold into a deletion date. Record the hold separately, including its matter reference and scope. Also record the custodian or location and release authority.

Microsoft says permanent deletion of Teams content is suspended when an applicable retention policy, litigation hold, delay hold, or eDiscovery hold affects the mailbox. Content may no longer be visible in the Teams app while remaining discoverable through eDiscovery.

The practical control is simple: retain the corrected clock, but block execution until the hold owner formally confirms release. The policy owner and legal owner may be different people.

How should copies and released derivatives be handled?

Treat every released derivative as its own record until system evidence proves it inherits the same rule. A recording file or transcript can be stored in different places with different policy coverage. The same is true of a chat export, local download, Drive upload, or release package.

Google specifically distinguishes original Meet recordings and associated meeting artifacts from copies downloaded and uploaded to Drive. The original and the copy should therefore be separately identified in the reassociation ledger.

For media that reaches end of life, disposal needs an approved sanitization method appropriate to the information and media. NIST SP 800-88 Rev. 2 describes media sanitization as rendering access to target data infeasible for a given level of effort and frames it as part of a sanitization program.

What should the approver sign off before disposal resumes?

The approver should sign off on the recording identity and authoritative schedule and policy IDs. The approver should also sign off on rule scope and trigger date, then on the corrected clock and hold status, derivative inventory, and disposal method. A vague approval such as "schedule corrected" leaves the actual disposal decision untestable.

Keep the approval attached to the ledger and change record. The record should show who made the reassociation and what evidence they used. It should also show when they checked it and which workflow was released or kept paused.

A recording must not resume disposal because a schedule field was edited. Resume only after the ledger shows the new authoritative binding and every affected deadline has been reviewed.