For whom and why this matters
The HSE manager is usually responsible for who enters the site and with what permissions. Access requests submitted from the contractor portal reach the plant at any time of day, and the decision is limited to the service administrator role. If this role is not planned, the request waits and the contractor stands at the gate.
The recommendations below help to share responsibility so that decisions are quick and control stays with the people who know the plant.
Recommendation 1: name who holds the service administrator role on each shift
A new request creates a notification for the service administrator role, and only this role may approve, reject or resend a decision. In a plant working three shifts, the role must therefore be assigned to at least one person per shift, or a rule for substitutes must be set.
A practical pattern: one main person from HSE, one deputy from security and one from the maintenance department. Record this in the duty roster and in the job instruction, so that holidays do not block the decision path.
Sample staffing of the role across three shifts
Recommendation 2: separate the substantive assessment from the decision in the system
The decision in the system is a single click, but the substantive assessment can be complex: whether the scope of work matches the contract, whether the firm is known, whether the authorisations are adequate. We recommend that the operator (security, reception, coordinator for external firms) prepares the assessment, and the service administrator approves it.
The LivePermit SSO panel in the authorisations and training module shows the integration status, the number of active passes, linked accounts, requests waiting for a decision, and errors from the last 7 days. This is the screen worth using at the start of every shift.
- Integration status.
- Number of active passes.
- Number of linked accounts.
- Requests waiting for a decision.
- Errors from the last 7 days.
Recommendation 3: 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. This means that approving the request does not replace checking the documents.
Set in the plant the moment of verification: at approval, at the first visit, or before the first hazardous work. Record who changes the status of an authorisation to confirmed and on the basis of which document.
Recommendation 4: reduce manual decisions where the risk is low
For firms linked to the plant, requests can be accepted automatically, but only for new e-mail addresses, and only after a configuration variable is switched on. The decision to switch it on belongs to the HSE manager together with IT, not to the service administrator alone.
We recommend that automation applies to contractors with stable cooperation, and that all hazardous work still requires a permit from a separate workflow. A request for access to the plant is not a work permit.
Recommendations 5 and 6: resending and reporting
An undelivered decision to the portal is saved with the request, together with the error description, and it can be resent from the panel. This is a task for the service administrator, so include it in the shift routine: at the start, check whether any decision needs resending.
Once a month review the statistics: how many requests came in, how many were approved, how many rejected, and how many decisions needed resending. The findings from the review go into the HSE protocol and help to judge whether the role is overloaded.
Checklist
Video
Frequently asked questions
Can a security operator approve a request?
Only if they hold the service administrator role. Decisions are limited to that role.
Does approving a request mean consent to hazardous work?
No. It is consent to access the plant. A work permit is issued in a separate workflow.
How do I learn about a new request?
A new request creates a notification for the service administrator role, and the number of requests waiting for a decision is shown in the integration panel.
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