Definition
An audit trail is the set of approval records attached to a piece of marketing work. The guide to marketing approvals and compliance reviews defines its contents: what was reviewed, which version, who reviewed it, when, what they decided and what evidence they relied on. Each of those fields does a job. The version ties the decision to the thing that went live rather than to an earlier draft; the reviewer and the date show that the right person looked at it in time; the evidence shows why a claim or a data use was accepted.
It is not the review itself. The approval matrix decides which reviews a piece of work needs; the audit trail proves that those reviews happened. A team can have an excellent matrix and no trail, in which case it follows its rules but cannot demonstrate that it does.
Where the trail lives
The approvals guide names the work management system as the natural home, because the record then sits next to the work and the final version. Approvals rarely arrive there on their own. They are given in email, in chat threads and in conversations, so the routine is to copy each one onto the item, and to set the workflow so that nothing reaches the launch check without its records.
The same rule holds wherever the work is made. The social media approval workflow puts the record in the calendar row or the scheduler's approval history, next to the post, and copies approvals given in a chat or a hallway onto the item. Its fast lane needs no record per reply, because the bank of pre-approved lines is itself the approval.
In practice: records that other routines rely on
A trail earns its keep when someone reads it. The tutorial on auditing marketing approvals samples recent live work and checks two things: that each item had the reviews the matrix required, and that the records exist and point at the right version. A complete record does not prove the work was right, only that the process ran, which is why anything that looks wrong goes back to the reviewer who owns that row.
Other controls keep the same kind of record. The access review tutorial records each change to who can use a tool, with the date, what was done, who did it and why, because that record is the evidence the review happened. The budget reallocation memo has an approval row for who approved a move, when, and which version of the budget sheet reflects it, so that at year end the approved memos explain the gap between the plan that was signed off and the money that was spent.
A pharmacy chain finds an approval that only existed in an inbox
Vorkirk Pharmacy, a chain of 14 shops, was asked by a local trading standards officer who had approved a health claim on a winter leaflet. The claim had been checked: the marketing manager had emailed the superintendent pharmacist, who replied "fine to go" on 3 October. But the reply sat in one inbox, it did not say which of the leaflet's 4 drafts it covered, and the printed version had a changed headline. Finding it took 2 days. The team then copied every approval onto the work item in its project board, with the version attached, and set the board so an item could not move to "ready to print" without a recorded sign-off. An approval audit 3 months later sampled 20 items and found complete records on 19.
Related terms
The Approval MatrixA table that says which reviews each type of marketing work needs, such as legal, brand or budget, and who gives each, matched to the risk of the work. sets which reviews each kind of work needs; the audit trail records that they happened. A Change LogA dated record of changes made to tracking, accounts, reports, lists or rules, with who made each and why, so later movements in the figures can be traced. records dated changes to tracking, accounts and reports, and a Decision LogA running record, one row per decision, of what changed and why, what was expected, who decided and when the result will be checked. records decisions and their reasoning; both are records of a different event. The Claims LibraryA record of every marketing claim in its exact approved wording, with the evidence behind it, the conditions and markets it is approved for and the approver. holds approved wording with its evidence, so a trail for work that uses only library claims can point to the library entry instead of a fresh legal review.
Common confusions
- An approval in an email is an audit trail. It is a record somewhere. Until it is attached to the work item, with the version it covers, nobody else can find it or tell what it approved.
- The audit trail and the change log are the same record. The change log explains why figures moved; the audit trail shows who approved a piece of work before it went live.
- A complete trail means the work was right. It shows the process ran. Whether the reviewer's judgement was sound is a separate question that the audit refers back to the reviewer.
- Only regulated work needs a trail. Any approval someone may later need to show, from a price claim to an access change or a budget move, is worth recording in the same way.
