The Reactive Trap in Facility Management

Ask any facility manager what proportion of their work is planned rather than reactive. Most will give you a target, then a slightly embarrassed estimate of the reality, and the gap between the two has been there for years.

It is not a discipline problem. It is that reactive work arrives with a person attached to it and planned work does not.

How the trap closes

A tenant reports a problem. Somebody takes the call, writes it down, works out who should handle it, calls a contractor, agrees a time, tells the tenant, then follows up to confirm it was done.

That sequence takes perhaps forty minutes of attention spread across two days, for a job the contractor completes in an hour. Multiply by the volume of small issues in any portfolio and coordination consumes most of a team's week.

Planned maintenance is what gets postponed, because nobody is asking about it. And every postponed planned task eventually becomes a reactive one, usually more expensive and at a worse moment.

The intake problem

Most of the cost sits at the front, in how issues arrive.

They come by phone, by email, by text to somebody's personal number, and in person when a tenant sees a member of staff in a corridor. Some get logged. Some live in one head until they are done. Some are reported three times by three tenants and become three jobs.

Nothing downstream can be measured while intake is this loose, because the denominator is unknown. Any conversation about response times or contractor performance is guesswork until every request enters through one route.

Why tenants escalate

Tenant frustration is usually not about repair time. It is about silence.

Somebody reports a problem and hears nothing. They do not know whether it was received, whether anyone is coming, or when. After a few days they escalate, which means somebody senior now spends time on a job that was already in hand.

An acknowledgement on receipt and a note when a contractor is booked removes most escalations, and neither requires a person once intake runs through one channel. The information already exists. It simply never travels back.

Contractor coordination

The second block of time goes on contractors. Finding one who covers the trade and the site, confirming availability, passing access details, chasing when they do not attend, and collecting the paperwork afterwards.

Most of that is scheduling and reminding, which needs no judgement. What does need judgement is which contractor, at what priority, against what budget, and those decisions are quick once the coordination around them is not consuming the day.

Compliance is the risk nobody sees until an inspection

Every property carries recurring obligations. Fire systems, lifts, water testing, electrical inspection, insurance, contractor certification.

These are tracked in spreadsheets, in calendars, and in the memory of whoever has been there longest. The failure is silent. A certificate expires and nothing happens on the day, so nobody notices until an inspection, an insurance claim, or an incident.

This is the clearest automation case in the whole function. The dates are known in advance, the sequence is fixed, and the cost of missing one is disproportionate to the cost of tracking it.

Asset history turns data into decisions

The longer term prize is knowing which assets keep failing.

When every job is logged against a specific asset rather than against a building, patterns become visible. The unit repaired four times this year. The plant costing more in callouts than replacement would cost. The contractor whose work generates return visits.

None of that is available while jobs are recorded as free text against an address. It becomes available almost immediately once they are not, and it is the basis for every capital argument a facility manager needs to make.

What to fix first

One intake route, for everything, from everyone. Nothing else can be measured or improved until this exists, and it is the cheapest change on the list.

Then automatic acknowledgement and status updates back to the reporter, which removes most escalations for almost no effort.

Then compliance date tracking, because the risk is asymmetric.

Then contractor scheduling and paperwork collection, which is the largest time saving but only works properly once intake is clean.

The numbers worth pulling

• Share of work orders that are reactive against planned. The headline number, and it should move.

• Requests arriving outside the official channel. Ask the team honestly. It is usually most of them.

• Time from report to acknowledgement, separately from time to completion. Escalations track the first number, not the second.

• Repeat visits per asset. The replacement argument lives here.

• Compliance items within thirty days of expiry that nobody has actioned. Run this once before deciding whether the current system works.

What AI does with intake

One intake route is the foundation, and AI is what makes it work without adding a coordinator.

A tenant reports a problem however they prefer, by message, by email, by voice. AI reads it, works out the trade, the urgency and the location, checks whether it duplicates an open job, acknowledges the tenant immediately, and raises the work order with the detail already filled in.

It then handles the contractor side: matching the trade to the site, sending the access details, chasing attendance, and collecting the paperwork afterwards. The facility manager decides which contractor and what priority. Everything around that decision stops consuming the day.

Compliance runs on the same engine. Certificates are read on arrival, expiry dates tracked forward, and renewals started before anything lapses.

Start with the twenty percent that generates most calls

Before changing any process, look at where the work actually comes from.

In most portfolios a small number of assets or buildings generate a disproportionate share of reactive jobs. Identifying them turns an unbounded workload into a specific problem, and it is frequently the strongest argument for capital spend you will ever assemble.

AI Optimize builds the intake, the acknowledgements, the contractor coordination and the compliance tracking behind a facility operation. That work sits under Workflow Automation and Document Intake & Validation.