There is a familiar moment in a review when somebody asks how many of last week's enquiries became customers.
For a simple, quick arrangement, that may be a useful question.
For a service involving a visit, several choices or another person's approval, the answer may mostly describe how little time has passed.
The enquiry is still thinking about it. Or arranging it. Or waiting for a detail. That does not mean it is good, bad or secretly lost. It means the story hasn't reached the point the report is asking about.
I like reviewing groups of requests with enough time for the actual process. The business can explain that rhythm far better than a generic reporting rule.
What normally happens after the first reply? When is a visit arranged? Which decisions can take longer? At what point can the team reasonably describe the outcome?
Keep those answers beside the comparison.
A recent group may show whether requests were suitable and whether the first handover worked. An older group may show more about later conversations and completed work.
Both are useful. They are answering questions at different stages.
I would also note process changes. If the response arrangement improved, or the offer became clearer, we want to know which group encountered which version. Otherwise the date comparison can mix several explanations together.
This doesn't have to become an enormously elaborate model. A few clear groups and honest labels can be enough for a small service business.
The uncomfortable habit is using whichever window produces the happiest number. Too short for the outcome, then longer when the result looks better, then a new definition next month.
That makes a report difficult to trust even when the underlying work is decent.
Choose a sensible arrangement, explain it and revisit it for a reason. An inconclusive result can stay inconclusive while the requests mature.
We still need to spot a poor response or a broken route quickly. Patience is not a request to ignore those problems. It is a request to let a considered decision take the time it normally needs.
I sometimes picture a report tapping its foot beside a customer who is reading the proposal.
The customer has no obligation to move faster because the monthly review is on Thursday.
Give the evidence room. Thursday will manage. It usually does, despite being an impatient little nuisance.
A thought worth keeping?




