How to apply record retention schedules with an AI agent

Retention work splits cleanly: the agent works out what is due; a person decides what goes. It classifies records against the retention schedule, calculates each end date from the right trigger, checks for legal holds, complaints and investigations, and drafts a disposal list. A named records owner approves it. Deletion cannot be undone, so it is depth 4 work.

What does applying a retention schedule involve, and who owns it?

A retention schedule says how long each class of record must be kept and from what point the clock runs: account opening documents for a set period after the relationship ends, call recordings for a set period after the call, transaction records after the transaction date. Applying it means finding every record in every system, putting each in the right class, working out its end date, and disposing of it when the date passes unless something requires it to be kept.

Data protection law pulls one way: GDPR Article 5 includes the principle that personal data should be kept no longer than needed. Other duties pull the other way, such as AML record-keeping, litigation and regulatory inquiries. The records management or data protection team usually owns the schedule. System owners own the data. Legal owns holds. The agent sits between them, doing the matching that rarely gets done by hand.

What does the agent prepare, and what does a person approve?

1. Agent, depth 1: inventories records. By system and record type, with the dates that matter for each.
2. Agent, depth 1: classifies them. Against the schedule's record classes. Records that do not fit a class cleanly are listed for a person.
3. Agent, depth 1: finds the trigger date. The end of the customer relationship, the date of the transaction, the date a complaint closed. The trigger is often the hardest part.
4. Agent, depth 1: calculates end dates.
5. Agent, depth 1: checks for holds. Legal holds, open complaints, regulatory requests, ongoing investigations, and records linked to suspicious activity reports, which are handled under their own rules.
6. Agent, depth 2: drafts the disposal list. Records past their end date with no hold, by class and system, with the rule applied to each.
7. Person, records owner: approves. Reviews the list, samples records, and approves or removes items.
8. Person: executes or releases disposal. Deletion is depth 4. Where the system supports it, the agent can prepare the deletion job; a person releases it.
9. Agent, depth 2: drafts the disposal record. What was deleted, when, under which rule, approved by whom.

Which controls apply, and what evidence do they leave?

Hold check from every source. Legal, complaints, regulatory and financial crime each keep their own lists. The agent checks all of them for every record on the list. Evidence: the hold check result per record, naming the lists checked.

Rule shown per record. Each item on the disposal list shows its class, trigger, period and end date. A reviewer can check the arithmetic.

Sampling before approval. The approver opens a sample of records to confirm they are what the list says. Evidence: the sample and its results.

No deletion capability. The agent's role cannot delete. Whether an agent can delete data when retention periods end is answered with a held action: prepared by the agent, released by a person. Any deletion attempt by the agent is refused and filed.

Disposal record kept. The record of what was destroyed is itself kept, so you can answer later questions without the data.

The retention periods themselves usually sit alongside the firm's record of processing activities under GDPR Article 30, and whether an agent can maintain a record of processing activities is a closely related job.

Where does it usually go wrong?

Wrong trigger. The clock should start when the relationship ended, but the system only holds the date of the last transaction. Records are deleted early or kept too long. Agree the trigger for each class before the agent applies it.

Copies left behind. The master record goes, and copies remain in reporting databases, email and shared drives. The inventory must include where copies live.

Holds missed. A complaint was closed but a related legal claim is still open. Linking records to cases is where the agent helps most, and where errors hurt most.

Over-retention by default. Fear of deleting the wrong thing leads to keeping everything. That is a breach of the storage limitation principle in its own right. The disposal list should run on schedule, not wait for a quiet month.

Compliance records with their own rules. AML case records, including alert dispositions filed using the AML alert disposition record template, carry periods set by AML duties and must not be swept up with general customer data.

What should you measure?

• Records past their end date and not disposed of, by class.
• Items removed from disposal lists by approvers, and why.
• Records deleted that were later needed. Should be none; review every case.
• Unclassified records. Shows where the schedule does not fit reality.
• Time from end date to disposal.

Broader limits on compliance agents are in AI compliance agents.