Maintenance request

The request, triaged, and the work order it becomes.

Somebody reports a problem; maintenance decides what to do about it. This is the first half — the record that exists before anybody has agreed to do the work, and the one tap that turns it into a work order.

What the maintenance request is for

Turn something that needs doing into something that gets done, and prove it was. Somebody reports a problem — staff, a tenant, a resident’s family — and it goes on a list before anybody has agreed to do it. Triage it, give it an owner and a date, and turn it into a numbered work order in one tap. The thing you came to do is “report a problem”, and this is the page that does it.

It is filed under maintenance & work — dispatching, doing and proving the physical work — and under “fix something”, which is raise it, own it, close it out. There is one page for it, at this address, however you arrived.

Written for anyone reporting a problem — staff, tenants, residents' families.

When people reach for it

  • Log what needs doing so it waits on a list rather than in somebody's head — people arrive here typing “maintenance request”, “work request”, “report a problem”.

What it records, and where the record goes

The request, triaged, and the work order it becomes. Each entry is kept in this tool's own register rather than as a loose document, which is what lets the register answer the question months later instead of you re-reading a stack of paper. What you enter stays in this browser, on this device. There is no account to make and nothing is uploaded; it reaches another device only if you activate CompliMaint Cloud Beta and sign in.

  • Records — every document this device holds, filed as you work.
  • CompliMaint Facilities — Know what is required, do it on the day, keep the record that proves it.
  • Incidents — What went wrong, who owns it, when it closed.

Related tools and workflows

  • Corrective Action Tracker — Every finding on one list, with an owner and a date, until it is closed. The same workflow, set up for facilities and compliance.
  • Incident Report — The report, and — where the state is one we have read — who has to be told. Also in Incidents.
  • Near-Miss Report — The same record as an incident, without the duties an injury would trigger. Also in Incidents.
  • Corrective Action Plan Tracker — Every finding, its owner, what is being done, and what came back. Also in Incidents.
  • Service Follow-Up Tracker — The part on order, the return trip, the quote that never came. Also in Incidents.
  • OSHA 300 Log & 300A Annual Summary — Is it recordable? Then the log, then the 300A you post. Also in Incidents.

This work belongs to Facilities, Property and Services, so it is listed in each. There is still one page, at this address.