What this is
What is a site access authorisation?
What is a site access authorisation?
A record that grants a named contractor worker permission to enter specified areas of a site, during specified hours, from a Valid From date to a Valid Until date. It is issued only when the prerequisites are current, induction, worker register, competency, contractor approval and insurance among them, and it carries the card number so the permission on paper and the credential in the person's pocket are the same fact.
How is it different from the site induction?
The induction (CON-008) is a knowledge gate: it evidences that a person was taught the site and understood it. The authorisation is a permission gate: it evidences that a person is allowed in, where, when and until when. Induction is a prerequisite of authorisation, never a substitute for it, and the two fail differently: a bad induction admits someone ignorant, a bad authorisation admits someone who should not be there at all.
Why does contractor access need an expiry date?
Because revocation is the step organisations forget. An access grant with no expiry depends on someone remembering to cancel it when the job ends, the contract lapses or the worker leaves the contractor, and audits of badge systems routinely find live cards outnumbering active workers several times over. An expiry makes access default to off; without one it defaults to on, indefinitely.
Scope
When is a site access authorization required?
This record sits at the gate, after the knowledge and competence records and before any task authorisation. It decides entry, and only entry; teaching, task control and removal-for-cause each live in a neighbouring template.
Use this template when
- A contractor worker has completed induction and verification and needs entry for a defined piece of work
- An existing authorisation has reached its Valid Until date and the work genuinely continues
- The scope of access needs to change: new areas, different hours, escorted to unescorted
- A returning contractor worker arrives for a new job after their previous authorisation expired
- Security or reception needs a single record tying a card number to a person, an employer, an area set and two dates
Do not use it for
- Teaching the site's hazards, rules and emergency arrangements, which is the Contractor Site Induction (CON-008) and a prerequisite of this record
- Authorising a specific high-risk task, which is the permit system, checked by the Contractor Permit Compliance Check (CON-036)
- Removing access early for cause, which is the Access Revocation Record (CON-031) that this record's closure links to
- Closing out the whole engagement, tools, materials, documentation and cards together, which is the Contractor Demobilization Record (CON-030)
- Tracking who is physically present today, which is the sign-in process and the Contractor Worker Register (CON-009), not the standing permission
Compliance mapping
Which ISO 45001 cl.8.1.4 requirements does this satisfy?
Regulation reaches contractor access from two directions: safety regimes require the host to control who works under its roof and on what conditions, and food defense regimes require the site to control who can reach product at all. The authorisation record is where both duties become a named decision.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 45001 cl.8.1.4.2 | Ensure the requirements of the OH&S management system are met by contractors and their workers before and during work | Prerequisites |
| ISO 45001 cl.7.2 | Ensure persons doing work that affects OH&S performance are competent, on the basis of training and experience | Prerequisites |
| FDA 21 CFR Part 121 | Intentional adulteration rule: mitigation strategies for actionable process steps, which in practice restrict who has unescorted access to them | Prerequisites |
| OSHA 29 CFR 1910.119(f)(4) | Safe work practices to control the entrance, presence and exit of contract employees in covered process areas | Access granted |
| CDM 2015 reg.13 | Principal contractor must take reasonable steps to prevent access by unauthorised persons to the site | Access granted |
| SQF Food Safety Code Edition 9 cl.2.7 | Food defense plan including methods to control access to the site and to sensitive processing and storage areas | Issue |
| BRCGS Food Safety Issue 9 cl.4.2 | Site security and food defence: measures to ensure only authorised personnel have access to production and storage areas | Closure |
| ISO 45001 cl.9.1.1 | Monitor and measure whether operational controls are effective, which for access means verifying grants actually end | Closure |
What it does not cover
- Contractor Site Induction (CON-008), which is the knowledge gate this record checks for currency but does not deliver; a card is not a briefing.
- Permit to work, which authorises a specific hazardous task under specific controls; being allowed through the door says nothing about being allowed to break containment on line three.
- Contractor Competency Verification (CON-010), which does the verifying; this record only confirms a current verification exists before granting entry.
- Access Revocation Record (CON-031), which handles removal for cause mid-period, with its own reasons and evidence; the closure here links to it rather than replacing it.
- Contractor Demobilization Record (CON-030), which closes the whole engagement at job end; returning one card is a line in that story, not the story.
Global
Site Access Authorization requirements by country
No jurisdiction publishes a contractor badge standard. The duty assembles itself from host liability for who is on site, process safety rules about who may enter covered areas, food defense rules about who may reach product, and employment law about who may work at all.
29 CFR 1910.119(f)(4) and (h); FSMA IA rule, 21 CFR Part 121
PSM sites must control contractor entrance, presence and exit in covered process areas; food facilities must mitigate insider access to vulnerable process steps.
On an ammonia refrigeration food plant both regimes apply at once, and the access record is the evidence line for each: who could enter the machinery room, and who could reach exposed product.
CDM 2015 reg.13; HSWA 1974 s.3; Immigration, Asylum and Nationality Act 2006
Construction hosts must prevent unauthorised access; general s.3 duties make the host answerable for contractor exposure; right to work checks carry civil penalties per illegal worker.
The right to work field is not bureaucracy: where agency labour is involved, the record of who checked, or of reliance on the agency's check, is what the penalty regime turns on.
Framework Directive 89/391/EEC art.10; national site security and employment law
Shared-workplace information duties are harmonised; physical access control and worker eligibility checking are national matters.
Multi-country operators should treat this template's prerequisite list as the superset and let each site map its national checks onto the same gate.
Provincial OHS acts with prime contractor regimes; Safe Food for Canadians Regulations
The prime contractor coordinates who is on a multi-employer site; federal food licensing expects preventive controls that include site security.
Access records are the artefact a prime contractor produces when asked how it knew, on any given day, who was working under its coordination.
Model WHS Act s.19; state security of critical infrastructure and food safety rules
PCBU duties extend to controlling the workplace and the workers whose activities it influences, contractors included.
The narrow grant is the defensible one: an authorisation showing areas, hours and escort status is direct evidence the PCBU exercised the control the Act assumes it has.
ISO 45001 cl.8.1.4; GFSI-benchmarked schemes (BRCGS cl.4.2, SQF cl.2.7)
Safety certification requires contractor control before and during work; food certification requires demonstrable site security and food defence.
GFSI auditors increasingly reconcile the badge system against the contractor register on site, and orphaned live cards are the finding that writes itself.
How to complete it
How to complete a site access authorization, step by step
The form will accept a year-long, site-wide, twenty-four-hour grant issued against an expired induction, and score it badly. The judgement calls are the ones that keep such a record from ever being signed.
The Prerequisites section is pass or fail. Induction expired, not on the register, insurance lapsed: each of these is a stop, not a note, and issuing anyway with a comment is the programme announcing its gate is decorative. The two soft options, insurance Expiring and competency Partly, are for grants that will end before the lapse; if the Valid Until date runs past the insurance expiry, Expiring was a No.
Areas Authorised, hours, escort status and lone working are scored so the narrow option wins, deliberately. Unescorted site-wide, twenty-four-hour access exists in the picklists because sites genuinely grant it, and the zero score is the template's opinion of that. Every widening should trace to the scope of work, and someone should be able to say which job needs the freezer plant room at 3am.
Valid Until is the control the rest of the record exists to serve. Date it to the work's planned end plus a sensible margin, never to year-end for convenience, and set Automatic Expiry wherever the badge system supports it, because a card that dies by itself does not depend on anyone's memory. Extending a live grant is cheap; retrieving a forgotten one is the thing that never happens.
Card Returned and Access Revoked are separate facts and the closure needs both: a returned card can leave a live credential in the system, and a revoked credential can leave a card in a pocket that still opens doors at sites with offline readers. If access ended early for cause, link the Access Revocation Record ID rather than burying the reason here, because the reason will matter at the next award decision.
What auditors find
Most common site access authorization findings
Access findings are the easiest in the contractor domain to generate, because the evidence is mechanical: pull the live card list, pull the contractor register, and diff them.
| Finding | Clause | What fixes it |
|---|---|---|
| Live access held against an expired induction; prerequisite recorded as Expired but card issued anyway. | ISO 45001 cl.8.1.4.2 | Make induction currency a hard block on issue and on renewal, enforced by the system rather than the issuer. |
| Valid Until dated twelve months out for work scoped in days. | FDA 21 CFR Part 121 | Date the grant to the job's planned end plus margin, and renew if the work genuinely runs on. |
| Cards never returned at job end; closure section blank on the majority of authorisations. | BRCGS Food Safety Issue 9 cl.4.2 | Reconcile live cards against open authorisations monthly and chase every orphan to a returned card or a revocation. |
| Automatic expiry marked No with no compensating manual revocation process in evidence. | ISO 45001 cl.9.1.1 | Enable time-limited credentials in the badge system, or name an owner and a trigger for manual revocation. |
| Unescorted site-wide access granted for work confined to one plant room. | OSHA 29 CFR 1910.119(f)(4) | Restrict Areas Authorised to the areas the scope of work names, and record the justification for anything wider. |
| Identity recorded as Assumed; card issued against a name nobody checked. | SQF Food Safety Code Edition 9 cl.2.7 | Verify photographic identity at first issue, every time; an unverified credential defeats the entire food defense case. |
| Insurance marked Expiring treated as a pass on a grant that outlives the policy. | ISO 45001 cl.8.1.4.2 | Cap Valid Until at the earliest expiry among the prerequisites, insurance included. |
| Background check marked No for unescorted access to exposed product areas. | FDA 21 CFR Part 121 | Let the food defense plan define which areas require the check, and escort anyone who has not cleared it. |
| Lone working recorded as With controls, with the controls stated nowhere. | ISO 45001 cl.8.1.1 | Name the controls, check-in cadence, monitored alarm or buddy rule, on the record or in a linked arrangement. |
| Entry logs show badging outside authorised hours with no reconciliation or escalation. | OSHA 29 CFR 1910.119(f)(4) | Reconcile entry logs against Hours Of Access periodically and treat out-of-hours entry as a reportable exception. |
Case in point
Case in point: the forty cards and the twelve workers
A food manufacturer preparing for its BRCGS audit ran, for the first time, a reconciliation between its badge system and its contractor programme. The contractor register showed twelve workers with current jobs on site. The badge system showed forty-one live contractor credentials, several with site-wide access, the oldest issued four years earlier to an electrician whose employer no longer traded. Nobody could say which of the twenty-nine orphans still had a physical card.
The trail was easy to read in the authorisation records. Valid Until dates were set to 31 December by habit, whatever the job length. The closure section was completed on fewer than one record in five, and where it was, Card Returned was ticked while the credential stayed live in the system, because reception took cards and nobody told security. The prerequisites had been checked diligently at issue; the programme's whole weight sat on the front of the record and none on the back.
The audit raised it under site security and food defence, and the fix was structural rather than heroic: automatic expiry switched on for every contractor credential, Valid Until capped at the job end and at the earliest prerequisite expiry, and a monthly diff of live cards against open authorisations with a named owner. Six months later the reconciliation ran to zero orphans, not because people remembered, but because nothing any longer depended on their remembering.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
5 sections
- Reference
- CON-013
- Archetype
- Record
- Record ID
- SAA-2026-000
- Scoring
- Not scored
- Direction
- n/a
- Singleton
- No
- Basis
- ISO 45001 cl.8.1.4
- Links
- Links Vendor, Worker, Site
- Tags
- Contractor, Access
- Sections
- 5
- Fields
- 42
- Follow up fields
- 0
- Repeating sections
- 0
- Links out
- 4
Header
12 fieldsAuthorization ID*
Auto sequence. Format SAA-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Contractor*
Vendor ID*
Format VEN-0000.
Links to FDN-005 Vendor ID
Access Is Granted, Not Assumed
The card opens specific doors for a specific period. A permanent unrestricted pass issued to a contractor two years ago is a security and safety exposure.
Worker Name*
Employer*
Access Type*
Prerequisites
9 fieldsInduction Complete And Current*
- Yes3 pts
- Expired0 pts
- No0 pts
Induction ID
Links to CON-008 Induction ID
On Worker Register*
- Yes3 pts
- No0 pts
Competency Verified*
- Yes3 pts
- Partly1 pt
- No0 pts
Contractor Approved And Current*
- Yes3 pts
- Expiring1 pt
- No0 pts
Insurance Current*
- Yes3 pts
- Expiring1 pt
- Lapsed0 pts
Right To Work Confirmed
- Yes3 pts
- By agency only1 pt
- No0 pts
Identity Verified*
- Yes3 pts
- Assumed0 pts
Background Check Where Required
Food defense requirements may apply to anybody with unescorted access to production.
- Yes3 pts
- Not required3 pts
- No0 pts
Access granted
8 fieldsAreas Authorised*
Escorted Or Unescorted*
- Escorted3 pts
- Unescorted in agreed areas2 pts
- Unescorted site wide0 pts
Hours Of Access*
- Day shift only3 pts
- Extended hours2 pts
- Twenty four hours0 pts
Out Of Hours Access*
- No3 pts
- With notification2 pts
- Unrestricted0 pts
Lone Working Permitted*
- No3 pts
- With controls1 pt
- Unrestricted0 pts
Valid From*
Valid Until*
Automatic Expiry Set*
Time limited cards expire by themselves. Manual revocation is the step that gets forgotten.
- Yes3 pts
- No0 pts
Issue
6 fieldsCard Number*
Issued By*
Card Rules Explained*
- Yes3 pts
- No0 pts
No Sharing Or Lending Explained*
- Yes3 pts
- No0 pts
Lost Card Process Explained*
- Yes3 pts
- No0 pts
Return On Completion Explained*
- Yes3 pts
- No0 pts
Closure
7 fieldsCard Returned
- Yes3 pts
- No0 pts
Access Revoked
- Yes3 pts
- Pending1 pt
- No0 pts
Revocation Record ID
Links to CON-031 Record ID
Issued By*
Signature*
Worker*
Second Signature*
CON-013 · record IDs look like SAA-2026-000 · Links Vendor, Worker, Site
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The record is a gate that works on the day it is signed. What fails is time: the prerequisite that expires mid-grant, the job that ends without telling security, and the badge system drifting away from the register nobody diffs.
Holds each authorisation against its prerequisite records, induction, register, competency, approval and insurance, and surfaces any live grant whose weakest prerequisite has lapsed.

