Field notes
Mapping complaint evidence trails
When a consumer protection audit stalls, it is rarely because the team lacks opinions. It stalls because nobody can show which policy version governed a refund decision on a Tuesday three months ago.
Start with a single spine
Pick one identifier that every artifact must carry: usually the ticket ID. Call recordings, chat transcripts, fee tables, and push notification templates should reference that ID in a shared index—even if the files live in different systems. Without a spine, reviewers invent timelines from memory.
Version the rules people actually used
Policy PDFs with “current” in the filename are not evidence. Export the version effective on the complaint date, or capture a screenshot of the intranet page with a visible timestamp. In our Intensive Module 2 inventory, teams list where versions live before they open samples.
Separate narrative from artifact
Analysts love to summarize. Auditors need the raw note plus the summary. Keep both: a short finding sentence and a link or attachment that another reviewer can open without asking for a Slack thread.
Close the trail
When remediation lands, attach the change ticket and the re-test sample to the original complaint spine. That is how next quarter’s audit avoids rediscovering the same gap with new adjectives.