Skip to content
Select language:English

Checklists and traceability: who did what, where and when

Updated 3 min read

A checklist organizes the checks to be documented and makes records comparable. Traceability connects that information to an asset, activity, person and time. Together they help reconstruct work, but a completed list does not automatically demonstrate that every check is correct or that all applicable requirements are met.

A check that leaves a trace: who verified what, on which asset, where and when

A useful question identifies what to observe and which result to record. “Everything OK?” leaves considerable room for interpretation; an item tied to a precise check distinguishes measurement, observation and judgement. Technical content and acceptance criteria must come from relevant instructions prepared or validated by competent people.

The list should distinguish checks not performed from those not applicable. Neither should be confused with a positive result. An anomaly needs a recipient and follow-up: collecting information without deciding who assesses it leaves the process incomplete.

Reconstructing a job benefits from asset identity, activity reference, record author, date and time, instruction revision and outcome. Depending on the check, measurements with units, notes, attachments or photographs may be needed. A signature may acknowledge information or a declaration, but its meaning needs defining: signatures do not all have the same legal standing.

A photograph should show what is needed to assess the outcome and stay connected to the correct check. An isolated photograph may not establish which item appears, when it was captured or which requirement it demonstrates. An observed location adds context without proving by itself that work was performed.

At the imaginary Aurora centre, an inspection concerns a safety device. The assigned person identifies the individual item, follows applicable instructions and records an anomalous outcome with a contextual note. The supervisor can understand which check needs attention and organize follow-up.

This is an organizational example, not a technical procedure for working on that device. When an item cannot be checked, recording the reason is preferable to choosing a positive result merely to finish the list. The job process distinguishes documentation, completion and verification.

UNI EN ISO 9001:2026 (opens in a new tab), current since September 2026, concerns the quality management system. It provides an organizational framework rather than a universal checklist, and does not make an activity compliant simply because it is recorded digitally.

A specific Italian example is the Ministerial Decree of 1 September 2021, Annex I (opens in a new tab): it requires an up-to-date register of periodic inspections and maintenance of fire safety systems, available to inspection authorities. An operational checklist does not automatically replace that register or other obligations. This is educational context: competent specialists should check the applicable official text and subsequent provisions. The Italian example is not a statement that identical rules apply in every country.

Required fields and structured information help reduce omissions but do not eliminate inaccurate records, unsuitable criteria or work not actually performed. Questions need review, sample checks are useful and corrections should leave an understandable history.

Photographs and notes may contain unnecessary personal information. Location privacy helps assess proportionality, access and retention. Smartphone use also needs consideration of local records and synchronization.

GiPStech’s field operations app page (opens in a new tab) provides the application context. Operations for Check Lists are in the reserved documentation and require sign-in.