Helpdesk & CAFM | Service Request Management | UKFM

The FM helpdesk is the most under-invested function on most contracts. It sits at the intersection of three things — occupier experience, service delivery and management information — and is therefore the single highest-leverage point in the operation. A poorly run helpdesk produces consistent occupier complaints (about everything, not just the helpdesk itself), opaque service performance data, and a CAFM platform full of data nobody trusts. A well-run helpdesk produces the opposite: clean ticket flow, accurate trend data, and a service that occupiers stop noticing because it works. UKFM's helpdesk and CAFM proposition is built on the assumption that this function is core to the FM operation, not a back-office afterthought.

What the helpdesk actually does

The FM helpdesk has six functions, in roughly descending order of volume: receiving and triaging reactive service requests, dispatching mobile and on-site engineers, tracking and routing statutory compliance tasks, monitoring CAFM-driven planned maintenance schedules, providing first-line information services to occupiers, and producing the management reporting that feeds tactical and strategic governance reviews. The helpdesk is the only function that touches all of these data flows, which is why its data quality determines the quality of the rest of the management information system.

24/7 vs business hours — the model decision

The first design decision on a helpdesk is the operating window. The two principal models are 24/7 in-house operation and business-hours in-house with out-of-hours overflow to a third-party shared service. The trade-offs are real and depend on portfolio characteristics. The chart below shows typical ticket volume distribution across the day for a mixed-use commercial estate — a useful data point in choosing the model.

The pattern shows what intuition would suggest: 70%+ of tickets arrive within the standard business window. The argument for 24/7 in-house operation rests on the remaining 30% — typically critical environments (data centres, healthcare, manufacturing), high-net-worth real estate where occupier expectations demand it, or estates where out-of-hours response time is a contracted SLA. For most mid-market commercial estates, business-hours in-house with out-of-hours overflow to a specialist third party is the cost-rational answer, with the overflow provider integrated into the same CAFM ticket flow so that the data trail remains continuous.

CAFM platforms — the major systems and the choice criteria

The CAFM market in the UK is dominated by a handful of major platforms, with several specialist tools at the edges. The principal systems UKFM has worked with, and the contexts in which each typically wins, are summarised below.

The choice criteria are partly about scale (Tririga and Planon for very large estates, FSI and MRI for UK commercial mid-market, CAFM Explorer for UK public sector), partly about ecosystem fit (does the client run Workday, ServiceNow, Microsoft Dynamics, and how do these integrate), and partly about the FM provider's existing platform expertise. UKFM is platform-agnostic and runs contracts on the client's CAFM where one is in place, with our preferred mid-market default being FSI Concept Evolution for new deployments.

Reactive ticket flow — the lifecycle that determines everything

Every reactive ticket follows a defined lifecycle. The stages are familiar — log, triage, dispatch, attendance, resolution, closure, occupier feedback — and the operational quality of the helpdesk is the percentage of tickets that complete the full lifecycle without information loss at any handover point. UKFM's standard performance metrics on the reactive flow are: time to acknowledge (< 15 minutes business hours, < 30 minutes out of hours), time to attend (per criticality band, P1 < 1 hour, P2 < 4 hours, P3 < 24 hours, P4 < 5 days), first-time-fix rate (target 75%+ for routine reactive), reopened ticket rate (target < 8%), and occupier satisfaction on closed tickets (sampled survey, target 85%+ satisfied or better).

The leading indicator of helpdesk health is not the headline response time numbers — it is the reopened ticket rate. Reopened tickets indicate either that the original resolution was incomplete (engineering competence issue) or that the closure was premature (helpdesk discipline issue). Either way, it is the metric that distinguishes a helpdesk that is delivering service from one that is closing tickets to hit SLA.

Statutory compliance tracking — the highest-stakes use of CAFM

The most important use of CAFM is statutory compliance tracking. Every statutory task across the regimes covered on the Hard FM page — PUWER, LOLER, Gas Safety, EICR, L8, Fire Safety, F-Gas, COSHH, asbestos surveys — generates evidence (a certificate, a checklist, a report) that has to be retained, accessible and produceable on demand. CAFM is the system of record for this evidence, the trigger for the next due date, and the audit trail of who did what when. A CAFM deployment that doesn't have statutory compliance running cleanly through it is a CAFM deployment that is failing at its primary job. UKFM's standard CAFM configuration includes a compliance dashboard at the site level showing the status of every statutory regime, the next due date, the named competent person, and the document location, all auditable in real time.

