How a forecourt came to keep a file on every asset

Clickpad copilotScreenshot

Shell sits in Clickpad as a register of 210 assets. The dispensers on each island, the canopy and its lighting, the shop and its fit-out, and the customer washrooms — each one entered against the place it actually stands, so it is opened from the site plan rather than found in a row of a spreadsheet.

An asset page is not a specification sheet. The specs are on it, and under them sit the service logs and a history timeline: what was replaced, when, and against which job it was raised. A fixture in the customer washrooms reads as a sequence rather than a status — a flush valve diaphragm replaced, a wax seal replaced after an earlier leak, an auger clearance. When a customer scans the code on that fixture rather than queueing at the till, the report they leave lands against that history instead of arriving on its own, and the earlier leak is the line worth reading twice.

Every asset also carries a section for what we do not know about it. A serial nobody has read off the dispenser, no install date on a run of canopy lighting, no manual on file, a service interval nobody has confirmed. The gap is written down as a gap rather than left as an assumption, so the register is honest about its own coverage and the holes can be closed on the next visit rather than rediscovered on the next fault.

The copilot is per property. Asked who last inspected a dispenser, it answers out of this site’s register: who attended, when, what they checked — the skimmer seals, the nozzle and hose, the breakaway date — and the one thing they flagged on the way past. A dead pixel on a display is a small enough finding to go unrecorded anywhere else. Here it stays open on the dispenser it belongs to, and can be turned into scheduled work from the same card.

Maintenance runs off the same entries. Intervals live on the asset, so a dispenser that has gone past its own interval is visible as itself and not as a line in a schedule kept somewhere else. CapEx planning is a separate hub reading the same register — the assets, their ages, their histories and the work already done to them — so the canopy and the pumps under it are planned for against what is recorded rather than against what is remembered.