The Trust Surface Review: Where Clients Decide Before They Call

A prospective client conducts their entire evaluation before they ever contact you. They read the website, then the directory profiles, then the professional network, then whatever a search engine and an answer engine assemble on their behalf. Each of those is a trust surface — a place where consideration either continues or quietly ends.

This is the second Authority Studio work product. It audits every public-facing surface as a single system, because machines and buyers both read them as one.

§ 01Why surfaces are audited together

Entity resolution is corroboration. A machine trusts a claim in proportion to how many independent surfaces repeat it consistently. A credential asserted only on your own domain is a claim; the same credential present in the issuing body's registry, a professional directory, and a network profile is evidence.

Buyers behave the same way, informally. They cross-check. One inconsistent address, one stale profile with a former firm name, one directory listing with a disconnected phone number — and the evaluation stops without anyone telling you it happened.

§ 02The surface inventory

Each row is a checkpoint. A gap on any one of them can end consideration before it begins.

§ 03The three consistency rules

Everything in the audit reduces to three rules. They are unglamorous and they decide whether the cluster resolves.

1. 01One name everywhere. One legal and trading name, spelled identically across every surface, including punctuation. If a secondary brand exists, it must be published as part of the same organization rather than as a competing one.
2. 02One verified address and one contact path. Multiple phone numbers scattered across surfaces fracture both attribution and intake. Segment numbers deliberately if you must, and publish only the primary on identity surfaces.
3. 03One explicit service menu. Name the matter types the way buyers name them. A visitor should be able to self-select in one screen, and a machine should be able to classify the practice without inferring.

§ 04Practitioners are entities too

Most practices model the organization and stop. Credential-led queries select people, not paragraphs. Every practitioner who carries a distinguishing credential needs:

• A stable identifier on the practice's own site — a real page, not a modal.
• The credential attached to the person, with the issuing body named.
• An explicit relationship to the organization, stated in structured data.
• A matching, current profile on at least two independent surfaces.

This is the Entity Lock Protocol applied at the level of a team rather than an individual.

§ 05Grading each surface

Score each surface on four binary questions. Anything scoring below four is on the cleanup list.

• Claimed. Does the practice control it?
• Complete. Are credentials, matter types, and contact details all present?
• Consistent. Do the name, address, and claims match the primary site exactly?
• Current. Has it been touched since the last material change to the practice?

§ 06What the review produces

• A full surface inventory, one row per profile, with owner and access status.
• A consistency table flagging every name, address, and credential mismatch.
• A practitioner coverage matrix: who resolves where, and who does not resolve anywhere.
• A cleanup roadmap ordered by trust weight, not by effort.
• A short list of surfaces worth creating that do not exist yet.

§ 07Why it comes before content

Producing new assets on top of an inconsistent surface layer spreads the inconsistency further. Fix identity first, then publish into it. That sequence — resolve, corroborate, then produce — is what makes the content map compound instead of scatter.