What needs doing in your building, before 8am.

A day with Runstead

The day, in order.

1. 08:00

   Open it, and it’s already sorted

   Today shows what needs your attention, what’s due, and who’s coming in. An overdue check has a red dot. Recording a check is one press.

2. 09:40

   A teacher reports a leak

   Nothing to install, nothing to log into. They open the school’s own link, say what’s wrong and where, and it’s a ticket with their name on it.

3. 11:15

   It becomes a job, and Dee gets it

   You make a job from the ticket and give it to Dee. It’s on her phone. She starts it, and closes it with a note and a photo. The history writes itself.

4. 15:00

   The gas certificate arrives

   Upload it. Runstead reads the dates and the issuer and suggests where it belongs. You confirm. Next year’s expiry is already in Coming up.

5. Any time

   Say it while you walk

   “Book the alarm engineer for Tuesday at half nine.” One card comes back with what it understood. You press Create, or fix it first. Nothing is written until you do.

For whoever signs it off

How the records are kept.

• Every check, ticket and job keeps its history. Entries are added, never rewritten, so the record shows who did what and when.
• Each building’s data is separate at the database. Row-level security decides what a request may read. It is not left to the application to remember.
• Three roles, and documents per person. Manager, maintenance operative, leadership. A document is seen only by the people the manager has named. The people who report problems are never users.
• Your records and documents are held on servers in London. When someone uses the assistant or uploads a document, that text goes to OpenAI under a data-processing agreement. It is not used for training and is deleted within 30 days.
• Nothing is written on your behalf. A rule or the assistant can propose a ticket, a job, a date or a document. A person confirms it, every time.

Pricing

Talk to us