Table of Contents

• A log is a route to action, not a place to park a concern
• Make the item and time unmistakable
• Record the observation in ordinary language
• Separate what happened from what happens next
• Keep different kinds of record distinct
• Close the loop without erasing the story
• Frequently Asked Questions

Last Updated: October 27, 2026

“Playing up again” may be an accurate description of your printer. It is a less helpful entry in a manufacturing shift log.

The person reading it next needs to know which item, what happened, when it happened and what has already been done. Without those details, a small observation becomes a detective story, often at exactly the point when one team is leaving and another is trying to understand the shift ahead.

Good equipment fault reporting does not require dramatic language. It requires a record that someone else can act on through the site's agreed process. Here is how to make that record clearer without treating a note as a diagnosis or permission to repair machinery.

A log is a route to action, not a place to park a concern

HSE maintenance guidance calls for procedures that allow workers to report damaged or faulty equipment. It also says that, where machinery has a maintenance log, that log must be kept up to date.

Those are connected but different activities: noticing something, reporting it through the right route and maintaining the record. A note that nobody is responsible for reviewing may preserve information without getting the concern addressed.

Follow the site's safety and reporting procedures immediately when a concern arises. Do not wait for the end-of-shift write-up if action is required now. This article offers communication examples, not instructions to keep operating, investigate a fault or decide that equipment is safe.

Make the item and time unmistakable

Use the identifier your workplace actually uses: the asset number, equipment name or agreed location reference. “The machine at the back” becomes unreliable when a reader works in another area or equipment has moved.

Add the time of the observation, including the date when a shift crosses midnight. Distinguish that from the time you entered the report if the two differ. A later reader should not have to work out whether 01:10 means before or after the event described above it.

For a fictional example, “Unit A, 22:15 on Tuesday: display showed error code X during the normal cycle” locates the observation more clearly than “fault last night”. Here, the unit and code are placeholders, not technical instructions or a real incident.

Use the site's existing fields rather than inventing a private naming scheme. Consistent identifiers allow later records to be connected without relying on one person's memory.

Record the observation in ordinary language

Describe what you actually saw, heard or read from a permitted position during normal work. If an approved system displayed a code, record it accurately. If you do not know the cause, say so.

A useful fictional note might say: “The displayed count stopped changing during the normal cycle; supervisor informed at 22:18.” That reports an observation and a communication. “Sensor definitely broken” adds a diagnosis that the writer may not be qualified to make.

Do not run equipment again merely to recreate a symptom for a more impressive report. Do not remove guards, reach into equipment or perform checks beyond your training and authorisation. HSE says maintenance should be undertaken by people competent to do the work, with appropriate information and training.

The note can be precise while remaining modest. “Not observed” and “not checked” are useful distinctions when they are true. They prevent the next reader from interpreting an empty field as an all-clear.

Separate what happened from what happens next

Record actions already taken under the site's procedure, who received the report and the current recorded status. Keep proposed next steps separate from completed actions.

Compare “maintenance” with “reported to the maintenance coordinator at 22:20; awaiting assessment”. The second tells a reader where the process has reached. It does not imply that an assessment or repair has happened.

A named person or agreed responsible team gives the next action somewhere to go. If a report passes across shifts, the receiving person needs to know what remains unresolved. Avoid rewriting “reported” as “sorted” merely because the original observer has gone home.

Likewise, “repaired” and “authorised for use” should not be treated as interchangeable shorthand. Follow the site's actual controls and record the appropriate confirmation from the responsible person.

Keep different kinds of record distinct

A fault note is not automatically an inspection record, maintenance record or near-miss report. The same event may require more than one process, but the labels have different purposes.

HSE's inspection guidance explains that inspection requirements depend on risk and that inspection results should be recorded and retained at least until the next inspection. An informal comment in a shift log does not establish that a required inspection took place.

HSE also describes near-miss records as a way to identify patterns and concerns needing attention. Use your employer's process for deciding which reporting routes apply; do not assume that entering something once in a general log fulfils every requirement.

Where systems permit it, reference the related record so that information can be traced without making several conflicting copies. One clear reference is usually more useful than three slightly different retellings.

Close the loop without erasing the story

When the responsible team has assessed the concern, the record should show the outcome and any remaining action under the site's arrangements. Preserve the original observation rather than silently rewriting it to match what was later discovered.

That makes the sequence readable: observation, report, assessment, action and confirmation. A recurring issue can then be recognised as recurring, rather than appearing as several unrelated complaints.

For tired readers at a shift boundary, clarity is a courtesy with practical value. Keep sentences short, use familiar terminology and avoid unexplained abbreviations. A longer entry is not automatically a better one; the useful details are those that let another person understand the actual state of work.

The best test is simple: could a colleague who was not there tell what is known, what is unresolved and who owns the next step? If so, the log has done more than record that something was “playing up”.