Direct answer: write one Persona Source Card containing the creator's approved public name, promise, voice, visual cues, recurring motifs, public boundaries and active versions. Then inspect each approved touchpoint with a Surface Audit Row, mark exact matches, acceptable variations and contradictions, and fix the highest-severity mismatch first.
This Persona Consistency Checklist checks whether a public visitor encounters recognisable cues from one surface to the next. It does not score overall trust, plan shoots, decide identity exposure or write a fictional life story. The source card should reflect a persona the creator can sustain truthfully and comfortably.
For the separate question of whether a live profile provides enough verifiable continuity, use the faceless trust signal checklist. This audit focuses on whether approved cues agree with each other.
List the public surfaces in scope
Create a surface register before reviewing content. Include public profile name, handle, avatar, header, bio, pinned item, link destination, active promotion profiles and any public page that currently introduces the creator.
Record URL, surface owner, last reviewed date, current status and capture ID. Exclude private messages and internal records. The checklist should inspect what an ordinary public visitor can encounter in the selected journey.
Retired or inaccessible surfaces get a separate state. Do not compare an old cached page with a live profile without noting the date. The aim is a current controlled view, not an endless search for every historical mention.
Create the Persona Source Card
The Persona Source Card is the approved reference, not a creative brainstorm. Fields: persona version, public display name, handle rules, one-sentence promise, three voice traits, phrase bank, visual cue set, recurring motifs, public facts approved for mention, topics not used and owner.
Every trait needs an observable example. “Playful” might mean short first-person captions, light teasing and one direct question. It should also state what does not fit, such as formal corporate wording or unexplained aggressive language.
Version the card when the creator deliberately changes a cue. Preserve the effective date and migration plan. Without a version, an intentional refresh can look like an audit failure and an accidental mismatch can be dismissed as evolution.
Define a cue taxonomy
Group cues so reviewers compare equivalent things. A practical taxonomy includes naming, promise, voice, visual treatment, recurring object or motif, content expectations, availability wording and interaction style.
Separate stable cues from flexible expressions. The promise and display name may need close alignment everywhere, while a colour palette can vary by channel as long as the anchor remains recognisable.
Assign each cue an importance level: identity-critical, journey-supporting or decorative. This makes correction priorities more useful than a simple percentage score.
Set match rules before the audit
Use four states: exact match, acceptable variation, unresolved and contradiction. Write one rule and example for each state. An acceptable variation changes wording to fit the surface while keeping the same meaning.
A contradiction occurs when two active public surfaces create incompatible expectations. For example, one bio promises frequent behind-the-scenes updates while the linked destination describes a polished weekly set only. The issue is the conflicting promise, not different sentence length.
Unresolved means the reviewer lacks enough context or approval to classify the difference. Do not force it into a pass or fail. Assign an owner to confirm the source card or surface.
Copy the Surface Audit Row
Use one row per cue on each public surface:
- Surface: URL, element, capture date, owner and status.
- Reference: Persona Source Card version, cue ID and approved meaning.
- Observed: exact text or visual description and evidence capture ID.
- Classification: exact match, acceptable variation, unresolved or contradiction.
- Action: severity, correction owner, due date, approval need and completion evidence.
Keep observations specific enough for another reviewer to reproduce. “Feels off-brand” is not an audit result. Name the visible cue and the precise reference it conflicts with.
Review naming and handles
Check display name spelling, capitalisation, handle presentation and the way the creator introduces themselves. Variations may be necessary when a handle is unavailable, but the relationship should remain understandable.
Flag unexplained extra names, outdated aliases and link labels that send visitors toward a different identity. Record surface constraints before requesting a change.
Do not assume identical handles are always possible. The source card can define approved variants and a visible bridge, such as the same display name and avatar treatment.
Review promise and expectation language
Extract the main promise from each bio, header, pinned post and destination. Compare what the visitor is told they will receive, how often, in what style and where. Keep the source wording attached.
A short promotion bio can omit detail without contradicting a fuller destination. It becomes a problem when it adds a promise the creator does not make elsewhere or removes the essential qualifier that keeps the expectation accurate.
If the mismatch is really a missing trust cue rather than a contradiction, route it to the trust-signal workflow. This checklist should not expand into a full profile rewrite.
Review voice without demanding identical copy
Sample recent public captions, bio lines and pinned introductions. Check sentence rhythm, point of view, repeated vocabulary, humour style, question style and call-to-action tone against the voice traits.
Consistency does not mean copying the same sentence onto every channel. A short-form caption and a destination bio have different jobs. The audit asks whether both sound like plausible expressions of the same approved persona.
Flag abrupt register changes that are unexplained by context. Provide two or three evidence examples rather than classifying an entire channel from one unusual post.
Review visual identity cues
Compare avatar treatment, header composition, crop language, colour anchors, lighting, typography where used and recurring motifs. Note surface constraints such as circular avatars or mobile crops.
Look for recognition at small size. A profile image can vary while preserving a repeated silhouette, prop, colour edge or framing rule. The checklist records the cue; it does not require one image everywhere.
Final public assets should already be approved. Use the faceless promotion asset map for channel suitability and crop decisions. This audit only checks the live result against the source card.
Trace one visitor journey end to end
Select a realistic path: discovery post, public profile, bio link, landing page and creator destination. Capture the sequence on the same review date and device class.
At every transition, ask whether the name, promise, voice and visual anchors continue clearly enough that a visitor can understand they reached the intended creator. Record breaks and ambiguous handoffs.
A consistent individual surface can still create an inconsistent journey when the next click changes promise or identity cues. Journey evidence helps prioritise the mismatch closest to the visitor's decision.
Prioritise the contradiction queue
Use three severity levels. Critical contradicts identity or core promise in a live high-traffic path. Material creates a different expectation or weakens recognition. Minor affects a decorative or low-impact cue.
Each queue item needs evidence, affected journey, source-card reference, proposed owner and approval state. Fix critical active contradictions before polishing decorative consistency.
After correction, capture the updated surface and mark the row resolved with date and version. Do not close an item because an edit was requested; close it when the public result has been verified.
Carry approved cues into future content
Send stable public cues to the faceless content planner as constraints, not as a demand that every asset look identical. The planner can vary scene and format while preserving selected anchors.
When production reveals that a cue is difficult to sustain, return to the Persona Source Card owner. Change the reference intentionally rather than allowing individual posts to drift.
Keep surface corrections and production changes separate. This preserves a clear audit trail for what was wrong live versus what needs to change in future assets.
Repeat the audit at useful triggers
Run a full review after a deliberate persona refresh, new public channel, destination redesign or change to the central promise. Between those events, use a smaller monthly sample of the highest-traffic path.
Track repeat contradictions by cue and surface. Repeated errors may show that the source card is unclear, ownership is fragmented or an old template remains in use.
Retire cues that no longer help recognition or cannot be maintained. Consistency should reduce confusion, not trap the creator inside obsolete creative choices.
Check whether the source card is usable
Give an approved collaborator three recent public examples and the current Persona Source Card. Ask them to identify the relevant cue, classify the variation and cite the rule used. Record where two reviewers reach different outcomes.
Disagreement can reveal vague traits, overlapping cue IDs or missing examples. Rewrite the source card before correcting several surfaces under an unclear rule. The card passes this check when reviewers can apply it consistently while still recognising legitimate channel variation.
Limitations and sources
Limitations: this checklist evaluates agreement among selected public cues at a dated point in time. It does not prove who operates an account, measure audience trust, prescribe identity-protection practices or predict profile performance. Surface constraints can require legitimate variation.
W3C guidance explains consistent identification without requiring every presentation to be identical. GOV.UK service guidance supports a consistent end-to-end experience and the principle of consistency rather than uniformity. The Persona Source Card, cue taxonomy, Surface Audit Row and contradiction queue are original SirenCY editorial artifacts.