Separate arrival, induction, entry and permission to work
For warehouse contractor sign-in, use this operating rule: record the arrival, verify the induction evidence, obtain an entry decision, and leave permission to start maintenance work to the designated work-authorizing owner. If evidence is expired, missing or mismatched, keep the decision pending rather than treating a previous visit as approval.
This is a recommended procedure for local approval, not a universal legal standard. Have your facilities, safety, security and contractor-management owners set the accepted evidence, expiry periods, refresher triggers, approval authority and waiting arrangements. The applicable requirements for your particular site and task remain unknown until those owners confirm them.
### Keep these checks separate
| Check | Recommended question | Record the outcome as |
|---|---|---|
| Identity | Does the person presenting match the expected contractor and the induction record, using the locally approved identity-check method? | Matched, unresolved or rejected |
| Induction validity | Does verified evidence cover this person, destination site, relevant scope, required version and planned visit period? | Current and matching, expired, unverified, mismatched or expiring during visit |
| Authorization to enter | Has the locally designated entry approver permitted entry to a named destination under stated restrictions? | Pending, approved, deferred or declined |
| Authorization to work | Has the designated work owner completed the separately required work approvals? | Not authorized, pending or separately authorized with a reference |
An induction record or visitor badge must not be used as a substitute for any separately required permit, competency check or task-specific approval. The evidence behind this distinction is specific: Great Britain’s HSE workplace-transport guidance calls for contractor competence and qualification checks, while its COSHH guidance describes a permit-to-work as authorization for specified people, work and time, with defined precautions. Neither function should be collapsed into this article’s proposed sign-in check. HSE: Managing contractors; HSE: Permits to work.
For construction work in Great Britain, HSE says induction should address the particular site, its risks and controls. That construction guidance is not a blanket statement that every warehouse maintenance visit falls under construction requirements. HSE: Site rules and induction.
Name the verifier, decision owners and waiting points
Recommended local setup: complete this responsibility list before asking gatehouse staff to resolve exceptions. Replace every role with a named person or staffed duty position, an approved contact channel and a backup.
| Proposed role | Responsibility |
|---|---|
| Gatehouse operator | Match the arrival to the expected visit, perform approved identity checks, open the exception record and communicate the waiting instruction |
| Induction verifier | Check the controlled induction register or confirm evidence with its authorized custodian; report the person, site, scope, version and validity result |
| Induction policy owner | Decide what induction or refresher action is needed under site policy; resolve ambiguous scope, versions and validity rules |
| Entry approver | Approve, restrict, defer or decline entry after receiving the verification result |
| Work-authorizing owner | Resolve competency, permit and task-specific approvals through the separate work-control procedure |
| Records owner | Approve evidence storage, access permissions, retention and disposal arrangements |
One person may hold multiple roles if locally authorized, but record the verification, entry decision and work authorization separately. Do not assume the contractor’s host has authority to waive an unmet requirement.
### Give the verifier a specific question
Ask: “Does this record cover this identified person at this site for this task and visit window under our current policy?” Check the record reference, issuing source, induction version, covered site and scope, completion date, and validity dates where applicable. Compare the result with the planned arrival and departure—not just the arrival time.
Where a date or scope is absent, record unknown and ask the induction policy owner to interpret the requirement. Do not invent an expiry date, assume unlimited validity, or use a screenshot without whatever verification your policy requires. Set refresher triggers locally, including how to handle changed induction content, site conditions or task scope.
Also name the approved pre-entry waiting point and any separately approved induction-room route. If no suitable waiting arrangement is available, use the locally approved defer-or-reschedule process rather than improvising a location.
Run the induction-status decision tree
Recommended gatehouse decision tree: begin with the identity match. If identity is unresolved, pause the induction decision and refer it through the approved identity-exception process. Keep the contractor at the designated pre-entry waiting point pending instructions.
Once identity is matched, ask in sequence:
- Can the record be verified? If not, use the missing-evidence branch.
- Does it cover the destination site, relevant scope and required version? If not, use the mismatch branch.
- Is it current under site policy? If not, use the expired branch.
- Will it remain valid for the planned visit? If not, use the mid-visit-expiry branch.
- Are all those checks satisfied? Use the matching-current-record branch, then obtain the separate entry decision.
If several problems exist, record each one; resolving an expiry does not resolve a site mismatch.
| Branch | Who verifies the evidence? | Who decides, and what happens next? | Where does the contractor wait? |
|---|---|---|---|
| Matching current record | Induction verifier confirms person, site, scope, version and visit-period coverage against the accepted source. | Entry approver accepts, restricts or declines the visit after the remaining local entry checks. Work owner separately decides whether work may start. | Approved pre-entry waiting point until entry is authorized; then only the named destination or work-owner handoff point under local rules. |
| Expired record | Induction verifier confirms the expiry against the source and local validity rule. | Induction policy owner specifies the required renewal or refresher. Entry approver holds or defers entry, or authorizes a restricted induction-only visit if local rules permit it. Reverify completed evidence before a new entry decision. | Pre-entry waiting point; move to an induction room only through a separately approved route and admission arrangement. No maintenance-area access on the old record. |
| Missing or unverifiable evidence | Induction verifier contacts the authorized record custodian through an approved channel. Treat an inaccessible record as unverified, not as proof that induction never occurred. | Induction policy owner determines the accepted verification or induction route. Entry approver holds or reschedules if the required evidence cannot be established. | Designated pre-entry waiting point, or depart under the local rescheduling procedure. |
| Another site, scope or unacceptable version | Induction verifier compares the recorded coverage with the actual destination and task. | Induction policy owner determines the missing site- or scope-specific content; work owner reviews any task implications. Entry approver holds, redirects or permits an induction-only visit under local policy. Recheck after resolution. | Pre-entry waiting point; an approved induction location only after a specific restricted-entry decision. |
| Validity ends during the planned visit | Induction verifier confirms the validity endpoint and planned visit end. Ambiguous date-only expiry goes to the policy owner. | Induction policy owner confirms the rule; entry approver and work owner agree a permitted plan: renew first, reschedule, or shorten the visit if policy allows and the work owner approves the revised work plan. Record the boundary and who monitors it. | Pre-entry waiting point until the plan is approved. If admitted, use only approved locations and arrange the work-owner-managed return or departure before the permitted boundary. |
An escort is not an exception-approval mechanism. Under this proposed procedure, an escort may implement an approved movement restriction but cannot replace an unmet requirement. HSE’s Great Britain construction guidance permits a less detailed induction for escorted visitors, proportionate to their exposure; that statement should not be treated as permission for a maintenance worker to bypass the induction or work controls applicable to their task. HSE: Site rules and induction.
For inaccessible electronic evidence, pair this procedure with the warehouse sign-in outage checklist. Use only a locally approved alternative verification route; do not turn a recording fallback into an approval bypass.
- Start: identify the visitMatch before assessing validityRecommended procedure: match the person, employer, destination and planned task to the record. Leave unresolved identity pending.
- Matching and currentCurrent record → entry decisionRecommended procedure: verify person, site, scope, version and visit-period coverage; then obtain the named entry approver's decision.
- Evidence exceptionExpired or unverified → hold and resolveRecommended procedure: verifier checks the accepted source; policy owner identifies the required action; entry approver holds or defers. Wait at the locally approved pre-entry point.
- Coverage exceptionWrong site or scope → resolve the gapHSE's Great Britain construction guidance calls for site-specific induction. Recommended application: have the policy owner resolve mismatched coverage before the entry decision. HSE: Site rules and induction.
- Time exceptionExpires during visit → agree the boundaryRecommended procedure: policy owner confirms validity rules; entry and work owners agree renewal, rescheduling or a permitted shorter visit. Name the person monitoring the boundary.
- Separate work decisionEntry approval ≠ work releaseHSE describes permits-to-work as authorization for specified people, work and time. Recommended procedure: keep required permits and other work approvals separate from sign-in. HSE: Permits to work.
Copy this induction-exception worksheet
Copyable editorial worksheet: use one record per contractor visit or linked exception. Enter unknown for unresolved information and not applicable, confirmed by [owner] where appropriate. Do not leave a blank that could be mistaken for a completed check.
```text
Visit / exception reference:
Arrival date and time:
Contractor name and identifier:
Employer:
Identity-check outcome and checker:
Visit site and destination area:
Planned task / work-order reference:
Planned visit start and end:
Induction record reference:
Induction version:
Record's covered site and scope:
Completion date:
Valid from / valid until, where applicable:
Accepted evidence source / controlled reference:
Verifier name, role and verification time:
Verification result:
Induction policy owner and determination:
Approving entry owner / authorized delegate:
Entry decision and decision time:
Restrictions, permitted destination and time boundary:
Approved waiting location / movement instruction:
Work-authorizing owner:
Separate work-authorization status and reference:
Unresolved issue:
Next action, named owner and due / review time:
Contractor informed by / at:
Handoff accepted by / at:
Final outcome / departure time:
```
Keep the arrival visible as an arrival even if entry is refused. In the decision field, state exactly what was approved—for example, induction-room access only; no maintenance work—rather than writing an unexplained “approved.”
For a visit with a time boundary, assign a person to monitor it and establish the locally approved response to delay. Do not rely on an assumed software alert or automatic access cutoff. Any such capability is unknown unless separately verified for your setup.
Keep evidence access separate from the general visitor log
Recommended records design, not a statement of privacy law or a software capability: keep sensitive documents outside the general visitor log. Put the operational outcome and a controlled evidence reference in the visit record, rather than attaching identity scans, medical information or complete qualification files to it.
Use a locally approved role-based access arrangement:
| Role | Recommended access |
|---|---|
| Gatehouse operator | Identity-match result, induction status, covered site and scope, relevant validity boundary, restrictions and decision contacts |
| Induction verifier | Underlying induction evidence needed to check the record and its provenance |
| Entry approver | Verification outcome and information needed for the entry decision; underlying documents only where necessary and authorized |
| Work-authorizing owner | Relevant competency and work-control evidence through the separate authorized records process |
| Records administrator | Administration and retention functions within assigned authority, without making every document generally visible |
Have the records owner approve who may view, change, export or delete each record category. For paper evidence, propose the equivalent controls: named custody, restricted storage and no unattended document copies at the sign-in point.
If your visitor log cannot provide the approved separation, keep the documents in a separate controlled repository and expose only an authorized result or reference. Set retention and disposal through the applicable local records policy; this worksheet does not establish a legal retention period.

