InnerWeb
Skip to main content

Consent scopes in a contractor access request

An access request from the portal accepts authorisation, training and medical data only when the matching consent scope is ticked. No consent means no such data in the request. The practices below help contractors and the plant agree on the minimum needed for a decision.

3
consent scopes in a request
Source: card
30 days
warning threshold for an expiring training
Source: card

Rule: data only with consent in a given scope

The contractor portal lets a person decide what goes into the request. There are three scopes: authorisations, training and medical checks. The request accepts data from a given scope only when the matching consent is ticked, and no consent means that these data are absent from the request.

For the plant this is a good basis for data minimisation: it collects no more than necessary, and on the contractor's side every item is shared knowingly. In practice, however, it means that a request without consent to training data cannot be read as proof that there is no training. It is simply a request in which that information is missing.

Practice 1: agree the minimum set with the contractor before the request is submitted

For each type of work the plant should have one sentence saying what is needed to enter the site and what is needed to start hazardous work. Entering the site usually requires only identity, the firm and the scope of the visit. Qualification authorisations are needed for work, not for entry.

Give contractors a short table: type of work, required authorisations, training and medical checks. The contractor will then tick only the consent scopes that matter, and the operator will not need to ask about superfluous items.

  • For entry: identity, firm, scope of the visit.
  • For work: qualification authorisations.
  • For work in special conditions: medical checks and training.

Practice 2: treat authorisations in a request as subject to verification

Authorisations from an access request are created with a status pending verification, not as confirmed. Training and medical checks remain in the content of the request. The plant should not admit anyone to work on that basis without checking the documents.

Good practice is to set who changes the status to confirmed, and when. We recommend that someone from HSE or the department responsible for qualifications does this, after seeing the document, and that a trace of the verification is kept in the system.

Practice 3: no consent is a conversation, not a refusal

A request without data on training or medical checks should not be rejected automatically. The operator may approve access to the site and make work requiring qualifications subject to later completion.

If the plant requires data that the contractor has not shared, state this in the reply and indicate the scope for which consent is needed. Set this in the rules for external firms, so that decisions are repeatable.

Practice 4: the person and their data in the pass

The person's interface for the portal returns a list of trainings with the status to be done, done, expiring within 30 days or less, and expired, a personal link to the training, and a QR pass with information on whether a health declaration is required today.

In this way the contractor sees in the portal what is missing and does not need to call reception. Encourage contractors to tick the consents that let the system show what expires within 30 days or less.

Practice 5: document the consent rules

For audit purposes a short document is useful: which consent scopes the plant treats as required for each type of visit, who verifies the documents, and after what period the data are deleted. The document should comply with the plant's data protection policy and be agreed with the data protection officer.

We do not promise full compliance with the law in it. We record what evidence the plant collects and how it protects it. This supports meeting the requirement, but it does not replace a legal assessment.

Checklist

Video

Frequently asked questions

What does a request contain if the contractor does not tick consent for medical checks?

It contains no medical check data. The system does not accept data from a scope without consent.

Are authorisations from a request confirmed straight away?

No. They are created with the status pending verification, and a person confirms them after seeing the document.

Will the contractor see that a training is about to expire?

Yes. The training list shows the status expiring within 30 days or less, as well as expired trainings.

Sources

Let's talk about the contractor portal at your plant

We will show you on a live example how a contractor's request reaches the operator and how the plant keeps full control over entry to the site.

Let's talk