Purpose of the Template
Your records retention schedule specifies when to dispose of records. This checklist guides your team on how to do it, avoiding common pitfalls: ghosting (ignoring files), clinging (keeping copies "just in case"), and guilt-keeping (feeling deletion is disrespectful).
Use this template to create a disposition workflow that reflects real-world behaviors when someone hesitates over the delete button at the end of the day. It's meant for official records that have reached their retention period, not for temporary content or ROT, which can usually be deleted at your discretion.
Prerequisites
Before using this checklist, ensure you have:
- A current Records Control Schedule with specific retention triggers
- Legal hold monitoring to confirm if a record series is frozen
- Defined sign-off authority for each record category (records owner, legal counsel, or designated approver)
- A certificate of destruction process that logs what was disposed of, when, and by whom
If your retention schedule uses vague phrases like "retain as long as needed," revise it first. Ambiguity leads to ghosting.
The Disposition Checklist Template
Copy this template into your records management system, matter-closing workflow, or shared-drive cleanup protocol. Each section targets a specific behavior.
DISPOSITION READINESS CHECKLIST
Record Series: ___________________________
Retention Period: ___________________________
Cutoff Date: ___________________________
Disposition Eligible Date: ___________________________
Step 1: Verify Eligibility (Prevents Ghosting)
☐ Retention period has elapsed based on the Records Control Schedule
☐ All regulatory or contractual obligations have concluded
☐ No active legal hold, litigation, audit, or investigation involves this record series
☐ Records owner confirms the business purpose no longer exists
If any box is unchecked, STOP. This record is not eligible for disposition.
Step 2: Confirm Location (Prevents Clinging)
☐ Official record is in the designated system of record (name system: _______________)
☐ All convenience copies, duplicates, and personal-drive versions identified
☐ Convenience copies will be deleted with the official record
Why this matters: You can't defensibly dispose of what you can't find. Extra copies increase your discoverable footprint and create legal hold risks.
Step 3: Obtain Approval (Prevents Guilt-Keeping)
☐ Records owner or designated approver has reviewed this disposition request
☐ Approver confirms: "Disposition of this record does not erase the work. It honors the retention schedule and reduces organizational risk."
☐ Approval documented with name, date, and role: ___________________________
Script for approvers: "This work was completed and delivered. The record served its purpose. Keeping it past the retention period doesn't honor the effort, it creates privacy exposure and over-retention risk. You have permission to let it go."
Step 4: Execute Disposition
☐ Disposition method matches Records Control Schedule requirements (deletion, transfer to archives, physical destruction)
☐ All identified copies disposed of using the same method
☐ Disposition date: ___________________________
Step 5: Document
☐ Certificate of destruction completed with:
- Record series name and retention category
- Volume or count disposed of
- Disposition method
- Approver name and signature
- Date
☐ Certificate filed in disposition log (location: _______________)
Retention period for certificate: Permanent or per your organization's disposition-documentation policy.
Customization Tips
For project-based records: Add a matter-closing trigger to Step 1. Replace "Cutoff Date" with "Matter Close Date" and require project managers to start the checklist within 30 days of project completion. This prevents files from lingering unclassified.
For departments prone to clinging: Expand Step 2. Require quarterly audits of personal drives and email folders, with a report on how many convenience copies were found and deleted. Make this metric visible. When teams see that 40% of their stored data is duplicates, the system of record becomes more trustworthy.
For organizations with guilt-keeping issues: Strengthen Step 3. Require a conversation, not just approval. Schedule quarterly disposition review meetings where managers explicitly say, "You can delete this. I'm telling you to." Personal permission beats a policy buried in a handbook.
For high-volume environments: Automate Steps 1 and 4 where possible. Use retention triggers that calculate eligibility dates automatically and flag records for review. Create one-click disposition workflows that handle Steps 1-4, with human approval required but the legwork automated.
For regulated industries: Add a pre-disposition legal review to Step 3 for record categories with heightened regulatory scrutiny (financial records, clinical data, HR files). Require legal counsel to confirm no pending or anticipated litigation affects the series.
Validation Steps
After deploying this checklist, measure its impact:
Quarterly metrics to track:
- Percentage of records disposed of on schedule
- Volume of ROT identified and removed from shared drives
- Number of convenience copies found during legal hold execution
- Employee feedback: "I didn't dispose of this record because..." (track the reasons to identify which behavior is prevalent)
Annual audit questions:
- Can you produce a complete disposition log for the past 12 months?
- Do certificates of destruction include all required fields?
- Are approvers genuinely reviewing, or just rubber-stamping?
- Is the checklist being used, or is disposition still ad hoc?
If your disposition rate hasn't improved six months after implementing this checklist, the issue isn't the template. It's that your team hasn't been given the time, permission, or deadline to use it. Schedule cleanup days. Celebrate teams that meet disposition targets. Make defensible disposition the celebrated move, not the risky one.
Final validation step: Pull a random sample of records that should have been disposed of last year. If they're still there, ask the record owner why. The answer will reveal which section of the checklist needs reinforcement.