Two hypothetical completed exception records
Both completed examples below are entirely hypothetical. Names, employers, identifiers, dates, records, locations and policy decisions are invented to demonstrate the worksheet. The validity periods are not recommended industry standards or legal requirements.
### Example A: a returning contractor with an expired induction
| Worksheet field | Hypothetical completed entry |
|---|---|
| Visit reference and arrival | EX-A; 14 October 2026, 08:10 |
| Contractor identifier and employer | Alex Reed, C-104; Alder Maintenance |
| Identity check | Matched using the fictional site's approved method; gatehouse operator Sam Lee, 08:12 |
| Visit site and task | West Warehouse, conveyor hall; planned conveyor maintenance, WO-410 |
| Planned visit | 14 October 2026, 08:30–12:00 |
| Induction reference and version | IND-W-104, version W-6; West Warehouse maintenance scope |
| Validity | Completed and valid from 1 April 2026; valid until 30 September 2026 under this fictional policy |
| Evidence and verifier | Controlled induction register; Priya Shah, induction verifier, 08:16; expired |
| Policy owner | Morgan Ellis; renewal required before maintenance-area entry |
| Approving owner and decision | Jo Grant, duty entry approver, 08:22; maintenance entry deferred |
| Restrictions and waiting | No maintenance-area access or work; remain in approved gatehouse waiting room until departure |
| Work authorization | Dana Cole, maintenance work owner; not authorized, WO-410 rescheduled |
| Unresolved issue | Current induction not completed |
| Next action | Priya to arrange renewal before the proposed return visit; review by 15 October, 15:00 |
| Communication and closure | Sam informed Alex at 08:24; Priya accepted follow-up at 08:25; Alex departed at 08:30 |
The proposed lesson: familiarity does not change the branch. Record the renewal action and owner without rewriting the old expiry or treating a previous badge as permission.
### Example B: a current induction for the wrong destination site
| Worksheet field | Hypothetical completed entry |
|---|---|
| Visit reference and arrival | EX-B; 14 October 2026, 09:00 |
| Contractor identifier and employer | Casey Brown, C-208; Birch Technical |
| Identity check | Matched using the fictional site's approved method; Sam Lee, 09:03 |
| Visit site and task | South Warehouse, packing area; sensor inspection, WO-522 |
| Planned visit | 14 October 2026, 09:30–11:30 |
| Induction reference and version | IND-N-208, version N-3; North Warehouse only |
| Validity | Completed and valid from 1 July 2026; valid until 31 December 2026 under this fictional policy; no verified South Warehouse record |
| Evidence and verifier | Controlled induction register; Priya Shah, 09:07; destination-site mismatch |
| Policy owner | Morgan Ellis; South Warehouse induction required |
| Approving owner and decision | Jo Grant, 09:15; induction-room access only through the locally approved escorted route |
| Restrictions and waiting | Approved pre-entry waiting room until collection; induction room only afterward; no packing-area access or maintenance work |
| Work authorization | Dana Cole; pending, no work release |
| Unresolved issue | Destination-site induction incomplete; operational entry and work approval still pending |
| Next action | Priya to verify completed South induction; Jo to make a fresh entry decision; Dana to resolve separate work approval; review at 10:15 |
| Communication and handoff | Sam informed Casey at 09:17; induction facilitator Robin accepted the restricted handoff at 09:20; visit remains open |
The proposed lesson: an in-date record is not enough when its coverage does not match. In this example, the escort implements a separately approved induction-only visit—it does not authorize the maintenance task.
Finish with an absent-approver and changed-task tabletop test
Recommended tabletop test: gather the gatehouse operator, induction verifier, entry approver and work-authorizing owner. Use fictional records and your actual contact list, authority matrix and waiting-location rules.
### Test an unavailable approver
Present a returning contractor with an expired induction. Make the primary entry approver unavailable, then make the first contact attempt to the authorized backup fail.
Ask staff to demonstrate:
- Who verifies the expiry and who may decide the next step?
- What approved waiting instruction does the contractor receive?
- Where is the escalation attempt recorded, and when is it reviewed?
- What happens if no authorized decision-maker responds?
- Can staff defer or reschedule without inventing a grace period or treating silence as approval?
Suggested pass condition: the entry decision remains pending or is deferred under the approved policy; a named person owns follow-up; no escort or badge is used to bypass the unresolved requirement.
### Test a task change after arrival
Start with a contractor admitted for a verified inspection task. Introduce a request to undertake an additional repair outside the recorded task scope.
Ask staff to demonstrate:
- How is the changed task reported to the work-authorizing owner before it begins?
- Who rechecks induction scope and the separate competency, permit or task-approval requirements?
- Where does the contractor wait under local rules while the change is reviewed?
- How are the original authorization, revised task, restrictions and new decision recorded without silently overwriting the earlier scope?
Suggested pass condition: the added task remains unauthorized until the relevant owners complete their review and record the applicable approvals. The work owner directs any pause or transition through the site's work-control procedure; gatehouse staff do not improvise technical shutdown instructions.
This scope check reflects the distinction in HSE’s Great Britain guidance: a permit-to-work concerns specified work and time, while workplace-transport contractor guidance calls for concerns about proposed safety arrangements to be resolved before work starts. HSE: Permits to work; HSE: Managing contractors.
Close the exercise by assigning an owner and next action to every unresolved contact, waiting-location, evidence-access or authority question.
Conclusion
Before adopting the procedure, rehearse both tabletop cases. Require staff to identify the verifier, authorized decision owner, approved waiting point and next action—while keeping entry permission separate from permission to work.
Sources
Source pages checked 24 September 2026.
Pricing and plan details can change; verify current terms with the vendor.
