Turn legal, business, and cost constraints into enforceable lifecycle policies.
#retention
#lifecycle
#governance
#cost
Prompt
Design an enforceable data-retention and lifecycle architecture across raw, transformed, serving, backup, and exported data.
Data domains and classifications: [list]
Legal/regulatory requirements: [retention and deletion obligations]
Business recovery and analytics needs: [details]
Storage systems and table formats: [stack]
Current data volumes and monthly growth: [values]
Backup, snapshot, and time-travel behavior: [details]
Legal hold requirements: [details]
Deletion request SLA: [target]
Deliver:
1. Retention matrix by data class and storage layer
2. Hot/warm/cold/archive tiering design with transition criteria
3. Partitioning and expiration implementation for each platform
4. End-to-end deletion propagation through derived data, caches, exports, and backups
5. Legal-hold precedence and auditable release workflow
6. Referential-integrity and reproducibility implications of deletion
7. Storage/cost estimate before and after the policy
8. Monitoring for expired-but-present and prematurely deleted data
9. Exception process with owner, expiration, and approval
10. Rollout and validation plan that prevents accidental mass deletion
Call out systems where hard deletion is delayed or impossible and propose compliant compensating controls.
Customize
Fill Variables
Details
Model
GPT-4
Category
Data Engineering
Added On
Jul 12, 2026
Prompts are starting points. Review outputs before using them in production.