Data Retention Schedule & Defensible Deletion Plan
N.B. If you use specific competitor names for displacement plays, set [Competitors] to include 2–3 vendors you most frequently face to refine the outreach angle.
📄 Prompt Template
Create a cross-jurisdictional data retention schedule aligned to [Regulation] and business needs for [DataCategory] data stored in [System]. Map legal/regulatory minima/maxima, business utility, and litigation hold considerations, then recommend defensible deletion triggers.
Output format:
Assumptions and scope (bulleted).
Markdown table RetentionSchedule with columns: Data Category, System/Repo, Authoritative Source, Retention Period, Trigger (Start/Stop), Disposition Method, Exceptions/Litigation Hold, Control Owner.
Deletion workflow (numbered steps) with controls and evidence to be retained.
12-week rollout plan with milestones for [Timeframe].
Quantify storage and risk reduction benefits where possible.