To prove that a mobile technician can work on a site, you need an authorisation matrix linked to the person rather than the site: their valid certificates, the requirements shared across the group, those of the site where they will work and those of the client. This proof must be ready before the technician arrives.

Why do mobile technicians' authorisations create a proof problem?

Mobile technicians' authorisations create a proof problem because the person moves faster than their paperwork. Certificates are issued and tracked by the employer, while the site where the work takes place, often a client's, has to check that right to work at the moment the technician turns up at the gate.

What happens at a client site's gatehouse?

At a client site's gatehouse, authorisations are often checked under time pressure. Picture a typical situation: at 7 am, a maintenance technician arrives at a high-hazard chemical site to replace a motor starter in an ATEX zone. The security officer asks for the technician's electrical authorisation and ATEX training record. The technician shows a photo of the authorisation on a phone, two years old, but the ATEX certificate has been left at the branch office. The site's HSE manager refuses entry until the proof arrives. The branch manager is in a meeting, and the job starts two hours late. The technician was fully authorised: it was the proof that was missing.

What changes when the technician moves to another site?

When a technician moves to another site, the requirements change while the certificates stay the same. A refinery asks for its own contractor safety induction, an electrical substation requires a specific authorisation category, and a construction site expects a licence to operate a mobile elevating work platform. The maintenance company's HSE manager therefore tracks dozens of combinations of people, certificates and sites, often in one spreadsheet per client. Every new contract adds columns, and nobody is quite sure which version is current when a technician arrives at a client's site.

Why is maintenance at the heart of these issues?

Maintenance is at the heart of these issues because it exposes people to varied risks, on installations the technician does not always know. According to the European Agency for Safety and Health at Work, 15 to 20% of workplace accidents and 10 to 15% of fatal accidents are linked to maintenance operations (Eurostat data from 2006, cited by the French INRS in 2023). Meanwhile, the outsourced industrial maintenance market in France was estimated by Xerfi to exceed 10 billion euros in 2025: a growing share of maintenance work now takes place on client sites.


Who issues the authorisation of a technician working at a client's site?

The authorisation of a technician working at a client's site is issued by their employer, the contractor, not by the client. The client, as the host organisation, coordinates prevention: it checks certificates, explains the site's risks and can add its own access requirements on top of those set by the employer.

What is the employer's role, and what is the client's?

The employer's role is to train, authorise and keep its technicians' certificates up to date. In France, labour law gives the employer responsibility for issuing electrical authorisations, and the NF C 18-510 standard recommends refresher training every three years. The client does not issue an electrical authorisation to an external technician. It does, however, check before the work starts that the certificates presented cover the planned tasks and the installations concerned. The two roles complement each other: if either is missing, the right to work can no longer be demonstrated. This is why the check should be planned when the contract is signed, rather than discovered at the gate.

What does the prevention plan cover?

The prevention plan is the document that organises a contractor's work on a host site under French regulations, similar in spirit to the contractor coordination arrangements familiar to UK safety teams. It must be written down when the work reaches 400 hours over twelve months, or when it appears on the official list of dangerous work. It sets out the risks, the preventive measures and the qualifications required of the people involved. In practice, it often defines the list of authorisations the site will check at the gate. Reviewing it with the branch manager before each new contract avoids surprises on the day, especially when the client has updated its own access rules.


Group, site, client: which requirements apply to the same technician?

The same mobile technician combines three levels of requirements: the common framework set by their group, the local requirements of the site where they work, and those specific to the client. A useful authorisation matrix keeps them separate, so you can see at any time which level is holding up a job.

The group, site and client table

The table below sets out the three levels of requirements for an industrial maintenance technician, with common examples and the person responsible for keeping each level up to date.

LevelWhat it setsCommon examplesWho keeps it up to date
GroupThe common framework for all technicians in the same tradeElectrical authorisation, working at height, first aid at workGroup HSE
SiteRequirements linked to the installations at the site or branchATEX zone, confined space, mobile elevating work platformSite HSE manager
ClientRequirements added by the clientContractor safety training, site induction, permit to workBranch manager, with the client's HSE team

How do you read this table for a given technician?

