Documentation timeliness

Identify the governing deadline

A deadline may come from law, licensing, a payer contract, authorization, organizational policy, service agreement, or clinical workflow. Record the source, version, event that starts the clock, time unit, and owner.

An internal target can be earlier than the external requirement. Keep both dates so a missed internal goal is not mislabeled as a legal or payer violation.

Define completion precisely

Completion can require more than saved text. Depending on the record, it may include accurate required fields, authorship, signature or attestation when applicable, linked data, review, and locked or submitted status.

A draft, opened template, copied forward note, scheduled signature, or billing release is a different event. Choose the event that reflects the governing requirement.

Use a mature denominator

A clear formula is:

records completed by the applicable deadline ÷ records whose deadline occurred during the reporting period × 100.

Keep every due record in the denominator, including late, missing, rejected, corrected, and unavailable records. New records whose deadline has not arrived belong in a pending queue rather than the final rate.

A fictional timeliness cohort

Willow Current identifies 60 fictional session records whose documentation deadline occurred in July. Fifty-four meet the defined completion event by the deadline. Timeliness is 54 of 60, or 90%.

Three records finish one day late, two finish between two and three days late, and one remains open at the cutoff. The dashboard reports the six late or open records by age. It does not remove the open record from the denominator.

Five of the 54 timely records later require a correction. Timeliness remains 54 of 60, while timely-and-error-free-at-audit is a separate measure with its own review cohort.

Preserve truthful dates and history

Record the actual service time and the actual entry, signature, correction, or addendum time. Never backdate documentation or silently overwrite content to improve the metric.

A permitted late entry or correction should preserve the original record, author, dates, reason, and audit history under governing policy. Track correction resolution separately from original timeliness.

Measure lag as well as the rate

Report median time from the defined start event to completion, the range, percentiles when useful, and the oldest open record. A binary rate cannot show whether late records missed by minutes or weeks.

State whether durations use clock hours, business hours, calendar days, or business days. Account for weekends and holidays according to the source rather than a convenient dashboard default.

Examine the workflow behind delay

Reason groups can include unclear ownership, missing service data, inaccessible templates, device or network failure, clinical clarification, interpreter needs, workload, supervisor delay, payer change, or system integration problems.

Ask record authors about actual conditions. Avoid treating disability, communication needs, approved leave, or good-faith escalation as poor commitment. Route recurring system failures to corrective action.

Control the open-record queue

Every open record should have a current state, age, owner, next action, and escalation time. Distinguish a record awaiting the author, supervisor, clinical clarification, system recovery, or external evidence. A single “incomplete” status hides who can move the work.

Use reminders before the internal target, then route overdue records by risk and age. A record containing unresolved safety, health, privacy, or service-identity information needs case-level review even when the overall timeliness rate is strong. Close the queue item only when the defined completion evidence exists.

Track records reopened after completion. Reopening can signal a correction, quality review, or system issue and should preserve both the original completion time and later action.

Protect quality and safety

Speed targets can encourage copying, premature signatures, short narratives, or omitted concerns. Audit samples for accuracy, clinical meaning, person-centered content, privacy, and required evidence.

Immediate safety information should follow the designated escalation route rather than wait for routine note completion. A fast note does not replace timely clinical or emergency communication.

Use the metric fairly

Compare like record types, deadlines, roles, systems, and periods. A 24-hour session-note requirement and a monthly summary should not share one denominator. Show counts with percentages.

Pair timeliness with error rate, audit coverage, staff workload, safety events, claim outcomes, and client experience. Never make documentation speed the sole basis for clinical quality judgments or compensation.

Keep the source in scope

The CASP resources page links organizational and ABA practice materials, some requiring separate access or licensing. It does not define this timeliness formula as a universal standard. The controls above form an editorial measurement model.

When the rate declines, inspect overdue records by age, risk, record type, author role, system, and root cause before choosing a response. Fix workflow barriers while preserving authorship, truthful service dates, and the time needed for accurate clinical documentation.