DEMONSTRATION RECORDNOT CLIENT RESULTS

Sample Visibility Record

This fictitious example shows the structure D’Key Digital can use to document a business baseline, priorities, launch evidence and later review points.

Important:Every score, observation and business detail below is illustrative placeholder data. It has not been calculated from or attributed to a real client.
Example Local Business

Day 0 baseline snapshot

Illustrative format only. A live record would contain dated evidence sources and business-specific notes.

Illustrative overall54/ 100DEMO
Website presence68
Developing
Mobile usability76
Stronger
Local visibility44
Priority
Trust signals57
Developing
Enquiry journey52
Developing
Measurement readiness28
Priority
Evidence register

What supports the baseline.

A real record would point back to captured screenshots, analytics exports, listings, form tests or client-supplied evidence.

AreaIllustrative observationEvidence status
WebsiteCore services are present, but the primary action competes with secondary information.Observed — demo
Local searchLocation/service signals are incomplete and need a clearer local search foundation.Observed — demo
EnquiriesNo reliable baseline for form or call actions is available yet.Not available — demo
ReviewsThe example assumes some customer proof exists but is not consistently surfaced.Client-reported — demo
Priority register

Turn the baseline into controlled actions.

P1

Establish measurement baseline

Define the useful customer actions, configure agreed tracking and record the starting period.

High
P2

Strengthen local visibility signals

Correct the core location/service information and review the business’s local search presence.

High
P3

Simplify the main enquiry route

Make the primary action unmistakable on mobile and confirm the route works end to end.

Medium
Review cycle

Keep the baseline fixed. Add later evidence beside it.

This is how the record avoids rewriting history after a successful or unsuccessful result.

DAY 0

Baseline

Capture current position and unknowns.

LAUNCH

Delivery proof

Record what was actually completed and checked.

DAY 30

Early signals

Look for data quality and directional changes.

DAY 60

Pattern check

Compare useful actions without overstating causation.

DAY 90

Next decision

Continue, change, test or stop based on evidence.

Claim standard

What the final report is allowed to say.

Measured: “Form submissions increased from the recorded baseline.”

Observed: “The mobile enquiry route is now shorter and the form test passed.”

Client-reported: “The client reported more telephone enquiries.”

Not supported: “The website caused a 40% revenue increase” unless reliable evidence genuinely supports that causal claim.

Create a real baseline

Start with evidence from your own business.

The first useful record is the current position — before a redesign, campaign or growth claim changes the picture.

Request a Visibility Audit