Transparent reporting

Four events cover most of what a moving company needs: a phone call answered, a form submitted, a quote sent, and a move booked. Name them once, write the definitions down, and use the same names in every system.

• Call. An inbound call that reaches the office, separate from missed and abandoned calls.
• Form submission. A completed request with a reachable phone number, separate from spam and tests.
• Quote sent. An estimate delivered to the customer, recorded in the system of record.
• Booked move. A deposit taken or a date locked, recorded in the same system.

When a statistic is called a conversion, it should be one of those four. A page view is not a lead.

Place a test call from a phone you control and submit one test form with a note that marks it as a test. Then confirm the event appears in the analytics property, in the call record, and in whatever system closes the booking. If any of the three is missing, the report will be wrong for as long as the fault lasts.

Remove the test records after confirming them, and keep the note that records what you tested. This is the step most reporting skips, and the reason so many reports disagree with the phone bill.

Each line in the report names its source: Search Console for queries and pages, the analytics property for site events, the call system for calls, and the booking system for quotes and moves. Nothing is entered by hand except the explanation.

Where two sources disagree, the report says so and names the likely cause instead of choosing the friendlier number.

Every measurement has a boundary, and writing it down is part of the job:

• Analytics sees the last click, not the search that started the consideration.
• Calls from the map listing may never reach the website at all.
• Consent choices and blocked scripts mean some sessions are missing from the tool.
• A form that arrives with a bad phone number still counts as a submission and still wastes the office's time.
• Offline conversations, referrals and repeat customers are invisible to every dashboard.

A report that names these limits is more credible than one that implies the numbers are complete.

Marketing numbers move for reasons that have nothing to do with the work: weather, a competitor closing, a school calendar, a truck breaking down. The change ledger records what you changed, in what order, and what you expected it to move. When the next report looks better or worse, the ledger is what separates a cause from a coincidence.

Read the ledger before the charts. If nothing changed and the numbers moved, say that plainly.

What did we change? What did the sources show? What did we learn that changes the next batch? What is still unknown? Four questions, answered in writing, are a better report than a dashboard nobody opens. Anything that cannot be answered from a source gets a task, not an estimate.