What is a documentation gap?

A documentation gap is any difference between the work a clinician actually performed and what the note records. It matters because the note, not the memory of the visit, is what supports the code. A gap runs in one of two directions: the note describes less than was done, which loses revenue, or the code claims more than the note describes, which creates audit exposure.

Which direction is more common?

Under-documentation is more common in practices with heavy clinic loads, because the note is written at the end of a long day and compressed. Over-claiming is more common where template text or copy-forward populates fields that were not genuinely addressed at that visit. Most practices have some of both, in different providers.

Does copy-forward documentation create a problem?

It can, in both directions. Carried-forward text can populate a note with problems that were not addressed at that visit, which makes the note claim more than happened. It can also bury the work that was genuinely done at this visit inside text identical to last visit's, which makes the new work invisible to a reviewer. The issue is not the tool but whether the note distinguishes today from last time.

How does time documentation affect the level?

For office and outpatient visits you may select the level by total time on the date of the encounter, but only if the time is documented. An unrecorded forty minute visit is a forty minute visit that cannot be billed as one. A single explicit statement of total time is often the smallest change with the largest effect on a practice's coded levels.

What should an addendum look like?

An addendum should be clearly identified as an addendum, dated with the date it was written rather than the date of service, attributed to the author, and confined to work that was actually performed at the encounter. Retrospective additions that change the substance of the visit rather than clarifying it are not defensible. Follow your organization's amendment policy and your EHR's audit trail requirements.

Can I fix documentation gaps retroactively?

Clarifying an ambiguous note through a properly executed addendum is legitimate. Reconstructing work from memory months later is not, and a late amendment on a note whose code was also revised is exactly the pattern an auditor looks for. The durable fix is prospective: change how the note is written going forward, and leave closed encounters alone unless there is a genuine clarification to make.

Documentation Gaps: When Your Note Does Not Support the Code You Billed

Documentation gaps cut both ways. The same weakness that stops you billing the level you earned can also leave you unable to defend the level you did bill. Most practices have both, and treat neither.

8 min readReviewed by The Provider Partner

The gap runs in two directions

A documentation gap is simply a difference between what happened at a visit and what the note says happened. Practices tend to think of this as a compliance topic, which covers only half of it.

The two directions a documentation gap can run, and what each costs.
Direction	What it looks like	What it costs
Note describes less than was done	Work performed, note compressed or generic	The level you earned is unbillable
Code claims more than the note describes	Template or carried-forward text inflates the record	Repayment risk if reviewed

Both are the same defect: the note is not an accurate record of the encounter. Fixing the underlying habit addresses both at once, which is why it is worth treating them as one problem rather than two.

Direction one: the note says too little

This is the expensive direction and the one nobody audits for. Four patterns account for most of it.

Time is never recorded

Since the 2021 revision to office and outpatient E/M you may select the level by total time on the date of the encounter. But you can only bill the time you recorded. A visit that genuinely took thirty-five minutes, with no time statement in the note, cannot be billed on time at all.

This is usually the single highest-yield change available to a practice, because it costs one sentence per note. See the undercoding guide for the time bands.

Problems are listed, not addressed

A problem list is not a record of medical decision making. What supports the level is evidence that you addressed a problem at this visit: its current status, what you assessed, what you decided, and why. “Type 2 diabetes” appearing in a list tells a reviewer nothing. “Type 2 diabetes, worsening despite adherence; increasing metformin and adding an ACE inhibitor; repeat labs in six weeks” tells them everything.

Independent interpretation goes unwritten

When you personally review and interpret an image or a tracing that someone else billed, that interpretation counts toward the data element of medical decision making. When you write “imaging reviewed”, it is not clear that you did anything beyond noting a result. Record what you concluded, not that you looked.

External discussion disappears

A real conversation with the patient’s specialist about management counts. It almost never reaches the note, because it happens in a corridor or on a phone call between patients. One line naming who you spoke to and what you decided together preserves it.

The reviewer test

Read one of your own notes as if you were a reviewer who was not in the room, has never met the patient, and knows only what is on the page. Can you tell what was wrong, what was decided, and why? If you are filling gaps from memory as you read, so is everyone else — and a reviewer cannot.

Direction two: the note says too much

