Skip to main content
The Practice
Clinical operationsAugust 15, 2026

Where Your Documentation Hours Actually Go: A One-Week Audit

A one-week self-audit that splits documentation time into writing, searching, switching, and re-reading — because each category has a different fix.

Callie Editorial 12 min read
The time issue
Audit

4 notes left

Close-the-day system

Capture

Objective data at point of care

Interpret

One clinical decision

Close

Sign, route, and clear exceptions

A finish line for every clinical day

At a glance

What you’ll leave with

  • Track four categories for one week — writing, searching, switching, and re-reading — because each has a different fix.
  • Log in the moment with ten-second tallies, count after-hours time honestly, and close each day with a two-minute total.
  • Let the dominant category pick the intervention, change one thing, and re-run the audit before judging whether it worked.

Ask a therapist how much time documentation takes and you get a number — an evening hour, a working lunch, a lost Sunday. Ask where that time goes and the answer gets vague. The total is easy to feel. The composition is invisible. And the composition, not the total, is what decides the fix.

“Documentation time” is really four different kinds of time: writing, searching, switching, and re-reading. A better template shortens writing but does nothing for the minutes spent hunting for the last progress report. A quieter schedule cuts switching cost but will not fix a note that takes twenty minutes to compose. The audit below separates the four in one ordinary week, using nothing more than a paper tally card — so that whatever you change next is aimed at the category that is actually consuming the hours.

The hidden split

One total hides four different problems

Writing time is the part everyone pictures: composing the subjective line, the data, the interpretation, the plan. It is real work and it is the smallest surprise in most audits. Searching time is everything the note needs that is not in your head — the active goal, last session’s cueing level, the authorization visit count, the evaluation report — retrieved from wherever it lives. It is not writing; it is fetching.

Switching time is the re-orientation cost paid every time documentation starts, stops, and restarts: the note opened between sessions and abandoned, the chart reopened at 8 p.m., the thirty seconds of “where was I” that precede every resumed draft. Each individual switch is small, which is why it never gets counted and why its weekly total is so often the audit’s surprise. Re-reading time is reconstruction: when a note is written hours after the session, the details have decayed, so you re-read prior notes, your own half-finished drafts, and the schedule just to remember what happened. It is the interest paid on deferred writing.

None of this is a personal failing, and the burden is not imagined — reducing clinical documentation load is now an explicit national goal. What the federal strategy and the informatics profession cannot do is tell you where your particular hours go. That takes a week of your own data.

25%

the 25x5 target

AMIA’s 25x5 task force works to reduce U.S. health professionals’ documentation burden to 25% of its current state by the end of 2026.

4

federal burden areas

Clinical documentation is one of four burden areas in the 2020 HHS strategy on reducing health IT and EHR burden, required by the 21st Century Cures Act.

1

week of measurement

A principle, not a benchmark: five clinical days is long enough to be representative and short enough that in-the-moment logging survives.

The centerpiece

The one-week audit, step by step

The protocol is deliberately low-tech: a paper card and tally marks. Time-tracking apps fail here for the same reason evening notes fail — they add a switching cost to the thing being measured, and they get abandoned by Wednesday. A card next to the keyboard survives a real clinical week.

  1. 01

    Pick an ordinary week

    No holidays, no PTO, no evaluation pile-up you already know is unusual. If the week turns strange midway — two sick days, a crisis — finish the audit anyway and note it; a strange week still produces a real split, just a wider error bar. Do not wait for a perfect week, because there is none.

  2. 02

    Rule the card into four rows

    Writing, searching, switching, re-reading. Define them before Monday, in your own words, with one example each — the definition argument you have with yourself on Tuesday is a data-quality problem. Add a fifth row at the bottom: after-hours, tracked by location and clock, not by category.

  3. 03

    Tally in the moment, in minutes

    Each time you finish a documentation touch, jot the minutes in the right row — a ten-second act. Estimating a morning at lunch is already reconstruction, and reconstruction flatters the writing row: searching and switching evaporate from memory precisely because they feel like nothing. Round to the nearest five minutes; precision theater kills compliance.

  4. 04

    Count every switch as its own event

    A note opened, abandoned for a session, and reopened is two switching entries, not zero. Tally the re-orientation minutes — finding the chart again, re-reading the half-draft, remembering the plan — under switching, and keep the writing minutes that follow under writing. The split between those two rows is the audit’s most common surprise.

  5. 05

    Log after-hours time honestly

    The 8 p.m. hour on the couch counts, and so does Sunday. This row is the one most likely to be under-reported and the one that matters most, because after-hours documentation is where burnout and note quality problems concentrate. Whatever it totals, that number is the audit’s claim to being taken seriously.

  6. 06

    Close each day in two minutes

    Before leaving — or before closing the laptop at home — total the rows for the day. This is not analysis; it is preservation. A card totaled nightly survives to Friday. A card left for Friday gets totaled from memory, which defeats the point.

  7. 07

    Compute the split on Friday

    Sum each row for the week. Then compute three numbers: each category’s share of the total, the after-hours share, and the total divided by your visit count — your true per-visit documentation cost. The dominant category, not the total, is the finding.

Copy and print

The daily tally card

One card per day

Documentation time tally card

Print five, rule them by hand, or copy this into a note. Minutes, tallied in the moment, rounded to fives.

01

DAY: [Mon–Fri] VISITS TODAY: [count]

02

03

WRITING — composing the note itself: [ 5 | 10 | 5 | ... ]

04

SEARCHING — finding goals, data, auth counts, reports: [ ... ]

05

SWITCHING — re-orienting after every stop/restart: [ ... ]

06

RE-READING — reconstructing sessions written late: [ ... ]

07

08

AFTER-HOURS — any of the above outside clinic hours: [ ... ]