Mobile workforce dispatch

Mobile workforce dispatch — the operational coordination of engineers across multiple sites in real time — is the function where modern CAFM has materially improved on the previous generation. GPS-aware dispatch, route optimisation, mobile work-order delivery to phones and tablets, real-time status updates, photographic and signature evidence capture at attendance, parts inventory integration, and direct labour-hour capture for billing all run through the mobile app layer. The result is significantly higher engineer utilisation (typically 65–80% productive time, vs 50–60% on a paper-based dispatch model) and a cleaner audit trail. The implementation work — GIS data quality, app deployment, change management with engineering teams — is non-trivial and is often the part of a CAFM deployment where the project either succeeds or stalls.

Occupant experience — the helpdesk as the front door

The helpdesk is, for most occupants, the only direct interface with the FM service. They don't see the planned maintenance, they don't see the BMS engineering, they don't see the cleaning audit. They see whether their ticket got logged, whether someone turned up, and whether the problem got fixed. The occupant experience score on an FM contract is therefore largely a measure of helpdesk quality, regardless of how well the rest of the operation is running. UKFM's helpdesk design treats occupant experience as a primary objective: clear logging interfaces (web, mobile, phone, occasionally Teams or Slack integrations), confirmation messaging, status updates at attendance, post-resolution survey. The infrastructure is small; the discipline is the work.

IWMS — when CAFM grows up

Integrated Workplace Management Systems (IWMS) extend CAFM into adjacent domains: real estate portfolio management, lease administration, capital project tracking, space planning, occupancy analytics, sustainability reporting. The market boundary between CAFM and IWMS is increasingly fluid — Tririga and Planon are full IWMS, FSI and MRI sit at the CAFM-with-IWMS-modules end of the spectrum. For most mid-market commercial portfolios, full IWMS is overspecified; for large multi-region corporate occupiers and institutional landlords, IWMS is the appropriate scale. The choice should follow the data flows the organisation actually needs, not the platform vendor's positioning.

Implementation — why CAFM projects fail

CAFM and IWMS implementations have a poor industry success record, with a meaningful percentage of deployments either delivered late, descoped substantially from the original specification, or quietly abandoned in favour of spreadsheet workarounds. The failure modes are consistent across vendors and consultancies: under-specified data migration scope, unrealistic configuration timelines, inadequate change management with the on-site engineering teams, and the use of vendor-provided implementation partners whose incentives are misaligned with the operational outcome. UKFM's CAFM implementation methodology assumes the data migration is the primary risk, the engineering team adoption is the primary success factor, and the vendor's standard configuration is a starting point rather than a finished product. We allocate two-thirds of the implementation effort to data and adoption, and one-third to system configuration, in deliberate inversion of most vendor-led project plans.

Reporting and analytics — turning ticket data into decisions

The reporting layer on top of a CAFM platform is where ticket data becomes management information. Standard CAFM reporting tells the user what has happened — tickets logged, tickets closed, SLA performance, engineer utilisation. Useful reporting tells the user why it has happened — ticket clustering by location and asset, recurring fault signatures, trade-level mean-time-between-failures, occupier satisfaction correlated against issue type, statutory compliance trend against site age and refurbishment history. UKFM's reporting layer sits above the standard CAFM dashboards and feeds the tactical and strategic governance reviews described on the Integrated FM page. The point of the reporting is to support decisions about where to invest the next £100k of capex, not to summarise last month's activity for the file.

The helpdesk and CAFM platform are the operational and data backbone of any serious FM contract. They reward investment in process discipline, platform configuration and people, and they punish neglect more visibly than any other part of the operation. UKFM treats this function as core to FM delivery, not as overhead. If you'd like to discuss helpdesk operations or CAFM strategy for your portfolio, contact UKFM at https://ukfm.group/contact/.