Tool Gate · How it works
How the Retention Purge Scheduler gate works
How the Retention Purge Scheduler rolls a register of record classes up worst-first: a class under a legal or regulatory hold is suppressed from the purge no matter how far past its retention date — the hold always beats the calendar — while a single class past its purge-due date puts the whole register in PURGE BACKLOG.
How the gate works
This tool grades every record class's purge-due date against a pinned evaluation date, then rolls the register up to whether anything is overdue. It reads 5 classes and rolls them into one verdict — the worst, never the average — and then a gate that can only make it worse.
The 5 classes
| Class | Verdict |
|---|---|
| call recordings | WITHIN WINDOWdue 2027-03-01 · 229 days left |
| chat transcripts | PURGE DUEdue 2026-07-09 · 6 days past, inside the 30-day grace |
| lead exportsfix first | PURGE OVERDUEdue 2026-03-30 · 107 days past, outside grace |
| disputed-account PII | LEGAL HOLD530 days past but under hold · suppressed from the schedule |
| appointment logs | WITHIN WINDOWdue 2026-09-29 · 76 days left |
The verdict bands
A record class under a litigation or regulatory hold is suppressed from the purge schedule no matter how far past its retention date — deleting held data is spoliation, so the hold always beats the calendar. Every other class rolls up worst-first: one class past its purge-due date puts the whole register in PURGE BACKLOG.
In the worked sample it reads PURGE BACKLOG — Two of the five classes are safely within their window and one is under legal hold — but two are past their purge-due date. Chat transcripts are 6 days past (still in the 30-day grace) and lead exports are 107 days past. One class past its date puts the register in PURGE BACKLOG. The most overdue class of all — disputed-account PII at 530 days — stays off the schedule entirely because it's under hold; deleting it would be spoliation. The one thing to fix first: lead exports — 107 days past its purge-due date and outside the grace window, the only class overdue rather than merely due. Purge it in the system that holds it first; chat transcripts are still inside grace..
Common questions
Can every class look survivable on the How the Retention Purge Scheduler gate works and the company still read PURGE BACKLOG?
Yes. The roll-up takes the worst of 5 classes — never the average — then a worsen-only gate, the Legal-hold override gate, escalates when trouble clusters. In the worked sample it reads PURGE BACKLOG because two of the five classes are safely within their window and one is under legal hold — but two are past their purge-due date. Chat transcripts are 6 days past (still in the 30-day grace) and lead exports are 107 days past. One class past its date puts the register in PURGE BACKLOG. The most overdue class of all — disputed-account PII at 530 days — stays off the schedule entirely because it's under hold; deleting it would be spoliation.
What is a worsen-only gate?
A dispositive rule that can only lower a verdict, never raise it. One fatal flaw overrides an otherwise-set of survivable lines, because a single disqualifying gap shouldn't hide behind an average of the healthy ones. The tool also names the one thing to fix first — here, "lead exports — 107 days past its purge-due date and outside the grace window, the only class overdue rather than merely due. Purge it in the system that holds it first; chat transcripts are still inside grace.".
Schedules purges from retention periods you supply as policy — it sets no retention periods, deletes nothing, and never schedules a legal-hold class. What to keep and for how long, and what's under hold, are legal questions; confirm them with counsel. It schedules records, not people. Not legal advice.
Embed this diagram
Free to share and embed with attribution (CC BY 4.0) — keep the link to redhub.ai.
Interactive — renders the live diagram
<iframe src="https://redhub.ai/visuals/tool/retention-purge-scheduler.html" title="How the Retention Purge Scheduler gate works — RedHub AI" width="760" height="1848" loading="lazy" style="border:0;width:100%;max-width:760px"></iframe>
<p style="font:14px/1.5 system-ui,sans-serif"><a href="https://redhub.ai/visuals/tool/retention-purge-scheduler">How the Retention Purge Scheduler gate works</a> — by <a href="https://redhub.ai">RedHub AI</a>, the AI that tells you when to doubt it.</p>Image + link — a static picture for any blog
<a href="https://redhub.ai/visuals/tool/retention-purge-scheduler"><img src="https://redhub.ai/visuals/tool/retention-purge-scheduler-share.png" alt="Diagram of the Retention Purge Scheduler: record classes rolled up worst-first, a legal-hold suppression, and the register reading PURGE BACKLOG when one class is overdue." width="760" loading="lazy" style="max-width:100%;height:auto;border-radius:16px"></a>
<p style="font:14px/1.5 system-ui,sans-serif"><a href="https://redhub.ai">RedHub AI</a> — the AI that tells you when to doubt it.</p>
This is how Retention Purge Scheduler works. More diagrams in the Visual Field Guide.