09

10

DAY TOTAL (2 minutes, before you close): [ __ min ]

11

Strangest thing about today’s documentation: [one line]

The last line is not decoration. One observation per day — “spent ten minutes looking for the eval report,” “rewrote the same plan line three times” — is what turns Friday’s percentages into a specific fix instead of a general resolve to do better.

The payoff

Match the fix to the dominant category

On Friday, one category usually holds a clear plurality of the minutes. That category — not the total, and not whatever a vendor’s demo happens to fix — picks the intervention.

What each dominant category means

Dominant categoryWhat it usually meansThe fix that matches
WritingNotes are composed from scratch each time, or the note format demands more prose than the visit requires.Structured templates and point-of-service capture — preserve the six volatile facts during care, then compose once.
SearchingThe context a note needs — goals, last data, authorization counts — lives in too many places.Fix retrieval, not writing: one-screen prep, a plan line written to be found, chart organization, or an EHR that surfaces context.
SwitchingDocumentation has no protected home on the schedule, so it happens in fragments between other work.A schedule change, not a documentation change: micro-blocks after session clusters and a defended close-out block.
Re-readingNotes are written long after the sessions they describe, so every note starts with reconstruction.Move capture earlier, not evenings longer: the gap between session and note is the cost driver.

Two of these fixes are covered in depth elsewhere on this blog: the end-of-day documentation workflow shows the three-moment structure that shrinks writing and re-reading time, and the caseload scheduling template shows where documentation blocks belong on a week so switching stops being the default. If searching dominates, the problem is usually the system of record itself — worth knowing before any software renewal.

The total tells you documentation is expensive. Only the split tells you why.

The audit in practice

A week that did not say what she expected

Fictional worked case

A pediatric SLP audits her week

A composite, fictional example — not a real clinician, and the numbers are illustrative of the method, not benchmarks. A pediatric SLP with a full outpatient caseload believes she has a writing problem: notes feel slow, and she has been evaluating AI drafting tools to fix it.

The expectation

She assumes writing dominates. Notes feel like the work, so the plan is to make writing faster — a scribe, a better template, maybe dictation.

What the card showed

Friday’s tally puts writing at about a third of her documentation minutes. The plurality goes to searching and re-reading combined: hunting for prior session data scattered across the chart, re-opening the eval report for baselines, and reconstructing Tuesday’s sessions on Thursday night. Her after-hours row holds almost half of the week’s total, nearly all of it on the two days she left the clinic with unwritten notes.

The daily observation lines

Three of five days record a version of the same note to herself: “looked for last week’s cueing data again.” Her plan lines, she realizes, are written to satisfy the note — not to be read by the person writing the next one.

What she changed

Not the drafting tool — the sequence. She rewrote her plan lines to lead with next session’s target and cueing level, and moved a ten-minute capture block after her morning cluster so sessions stopped aging into the evening. The searching and re-reading rows were the target; writing was left alone.

The re-audit

Four weeks later she ran the card again. The comparison that matters is not her total against anyone else’s — it is her own after-hours row, week over week. That is the number the audit exists to move.

Keep it honest

Change one thing, then measure again

The audit earns its cost only if it ends in a single deliberate change. Change one thing — the plan-line format, the capture block, the retrieval setup — and run the card again a month later. Two changes at once produce a result that cannot be attributed; five changes produce a workflow nobody follows by Thursday. Against your own baseline, even a modest shift in the dominant category is real, visible progress — which is more than any benchmark can offer, because there is no defensible universal number for how long a therapy note should take.

Quick answers

Documentation time audit FAQ

How long should a therapy note take to write?

There is no defensible universal number — it varies with discipline, setting, visit type, payer requirements, and the note format itself. Any article quoting one is guessing. The audit gives you the only benchmark that matters: your own baseline, measured across one real week, which is what improvement gets judged against.

What counts as documentation time?

Everything the finished note consumed: composing it, finding the context it needed, re-orienting after each interruption, and reconstructing sessions written hours later — plus every minute of it done after hours. Counting only the writing is how a nine-hour problem gets treated as a four-hour one.

Why separate searching and switching from writing?

Because the fixes are different. Writing time responds to templates and point-of-service capture. Searching time responds to retrieval fixes — chart organization, prep, better plan lines. Switching time responds to schedule design. Buying a writing fix for a searching problem changes nothing except the software budget.

Will an AI documentation tool reduce my documentation time?

Only in the categories it actually touches, which is why the audit comes first. Drafting assistance targets writing time; some tools also cut searching time by surfacing context. None of them fix a schedule that forces switching, and every generated draft still requires clinician review before signing — the responsible clinician verifies accuracy and owns the record.

How often should I repeat the audit?

One week per quarter is enough, plus a re-run about a month after any deliberate workflow change. The re-audit is what separates a fix that worked from a fix that just felt like progress — compare your own split and after-hours share against the prior card, not against anyone else’s numbers.

Primary sources

Bibliography / 6
  1. 01AMIA 25x5: Reducing Documentation BurdenAmerican Medical Informatics Association
  2. 02Strategy on Reducing Regulatory and Administrative Burden Relating to the Use of Health IT and EHRs (2020)U.S. Department of Health and Human Services, Office of the National Coordinator for Health IT
  3. 03Documentation in Health CareAmerican Speech-Language-Hearing Association
  4. 04Documentation of Occupational Therapy ServicesAmerican Occupational Therapy Association
  5. 05Documentation of a VisitAmerican Physical Therapy Association
  6. 06Complying With Outpatient Rehabilitation Therapy Documentation Requirements (MLN905365)Centers for Medicare & Medicaid Services, Medicare Learning Network

Written by Callie Editorial

Published August 15, 2026

Educational content, not legal, billing, or patient-specific clinical advice.