Documentation completed at the time of service is the gold standard in regulated environments. It is more accurate, more credible, and more defensible than documentation completed hours — or days — after the fact.

When documentation is delayed, memory degrades. Details shift. Regulators and auditors are trained to look for documentation that was completed significantly after the service date — and they treat it with skepticism even when the underlying care was appropriate.

• Complete service notes before leaving the client's environment when possible
• If delayed documentation is unavoidable, note the reason for the delay explicitly in the record
• Never backdate documentation — this is considered falsification regardless of intent

Vague documentation creates ambiguity that can harm clients, expose staff, and undermine organizational credibility. Specific documentation tells a clear story that can be understood by someone with no prior knowledge of the case.

The test for specificity: could someone reading this record reconstruct exactly what happened, when, and why — without needing to ask you? If the answer is no, the documentation is not complete.

• Avoid: "Client was cooperative." Prefer: "Client completed all three prescribed exercises without verbal or physical resistance."
• Avoid: "Medication administered." Prefer: "2mg [medication] administered orally at 09:14 per care plan, client confirmed ingestion."
• Include observable facts, not assumptions about internal states you cannot verify

Altering a completed record — regardless of the reason — is one of the most serious compliance violations in regulated care. Even when the original documentation contained an error, the correction must follow a defined amendment process, not an overwrite or deletion.

In paper records, corrections require a single line through the error, the corrector's initials, the date, and a brief reason. In electronic systems, amendments create an audit trail that shows the original entry alongside the correction. Both formats are designed to preserve the integrity of the record.

• Never use correction fluid, erasing, or overwriting on paper records
• In digital systems, use the amendment or correction function — never delete and re-enter
• If you discover someone else's error, escalate to your supervisor — do not correct it yourself

Documentation containing protected health information (PHI) or personally identifiable information (PII) must be handled, stored, and transmitted according to your organization's privacy policies and applicable regulations including HIPAA.

Confidentiality obligations apply even when the information seems harmless or the disclosure seems minor. A casual mention of a client's name and diagnosis in a public setting is a privacy violation — even if no documentation was physically involved.

• Never leave paper records visible or unattended in common areas
• Log out of electronic systems when leaving your workstation, even briefly
• Do not discuss client information in public spaces — elevators, waiting rooms, hallways
• Report potential privacy breaches to your supervisor immediately, regardless of severity

Incident reporting exists to protect clients, staff, and the organization — and to create the data patterns that prevent future incidents. Underreporting is one of the most common compliance failures in regulated care environments, often because staff worry about consequences or believe the incident was "too minor" to document.

There is no such thing as an incident too minor to report. The threshold for incident documentation is not severity — it is whether the event deviated from expected care or created any risk, however small.

• Report all falls, medication errors, refusals, incidents of aggression, and near-misses
• Complete incident reports within the timeframe specified in your organization's policy — usually 24 hours
• Document factually — what happened, when, who was present, what was done in response
• Do not include opinions, blame, or speculation about cause in the incident report