Watches Valid Until dates and prerequisite expiries across the population, warns the contract owner before a grant dies mid-job, and chases the closure fields on every authorisation whose work completion record has landed.
Ties the access scope to the food defense plan, so unescorted grants into product areas without the checks the vulnerability assessment requires show up as exceptions before an auditor finds them.
Cross-references authorised areas and hours against permits and entry logs, flagging out-of-hours badging and access into covered process areas that no permit explains.
This template lives in KnowContractor — contractor management. Prequalification, approval, induction, permits and performance.
Meet KnowContractor→Glossary
Site Access Authorization definitions and key terms
- Access authorisation
- A grant of entry to a named person for defined areas, hours and dates, conditional on stated prerequisites; a permission with an expiry, not a status.
- Escorted access
- Entry permitted only in the continuous company of an authorised host, which substitutes supervision for the checks unescorted access requires.
- Unescorted access
- Entry without accompaniment, which in food defense terms makes the holder an insider and pulls identity, background and area restrictions into scope.
- Food defense
- Protection of food from intentional adulteration; distinct from food safety, which addresses unintentional contamination, and the reason access control is a certification topic.
- Actionable process step
- A point in a food operation where intentional contamination could cause wide-scale harm, identified in a vulnerability assessment under the FSMA IA rule; access to these steps is what mitigation strategies restrict.
- Automatic expiry
- A credential configured to stop working at a set date and time without human action, converting revocation from a remembered task into a default.
- Revocation
- The active removal of access before its expiry, for cause or on early completion; recorded separately (CON-031) because the reason carries forward to future awards.
- Right to work
- The legal eligibility of a person to work in the jurisdiction, checked by the employer or agency; hosts recording who performed the check are recording where the penalty would land.
FAQ
Frequently asked questions about site access authorization
We already do inductions. Why keep a separate authorisation record?+
Because they answer different questions. The induction proves a person understood the site; the authorisation proves they were permitted in it, where and until when. An inducted worker whose contractor's insurance has lapsed should be refused at the gate, and only the authorisation record can show that refusal happening. Sites that merge the two end up with neither question answerable.
How long should an authorisation run?+
The length of the job plus a working margin, and never past the earliest expiry among its prerequisites. A resident contractor on a rolling contract still gets a dated grant, renewed on a cycle that forces the prerequisites to be re-checked, quarterly or semi-annually in most programmes. The year-end date chosen for admin convenience is the single habit that produces orphaned access.
Should the default be escorted or unescorted?+
Escorted, until there is a reason. Unescorted access is the earned state: induction passed, identity verified, background check where the food defense plan requires it, and a scope of work that genuinely needs free movement. The template scores unescorted-site-wide at zero because it is a decision that should hurt a little to record.
Who owns this record, security or the contract owner?+
Both, in sequence, and the record separates them deliberately. The contract owner owns the decision, whether the prerequisites are met and what scope the work needs; reception or security owns the execution, the card, the rules briefing and the closure. When one party does both, the check that suffers is whichever one they understand less.
What happens if a prerequisite lapses mid-period?+
The authorisation lapses with it. A grant is only as current as its weakest prerequisite, so an insurance lapse or an induction expiry mid-period should suspend access, not annotate it. Practically this means the Valid Until date is capped at the earliest prerequisite expiry at issue, and a lapse event triggers revocation through CON-031 rather than a note.
Do we really need background checks for contractors?+
Where the vulnerability assessment says so, yes; as a blanket rule, no. The FSMA IA rule and the GFSI schemes push background checks for people with unescorted access to exposed product and other actionable process steps. The template's Not required option scores the same as Yes precisely so sites record the food defense decision rather than defaulting to whichever answer avoids paperwork.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Contractor Onboarding and Management
Contractor Prequalification Questionnaire
Collects a contractor's safety, insurance, training and performance information before they are approved
Contractor Safety Statistics Review
Reviews a contractor's injury rates, citations and experience modifier over recent years
Contractor Risk Classification
Classifies a contractor by the risk of the work they do, from low risk services to high risk construction
Contractor Approval Record
Records the decision to approve a contractor to work on site
Contractor Safety Program Review
Reviews the contractor's own written safety programme against your requirements
Subcontractor Declaration
Records any subcontractors a contractor intends to use
More in Site Induction
Contractor Site Induction
Introduces a contractor to your site rules, hazards, emergency arrangements and permit requirements
Contractor Worker Register
Lists every individual contractor worker on site, with their induction and certification status
Contractor Competency Verification
Verifies that contractor workers hold the tickets and training their work requires
Pre-Work Meeting Record
Records the meeting held before work starts, covering scope, hazards, controls and coordination with site activities
Contractor Method Statement Review
Reviews the contractor's proposed method of work and its risk assessment

Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 45001:2018 clauses 8.1.4, 7.2 and 9.1.1
- OSHA 29 CFR 1910.119(f)(4) and (h), Process Safety Management standard (US)
- FDA 21 CFR Part 121, mitigation strategies to protect food against intentional adulteration (US)
- BRCGS Food Safety Issue 9, clause 4.2 site security and food defence
- SQF Food Safety Code Edition 9, clause 2.7 food defense and food fraud
- Construction (Design and Management) Regulations 2015, regulation 13 (GB)
- Immigration, Asylum and Nationality Act 2006, right to work checks (UK)
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.