A/R Follow-Up Capacity Planning
A growing follow-up queue produces one instinctive question — how many more people do we need — and it is the second question rather than the first. Capacity is decided by how fast work arrives against how fast it clears. Where arrivals exceed clearance, the backlog is structural, and overtime moves the date on which it is measured rather than the direction it is heading. Every input to that comparison is measurable in the practice's own data, which is fortunate, because a borrowed productivity ratio describes somebody else's payer mix.
Updated 8 min read
On this page
Key takeaways
- Compare arrival rate against clearance rate first. A backlog where arrivals win is structural, and hours will not fix it.
- Every input is measurable locally: what enters follow-up, what leaves and how, and what each kind of touch costs in time.
- Count clearance by accounts resolved, not by accounts touched — a touch that changes nothing consumes capacity without producing any.
- Segment the demand before sizing it: the deadline-bound population and the merely old one need different responses.
- The largest lever is usually eliminating touches rather than adding people, because a removed touch reduces demand permanently.
- Under 45 CFR 162.923(a), a covered entity conducting a standard-adopted transaction electronically with another covered entity must conduct it as a standard transaction.
- A payer portal is not exempt: 162.923(b) requires a provider using direct data entry to meet the standard's data content and condition requirements, though not its format requirements.
- Capacity can be bought — 162.923(c) permits using a business associate — but it must be required to comply, so the work moves and the accountability does not.
The comparison that decides whether this is a staffing problem
A backlog is a stock, and stocks are produced by flows. Two measurements settle what kind of problem it is, and both come from the practice's own system.
Arrival rate
How many accounts enter the follow-up population in a period, by the trigger that put them there. Not how many claims were billed — how many became work.Clearance rate
How many leave, and how. Resolution and write-off are both exits and they mean opposite things; counting them together produces a clearance figure that improves as the practice loses money.Cost per touch, by type
A status check, a call, a resubmission and an appeal are different units of work. An average across all of them hides the only variable worth managing.The deadline-bound share
How much of the population cannot wait, from the remaining-time field in aged claims at timely-filing risk. This is the part of demand that is genuinely non-deferrable, and sizing without it plans for the average case only.
Arrivals above clearance is not a staffing finding
Removing a touch beats adding an hour
An hour of capacity is consumed once. A removed touch reduces demand every period afterwards, which is why the sequence is to shrink the work before sizing the team for it.
- Stop working claims that are progressing normally. Age-triggered queues generate touches on claims that need none. Triggering on state rather than on age is the single largest reduction available in most practices — see building an A/R follow-up process.
- Replace asking with checking. The 276/277 claim status transaction answers in bulk what a call answers one account at a time, and it produces a record rather than an assertion.
- Fix causes at the payer level. A pattern found through A/R by payer analysis is one configuration change against a population, which is a permanent reduction in arrivals rather than a faster way to work them.
- Separate the states before assigning them. No response from the payer covers why four different failures look identical — and applying the same action to all four is how capacity is consumed producing nothing.
The electronic route is the required one, not the ambitious one
Buying capacity, and what does not come with it
Some of the answer is genuinely more hands, whether hired or contracted. The model above is what makes that decision defensible rather than reactive, because it says how much and for which segment.
The work moves; the obligation does not
- Size to a segment, not to the queue. "We need more people for A/R" is not a plan. "This population, at this arrival rate, at this cost per touch" is one, and it can be checked afterwards.
- Model the oversight, not just the labor. Reviewing another party's work is real capacity consumed by the practice, and a plan that omits it under-costs the option it is recommending.
- Decide what happens to the reduction. If eliminating touches is working, demand falls. A plan that does not say what capacity is redeployed to will simply absorb the gain.
- Re-derive it on a schedule. Arrival rates move when payers change behavior or the practice changes what it bills. A model built once is a description of a period that has ended.
Why there are no numbers on this page
Common questions
How many accounts should one person handle?
There is no honest general answer, and a number here would be actively misleading. The figure depends on payer mix, specialty, balance sizes, how much of the population is deadline-bound, and above all on what a touch costs in that practice — which varies enormously depending on whether status is established electronically or by telephone. The defensible substitute is a model built from four locally measurable quantities: what enters the follow-up population, what leaves it and how, what each type of touch costs in time, and how much of the population cannot wait. That produces a capacity figure specific to the practice, and it can be checked against reality next period.
Our backlog keeps growing despite overtime. What does that mean?
Almost certainly that arrivals are exceeding clearance, which makes it a structural problem rather than an effort problem. Overtime raises clearance temporarily and does nothing to arrivals, so the queue resumes growing when the overtime stops — and the hours tend to be spent at the oldest, least recoverable end of the population. The productive responses are upstream: reduce what arrives, by fixing payer-level causes and by not generating touches on claims that are progressing normally, and reduce what each arrival costs, by establishing state through a transaction rather than a call. Sizing the team is the step after those, not instead of them.
Should we count a touch as work done?
Only if something changed. Counting touches rewards activity and hides the failure mode that matters, which is a queue being worked diligently and clearing nothing. Clearance is better counted by accounts leaving the population, separated by how they left — resolution means the process worked, and write-off means it ran out of options or out of time. Combining those produces a clearance figure that improves as the practice loses money, which is worse than having no figure at all.
Is using a portal instead of a transaction just a workflow choice?
Not entirely, and the distinction matters for a capacity model. Under 45 CFR 162.923(a), a covered entity conducting a transaction for which a standard has been adopted, electronically with another covered entity, must conduct it as a standard transaction; and under (b), a provider electing to use direct data entry offered by a plan must still meet the applicable data content and data condition requirements of the standard, being relieved only of its format requirements. So manual portal work is not a rules-free alternative and is not the natural baseline. A capacity model built on the assumption that this work is inherently manual is planning around a choice rather than a constraint.
Does outsourcing solve a capacity problem?
It can supply capacity, and it does not supply accountability. 45 CFR 162.923(c) expressly permits a covered entity to use a business associate, including a clearinghouse, to conduct a transaction — and requires that the covered entity require the business associate to comply with all applicable requirements, and to require any agent or subcontractor to do the same. The practical consequence for the model is that bought capacity carries an oversight cost the practice bears itself, so a plan comparing in-house hours against a vendor without that cost is comparing the wrong two numbers. It is also why the decision belongs before placement rather than after it.
Key terms in this article
Defined once, on their own pages.
Continue learning
The process this sizes, and the segmentations it consumes.
Building an A/R Follow-Up Process
The process whose thresholds this article derives — and why age is the wrong trigger.
Aged Claims at Timely-Filing Risk
The deadline-bound share of demand, which is the part that cannot be deferred.
A/R by Payer Analysis
Where a permanent reduction in arrivals usually comes from.
Outsourced A/R Vendor Oversight
The oversight cost that belongs in the model before the work is placed.
A/R Aging Distribution
Plot the distribution the arrival and clearance rates are moving.
Authoritative sources
- 45 CFR § 162.923 — Requirements for covered entities (opens in a new tab)
Provides that, except as otherwise provided in the part, if a covered entity conducts, with another covered entity that is required to comply with a transaction standard adopted under the part (or within the same covered entity), using electronic media, a transaction for which the Secretary has adopted a standard, the covered entity must conduct the transaction as a standard transaction. A health care provider electing to use direct data entry offered by a health plan to conduct such a transaction must use the applicable data content and data condition requirements of the standard, and is not required to use the format requirements of the standard. A covered entity may use a business associate, including a health care clearinghouse, to conduct a transaction covered by the part; if it does so, it must require the business associate to comply with all applicable requirements of the part and to require any agent or subcontractor to comply with all applicable requirements of the part.
