Servanda.

The tour · thirty seconds

06:29:57.

Hannah's list. Seventy-five sites, recalculated before anyone is in.

Six overdue. Worst first: twenty-three days, and nobody had noticed.

Click the pulsing one

Hannah's list · 1 of 6 · Larchmont Court, 24 flats

The fire risk assessment is twenty-three days overdue.

  • The works order is already written.
  • Example Fire Safety is on it, because they did the last one.
  • Nobody typed a word this morning. Your part is one click.

Larchmont Court · fire risk assessment

  1. Sent.A link of their own. No password, no app.
  2. Opened.You see the moment it happens.
  3. Booked.For 10:00. The reminders stop by themselves.
  4. In.The report arrives by email. Drop it on; Servanda reads it.

Fire risk assessment

Regulatory Reform (Fire Safety) Order 2005 · common parts

Premises
Larchmont Court
Date of assessment
Review by
Overall risk
Tolerable
Action 1, high
Flat 4 entrance door: replace damaged smoke seal
Action 2, medium
Stair 2: emergency light not working
Action 3, low
Riser cupboard: remove stored items
Assessor
J. Hart, Example Fire Safety

Read by Servanda · due dates set by priority

  • Assessed
  • Next review due
  • Overall riskTolerable
  • Fire door, flat 4 · high
  • Emergency light, stair 2 · medium
  • Riser cupboard · low
Servanda reads it. Hannah signs it off.

Larchmont Court · fire risk assessment

Kept.

Assessed, read and filed. Three actions, each with a due date, tracked until they are closed. The next review is due .

That was the first of six. Five to go.

No account and no obligation. The founder replies, not a sales team.

Every site, every morning.

The register recalculates overnight and each manager gets their own list, worst first, with the next step already prepared. Every step lands on the record and prints as the evidence pack.

A gap is not a lapse.

The hollow dots are things with no record at all. Servanda keeps them apart from the overdue ones, because "we never had one" and "it ran out" are different problems.

A person always signs off.

Servanda reads the report and proposes the dates and the actions. Someone on your team confirms it before the register moves, and the actions are chased until they are closed.