What this is
What is a shift and crew register?
What is a shift and crew register?
A shift and crew register records every shift pattern operated at a site, the area each shift covers, its start and end times, headcount, management structure and rotation direction. It is the master data that lets other records be grouped by the crew that actually did the work rather than only by site.
Why does this need a separate register rather than living in the site record?
A site can run several shift patterns across several areas at once, each with its own manager, rotation and fatigue profile. Folding that into the site register would flatten differences that matter: two shifts on the same site can have entirely different exceedance and fatigue signatures, and the register exists to keep that visible.
Who maintains the register?
HR together with production. HR owns the people and rostering side; production owns whether the pattern actually matches how the area runs day to day. A register maintained by one function alone tends to drift from the other's reality within a few months.
Scope
When is a shift and crew register required?
This register is foundational master data, not a record of an event. Using it to log a single shift's staffing, or to hold information belonging to the worker or site record, produces duplication that falls out of sync with its source.
Use this template when
- A site is being set up and its shift patterns need to be defined for the first time
- A new record is needed; each one gets its own ID in the form CREW-2026-000
- You are running the Fatigue and Shift Work programme and this register is one of its steps
- A shift pattern, area coverage, headcount or rotation direction has changed and the register needs to reflect it
- A linked record needs this one to exist: it feeds the competency matrix and fatigue screening
Do not use it for
- Site and Location Register, which holds every site, building, area and zone the organisation operates, independent of who staffs them
- Worker Profile, which holds the individual record for each worker, including role, department and start date, rather than the shift structure they sit within
- Competency Matrix, which records what each person is qualified for and reads the crew structure from this register rather than duplicating it
- Shift Fatigue Screening, which assesses the fatigue risk of a pattern once this register has defined that the pattern exists
- Anything outside General, which belongs in the workspace that owns that process
Compliance mapping
Which ISO 45001 cl.5.4 requirements does this satisfy?
ISO 45001 does not name a shift register directly; it requires consultation, competence and hazard identification that cannot be done correctly without knowing who is on which crew, which makes this register a prerequisite rather than a convenience.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 45001 cl.5.4 | Consultation and participation of non-managerial workers, which has to be targeted at the actual crew rather than a nominal shift list | Shifts |
| ISO 45001 cl.6.1.2.1 | Hazard identification must be proactive and cover work organisation and human factors, which requires the shift pattern to be known and current | Shifts |
| ISO 45001 cl.7.2 | Competence must be determined and maintained, which depends on knowing who is actually on a crew to check against a competency requirement | Related records |
| ISO 45001 cl.8.1.1 | Operational planning and control requires the people who execute a control to be identified, not assumed | Coverage |
| ISO 45001 cl.7.5.1 | Documented information must be kept current, with a defined review point | Header |
| ISO 45001 cl.9.1.1 | Monitoring and measurement of performance, disaggregated by the group that produced it | Coverage |
What it does not cover
- Shift Fatigue Screening, which assesses the fatigue risk a defined pattern carries, once this register has established that the pattern exists.
- Competency Matrix, which records what each individual on a crew is qualified for, reading the crew membership from this register rather than restating it.
- Worker Profile, which holds the individual's role, department and employment details independent of which shift they currently sit on.
- Operations Shift Handover, which records what happened on a specific shift and what needs to carry to the next one, not the standing pattern itself.
- Manning and Labour Plan, which allocates people to a shift for a specific period, distinct from the register's job of defining the pattern that plan fills.
Global
Shift and Crew Register requirements by country
The register sits under no direct regulatory duty; its consequence is in what depends on an accurate shift and rotation record, which is where working time and night-work law engages.
Working Time Directive 2003/88/EC
Sets limits on night work and requires health assessments for night workers, defined by the shift pattern they are rostered to.
A register that misstates who works nights, or how a rotation runs, misidentifies who the night-work health assessment duty actually applies to.
Working Time Regulations 1998
Domestic implementation limiting night work to an average eight hours in 24 and requiring health assessments before and during night work.
The register's nights-included and rotation-direction fields are the practical trigger for whether that assessment duty applies to a given crew.
ISO 45001
Management system requirement for consultation, competence and hazard identification, none of which can be correctly scoped without a current crew structure.
A certification auditor examining consultation records will ask who was consulted and how that group was identified, and a stale register is a direct route to that finding.
How to complete it
How to complete a shift and crew register, step by step
The register's fields are simple to complete and easy to let drift. What makes it useful is judgement about when it needs updating and what 'coverage' actually means.
A shift added, split or retired should update the register the same day, because every fatigue screening and competency check run in the gap works from a crew that no longer exists. An annual review catches nothing a mid-year change already broke.
An area can have a shift record and still go unstaffed for part of the day if the shifts defined don't span the hours it actually runs. 'Areas fully covered' should be answered against the clock, not against whether a row exists.
Backward rotation and night inclusion are the two fields that determine whether a fatigue screening is warranted at all. Marking rotation as 'not rotating' for a pattern that in fact rotates removes the trigger that would otherwise flag it.
A matrix ID recorded once and never rechecked gives a false sense that competence has been verified. The register should be where someone actually asks whether the matrix still matches who is on the crew.
What auditors find
Most common shift and crew register findings
Findings here are rarely about a missing field. They are about a register that answers its own questions correctly while describing a crew that no longer exists.
| Finding | Clause | What fixes it |
|---|---|---|
| Shift added or changed operationally with no corresponding update to the register. | ISO 45001 cl.7.5.1 | Make the register update part of the change itself, not a follow-up task. |
| Areas marked fully covered despite hours in the day with no shift assigned. | ISO 45001 cl.8.1.1 | Check coverage against actual operating hours, not against whether a record exists. |
| Competency matrix linked but not verified against current crew membership. | ISO 45001 cl.7.2 | Re-check matrix alignment whenever the crew changes, not only at the review date. |
| Backward-rotating pattern recorded without a fatigue screening having been triggered. | ISO 45001 cl.6.1.2.1 | Route any backward-rotating or night-inclusive pattern to a screening automatically. |
| Headcount figures reflect the nominal establishment rather than who is actually rostered. | ISO 45001 cl.5.4 | Update headcount from the roster, not the position count the shift was designed around. |
| Register overdue for review, with no action raised despite the next review date having passed. | ISO 45001 cl.9.1.1 | Flag an overdue review as an open finding, not a background administrative lapse. |
Case in point
Case in point: the fatigue screening that read the wrong crew
A production site introduced a third shift on its packing line to meet seasonal demand, rostered as a backward-rotating pattern around an existing two-shift system on the same line. The change was made through the roster directly; the register, still showing the original two-shift pattern, was not updated for eleven weeks. A scheduled fatigue screening cycle then ran across all registered shifts. Because the register had no record of the new pattern, the third shift was never screened, and the backward rotation, a direct trigger for screening, went unflagged. The gap surfaced only when a supervisor asked why a shift running for over two months had no fatigue record on file.
The register had not been wrong when last updated; it had simply stopped keeping up with a change made faster than the administrative process around it. The fix was not a better screening cycle, since the cycle ran correctly against what it was given, but a rule that a roster change cannot go live without the register being updated first.
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.
4 sections
- Reference
- FDN-023
- Archetype
- Register
- Record ID
- CREW-2026-000
- Scoring
- Coverage complete
- Direction
- High is good
- Singleton
- No
- Basis
- ISO 45001 cl.5.4
- Links
- Feeds Competency matrix, Fatigue screening
- Tags
- Registry, Shift
- Sections
- 4
- Fields
- 32
- Follow up fields
- 3
- Repeating sections
- 1
- Links out
- 4
Header
8 fieldsRegister ID*
Auto sequence. Format CREW-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
Last Reviewed*
Maintained By*
Next Review Due*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Read Trends By Shift, Not Only By Site
Most performance differences on a site are between shifts rather than between areas. Without a crew structure you cannot see it.
Shifts
Repeats12 fieldsShift Name*
Pattern*
Area*
Start Time*
End Time*
Headcount*
Shift Manager*
Supervisor
Rotation Direction
- Forward3 pts
- Backward0 pts
- Not rotating2 pts
Nights Included*
- No3 pts
- Yes1 pt
Weekend Working
Fatigue Screening ID
Links to ERG-024 Screening ID
Related records
1 fieldCompetency Matrix ID
The matrix showing what this crew is qualified for.
Links to TRN-020 Matrix ID
Coverage
11 fieldsShifts Defined*
Areas Fully Covered*
- Yes3 pts
- Partly1 pt
- No0 pts
Competency Matrix Aligned To Crews*
- Yes3 pts
- Partly1 pt
- No0 pts
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
HR*
Signature*
Production Manager*
Second Signature*
FDN-023 · record IDs look like CREW-2026-000 · Feeds Competency matrix, Fatigue screening
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The register is simple to fill in once. What fails is the discipline of updating it the moment a shift changes, and the silent gap between roster reality and what the register still says.
Reads rotation direction and nights included from the register to decide whether a fatigue screening should trigger.
Checks the competency matrix against current crew membership whenever the register changes, rather than trusting a stale link.
Flags a roster change made through shift handover or manning records not yet reflected in the register it depends on.
Watches for a register past its review date or a shift change with no corresponding update, and raises it.
This template lives in General — control tower. The orchestration layer. Registries and engines every other workspace reads from.
Meet General→Glossary
Shift and Crew Register definitions and key terms
- Shift pattern
- The defined rotation, start and end times and rest structure a crew works to, such as three-shift rotating or permanent nights.
- Crew
- The group of workers assigned to a specific shift and area, distinct from the establishment or nominal headcount a shift was designed around.
- Rotation direction
- Whether a shift rotates forward (earlier to later shifts) or backward (later to earlier), with backward rotation carrying a materially higher fatigue burden.
- Coverage
- Whether every area's operating hours have an assigned shift, as distinct from whether a shift record exists somewhere for that area.
- Fatigue screening
- The assessment of fatigue risk arising from a specific shift pattern, night inclusion and rotation direction, triggered from this register rather than duplicating it.
FAQ
Frequently asked questions about shift and crew register
How current does the register need to be?+
Current as of the last actual change to a shift, not the last scheduled review. Anything reading from it, fatigue screening and the competency matrix both, inherits whatever crew structure is recorded, so a lag between the change and the update is a lag downstream.
What does 'coverage complete' actually measure?+
Whether every area's operating hours have a shift assigned, not whether a record exists for every area name. A register can look complete by row count and still leave a stretch of hours with nobody accounted for.
Does every shift pattern need a fatigue screening?+
Not every pattern, but any that includes nights or rotates backward should trigger one. Those two fields are the practical signal; a pattern with neither carries a materially lower fatigue burden and can wait for a routine cycle.
Who should be listed as shift manager versus supervisor?+
The shift manager is the accountable owner of the pattern and its output; the supervisor is present with the crew. Recording only one when both exist loses a distinction that matters when a consultation or incident needs the right person quickly.
Should the register be updated before or after a roster change goes live?+
Before, if the change will trigger a fatigue screening or affect the competency matrix. A register updated after the fact means every record generated in the gap was built against the wrong crew, the single most common failure this template sees.
Can one site have several shift and crew registers?+
No; the register is set up once per site and updated as an entry within it, with shifts repeating for each pattern and area. Splitting it into several records per site defeats the point of reading trends across the whole site by shift.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Fatigue and Shift Work
Fatigue treated as a designed risk rather than an individual failing.
Master Data and Foundations
One place for each thing, so a change updates everywhere rather than in eight lists.
Shift Management
Known problems crossing the handover, and nobody placed on a position they are not signed off for.
Used together in Fatigue and Shift Work
Contractor Fatigue and Hours Check
Checks hours worked and rest taken by contractors on extended shutdowns or overnight work
Area Ergonomic Screening
A quick first pass across a whole area to find which tasks need a full assessment
Manual Handling Screening
A rapid check of manual handling tasks to band them by risk
New Task Ergonomic Screening
Screens a new or changed task before it goes live
Shift Fatigue Screening
Screens work patterns for fatigue risk, covering shift length, rotation, breaks and consecutive days
Screening Follow Up Log
Tracks which screened tasks went on to full assessment and which did not
More in Registries
Site and Location Register
Holds every site, building, area and zone your organisation operates
Asset Register
Holds every piece of equipment, machine, vehicle and tool you track
Worker Profile
Holds a record for each worker, including role, department, site and start date
Job and Task Register
Lists the jobs and tasks people perform, so risk assessments and ergonomic assessments can be tied to real work rather than job titles
Vendor and Contractor Register
Holds every supplier, contractor and service provider you work with, including their status and approval level
Chemical and Substance Register
Lists every chemical and hazardous substance held on site, with quantity, location and hazard class
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 5.4, 6.1.2.1, 7.2, 7.5.1, 8.1.1 and 9.1.1
- Working Time Directive 2003/88/EC on the organisation of working time
- Working Time Regulations 1998 (UK), night work provisions
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.