Reporting and Documentation
What the domain covers
Documentation is the supervisor's evidence that the service was delivered, that staff were managed, and that risks were controlled. Candidates must understand the qualities of good records: accurate, contemporaneous, legible, objective, complete, and retained per policy. Know the main record types: attendance and timesheets, inspection and audit reports, incident and near-miss reports, training and competence records, equipment maintenance logs, and client communication records.
Key concepts include fact versus opinion in reports (write what was seen and heard, not what was assumed), the difference between objective and subjective language, and why dates, times, names, and locations matter. Understand data protection and confidentiality - share only on a need-to-know basis and follow retention rules. Know the purpose of reporting: to inform decisions, support audits, defend against claims, and drive improvement. Understand escalation reporting - who needs to know, how quickly, and in what format. Recognise the risks of late, incomplete, or altered records.
Traps to watch for
Questions often present a report full of opinion ("the cleaner was lazy") - the correct answer uses observable facts. Another trap is writing records after the event from memory and back-dating; contemporaneous records are expected. Watch for answers that share confidential information widely, or that omit near-misses because "nothing happened". Beware of reports that record the outcome but not the action taken.
Worked example / rule of thumb
You find a damaged floor buffer at the start of a shift. Rule of thumb: what, when, where, who, action. Record what was found (damage and apparent cause if known), when and where, who was informed, and the action taken (tagged out, replacement requested). Keep it factual and dated; avoid blame and speculation.