Engineering and construction firms buy workplace software for a different reason to everyone else. The office is only part of the estate, the people arriving are frequently not employees, and the record you keep has to stand up in an incident investigation. Desk booking is the easy part.
What makes this sector different
Most workplace platforms are designed around one office and one type of person: an employee booking a desk. An engineering or construction business runs a head office, project offices, depots and live sites, and the population moving through them includes subcontractors, inspectors, clients and delivery drivers.
That changes the requirement from “who booked a desk” to “who was on this site, under whose authority, with what evidence”.
| Need | Typical booking tool | What the sector requires |
|---|
| Population tracked | Employees | Employees, subcontractors, inspectors, visitors |
| Unit of reporting | The individual | The contractor company |
| Pre-arrival evidence | None | Insurance, competency, RAMS or SWMS |
| Authorisation | A booking | A permit to work with a validity window |
| Sites covered | One office | Head office, project offices, depots, live sites |
| Record purpose | Utilisation reporting | Audit and incident evidence |
The three things to get right
First, one list across every site. If each project office runs its own process, you cannot answer a portfolio-level question, and head office will eventually be asked one.
Second, company-level records. Insurance and competency belong to the contractor company with an expiry date attached, so a lapsed certificate surfaces before the person arrives rather than after an incident.
Third, the roll call has to include contractors. Sites that track them separately discover the gap during a drill, when nobody can say how many were on site.
What the research says about the office half
The site half of the estate runs on compliance evidence, but the office half follows the same trends as every other sector. Gensler’s Global Workplace Survey 2025 reports in-person collaboration time rising across its 15-country panel, which matches how engineering delivery actually works: design reviews, bid war rooms and project kick-offs are group events. The office that supports them needs bookable project space more than rows of desks.
That argues for treating project offices as elastic: a core of fixed space, a bookable pool that scales with the project pipeline, and utilisation reporting that tells the board which regional offices are earning their cost of occupancy as portfolios shift between sites.
What IT will ask before it goes live
Single sign-on, user provisioning, where the data is stored, and what happens when the connection drops on a site with poor coverage. That last one is specific to this sector and is worth asking about early, because a sign-in system that fails offline is a sign-in system that will be bypassed.
Where to start
Take one site and answer this: who was here on a given date last month, from which contractor, inducted when. Whatever you cannot answer in ten minutes is the gap, and it will be the same gap at every other site.
The contractor compliance pack is the checklist behind this.
References
General information, not legal advice. Confirm what applies to your jurisdiction, sector and site.