Who Can Start the Machine? A Key-Control Framework for Powered Access on Shared Sites

On a shared construction or facilities site, the powered access machine is rarely short of interested parties. The principal contractor has an programme to protect, the facilities team has operations to maintain, the hire company has an asset to recover and several subcontractors have work to complete. In that environment, the key can acquire the status of a minor courtesy: handed over at the gate, left in a site office, or passed to a supervisor who happens to be on shift. That is not control. Control exists when the site can demonstrate who was authorised to start, move and operate each MEWP, and when that authority was withdrawn.

The distinction matters because a mobile elevating work platform is not a passive item of plant. Starting the machine is the first act in a chain that leads to movement, set-up and work at height. If the key is available to anyone who asks for it, the site has delegated that first act without evidence. The purpose of this framework is to make custody visible, auditable and reversible.

Map custody before the first machine arrives

Key control begins with a custody map, not a signing-in sheet. Before mobilisation, the principal contractor and facilities manager should agree which roles may hold, issue and receive keys or immobilisation codes. On a typical shared site that may include the principal contractor's plant coordinator, the facilities management supervisor, the hire company's delivery driver and the subcontractor's appointed supervisor. Each role needs a named backup, because custody that depends on one individual is fragile.

The map should record the machine by asset number, the immobilisation method, the location of the secure key point and the person authorised to release it. Where a machine uses a PIN or electronic code rather than a physical key, the same logic applies: the code is a key and should be issued, recorded and withdrawn in the same way. The hire agreement and the site's permit-to-work arrangements should align on this point. A key cabinet that sits outside the permit system is an uncontrolled key cabinet.

Make immobilisation the default state

The safest key is the one that is not available. Sites should treat immobilisation as the normal condition of a parked MEWP, not as an additional measure for high-risk periods. That means keys returned to a secure cabinet at the end of each shift, battery isolators switched off where the manufacturer permits, control panels locked and, where fitted, PINs or codes reset or withdrawn.

This is more than housekeeping. A machine left immobilised and clearly signed as such is harder to start inadvertently and easier to account for at handover. The site should also decide who can override an immobilisation and under what circumstances. That authority should sit with a named role, be recorded in the site rules and be reviewed when the subcontractor chain changes.

Where keyless systems are used, the risk does not disappear; it moves into code management. Shared codes, generic PINs and codes that remain active after an operative leaves site are common weaknesses. The site should maintain a code register, change codes at defined intervals and whenever custody changes, and avoid issuing a code to a company rather than to a named, competent person.

Out-of-hours handover is the weakest link

Shared sites rarely stop neatly at 17:00. Night shifts, weekend works, security presence and early deliveries all create handover points where key custody can quietly break down. A common failure is to leave keys with site security because security is present, without confirming that security has the competence, authority and instructions to issue them. Holding a key is not the same as controlling its issue.

A defensible out-of-hours handover records the time, the machine asset number, the person handing over, the person receiving, the immobilisation state and any damage or defect noted at the changeover. The record should be completed at the point of handover, not reconstructed the following morning. Where a key cabinet is used, a tamper-evident seal or a numbered tag can provide a simple check that the cabinet has not been opened between recorded handovers.

The same discipline applies to movement between site areas. A MEWP key that travels to a different compound, floor or building should be recorded as a transfer of custody, not merely as a movement of plant. If the machine is left in a new location, the receiving supervisor should confirm that it is immobilised and that the key has returned to the secure point.

Subcontractor change requires re-issue, not assumption

Multi-contractor sites change constantly. A subcontractor finishes a package, another arrives, a supervisor is replaced, an operative is added at short notice. Each of these events should trigger a custody review. The incoming subcontractor should be inducted into the key-control arrangements, not simply told where the cabinet is. Its appointed supervisor should be named on the custody map, and any previous holder's authority should be withdrawn before new authority is granted.

Withdrawal means more than asking for the key back. It means removing the name from the authorised list, recovering fobs or codes, updating the key cabinet record and confirming that the machine is immobilised. Where a code has been shared within a subcontractor team, the site should assume that the code is no longer controlled and change it. This is not a criticism of the subcontractor; it is the practical consequence of shared access.

A short re-issue briefing is usually enough if it is specific. It should cover the machine types on site, the location of the secure key point, the immobilisation procedure, the out-of-hours arrangements and the name of the person authorised to release keys. The briefing should be recorded against the individuals and the companies concerned.

Build an audit trail that proves control was exercised

An audit trail is not a single document. It is a set of linked records that allow a reviewer to trace a machine from delivery to demobilisation. At minimum, the site should be able to show the authorised key holders, the key issue and return log, the immobilisation checks, the out-of-hours handover sheets, the permit references for each period of work and the competence records for the operators concerned.

The test is whether the records answer three questions. Who could start the machine? When was that authority granted or withdrawn? What evidence shows the machine was immobilised when not in use? If any of those questions cannot be answered for a given day, the site has an assumption rather than a control.

A monthly sample audit is usually sufficient for most facilities and construction sites. Pick two or three machines and trace their custody across a week, including any out-of-hours periods. Look for gaps: a key issued but not returned, a handover sheet signed by someone not on the authorised list, a code that remained active after a subcontractor left. These are not administrative imperfections; they are indicators that the control framework has slipped.

A workable sequence for shared sites

In practice, the framework can be reduced to a sequence that fits alongside existing site induction and permit arrangements. Confirm the custody map before mobilisation. Agree the immobilisation standard and the secure key point. Brief every authorised holder on issue and return. Record out-of-hours handovers at the point of transfer. Review custody whenever the subcontractor chain changes. Sample the records monthly.

None of this requires a new bureaucracy. It requires the site to treat the key as a control rather than a courtesy. When the key is controlled, the question of who can start the machine has a clear answer, and the site can prove it.