Use caseRecords management

Retention applied to every file

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

Actions on this review
The reviewExpired this month

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 classes
Each expired document

Period over, no hold · the privacy officer approves the batch

01

The problem

In a nutshell

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.

Loan file PRT-2019-44817Repository
Expired since March. The class, the trigger and the end date are fields on loan file PRT-2019-44817.
Disposition review, Nov 2026Case management
This month's count. What expired, what was set aside before anyone read the list, and how many signatures still stand in the way.

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.

02

The clock

A period means nothing until it sits on a document, tied to the event that starts it. This groundwork is done once.

Step 1Admin

The schedule becomes rules on the document classes

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.

Retention scheduleRepository
Periods shown are the company's own schedule, used here as an example.
The schedule stops being a documentIt is part of the content model. A new class created tomorrow gets its rule at the same time.
Step 2AI check

Documents without a class get a proposal

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.

11,050 above the threshold1,250 to classify by hand
Classification reviewAI console
A threshold decides what goes to a person. Greg sets it, and can change it.
No document stays without a periodThe old scans join the schedule like the rest, and a person checks the ones the AI is unsure about.
Step 3Intake

The event that starts the clock arrives through the API

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.

One number to look up this week: how many documents in your repository could you give an end date for, if someone asked?
The period starts on the right dayThe date comes from the loan system itself. Nobody keys it in, and nobody guesses it.
03

The review

On the first Monday of each month, the retention rules list what has expired. People read that list before anything else happens.

Step 4Workflow

The monthly review lists what has expired

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.

Disposition review, Nov 2026Case management
The review is a workflow, with its tasks and its approvals.
Expired documents come up by themselvesNobody has to go looking for them. The list arrives every month, by class, with the reasons for what was held back.
Step 5Case

A legal hold suspends the planned action

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.

Legal hold LH-2026-007Case management
Only legal counsel can place or lift a hold. Each one is reviewed every six months.
A hold always winsThe file a lawyer needs is never in the batch. It is set aside before anyone reads the list.
Step 6Workflow

The business owner and the privacy officer approve

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.

Approvals, Nov reviewCase management
The approvals are stored with the review, in the order they were given.
Two signatures before anything goesThe business confirms it no longer needs the files, the privacy officer confirms the batch. Each signature is on the review.
More on thisContent governance
04

The deletion

The batch is approved. The deletion runs, and the log keeps a sealed record of what is gone.

Step 7Workflow

The secure deletion runs on the approved batch

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.

4,802 deleted18 kept by exception67 set aside
Disposition review, Nov 2026Case management
Each stage is a workflow task with its owner and its date.
Only what was approved is deletedThe batch that runs is the batch that was signed, minus every exception and every hold.
Step 8History

Each deletion leaves a sealed entry in the log

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.

Retention logCase management
The log says what was deleted without keeping what it contained.
The proof survives the documentsWhen a customer, an auditor or a regulator asks, the answer is in the log, each entry sealed to the one before it.
Step 9Case

The hold is lifted, the files rejoin the schedule

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.

Legal holdsCase management
A lifted hold sends its files back to the normal review. Nothing is deleted in the same move.
Lifting a hold deletes nothingThe files return to the schedule, and the next review asks the same people the same question.
More on thisContent governance
05

The possible results

A passed end date only opens the question. Each expired document gets one of three answers, and the answer decides who signs next.

Delete

Period over, nothing holds it

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.
Extend

An owner still needs it

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.
Set aside

A hold or a complaint

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.
What stays with people

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.

06

What it saves

Counted on the November 2026 review under schedule v3. Your counts will follow your own classes, and how long nothing has been deleted.

0 dateskeyed in by hand. The loan system sends the event, the end date follows.
2 signaturesbefore any deletion, the business owner's and the privacy officer's, stored with the review.
0 filesunder hold deleted. Holds and open complaints are set aside before the list is read.

Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.

The rules behind the gains

Zero stale dataProductivityExpired documents come up every month on their own. Nobody has to go looking.
Zero lost proofsProcess reliabilityEvery step of the review is timestamped and sealed in a log that exports as it is.
Decision supportA person decidesThe AI proposes classes. The schedule, the approvals and the holds stay with people.
07

Who uses it

A deletion batch needs three nods: records, compliance and IT. Each one checks the batch for a different reason.

Records and administration

Records managers

The schedule exists, and nothing in the repository knows about it.

  • Each class carries its period, trigger and end action.
  • Old documents without a class get a proposal.
  • The expired list comes up every month.
  • The log exports as it is for the records archive.
Risk and compliance

Privacy officers and legal counsel

You are asked to approve deletions you cannot see, or to keep everything just in case.

  • Every batch waits for your approval.
  • A legal hold suspends the action, whatever the date.
  • Exceptions carry a reason and a new end date.
  • Every action is sealed with a chained hash.
IT and architecture

CIOs and architects

Retention projects end up as a script nobody dares to run.

  • The loan system sends its events through the API.
  • Retention rules are part of the content model.
  • Deletion runs as a workflow step, by cohort, service online.
  • Deployed in your own data center or in the cloud.

Your first move

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

Load your schedule and see what has expired

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.

The screens on this page are drawn to show one step at a time, with example data.

Uxopian Software helps organizations put AI to work across the systems they already run, without giving up control of their data, their infrastructure or their critical processes.