
Measurement
Part of How to build local service marketing measurement that holds up
When to build a local service marketing reporting dashboard
How to time a local service marketing reporting dashboard: set baseline metrics, agree lead definitions and build a before and after table that earns its keep.
What to take away
- Build a local service marketing reporting dashboard when decisions stall, not when a tool vendor emails you.
- A dashboard is the output of measurement work you have already done, so settle the measurement questions first.
- Start with four to six metrics tied to leads and booked jobs, and drop anything nobody acts on.
- Record what each figure means and where it comes from, because definitions drift.
- Treat data protection as part of the build, not a later tidy-up.
The trigger is a stalled decision
The right moment to build a local service marketing reporting dashboard is when someone cannot answer a question that costs money. Perhaps you cannot tell which advert produced last month's boiler installations. Perhaps two people disagree about cost per lead because each uses a different spreadsheet. That friction is the signal.
A dashboard will not fix unclear questions. If your team cannot agree what counts as a lead, no chart resolves it. Read Local service marketing measurement mistakes before you buy anything, because the common failures start with definitions rather than software.
Write the questions before the charts
List the decisions you make each month and the evidence each one needs. A firm spending £2,000 a month on ads needs cost per booked job rather than impressions.
Question cadence by time frame
- Weeklylead volume and response speed
- Monthlycost per acquisition and source mix
- Quarterlywhether a channel still earns its place
- Before changesrecord baseline numbers with the date
Group the questions by time frame. Weekly questions cover lead volume and response speed. Monthly questions cover cost per acquisition and source mix. Quarterly questions cover whether a channel still earns its place. A dashboard that mixes all three on one screen gets ignored.
Set a baseline before you change anything. Record today's numbers, with the date, so the first month of dashboard data has something to compare against.
Build a small metric set
Pick four to six metrics. Each one should map to a decision and a person who owns it.
Reporting before and after
Before
- Enquiries
- Counted in three places
- Cost per lead
- Quoted from memory
- Source
- Recorded as the internet
- Data protection
- Handled separately
After
- Enquiries
- One agreed definition
- Cost per lead
- Monthly, plus cost per booked job
- Source
- Recorded at point of enquiry
- Data protection
- Consent and retention in the build
Keep the table visible for the first quarter. It reminds everyone why the reporting changed.
Decide who can see and change it
Access control matters more than chart design. Give edit rights to a small number of people, and view rights to everyone who needs the numbers. If you pull Google Business Profile data into the dashboard, follow the Business Profile owners and managers guidance so leavers lose access promptly.
Where the dashboard holds enquiry data, use the ICO direct marketing advice generator to check your collection and use of that data is compliant before you scale it.
Segment the audience you actually serve
Reporting improves when the audience is defined. Household composition, tenure and age shape who books a service and when. The ONS household characteristics data gives you a defensible way to describe your catchment.
The same discipline runs through Local service marketing: measurement and reporting, which maps the reporting cycle end to end. A dashboard split by service type and postcode district tells you more than one national total.
Set a build order and a review date
Week one: agree definitions and record the baseline. Week two: connect the two most important sources. Week three: build one page and test it against last month's known figures. Week four: hand it to the people who will use it and delete every chart nobody opens.
Review at 90 days. Ask which decisions changed because of the dashboard, and which figures nobody trusts. Retire the metrics that failed both tests. A dashboard is a working tool, not a monument.
Common questions
How many metrics should a small service firm track?
Four to six is usually enough, each tied to a decision someone makes monthly, such as where to move budget or whether to hire another engineer.
Can I build a dashboard in a spreadsheet?
Yes. A spreadsheet with agreed definitions beats an expensive tool with disputed ones. Move to dedicated software only when manual updating becomes the bottleneck.
How often should the dashboard be refreshed?
Match the refresh to the decision. Weekly for lead volume and response times, monthly for cost per acquisition, quarterly for channel reviews. Anything refreshed more often than it is used trains people to ignore it.