For a given technician, the table reads from top to bottom, as a series of conditions. The group level says whether the person can practise their trade, the site level says whether they can enter a given zone, and the client level says whether they can work for that particular client. In the gatehouse scene, the technician met the first two levels: only the proof for the third was missing at the time of the check. This reading also helps the HSE manager set priorities: a gap at group level affects every client, whereas a gap at client level only blocks one contract. Follow-ups therefore target different people.


How do you build an authorisation matrix that follows technicians from site to site?

An authorisation matrix that follows technicians from site to site starts from a common framework, adds the requirements of each site and each client, then links every piece of proof to the person. It can then answer a simple question at any time: can this technician work here, on this date?

Start from the group's common framework

The group's common framework is the foundation of the authorisation matrix. It lists, for each trade (electrical technician, mechanical fitter, automation technician), the certificates expected everywhere, along with how often they must be renewed. This shared base stops each branch from inventing its own labels: a given authorisation category should carry the same name in every region. It also makes it possible to compare branches and see where refresher training is falling behind, without multiplying files. Group HSE builds it with the technical leads for each trade, then reviews it when a standard or a client requirement changes for good.

Link each piece of proof to the person, not the site

Linking each piece of proof to the person means that the certificate, the training record and the expiry date follow the technician, whichever site they are working on. Site and client requirements are then layered on top: the matrix compares what the person holds with what the place of work requires. A technician sent to support a team in another region therefore arrives with a complete record, instead of starting from scratch in the host branch's spreadsheet. The HSE manager no longer has to copy the same certificates into several files, which reduces discrepancies between versions and saves time before each audit.


How do you make sure the proof arrives before the technician?

To make sure the proof arrives before the technician, check their authorisations when the job is scheduled, then share that record with the client site. The check at the gatehouse becomes a quick confirmation rather than a search for documents. The proof of their authorisations should arrive before they do.

Check at the scheduling stage, not at the gate

Checking at the scheduling stage means comparing the technician's authorisations with the site's requirements as soon as the job is added to the schedule. If a certificate is missing or expires before the planned date, the planner sees it straight away and can suggest another authorised technician. In Klara, this check draws on the authorisation matrix: the branch manager can see, for each scheduled job, whether the technician meets all three levels of requirements. The planner keeps the final say: the matrix highlights the gaps, and the planner chooses the solution that best suits the job and the team.

Make the right to work clear to everyone

The right to work becomes clear when everyone involved can access the same up-to-date information. Technicians can view their own certificates on their phone, with expiry dates. The branch manager filters the matrix by client to plan the week, and the client site's HSE team receives the record before the team arrives. The aim is to make the job easier: the proof travels with the technician, and it is not there to track their movements. For the client, it also saves time at the gate, since the check concerns a record that has already been verified.

Anticipate expiry dates that fall during an assignment

Expiry dates that fall during an assignment are the most common avoidable cause of a blocked job. A technician assigned for six weeks to a planned shutdown may see their electrical authorisation expire halfway through. An alert sent to the manager several weeks before the expiry date, with suggested refresher sessions, makes it possible to schedule the training before departure. The HSE manager stays in control of alert lead times, which are set according to how critical each certificate is. A rare certificate with sessions that fill up quickly, for example, deserves an earlier alert than training offered every month.


Where should you start to secure work on client sites?

To secure work on client sites, the simplest approach is to start with one family of critical jobs, such as electrical work in ATEX zones. This is where you test the group framework, the requirements of your main clients and the preparation of records before each job, before extending the approach to other trades.

The four steps of a pilot

A pilot on mobile technicians' authorisations runs in four steps, covering one branch and two or three regular clients. It works best when the branch manager, a planner and the HSE manager are involved from the start, as each knows part of the requirements.

  1. Take stock of the branch technicians' certificates, using existing files and records.

  2. List the requirements of the pilot clients, using the prevention plans.

  3. Check each job at the scheduling stage for two to three months.

  4. Measure the number of refused or delayed site entries, and the time spent looking for proof, before and after.

Connect the pilot to other authorisation projects

This pilot connects naturally with the HSE team's other projects. It extends the approach described in "How do you automate authorisation management on site?" and lays the groundwork for audits, covered in "ISO 45001 audit: what evidence of authorisation and competence should you prepare?". If choosing a tool is on the agenda, "Authorisation tracking software: 10 questions to ask before leaving Excel" helps frame the decision. For a broader view, the guide "Skills matrix: definition, examples and a method to move from completion to steering" places authorisations within the wider management of skills across all sites and trades.