What this is
What is a shift performance log?
What is a shift performance log?
A shift performance log is a running record of planned output against actual output for a production shift, broken down hour by hour rather than reported as a single shift total. It is built against ISO 9001 cl.9.1 and sits within the Shift Management programme, feeding the Daily Production Report and the Downtime Log.
What does 'plan attainment' mean as a score, and why is it scored at all?
Plan attainment is actual output measured against target for the same period, expressed as a percentage where higher is better. Scoring it forces the log to produce a number that can be trended shift over shift, rather than a narrative that reads differently depending on who wrote it.
Why is the hourly section mandatory but its reason and downtime fields aren't?
Hour, Target This Hour and Actual This Hour are required because they are the record's whole purpose: a variance for every hour, good or bad. Main Reason For Loss and Downtime Minutes are optional because a good hour has nothing to explain, but that same optionality lets a bad hour go unexplained too.
Scope
When is a shift performance log required?
This log is one step in a larger programme. Using it for work that belongs to a neighbouring template produces records hard to report on later.
Use this template when
- A shift is running now, or is about to start, and its output needs tracking against plan as it happens
- The line has a target volume for the hour and someone needs to see the gap while the hour is still live
- You are running the Shift Management programme and this log is one of its steps
- A linked record needs this one to exist: it feeds the Daily Production Report and the Downtime Log
- A loss needs a reason code attached at the hour it occurred, so a pattern across shifts can actually be seen
Do not use it for
- Operations Shift Handover, which passes the state of the operation from one shift to the next, covering what ran, what broke, what is held and what the next shift must know
- Shift Start Up Check, which confirms the area, the people and the equipment are ready before the shift starts producing
- Manning and Labour Plan, which sets who is working where for a shift, against the competencies each position requires
- Escalation and Andon Log, which captures a call for help and how long it took to answer, not the hour-by-hour output record itself
- Anything outside KnowOps, which belongs in the workspace that owns that process
Compliance mapping
Which ISO 9001 cl.9.1 requirements does this satisfy?
ISO 9001 cl.9.1 does not name an hourly log; it requires performance to be monitored, measured, analysed and evaluated at a frequency that lets an organisation act on the result, which is what the hourly section satisfies.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 9001 cl.9.1.1 | Monitor and measure output against plan at a frequency that lets the organisation act on the result, not just report it afterwards | Hourly |
| ISO 9001 cl.8.5.1 | Control production by measuring output against the target set for the process | Header |
| ISO 9001 cl.9.1.3 | Analyse and evaluate the shift's monitoring data, including where it fell short of plan and by how much | Shift summary |
| ISO 9001 cl.10.2 | React to underperformance, determine its cause, and raise a corrective action where one is warranted | Shift summary |
| ISO 9001 cl.7.5.1 | Maintain documented information as evidence of conformity to the plan, identifiable and retrievable by its own key | Header |
| ISO 9001 cl.5.3 | Assign and communicate responsibility for reporting shift performance, including who signs it off | Shift summary |
| ISO 9001 cl.4.4 | Determine how this record's outputs feed the other processes that depend on it | Related records |
What it does not cover
- Hourly rows completed retrospectively at shift end, which collapses the record back into a single shift total and defeats the reason the log exists.
- Main Reason For Loss left blank against a logged negative variance, which leaves a number with no explanation anyone downstream can act on.
- Attainment Percent entered without a matching Total Downtime Minutes, which makes the headline figure unverifiable against the hourly detail beneath it.
- Action Required marked No on a shift where Carried Into The Next Shift is Yes, which contradicts the log's own answer two fields earlier.
- Second Signature missing from a log marked Complete, which leaves the record without the countersign its own design requires before it can stand as evidence.
Global
Shift Performance Log requirements by country
ISO 9001 cl.9.1 sets a general duty to monitor and measure; what that looks like on a floor walk differs by certification scheme and by the customer auditing the site.
ISO 9001:2015
Clause 9.1 requires monitoring, measurement, analysis and evaluation of process performance, without prescribing a frequency for any specific process.
Auditors judge frequency against the organisation's own stated method: if the line procedure says hourly, an end-of-shift total is a nonconformance against the site's own system before it's even measured against the standard.
BRCGS Food Safety Global Standard
Site audits under BRCGS expect production and downtime performance reviewed as management KPIs, not simply recorded on a form.
An hourly log nobody ever aggregates into a trend is paperwork sitting next to the process, not the monitoring the scheme's site audit is looking for.
SQF Code
SQF verification activity checks that monitoring records match the frequency stated in the site's own food safety plan.
If the plan claims hourly checks and half the rows are blank or duplicated, the auditor has found a verification failure, not a paperwork gap explained away at the desk.
How to complete it
How to complete a shift performance log, step by step
Filling in the fields is easy. What decides whether the log is defensible later is judgement the form itself can't enforce.
An hourly row entered while the hour is running captures a real number and a remembered cause. The same row entered at handover captures a plausible number and a guessed cause, and no field distinguishes the two once both are in the system.
Main Reason For Loss gives a category a report can trend across shifts; Action Taken In The Hour is the only place that says what was actually done. A log with the code but not the action says what kind of hour it was and nothing about whether the response was right.
Escalated is a plain yes or no against an hour, but the judgement behind it, whether a stoppage was serious enough to raise through the Escalation and Andon Log, is where the two records stay in step or drift apart.
A loss can be technically recovered in total output by shift end while still costing a specific customer order its slot. Recovered Within The Shift and Carried Into The Next Shift are answered against the aggregate, and a shift lead has to decide whether that aggregate is the honest answer.
What auditors find
Most common shift performance log findings
Findings against this log are rarely a missing field. They are numbers that don't reconcile, or a summary answering questions the hourly rows never raised.
| Finding | Clause | What fixes it |
|---|---|---|
| Hourly rows show the identical Main Reason For Loss for every hour of a shift. | ISO 9001 cl.9.1.1 | Require the shift lead to update the hourly row within the hour, not at handover, and block bulk-copy entry across rows. |
| Variance is populated but Downtime Minutes reads zero across a shift with a low Attainment Percent. | ISO 9001 cl.9.1.3 | Make Downtime Minutes required whenever Variance is negative, so the summary total has something underneath it to reconcile against. |
| Attainment Percent doesn't reconcile with the sum of the hourly Target This Hour and Actual This Hour rows. | ISO 9001 cl.9.1.3 | Calculate Attainment Percent from the hourly rows automatically rather than accepting a typed figure. |
| Action Required is answered No on a shift where Carried Into The Next Shift is Yes. | ISO 9001 cl.10.2 | Add a validation rule so Carried Into The Next Shift = Yes forces Action Required to Yes. |
| Handover ID is blank on shifts that carried a loss into the next one. | ISO 9001 cl.7.5.1 | Make Handover ID required whenever Carried Into The Next Shift is Yes, so the two logs actually link. |
| Second Signature is missing on a log with Status set to Closed. | ISO 9001 cl.5.3 | Block Status moving to Closed until both signatures are present. |
Case in point
Case in point: the shift that looked fine until hour six
A packing shift ran within two percent of target for the first five hours, each hourly row logged live with Main Reason For Loss left blank because there was nothing to explain. In hour six, Actual This Hour dropped sharply; the shift lead, mid-changeover elsewhere, entered a round number at handover and marked Main Reason For Loss as Changeover from memory. Attainment Percent still cleared eighty percent, so the summary went through without comment.
Three shifts later the same drop recurred at the same hour, and only then did anyone check the Downtime Log the hourly row should have referenced. It hadn't: the real cause was a recurring jam on a specific labeller, not a changeover, mislabelled the first time because nobody wrote it down until the hour had already passed. The fix wasn't a new field; it was refusing to let an hourly row be entered after the fact.
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
- OPS-005
- Archetype
- Log
- Record ID
- SPL-2026-000
- Scoring
- Plan attainment
- Direction
- High is good
- Singleton
- Yes
- Basis
- ISO 9001 cl.9.1
- Links
- Feeds Daily Production Report and Downtime Log
- Tags
- Shift, Performance
- Sections
- 4
- Fields
- 38
- Follow up fields
- 3
- Repeating sections
- 1
- Links out
- 6
Header
13 fieldsLog ID*
Auto sequence. Format SPL-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*
Shift*
Shift Lead*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Area*
The area within the site.
Exact Location
Drop a pin for anything hard to find.
Line*
Target Output*
Actual Output*
Hour By Hour Finds The Two Hours
A shift total tells you the day was bad. An hourly record tells you it was bad between two and four because the labeller was jamming, which is something you can actually fix.
Hourly
Repeats9 fieldsHour*
Target This Hour*
Actual This Hour*
Variance
Main Reason For Loss
Downtime Minutes
Action Taken In The Hour
Escalated
Log ID
Links to OPS-006 Log ID
Related records
2 fieldsDaily Report ID
The report this shift feeds.
Links to OPS-012 Report ID
Downtime Log ID
The stops behind the hourly losses.
Links to OPS-010 Log ID
Shift summary
14 fieldsAttainment Percent*
Total Downtime Minutes*
Largest Single Loss*
Recovered Within The Shift*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Carried Into The Next Shift*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Handover ID
Links to OPS-001 Handover ID
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
Shift Lead*
Signature*
Production Manager*
Second Signature*
OPS-005 · record IDs look like SPL-2026-000 · Feeds Daily Production Report and Downtime Log
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form is the easy part. Keeping it current hour by hour and routing losses to the right owner is the work that actually slips.
Holds the shift performance log against the Daily Production Report and Downtime Log it feeds, and flags an hourly row entered after the hour has already passed.
Picks up an Equipment Failure reason code and checks whether a work order already exists for the line, rather than letting the same fault recur unlinked.
Watches for Quality entered as the loss reason and confirms the underlying nonconformance has been raised, not just coded here.
Rolls hourly attainment and open actions into one view across the shift, and holds every write for approval before it touches a record.
This template lives in KnowOps — frontline execution. Shift handover, production control, daily management, worker lifecycle and improvement.
Meet KnowOps→Glossary
Shift Performance Log definitions and key terms
- Attainment
- Actual output measured against the target for the same period, expressed as a percentage, where a higher figure is better.
- Variance
- The gap between Target This Hour and Actual This Hour, positive or negative, recorded for every hour whether or not anything went wrong.
- Changeover
- Planned downtime while a line switches product or format, distinct from an unplanned loss even though both cost the same output.
- Escalation
- The point at which an hourly loss is judged serious enough to raise through the Escalation and Andon Log rather than absorbed and noted.
- CAPA
- Corrective and preventive action, raised when Action Required is answered Yes and referenced back into this log by its own ID.
FAQ
Frequently asked questions about shift performance log
Why does the log repeat by hour instead of just holding a shift total?+
A shift total tells you the day was bad and nothing else. An hourly breakdown tells you which specific hour lost the day and, if the reason field is actually completed at the time, why, which is the version a supervisor can act on.
Why is this a singleton if a new log gets raised every shift?+
Singleton describes the template's setup, not the record count: the log is configured once per workspace and every shift becomes a new entry against that same configuration, rather than each shift requiring its own separate form.
How does this log relate to the Downtime Log and Daily Production Report?+
This log records the hour-by-hour plan-versus-actual picture and feeds both: the Daily Production Report rolls its attainment figure up across shifts, and the Downtime Log holds the detail behind any stop long enough to need one, referenced back by ID.
Who has to sign off a completed log?+
The Shift Lead who ran the shift and the Production Manager who reviews it, both as a required signature. A log missing either is incomplete evidence even if every hourly row is filled in.
What triggers a CAPA from this log?+
Action Required answered Yes, at which point a Priority is set and a CAPA ID entered once the corrective action record has been raised elsewhere. The log holds the reference, not the investigation itself.
Does a good Attainment Percent mean the log needs no further attention?+
Not on its own. A shift can clear its attainment target in aggregate while still carrying a loss into the next shift or leaving a repeat cause unaddressed, both asked about separately from the headline percentage.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Shift Management
Shift Fatigue Screening
Screens work patterns for fatigue risk, covering shift length, rotation, breaks and consecutive days
Shift and Crew Register
Holds the shift pattern and crew structure for each area, so records can be grouped by the team that actually did the work
Operations Shift Handover
Passes the state of the operation from one shift to the next, covering what ran, what broke, what is held and what the next shift must know
Shift Start Up Check
Confirms the area, the people and the equipment are ready before the shift starts producing
Manning and Labour Plan
Sets who is working where for a shift, against the competencies each position requires
Overtime Authorisation
Authorises hours beyond the planned shift, with the reason and the cumulative position for that person
More in Shift Management
Operations Shift Handover
Passes the state of the operation from one shift to the next, covering what ran, what broke, what is held and what the next shift must know
Shift Start Up Check
Confirms the area, the people and the equipment are ready before the shift starts producing
Manning and Labour Plan
Sets who is working where for a shift, against the competencies each position requires
Overtime Authorisation
Authorises hours beyond the planned shift, with the reason and the cumulative position for that person
Escalation and Andon Log
Records a call for help from the floor, who responded, how long it took and what was done
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 9001:2015 cl.9.1 — Monitoring, measurement, analysis and evaluation
- ISO 9001:2015 cl.8.5.1 — Control of production and service provision
- ISO 9001:2015 cl.10.2 — Nonconformity and corrective action
- BRCGS Food Safety Global Standard, Issue 9
- SQF Code, Edition 9
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.