Understand the decision
The useful level of detail is the smallest amount needed to make a decision. Protect customer information and avoid turning a public report into a list of identifiable enquiries.
Define accepted services, coverage, customer type and practical project requirements. Keep the rules stable enough for comparisons and note when they change.
A practical workflow
Work through the sequence below. Keep the evidence, the change you make and the acceptance check together so the next person can understand the decision.
Agree qualification rules
Define accepted services, coverage, customer type and practical project requirements. Keep the rules stable enough for comparisons and note when they change.
Connect records carefully
Use an appropriate enquiry system and limited identifiers where authorised. Keep raw personal information out of general analytics. Record source uncertainty honestly.
Review reasons, not just totals
Group unsuitable enquiries by recurring cause such as wrong service or area. Improve the page information or targeting when the pattern is clear.
Illustrative scenario
What this looks like in practice
A specialist receives ten enquiries, three of which match the agreed service and budget context. The report includes ten total and three qualified, then explains the most common mismatch without disclosing customer identities.
This is a worked example, not a claim about a client campaign or a promised result.
Before you sign it off
Do not count spam or test submissions as genuine demand. Do not infer a customer’s sensitive attributes to decide marketing qualification.
Keep a useful decision record
- Purpose
- Write the customer task this change is meant to improve.
- Evidence
- Save the relevant page, source or observation and its date.
- Owner
- Identify who implements the change and who verifies it.
- Acceptance
- State what a correct result looks like before measuring its wider effect.
What to measure
Track valid enquiries, qualification rate, recurring mismatches and the steps that lead to an agreed project.
Record the baseline and the observation window. If the measurement setup changes, annotate the report before comparing periods. Use the findings to choose the next useful improvement, rather than treating one encouraging result as proof of a permanent outcome.
Sources and further reading
These primary references provide platform guidance and context. The workflows and scenarios on this page are editorial explanations; a source link does not turn an example into a measured result.
Need help applying this?
Start with your website, target audience and the problem you want to solve. We can agree on the useful work, implementation responsibilities and reporting.
Explore the relevant serviceDiscuss the scope