Days from encounter to claim submission is the only major revenue cycle metric no payer influences, which makes it the fairest measure of the practice half of the partnership. Every day of lag is a day added to every downstream number.
Nearly every revenue cycle metric is partly the payer's doing. Days in A/R depends on how fast they adjudicate. Denial rate depends on their policies. Net collection rate depends on their decisions.
Charge lag does not. It is the days between the date of service and the day the claim goes out, and no payer touches it.
Why it matters more than it looks
Charge lag sits in front of everything. A claim submitted twelve days late is paid twelve days late in the best case, and in the worst case it is submitted against a filing window that has already been partly spent. Every downstream metric inherits the delay.
It is also the cheapest thing to fix. It requires no negotiation, no policy change, and no payer cooperation — only a defined cadence and somebody watching it.
What creates lag
- Unsigned notes. The single largest contributor in most practices, and the one billing cannot solve.
- Batch habits. Charges entered when someone gets to them rather than on a schedule.
- Coding queues without a clock. Work that has no deadline expands.
- Missing documentation nobody is tracking as an exception.
The uncomfortable, useful part
Because no payer influences it, charge lag is the cleanest measure of the practice's own contribution. If your biller reports it and it is poor, that is usually not their failure — it is documentation timeliness, and it belongs to the clinicians.
That is exactly why it should be on the monthly report. A number that occasionally implicates the practice rather than the vendor is a sign the reporting is honest.
Measure it per clinician
An average across the practice hides the distribution, and charge lag is almost always concentrated in a few people rather than spread evenly.
Reporting it individually is uncomfortable and it is the only version that changes anything, because the fix is one person closing notes sooner rather than a process redesign.
Separate documentation lag from billing lag
Encounter to note signed, then note signed to claim submitted. The first is clinical, the second is billing, and they need different owners and different fixes.
Reporting only the combined figure lets each side attribute it to the other, which is why the number rarely moves.
Watch the filing window it consumes
A payer with a ninety-day filing limit and a two-week charge lag has already spent a sixth of the window before submission. For payers with shorter limits, a slow month can put claims out of time before anyone has looked at them.
Common questions
- What is charge lag?
- The number of days between the date of service and the date the claim is submitted. It is entirely within the practice’s control.
- What is a good charge lag?
- As close to same-day as the workflow allows. Two to three days is achievable for most outpatient practices; anything beyond a week is usually a documentation bottleneck.
- Why does charge lag matter so much?
- It adds directly to days in A/R and consumes filing window before the claim has even been submitted. It also delays discovery of any denial.
- What causes charge lag?
- Unsigned notes, missing documentation, coding queues and batch submission schedules. Almost always documentation rather than billing.
- Who owns charge lag?
- Clinicians, mostly — which is why it is uncomfortable. The billing team cannot submit a claim for an encounter that has not been documented.
Denials Piling Up?
We handle the revenue cycle end to end — coding by certified coders, claim submission, denial management and appeals, and A/R follow-up, with six reported numbers every month.