An answering service keeps every recording because storage is cheap. Two years later a client asks for a call from last month and the team cannot find it among thousands of files, or a caller asks for deletion and no one knows which recordings contain their voice.

A retention review makes the choice deliberate. This method note describes what to decide, how to apply the decision, and what the policy cannot prove.

Start with the client agreement

The retention period should come from the client agreement and applicable law, not from the storage plan. Record the agreed period and the date it was set.

Where clients differ, keep the periods separately. A single default applied to every client will be too long for some and too short for others, and the difference matters when a dispute arises.

Separate the purposes

Recordings are kept for quality review, dispute evidence, and training. Each purpose has a different retention need, and a single period rarely fits all three.

Decide which recordings support which purpose and retain accordingly. A quality sample does not need to be kept for years, while a disputed call may need to be preserved beyond the normal period.

Limit access

Access should be limited to the people who need it, with a named role and a logged reason. A shared folder with every recording is a privacy risk and a weak control.

Review access quarterly. People change roles, and an access list that is never reviewed slowly includes people who no longer need it.

Handle deletion requests

A caller may ask for a recording to be deleted. The process should record the request, confirm the scope, and apply the client's policy and legal obligations.

Do not delete a recording that is subject to a dispute or a legal hold. The request should be paused and the reason recorded, with the client informed.

What the policy can show

The policy can show that the team made a decision and applied it. It can show the period, the owner, the access rules, and the deletion log.

Those facts support a review. A client who asks how recordings are handled can receive a clear answer rather than a description of the storage plan.

What the policy cannot show

The policy cannot show that recordings are stored securely. That needs a technical review of encryption, access, and backups.

It cannot show that the team follows the policy. A deletion log with no entries may mean nothing was deleted, or it may mean the process was never run.

It also cannot prove compliance with every legal requirement. The policy should be reviewed with the client's counsel where the obligations are unclear.

Storage and security

Recordings should be encrypted, access-controlled, and backed up. A retention policy that ignores storage security keeps the recordings but not the trust.

Review who can export recordings and where exports are stored. An export to a personal device bypasses the policy entirely.

When a dispute or investigation is known, pause deletion for the relevant recordings and record the hold. The hold should name the scope and the person who can release it.

A legal hold that is applied to the whole archive is expensive and hard to explain. Narrow the scope to the calls involved and keep the reason with the record.

Quality samples

Keep a small set of recordings for training and quality review beyond the normal period, with identifying detail removed where possible. The sample should be chosen for its teaching value.

Record the sample size and the review dates. A sample that is never reviewed is just a longer retention period with a different label.

Client communication

Tell clients how recordings are retained, who can listen, and how deletion works. A short section in the service agreement prevents most disputes later.

Provide the policy summary when it changes. A client who learns about a retention change during an audit will assume the worst.

Deletion log

Keep a log of deletions: the date, the scope, the reason, and the approver. The log is the evidence that the policy was applied.

Review the log quarterly for gaps. A long period with no deletions may mean the policy is not running, not that nothing has expired.

Retention and backups

A backup is not a retention policy. Backups may keep a deleted recording for longer than the policy allows, and the retention review should cover them.

Ask the provider how deletions propagate to backups and how long that takes. Record the answer, because it is the part most policies overlook.

Training the team

Train the team on what may be shared, what must be escalated, and how to record a request. A policy that only the manager understands will be applied inconsistently.

Review the training annually and after a change in the policy. Record who attended and when.

A worked example

A client asks for a call from six weeks ago. The retention period is ninety days, so the recording should exist. The team finds it, exports it to the client's secure portal, and logs the access.

A second client asks for a call from seven months ago. The recording has been deleted under the policy, and the deletion log shows the date and approver. The team explains the policy and provides the call note instead.

Methodology and limits

This note is an operating design informed by public guidance on privacy, records management, and security. It does not report an empirical study or provide legal advice.

The fields were tested against common cases: a quality review sample, a disputed call, a caller deletion request, and a client that changes providers. The design keeps those cases distinguishable.

Review the policy annually

Review the period, the access list, and the deletion process once a year, and after any significant change in the client base or the law.

Record the review date and the changes made. An annual review that leaves no trace is indistinguishable from no review at all.

Conclusion

A retention review turns an inherited default into a deliberate decision. It shows what is kept, for how long, and who may listen. It does not prove security or compliance on its own, but it makes the questions answerable and the practice consistent.