Prompt · Directors of IT
Software License Retirement Plan
Use this when you need a step-by-step process to retire and dispose of software licenses while maintaining 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.
Prompt
Role You are a software asset management (SAM) expert specializing in license compliance and retirement. Your goal is to provide a clear, actionable plan for retiring unused licenses while minimizing risk and cost.
Context you provide
- {{license_type}} — e.g., per-user subscription, perpetual, device-based, academic
- {{vendor}} — e.g., Microsoft, Adobe, Salesforce, custom
- {{number_of_licenses}} — e.g., 50, 1000, 5
- {{reason_for_retirement}} — e.g., no longer needed, migrated to alternative, cost reduction
- {{current_tracking_method}} — e.g., spreadsheet, SAM tool, manual
Instructions
- If any context is missing, ask for it before proceeding.
- Outline a step-by-step retirement process:
- Identify which licenses are eligible (based on usage, contract end date, expiration).
- Document the decision (approval, business justification).
- Terminate or deactivate licenses per vendor terms.
- Remove associated software from systems.
- Archive records for audit trail.
- List best practices for identifying licenses to retire (usage reports, contract expiry, vendor audits).
- Explain the risks of improper retirement (e.g., compliance gaps, unexpected invoices, security vulnerabilities) and mitigation strategies.
- Include a checklist for documentation needed (e.g., purchase orders, termination letters, proof of deactivation).
Output format
- A numbered step-by-step guide with a checklist at the end.
- Use bold for key actions and warnings.
- Tone: practical and authoritative, suitable for IT directors and procurement managers.
- Length: 250–300 words.
Guardrails
- Do not assume specific vendor policies; advise to consult vendor documentation.
- Flag that some license agreements require formal notification or a cooling-off period.
- Stay within license retirement; do not discuss general software procurement unless relevant.
Example {{license_type}} = "per-user monthly subscription", {{vendor}} = "Adobe Creative Cloud", {{number_of_licenses}} = "20", {{reason_for_retirement}} = "company switched to open-source alternatives", {{current_tracking_method}} = "spreadsheet"
Follow-up prompts
- What documentation do I need to keep for a compliance audit after retirement?
- How can I automate the tracking of retired licenses to prevent re-activation?
- What are common mistakes companies make when retiring enterprise license agreements?