From scan counts to vendor reports: reading board data as an agency
A scan means someone stood close enough to point a phone at the board and did. That is real, local, physical interest, and it is a genuinely different signal from a portal click, which can come from a browser three counties away or from the vendor themselves from their sofa. It is not a lead: nothing in a scan says the person could afford the house, liked it, or wants to be contacted. Agencies that report scans as footfall evidence keep the number's credibility; the moment it is dressed as demand or leads, a sharp vendor asks how many of those scans were the postman, and the whole report loses authority.
The vendor-facing version needs four numbers and two sentences. The numbers: scans this period, total scans since the board went up, the best day or week, and the same for a comparable local listing if the branch has one. The sentences: one saying what the board data shows plainly, one saying what happens next. Anything longer and the report becomes about the agency's tools instead of the vendor's property. The dashboard's daily series is the source for all of it; the discipline is choosing the four numbers before opening the laptop, not after.
| Pattern | Likely reading | Worth doing |
|---|---|---|
| Steady scans from listing week | The board location works and the listing holds interest | Quote it in the vendor review as proof of coverage |
| Scans collapse after a price change | Interest was price-led; the new price stopped the passers-by | Discuss price expectations with evidence, not opinion |
| A few scans, ever | Placement or size problem: too far from the pavement, code too small, board in shadow | Re-check the board against the sizing guide, then move it if the agreement allows |
| Scans continue past completion | The sold page is being read; the local-interest page is earning its keep | Keep the sold destination live until the board comes down |
The board that never scans is the number agencies quietly refuse to look at, because it seems to indict the tool. It usually indicts the placement instead: a board set back from the pavement, a code sized for a window card standing on a verge, a position in shade where the phone cannot read the glare. Those are all checkable against the sizing method in minutes, and the branch that treats zero-scan boards as a placement audit rather than a data failure ends the quarter with better boards everywhere. The data cannot tell you why a board was never scanned; it reliably tells you that one deserves a look.
No scanner is identified: no name, no device ID, nothing that links two scans to one person. Location is carried only roughly, and no specific location is named below five scans in the window, so a quiet board cannot be traced to one curious neighbour. That is not a limitation to apologise for in a vendor meeting; it is the reason the report is comfortable to give. A footfall figure that cannot be decomposed into who scanned is a footfall figure that carries no data-protection baggage, for the agency or for the person who scanned, and it is worth saying so out loud when handing the report over.
A monthly board report, end to end
Pick the four numbers first
Period scans, total, best week, one comparable. Decide before you open the dashboard so the data is not arranged backwards from a conclusion.
Check the dead boards
Any listing with near-zero scans gets a placement look: distance, size, glare, shadow. Fix the board, not the report.
Write the two sentences
One plain finding, one next action. Footfall language, never lead language.
Send it inside the normal vendor update
A scan section in the existing communication beats a separate report nobody opens.
Keep the archive
The code's lifetime count survives repoints and reprints, so the end-of-instruction summary covers the whole marketing period in one figure.