6 min read
Updated 2026-06-07
What payers check before they approve a prior authorization
A payer approves or denies a prior authorization against an internal checklist the practice rarely sees. Here is what is on it.
Short answer
Before approval, payers usually check clinical criteria, step-therapy proof, code alignment, and the functional or chart evidence that supports the request.
A prior authorization is decided against an internal policy the practice almost never sees in full. The policy says, in detail, what a payer needs in order to approve a given procedure on a given plan. When a submission misses one item on that list, it is denied, even when the care is clearly appropriate. Knowing the list is most of the work.
The four things a payer almost always checks
Across payers and procedures, four categories show up again and again.
- Clinical criteria. Proprietary rule sets (for example InterQual or MCG) or the payer’s own medical policy define what qualifies as medically necessary for this procedure.
- Step therapy. Proof that required earlier treatments were tried and documented, in the order the policy expects.
- Code alignment. The diagnosis (ICD-10) and the procedure (CPT or HCPCS) have to match a covered indication. A small mismatch reads as not covered.
- Functional baselines. Scores or measures that justify the level of care, such as a documented functional limitation.
Why the list keeps moving
Payer policies change, and they change quietly. A criterion that approved a procedure last quarter can be tightened this quarter with no notice to the practice. Teams that rely on the last approval as a template eventually submit against a rule that no longer exists.
This is why the same procedure, for the same diagnosis, can sail through one month and stall the next. The clinical picture did not change. The checklist did.
How to close the gap
The practical move is to know the current requirement before a submission goes out, and to assemble the documentation against that requirement rather than against memory. That means watching the policy at the source, not waiting for a denial to reveal that it moved.
Upstream reads payer behavior and requirements at the source and tells the team what a payer checks for a given procedure, so the submission is built to the rule that is in force today.