The second direction is less common in volume but carries more consequence per instance.

Carried-forward text.Copying yesterday’s assessment into today’s note populates the record with problems that may not have been addressed today. It also hides whatever is genuinely new, because a reviewer cannot distinguish this visit from the last.
Template defaults. A template that auto-fills a complete review of systems or a full exam produces documentation of work that may not have occurred. This is the classic finding in a template-driven practice.
Coding to the note that was generated rather than the visit that happened. If the level is chosen from what the template produced rather than what was clinically done, the code is following an artefact.

The tell is uniformity. When notes across different patients on different days are substantially identical, the documentation has stopped describing individual encounters, and a reviewer will read that as evidence about the whole sample rather than one note.

Auditing your own notes

Sample small and read properly. Ten encounters per provider, read carefully, beats a hundred skimmed. Choose ordinary visits, not the ones you remember.
Score each note against the code billed.For each, answer one question: does this note support the level submitted — under, over, or accurate?
Check for time. Count how many notes contain an explicit total time statement. In most practices this number is far lower than expected, and it is the cheapest thing on this list to fix.
Test for uniformity. Put two notes from the same provider on different patients side by side. How much text is identical? Substantial overlap in the assessment and plan is the signal worth acting on.
Record the pattern, not the verdict. The output of this exercise is a description of what your notes habitually omit. That is what you fix. Individual encounters are examples, not the target.

Fixing it prospectively

Documentation habits are the hardest of the four leaks to correct, because they are hundreds of small daily behaviors rather than one workflow step. That argues for changing few things and changing them properly.

Start with total time. One sentence, every note. It is the smallest change with the largest effect.
Give the assessment a required shape. Problem, current status, decision, reason. Four beats, every problem addressed.
Turn off template defaults that document work. A template should prompt, not assert. Anything that pre-fills findings is creating a record of care that may not have been delivered.
Re-sample after a quarter. Ten notes per provider again. You are measuring whether the habit changed, not grading anyone.

Leave closed encounters alone unless there is a genuine clarification to make through a properly dated and attributed addendum. A late amendment alongside a revised code is the exact pattern that draws scrutiny, and the recovery available from reworking old notes is small next to the risk.

Documentation gaps are the root cause underneath the other three. A note that does not record total time causes undercoding. A note that does not separate the visit from the procedure prevents modifier 25 being supportable. A note that records a service the charge workflow never reads produces a missed charge. Fix the note and the other three get easier.

Common questions

What is a documentation gap?: A documentation gap is any difference between the work a clinician actually performed and what the note records. It matters because the note, not the memory of the visit, is what supports the code. A gap runs in one of two directions: the note describes less than was done, which loses revenue, or the code claims more than the note describes, which creates audit exposure.
Which direction is more common?: Under-documentation is more common in practices with heavy clinic loads, because the note is written at the end of a long day and compressed. Over-claiming is more common where template text or copy-forward populates fields that were not genuinely addressed at that visit. Most practices have some of both, in different providers.
Does copy-forward documentation create a problem?: It can, in both directions. Carried-forward text can populate a note with problems that were not addressed at that visit, which makes the note claim more than happened. It can also bury the work that was genuinely done at this visit inside text identical to last visit's, which makes the new work invisible to a reviewer. The issue is not the tool but whether the note distinguishes today from last time.
How does time documentation affect the level?: For office and outpatient visits you may select the level by total time on the date of the encounter, but only if the time is documented. An unrecorded forty minute visit is a forty minute visit that cannot be billed as one. A single explicit statement of total time is often the smallest change with the largest effect on a practice's coded levels.
What should an addendum look like?: An addendum should be clearly identified as an addendum, dated with the date it was written rather than the date of service, attributed to the author, and confined to work that was actually performed at the encounter. Retrospective additions that change the substance of the visit rather than clarifying it are not defensible. Follow your organization's amendment policy and your EHR's audit trail requirements.
Can I fix documentation gaps retroactively?: Clarifying an ambiguous note through a properly executed addendum is legitimate. Reconstructing work from memory months later is not, and a late amendment on a note whose code was also revised is exactly the pattern an auditor looks for. The durable fix is prospective: change how the note is written going forward, and leave closed encounters alone unless there is a genuine clarification to make.