Most proof pages stop at a one-line quote. This one shows the full shape of an engagement — the day-one score, what got classified in the first month, the single recommendation that landed, and what it actually moved on the floor. It is written for buyers who want more than a testimonial before they set up a demo.
Setting
24-bed residential home
Greater Manchester
Day-one score
42 / 100
Incidents (30 d)
47
Across three corridors
Recommendation
Lighting + corridor check
Two changes, one SOP
Numbers are representative of the cohort Lookpost serves — not a single named customer.
What an engagement looks like
The shape below is the same on every sector Lookpost serves — a care home, a warehouse, a construction site. The contents change; the rhythm does not.
A 60-minute walk-through recorded as a structured profile — service users, shift pattern, exits, call-bell coverage, lighting, lone-worker roles — so the engagement has a grounded starting point.
Every shift logs incidents through the worker app on the floor; anything outside an app context (a phone call from a parent, a neighbour flagging a yard event) drops into the same record via a 60-second web form.
On the way through the queue, Lookpost tags severity, deduplicates near-duplicate reports and surfaces the recurring vulnerability — three unwitnessed events in the same corridor this month, not three separate incidents.
Each regulated incident becomes a timestamped evidence pack a regulator can read in one sitting; the whole engagement closes out in a monthly report carrying provenance — who recorded what, when, and what action followed.
Illustrative operating scenario
All figures on this page are illustrative sample content, not customer records, attributable evidence or verified outcomes. If you would like to see the same structure discussed against your own setting, request a demonstration.
Day one: where the operating system started.
In this sample scenario, the score represents two correlated signals — a missing corridor loop on the night shift and lighting below 40 lux on two corridors between 23:00 and 05:00. Either on its own would have flagged amber; together they flagged the recurring vulnerability Lookpost expected to surface within the first two weeks of operation.
Incidents classified in the first 30 days.
In this illustrative dataset, the first 30 days contain 47 sample incidents through the worker app and web form combined. After AI triage, they collapsed into four recurring shapes — and one of them, an unwitnessed corridor event between 01:30 and 02:15, appeared 18 times on three corridors.
Unwitnessed fall in corridor
Bedroom 12 — unwitnessed fall, call-bell pressed 01:58
Lone-welfare tap missed
Lone-worker device — tap missed at 02:30, escalated within 4 minutes
Missing personal property
Resident clothing missing from named drawer, no staff witness
Door-alarm test failure
Daytime exit door alarm silent on test, serviced same morning
The recommendation that landed.
The recommendation that landed was a single combined change — a 01:30 corridor-loop check added to the night-shift briefing, daylight-level corridor lighting brought in line with the home’s existing falls policy, and a weekly door-alarm test folded into the same briefing. Nothing else changed; the SOP did the work because the corridor loop covered the gap.
Measurable outcome (30 days post-change).
In this illustrative scenario, the sample change is followed by a smaller sample count. It is a demonstration of how a report might be structured, not a measured customer outcome or a promise that Lookpost will produce one.
Framing note — this is illustrative sample content, not a customer record, testimonial, attributable evidence or verified outcome.
See pricing →if you want this on your own floor.
Why this page exists
A one-line testimonial tells you somebody liked the software. A case study tells you what it actually did on a floor, ward, loading bay or yard — the score on day one, the incidents classified, the recommendation made, and what changed. Same product, different reader question.
See the published testimonials →for the receipts from opted-in customers.
Bring a recent fall, a bay intrusion or a cab-fence event — we’ll show the answer Lookpost would give on your own data, not a generic sandbox. The first 20 minutes is on us.
or write directly:lookpost-xk94iw@polsia.app