A homepage may sound calm, a social account more assertive and a support reply more formal. I would not classify every difference as a mistake. Support should not necessarily sound like an advertising headline. The useful distinction is between adapting to context and contradicting the brand’s meaning.
Choose a small but representative sample
Rather than inspecting every file at once, I begin with frequently encountered touchpoints: the homepage opening, an offer page, several social posts, an email and a typical support response. I record the purpose and date of each item.
The sample should not consist only of the team’s favourite work. Ordinary production often reveals the actual system more clearly. If I assess an older campaign against a current guide, I note that difference. Ignoring historical context can create a misleading list of inconsistencies.
Read the material in three passes
First I examine meaning: who is prioritised, what is promised and which evidence is provided? Next I examine voice: forms of address, sentence length, humour and specialist language. Finally I review visual application, including typography, colour, imagery and hierarchy.
These passes should remain distinct. Matching colours cannot reconcile contradictory promises. Similar sentence structure cannot repair inaccurate product information. Reviewing brand voice separately from messaging architecture also helps assign the right correction to the right person.
Prioritise by the effect on the reader
Not every discrepancy deserves equal attention. A misleading promise should take priority over a minor spacing difference. I rank findings by their effect on a decision, frequency of exposure and dependencies involved in the correction.
If the same service appears under two names, decide which name should remain before editing individual files. Then update navigation, descriptions and associated assets together. Without a shared decision, local corrections can recreate the problem somewhere else.
Finish with examples the team can use
I want a before example, an after example and the reason for the change. “Be more consistent” is not an actionable instruction. A useful example shows which information moves to the beginning of a product description or why a phrase is removed from a support response.
I then set a modest review point. If the same issues recur, I examine templates, access to source files and the approval process before blaming attention to detail. A system that requires everybody to remember every rule is not yet providing enough practical support. The purpose of the audit is to make future decisions clearer, not merely produce a longer correction list.