Sample Work Product

An actual findings register, written exactly the way it gets written for a paying client.

No real client data appears below. The company is fictional. The clauses, the evidence-trace method, and the verdict language are not — this is the same format and the same standard applied to every engagement.

Client (Illustrative)
Halcyon Risk Partners LLP — 140 staff, two UK offices
Audit Type
Internal audit, ahead of surveillance audit
Scope
Clauses 6.1, 9.2, 9.3, 10.2, Annex A.5, A.6, A.8
Auditor
Brian Colborne — The Audit Engineer
This document is a sample work product produced for illustrative purposes using a fictional client. It demonstrates the format, depth, and evidentiary standard applied to live engagements.
Summary Verdict

Four findings raised across seven clauses sampled. Two Major Nonconformities, one Minor Nonconformity, one Opportunity for Improvement. The management system is documented to a defensible standard. The evidence chain beneath it is not.

A surveillance auditor sampling these same clauses under standard ISO 17021-1 sampling intensity would, on the balance of probability, surface Findings 01 and 02 independently. Neither requires unusual diligence to find. Both are reachable through first-pass evidence requests.

Findings
F-01 — Risk Treatment Plan Stalled Eight MonthsMajor NC
Clause Ref. 6.1.3 / A.5.7
Condition

Risk Register entry RR-014 (“Third-party access logging gap — vendor portal”) was risk-assessed and a treatment plan approved by the ISMS Steering Group on 14 February. Target completion: 30 April. As of the audit sample date, the control remains unimplemented. No revised target date exists in the register. No escalation record exists.

Evidence Trace

Risk Register RR-014 (approval minute) → IT Operations sprint backlog (ticket VPN-2231, status: backlog, untouched 6 months) → Management Review minutes, Q1 and Q2 (no mention of RR-014 in either).

The risk was assessed correctly. The plan was approved correctly. The system then produced no mechanism that forced the gap between plan and delivery into anyone’s view. That silence is the finding — not the missed deadline.
Verdict

Clause 6.1.3 requires that risk treatment plans be implemented. A plan that exists only as a document, with no enforced checkpoint and no escalation trigger when it stalls, does not satisfy the clause regardless of how well the plan itself was written. This is reachable on a routine sampling pass.

Recommended Ownership

Escalation accountability sits with whoever holds delivery authority over the IT Operations backlog — not with the ISMS Manager who correctly identified, assessed, and assigned the risk.

F-02 — Access Revocation Timing, Termination Outside Business HoursMajor NC
Clause Ref. A.5.18 / A.6.5
Condition

Documented procedure SOP-HR-09 states system access is revoked “within one business day” of termination. Sample of three involuntary terminations showed access revoked at 1, 3, and 4 business days respectively. The 4-day case involved a termination processed at 16:40 on a Friday; the IT ticket was not logged until the following Tuesday.

Evidence Trace

HR termination log (timestamp 16:40 Friday) → IT access ticket queue (first entry, following Tuesday 09:14) → SOP-HR-09 (states 1 business day, no exception handling for after-hours terminations).

The procedure was written by someone assuming terminations happen on schedule, during office hours, with everyone available to act immediately. They don’t. The exception case is the one that matters to an auditor, because it’s the one most likely to coincide with an actual incident.
Verdict

The organisation’s own documented SOP sets a one-day standard it then fails to meet in 100% of the sampled exceptions. An auditor sampling termination records against the access log will find this on first pass.

Recommended Ownership

Jointly HR (notification timing) and IT (ticket processing cadence). No single name currently owns the after-hours exception — which is precisely why it has gone uncorrected.

F-03 — Internal Audit Coverage, Annex A.8 Not SampledMinor NC
Clause Ref. 9.2 / A.8.9
Condition

The internal audit programme listed Annex A.8 (technical controls, including configuration management) in scope. The internal audit report contains no sampled evidence, findings, or test records against it — the heading is present in the report; the content beneath it is not.

Evidence Trace

Internal Audit Programme (lists A.8 in scope) → Internal Audit Report, Section 6 (A.8 heading present, no content) → Internal Auditor interview (confirmed time constraints, deferral not documented).

A scope document that lists a control domain and a report that says nothing about it look, to a casual reader, like compliance. To an auditor checking whether the programme was actually executed, it looks like exactly what it is.
Verdict

Clause 9.2 requires the internal audit programme to be implemented, not merely planned. Classified Minor because no control failure has yet been demonstrated within A.8 itself — only the fact that nobody has checked.

Recommended Ownership

Internal Audit Manager, specifically the planning-to-execution handoff.

F-04 — Management Review Decisions Lack Named OwnersOFI
Clause Ref. 9.3 / 10.2
Condition

Management Review minutes record decisions in passive voice, with no individual named as responsible and no target date attached. Three of five decisions sampled across two review cycles show no subsequent evidence of action.

Evidence Trace

Management Review minutes (five decisions recorded) → Corrective Action Log (two of five appear; three do not) → follow-up interview (decisions “generally understood” to sit with Security Operations, not formally assigned).

“Generally understood” is not the same sentence an auditor will accept as an answer to “who owns this.”
Verdict

Not yet a nonconformity, but the same structural defect found in F-01 and F-02: decisions without a named owner and a date do not survive a surveillance auditor’s follow-up question.

Recommended Ownership

Chair of the Management Review should adopt a fixed minute template: decision, owner, date, status — four fields, no exceptions.

This is the standard applied to every engagement.

Fixed scope. Findings delivered in writing. No reassurance language, no softened verdicts.

Book an Audit Engagement →