How we run a facility
Four moves, repeated: define the site as a system, run it to checklist, record what happened, and let the record change the next cycle.
- Method
- Define, run, record, review
- Evidence
- Captured at the point of work
- Review
- Monthly, against the record
- First full cycle
- Complete by day 30
- Coverage
- On site across Saudi Arabia
We run buildings the way management systems are audited. The site is defined as assets, zones, routines, risks and owners. Work runs to a checklist. Evidence is captured at the point of work. The monthly review changes the schedule, and a review that changes nothing was a presentation.
Where FM providers actually lose
The work usually gets done. What fails is the part after it, and the part after that is what you are paying for.
Almost every facilities complaint we have inherited traces to a missing handoff rather than a missing skill. A task was completed and not recorded. A defect was mentioned and not ticketed. A recommendation was made and never given an owner. Nobody was lazy. The chain just had no link at that point.
This is the same failure we spend our professional lives finding inside other companies' management systems, which is why our own operation is built around closing it. Not because documentation is virtuous, but because an unrecorded month cannot be reviewed, and a month that cannot be reviewed repeats.
It also means we will show you the bad numbers. A report where everything went well every month is a report nobody is reading.
The four moves
| Move | What it means in practice | Output |
|---|---|---|
| Define | The building is turned into a list: assets, zones, routines, risks and the person who owns each one. Nothing gets scheduled against a building, only against an item on that list. | Survey and mobilisation |
| Run | Planned work executes to a checklist and reactive work runs to a priority with a clock. Neither depends on which technician showed up. | Daily |
| Record | Evidence is captured where the work happens, not written up afterwards. Photographs, readings, times and names, attached to the asset or the zone. | At the point of work |
| Review | The month is read together and something changes: a frequency, a scope line, a roster, a priority level. A review that changes nothing was a presentation. | Monthly |
What the method produces
These are the same artifacts named on every service page, because the method does not change between service lines.
The asset and zone register
The definition of your site as a system. Everything else in the contract points at a line in it.
The schedule
Planned work placed on dates, per asset or per zone, visible a year ahead.
The evidence trail
Work orders with photographs, readings, times and names, queryable by asset rather than by month.
The monthly report
Assembled from the record rather than written at month end, which is why it arrives on time and is not flattering.
The action list
What the review decided, with an owner and a date, carried forward until it closes.
The first month on a warm office building
An office building in Khobar changes provider after a summer of cooling complaints. The outgoing contractor hands over an equipment list and a folder of service sheets with ticks on them.
Define comes first. The survey walks every floor and the roof and lists air handling units, fan coils and split units by location, with the person who owns each zone. Units that were never on the old list are added, and units on the list that no longer exist are removed. Run starts from that register: planned tasks go on the calendar, and every complaint becomes a ticket with a priority and a clock.
Record happens at the unit. Filter pressure, supply temperature and the technician's photographs are attached to the asset, not typed up at month end. By the first review, the record shows the same two fan coils on the top floor tripping again and again, and complaints clustering on that floor after midday.
The review changes two things: the filter interval for that floor is shortened, and a replacement case is raised for the two units with their repair history attached. The client holds the register, the calendar, the ticket history, the first monthly report and an action list with an owner and a date against each change.
What this looks like from your side
You stop being the record system
The most common thing we replace is a person holding the whole building in their head and in a spreadsheet. That works until they take leave.
- Every routine and every defect has a place it lives that is not your inbox
- One monthly document instead of assembling five vendor reports
- A handover that survives you being away for two weeks
You can see what you are buying
Facilities spend is usually opaque because the activity behind it is invisible. Defining the site is also what makes the spend auditable.
- Planned versus reactive spend separated and trended
- Repeat failures visible per asset, which is where replacement cases come from
- Variation orders explained against the scope rather than appearing at month end
You can produce evidence on demand
If your site is audited by anyone, the FM evidence pack is part of your system whether you built it that way or not.
- Records in a format your own auditors already recognise
- Prerequisite programmes evidenced rather than described
- Due dates and expiries visible in advance of the audit rather than during it
Fair challenges to this
Is this just paperwork with a different name?
It is paperwork if nothing reads it. The test is whether the review changes the schedule. If we hand you a monthly report for six months and nothing about the operation has changed, then yes, it was paperwork, and you should say so at the review.
Our building is small. Is this overkill?
The register and the schedule scale down honestly, and on a small site they take a day to build. What does not scale down is the value of knowing what is on the roof. Small buildings usually have worse records than large ones, not better.
We already have a CAFM system nobody uses. How is this different?
A system is not a method. The reason most CAFM deployments go quiet is that nobody defined the site first, so the tool had nothing true to hold. We would rather spend the first two weeks on the register than on software configuration.
Will you show us the months that went badly?
Yes, and that is the part of this you should test us on. Ask for a month where the completion rate dropped and see whether we can produce it with the cause written next to it.
Does the method change between service lines?
No. The same four moves run on every line, from HVAC to pest control to support staffing, which is why every service page names the same kinds of documents.
Part of one system
Every division keeps records to the same standard, so the second one you need works the way the first one did.
Book a site survey
The survey is the define step, done once. The register and the draft schedule that come out of it are what the quote is written against.