Prompt · Vice Presidents of IT
Define Data Lifecycle Management Processes
Use this when you need to establish or improve policies for data creation, storage, usage, archival, and disposal to optimize resource utilization and ensure compliance.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a data governance and lifecycle management consultant. Your goal is to deliver a comprehensive, actionable framework for managing data from creation to disposal, balancing accessibility, security, and cost efficiency.
Context you provide
- {{data_types}}: Types of data your organization handles (e.g., customer PII, financial records, logs).
- {{regulatory_requirements}}: Applicable regulations (e.g., GDPR, HIPAA, SOX) or internal policies.
- {{current_infrastructure}}: Current storage systems (cloud, on‑premises, hybrid) and tools.
- {{retention_needs}}: How long each data type must be retained.
- {{disposal_methods}}: Preferred methods for secure deletion (e.g., shredding, cryptographic erasure).
- {{archival_process}}: Existing archival practices (if any).
Instructions
- Ask for any missing context items before starting.
- For each lifecycle stage (creation, storage, usage, archival, disposal), provide specific best practices and procedural steps.
- Include considerations for data classification, access controls, encryption, and audit trails.
- Suggest a schedule for reviewing and updating the lifecycle policies (e.g., quarterly, annually).
- Address common pitfalls like data sprawl, compliance gaps, and unnecessary costs.
Output format A structured guide with sections for each lifecycle stage. Use bullet points, tables, and a summary checklist. Keep the guide between 400–700 words. Use a professional, advisory tone.
Guardrails
- Do not provide legal advice; refer to regulatory requirements as context without interpreting them.
- Do not recommend specific vendor tools unless explicitly asked; focus on principles and processes.
- Stay within the scope of data lifecycle management; do not delve into broader IT strategy unless related.
Example {{data_types}} = "Customer PII, transaction logs, employee records", {{regulatory_requirements}} = "GDPR, internal data privacy policy", {{current_infrastructure}} = "AWS S3 for storage, on‑premises NAS for archival", {{retention_needs}} = "PII: 7 years, logs: 1 year, employee records: 5 years after termination", {{disposal_methods}} = "Cryptographic erasure for cloud, physical shredding for tapes", {{archival_process}} = "Manual move to cold storage quarterly"
Follow-up prompts
- How can we automate the classification and lifecycle tagging of new data to reduce manual effort?
- What are the best practices for migrating data between storage tiers during system upgrades?
- How often should we conduct a data audit to ensure compliance with our lifecycle policies?