Customer communication audit trail: what regulators expect


Tuesday, Oct 27th 2026
The post title in large type next to a shield with a check mark in orange

A regulator, an auditor or a court asks the same question in different words: show me what this customer received, when, who approved it, and why this version. A customer communication audit trail answers that question from records, not from memory. For every communication that leaves the organisation it holds five things:

  1. The exact content the customer received, as rendered, on the channel it went out on, kept for the full retention period.
  2. The version of the template and the business rules that produced it.
  3. The customer data the rules were applied to, or a reference to it, so the variant can be explained.
  4. Who approved that version, and when.
  5. Evidence of delivery, or of the failure to deliver.

Few organisations can produce all five. The gap is usually the approval record, and the link between the archived document and the template version that made it.

What does a customer communication audit trail have to prove?

Three things, and they are different questions.

  • Content. That this customer received this text, with this clause, on this date. A PDF in an archive proves the first part. It does not prove the clause was the approved one at the time.
  • Control. That the text was approved by the right person before it was used, and that nobody changed it between approval and production. This is the part a regulator looks at when something has gone wrong.
  • Delivery. That the communication reached the customer, or that the organisation knows it did not and acted on that.

A trail that proves content but not control is a filing system. A trail that proves control but not delivery is a change log. Supervisors expect all three.

Which rules ask for it?

No single regulation says “keep an audit trail of customer communication”. The requirement is assembled from several that do, each from a different angle.

Rule What it asks What it means for the trail
GDPR, Article 5(2) The controller must be able to demonstrate compliance with the data principles Records of what personal data was used, for which communication, under which rule
GDPR, Article 12 Information to the data subject must be concise, transparent and accessible The privacy information that accompanies a communication must be reproducible for each version sent
Insurance Distribution Directive, Article 23 Information to customers is provided on paper or another durable medium A retrievable copy of exactly what the customer was given, accessible for as long as the information is relevant to the customer
DORA, Articles 28 and 30 Financial entities stay responsible for ICT services they outsource, with contractual access and audit rights If a provider produces the communication, the trail must still be available to you and to your supervisor

Sector rules add retention periods per document type, mandatory wording per product and deadlines for informing customers of specific events. The structure above is the same in every sector.

What should the trail record per communication?

The practical answer is a record with five fields, created at the moment of production, completed with the delivery status as it comes in, and not editable after that.

Field What it holds Where it usually lives
Rendered output The document or message exactly as sent, per channel Archive
Template and rule version Identifier and version of the template, the content blocks and the business rules applied Platform change history
Data snapshot The customer data the rules were applied to, or a reference to it Platform or source system
Approval record Who approved this version of the template and the rules, when, and what changed from the previous version Platform workflow, too often email
Delivery event Sent, delivered, bounced or rejected, with timestamp and channel Platform and channel providers

The fourth field is the one to check first. A customer communication operating model names an accountable owner per document family; the audit trail is where that ownership becomes evidence. If approvals live in email threads, the trail breaks at exactly the point a supervisor will test.

Where do audit trails usually fail?

In four places, and rarely in the archive itself.

  1. The template changed after approval. A text correction goes straight to production because the approval route takes a week. The archive shows the corrected letter; the approval record shows the previous one.
  2. The archive holds a PDF, not the inputs. The organisation can show what the customer received, but not which rule decided that this customer got this variant. The question “why did this customer get this clause” cannot be answered.
  3. Delivery is assumed. Print and mail went out, the email was sent, the SMS batch was handed to the provider. Nobody records that the provider rejected part of the batch, or who followed up.
  4. The trail stops at the channel boundary. The letter is archived. The portal message, the app notification and the SMS that pointed to it are not, so the same customer has three partial trails.

Each of these is a design problem, not a discipline problem. A platform that records the five fields at production time removes them.

Key takeaway: You should be able to show the exact communication a customer received, and the template version that produced it, even after someone has changed that template.

What changes when AI drafts the communication?

Nothing in the list above, and one thing in practice. When a prompt produces the draft of a template or a journey step, the approval record has to show that a named person reviewed the draft and approved it before it was used, and what that person saw. An AI-drafted change without an approval record is an unapproved change, and the trail should make that visible rather than hide it.

What changes when a provider runs the platform?

The responsibility does not move. Under DORA, a financial entity that outsources the production of customer communication keeps the obligation to demonstrate control, and the contract has to give it and its supervisor access to the records. In practice that means three things to settle before signing:

  1. The five fields above are produced by the provider and are yours, exportable in a usable format, for the full retention period.
  2. The approval workflow runs on your owners and your approvers, not the provider’s staff.
  3. Audit and access rights are written into the contract, including after it ends.

A managed service, Eclipse is one example, is set up to keep those records as part of normal production. In Eclipse you can retrieve the original document and the exact communication that was sent, to whom and when, together with the version of the template and scenario that produced it. If someone updates that template or scenario later, the original stays retrievable. The contract is still where the obligation lives, so read that part of it with the audit trail in mind.

How to test your own trail in an afternoon

  1. Pick one document family that carries mandatory text, such as a policy document or an annual statement.
  2. Take one customer and one date from the last year.
  3. Retrieve the rendered output, the template version, the approval record and the delivery event for that one communication.
  4. Time how long it took and count the people you had to ask.

If the answer came from one system in minutes, the trail works. If it came from three people and an email search, the gap is found before a supervisor finds it. The same test belongs in the inventory phase of a migration roadmap, because a platform move is when the old trail is most at risk.

Frequently asked questions

What is a customer communication audit trail?
The set of records that shows, for each communication sent to a customer, what was sent, which template and rules produced it, who approved that version, and whether it was delivered. It is kept for the retention period of the document and must be retrievable on request.

Is an archive of PDFs enough?
No. An archive proves what the customer received. It does not prove the content was approved, by whom, or why this customer received this variant. Those answers need the template version, the approval record and the data reference as well.

How long must customer communication be kept?
It depends on the document type and the sector. Retention periods come from the applicable financial, pension, tax and data protection rules, and the longest one that applies to a document family sets the period for that family. The platform should hold the period per family rather than one blanket setting.

Who is responsible for the audit trail when communication is outsourced?
The organisation that sends the communication. A provider can produce and store the records, but the obligation to demonstrate control, and to give the supervisor access to the records, stays with the regulated entity.


Related: CCM, CRM and marketing automation: who does what?

If your next audit will ask for one of these records and you are not sure which system holds it, we are glad to help you look.