Use caseRecords management
The retention schedule was approved years ago. Nothing has been deleted since: nobody can tell which loan files expired, or which a lawyer needs.
Each document carries its class, its trigger and its end dateA legal hold suspends the planned action, alwaysEach deletion batch is approved by people and logged
4,820 documents in 612 loan files are proposed for deletion under schedule v3, after 67 were set aside.
source · retention rules on 5 document classesPeriod over, no hold · the privacy officer approves the batch
Ask Greg Lawson, the records manager, how long a loan file is kept and he answers in a second: five years after the loan ends. Ask which files passed that date this month and he cannot say. The schedule sits in a policy document, the documents sit in the repository, and nothing connects the two. Under GLBA, the FTC Safeguards Rule expects lenders to dispose of customer data they no longer need, and state privacy laws push the same way.
The period belongs on the document. Each class carries its rule, each document gets its end date when the event that starts its clock arrives, and the retention rule triggers a review workflow. People approve every batch, legal holds always win, and every deletion is logged.
The loan file and the November count are one rule seen from two sides: the period is set when the loan ends, the expired documents come up once a month, and nothing is deleted until the owner and the privacy officer have signed. What follows sets the clocks once, then runs the November review to its last signature.
A period means nothing until it sits on a document, tied to the event that starts it. This groundwork is done once.
Greg Lawson, the records manager, enters the company's retention schedule as rules on the document classes in the repository. Each class gets a period, the event that starts it and the action at the end. The periods are the ones the privacy officer and legal approved.
12,300 older documents have no class, mostly scans filed before 2019. The AI reads each one and proposes a class and its retention period, with a confidence level. Proposals above the threshold are accepted by Greg in batches, after he checks a sample. The rest he classifies one by one.
Most periods start at an event the repository does not see: the end of a loan. The loan system calls the repository API when the last installment is paid. For loan PRT-2019-44817, closed on Mar 31, 2021, every document in the file gets its end date: Mar 31, 2026.
A document whose trigger event never arrives is never proposed for deletion. It shows up in a separate list for Greg to follow up.
On the first Monday of each month, the retention rules list what has expired. People read that list before anything else happens.
On the first Monday of the month, the retention rules open the November review. It proposes 4,820 documents in 612 loan files whose period has ended. Before anyone reads the list, documents under a legal hold and documents tied to an open complaint are already set aside.
Nine of the expired files belong to borrowers in a class action over credit insurance. Sarah Lindgren, legal counsel, placed a hold on them in June with the court reference. As long as the hold is active, the files stay, whatever their end date says.
Anthony Russo, head of loan servicing, checks the list for his team. He asks to keep one file six more months: the customer has just reopened a loan on the same contract number. He writes the reason. Then Monica Hayes, the privacy officer, approves the batch and the exception.
The batch is approved. The deletion runs, and the log keeps a sealed record of what is gone.
On Nov 8 the review reaches its last step and the 4,802 approved documents are securely deleted. The 18 documents kept by exception and the 67 set aside are untouched. The deletion is processed as one cohort, and the service stays online for the teams.
Every action of the review is timestamped and sealed with a chained hash: the listing, the holds, the approvals, the deletion. The entry names each document by its identifier, class and end date, with no customer name and no content. Greg exports the log as it is for the records archive.
In February the court closes the class action. Sarah lifts hold LH-2026-007 and records the date of the final decision. The nine files have long passed their end date, so they appear in the March review with a note that they come from a lifted hold, and go through the same approvals.
A passed end date only opens the question. Each expired document gets one of three answers, and the answer decides who signs next.
The end date has passed, there is no hold and no open complaint.
After that: the owner reviews, the privacy officer approves, the batch is securely deleted.A new loan on the same contract, a pending collection. The owner writes the reason.
After that: the privacy officer decides, and the new end date is set on the document.A legal hold or an open complaint suspends the planned action.
After that: the file waits until legal lifts the hold, then rejoins the review.It sets no period, deletes nothing and lifts no hold. The periods come from the approved schedule, and Anthony and Monica signed the November batch before a single file went.
The AI proposes a class for the 12,300 scans that had none. The rules on each class do the rest, month after month.
Counted on the November 2026 review under schedule v3. Your counts will follow your own classes, and how long nothing has been deleted.
Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.
A deletion batch needs three nods: records, compliance and IT. Each one checks the batch for a different reason.
The schedule exists, and nothing in the repository knows about it.
You are asked to approve deletions you cannot see, or to keep everything just in case.
Retention projects end up as a script nobody dares to run.
With one class. Take the declined applications, which have the shortest period and the clearest trigger, and run one review on them. The first list shows how much you are keeping without a reason.
The loan system, the repository and the approved schedule stay as they are. The retention rules connect them.
Your move
Send us your retention schedule and a sample of one document class. We will show your records manager and your privacy officer the first review on that sample.