# What Should a Prior Authorization Dashboard Actually Measure in 2026?

getpulse.care · September 25, 2026

> What a Prior Authorization Dashboard Should Actually Measure in 2026 Prior authorization dashboard metrics are the countable signals a clinic or care...

## What a Prior Authorization Dashboard Should Actually Measure in 2026

Prior authorization dashboard metrics are the countable signals a clinic or care network uses to see how authorization requests move from submission to decision, and what happens afterward. For a care-coordination team, the metrics that hold up under scrutiny are not abstract scores but events: requests open today, age of the oldest open request, approvals, denials and their stated reasons, appeal reversals, and staff minutes per request. Since January 2024, federal prior authorization rules have pushed most Medicaid managed care organizations, Medicare Advantage plans, marketplace issuers, and state Medicaid programs to publish response-time and denial data, so as of September 2026 a dashboard is a practical operating tool rather than an optional extra. GetPulse.care builds for B2B care networks and clinics around exactly that idea: prior authorization is a queue that patients experience as waiting time, and the dashboard is how a network keeps that queue honest.

**Also worth reading:** [Is AI Prior Authorization Automation Ready for Clinics in 2026, and How Should Health Systems Adopt It?](https://getpulse.care/knowledge/is_ai_prior_authorization_automation_ready_for_clinics_in_2026_and_how_should_health_systems_adopt_it.php) · [What are prior authorization reversal codes and how do they work in healthcare revenue cycle management?](https://getpulse.care/knowledge/what_are_prior_authorization_reversal_codes_and_how_do_they_work_in_healthcare_revenue_cycle_management.php) · [How do clinics and care networks actually measure the return on investment for care coordination software?](https://getpulse.care/knowledge/how_do_clinics_and_care_networks_actually_measure_the_return_on_investment_for_care_coordination_software.php)

The numbers fall into three families. Flow metrics describe movement — submissions per week, pending volume, aging buckets, median and 90th-percentile days to decision. Outcome metrics describe results — first-pass approval rate, denial rate by reason, appeal overturn rate, and the share of denials that are administrative rather than clinical. Cost metrics describe the toll — touches per request, coordinator minutes, dollars of admin labor per approval, and days of delayed care. A useful dashboard shows all three side by side, because a rising approval rate achieved by cherry-picking easy requests is not a win, and a falling denial rate that hides a 30-day backlog is not progress. Raw request counts alone are activity measures, not performance measures; a 10,000-submissions figure says only that volume exists, not whether any of it was approved on time.

## How These Numbers Behave and Why Public Data Misleads

KFF's analysis of the first wave of federally required insurer prior authorization reporting found that the published data offers little explanation of what actually gets approved or denied. Aggregated, payer-level files show timing and denial rates but rarely break results down by service line, condition, or requesting clinician, and definitions of a request or a denial differ from plan to plan. That matters for anyone building a dashboard: the public file is a sanity check, not a model of your own queue. KFF's separate work on Medicaid managed care reporting has made a similar point for state programs — annual reports describe the system, but the operational detail a coordinator needs lives inside the clinic's own records.

The federal rules, finalized in January 2024 as CMS-0057-F, set hard ceilings for impacted payers: 72 hours for expedited requests and 7 calendar days for standard requests, plus public reporting on approval rates, denial rates, response times, and appeal overturns. Compliance is a floor, not a target. A network averaging 6.9 days can still have a 200-request tail stuck past 30 days, and the mean will hide it, which is why the 90th percentile is the number to run. Service-line variation adds another layer: GLP-1 weight-loss requests carry step-therapy and quantity rules and drove much of the 2024–2026 authorization surge, while behavioral health and ABA requests follow different clinical and administrative patterns. Any dashboard that pools all of that into a single percentage is averaging away the very information operators need.

## The Core Metric Set, With Numbers That Matter

Start with aging buckets rather than a single pending count. Segment open requests into 0–7 days, 8–14 days, 15–30 days, and over 30 days, and track the volume in each bucket by payer and service line. The 8–14 day bucket is the early-warning zone because it is the last point before a routine request breaches the 7-day federal standard, and the over-30 bucket is where abandoned authorizations, manual faxes, and executive escalations accumulate. Pair that with median and 90th-percentile days to decision; if the median is 4 days and the 90th percentile is 26, the operational problem is the tail, not the typical case.

Then track first-pass approval rate, denial rate by reason code, and appeal overturn rate. KFF has reported that a large share of denials in Medicare Advantage and Medicaid managed care are later overturned, with reversal shares ranging roughly from one in five to more than half depending on the program and state, which is why a high overturn rate is a signal to examine documentation and escalation quality rather than a badge of honor. Split denials into administrative (missing signature, expired order, wrong code) and clinical (criteria not met) so a team can see which are fixable. Finally, connect the queue to the patient pulse: days from request to medication fill, imaging date, or therapy start, plus patient-reported friction such as status calls and repeat inquiries. That is where a B2B care-coordination platform earns its place, because the denial rate is a proxy and the started-on-time rate is the outcome.

## Building the Dashboard: A Practical Method

First, define the unit of analysis and its denominator. One request means one authorization request for one patient, one service, and one payer, and every rate should state its denominator — denials over decisions, not denials over submissions. Second, connect the data sources: the practice management or EHR system, the clearinghouse or portal submission log, the payer portal status feed, and a separate appeals log. Payer identifiers must be normalized because the same plan appears under different aliases across portals, and duplicate submissions after a portal timeout will otherwise inflate volume by 10–20 percent in some clinics. Third, build a 60–90 day baseline by payer and service line before setting any target, because a Medicaid mix with high behavioral health volume will never resemble a commercial imaging book.

Fourth, set control limits rather than arbitrary goals: flag any expedited request over 72 hours, any routine request over 14 days, and any segment whose denial rate drifts more than 5 percentage points above its trailing six-month baseline. Assign an owner to each alert — a named coordinator, not a shared inbox — and define what action follows, such as a portal re-submission, a peer-to-peer escalation, or an appeal packet. Fifth, fix the review cadence: a daily queue huddle, a weekly operations review, a monthly payer deep-dive, and a quarterly network trend review. Keep in mind latency: portal status updates daily, but appeal decisions can take 30–60 days, so a dashboard that only reads live status will systematically understate the denial burden.

## Build, Buy, or Borrow: Comparing Dashboard Options

The table below compares the three common approaches a care network faces. The right answer depends on volume, payer mix, and whether the organization has a data engineer on staff, not on which option has the longest feature list.

| Feature | Spreadsheet plus BI tool | Custom data pipeline | Care-coordination SaaS platform |
| --- | --- | --- | --- |
| Setup time | 2–6 weeks | 4–9 months | 2–8 weeks |
| Typical cost | $10–$30 per user per month plus admin hours | $25,000–$150,000+ implementation, then ongoing engineering time | Roughly $3–$15 per clinician per month, or network tiers of $1,000–$10,000 per month |
| Payer and service-line segmentation | Manual or fragile | Fully custom | Prebuilt, configurable by payer and service |
| Refresh rate | Daily at best, if exports run | Near real time via API | Daily to hourly, depending on integration |
| Appeal and overturn tracking | Usually absent | Possible but expensive to build | Standard, with escalation workflows |
| Maintenance burden | High on whoever owns the spreadsheet | Highest; requires dedicated staff | Shared across customers |
| Best for | Small clinics under 300 requests per month | Large networks with a data platform team | Multi-site care networks juggling several payers and high PA volume |

The trade-off is ownership. A spreadsheet is cheap and transparent until the person who built it leaves, and it rarely captures appeals. A custom pipeline can model anything but shifts the cost into engineering headcount and a six-month timeline, which most mid-size networks cannot absorb. A SaaS platform like the getpulse.care category of tools trades some customization for working payer logic and a patient-pulse layer out of the box. None of the three replaces governance: if no one reviews the queue each morning, the dashboard simply becomes a more expensive report that arrives too late.

## Common Mistakes That Distort Prior Authorization Numbers

The first mistake is mixing denominators across programs. Medicaid managed care, Medicare Advantage, and commercial plans have different approval baselines, and a blended rate tells a coordinator nothing actionable. The second is counting resubmissions as new requests, which inflates volume and depresses any rate built on submissions; deduplication by patient, service, payer, and a 24-hour window usually removes 5–15 percent of phantom requests. The third is relying on the mean instead of the 90th percentile, which flatters a queue with a long tail. The fourth is treating the denial rate as a quality score. Some denials are clinically correct, and a network that chases the lowest denial number may be submitting less appropriate requests rather than doing better reviews.

The fifth mistake is ignoring appeal lag, so dashboards look healthy while dozens of denials sit unresolved. The sixth is using public dashboards as ground truth. The Impact Counter, a federal impact metrics dashboard, was retired in 2026 and its pages were later archived, a reminder that public panels disappear and internal records are the durable evidence. Finally, watch for gaming: staff who mark requests as incomplete or withdraw them to shrink the pending list have made the numbers better without approving anything. A short definition sheet — what counts as a request, a decision, an appeal, and an overturn — reviewed quarterly with the coordinator team prevents most of these distortions.

## When to Act: Thresholds, Triggers, and Cadence

Treat thresholds as triggers, not warnings. Act immediately on any expedited request past 72 hours or any routine request past 14 days, which is twice the federal standard window and usually the point where a patient calls the clinic. Escalate a segment when its denial rate runs more than 5 percentage points above the payer's trailing six-month baseline with at least 50 decisions behind it, since smaller samples swing wildly. Investigate when the appeal overturn rate exceeds 20 percent for a service line, when pending volume exceeds twice the 90-day mean, or when a single clinician accounts for more than 30 percent of one payer's denials, which often points to a documentation or order-entry problem rather than a payer dispute.

Act sooner during surges. GLP-1 and other high-cost drug authorizations multiplied request volume between 2024 and 2026, and a network that adds staff only at quarter end will miss the bottleneck by weeks. Compliance calendars matter too: states such as Ohio have moved aggressively on Medicaid fraud and assistance reforms through legislation like SB 315, and networks should be able to produce clean audit trails of every submission, status check, and appeal on request. Run a daily huddle on the aging table, a weekly review of denial reasons and overturns, a monthly payer deep-dive, and a quarterly network trend review, then re-baseline after any payer policy change, EHR migration, or staffing shift.

## Cost, Pricing, and the Patient-Pulse Connection

Planning ranges matter more here than exact quotes, and they vary widely. Spreadsheet approaches cost mostly in coordinator time, typically several hours a week to reconcile exports, plus a low-cost BI license. Custom pipelines with FHIR-based submission and status feeds commonly run $25,000–$150,000 or more to implement, before ongoing engineering and integration maintenance. Care-coordination SaaS products in the getpulse.care category generally price in the range of $3–$15 per clinician per month or $1,000–$10,000 per month for a network tier, with appeals workflows, payer segmentation, and patient-pulse reporting included. Loaded coordinator cost commonly runs $45,000–$70,000 per year per full-time equivalent, so a single avoided appeal escalation can pay for a small monthly subscription.

The broader cost is delay. Administrative touch time of $10–$40 or more per request adds up at thousands of monthly authorizations, but the figure that should concern a care network is the downstream one: a therapy start pushed three weeks, a patient who never fills a prescription, a churn signal in an ABA or weight-management program. That is why the patient-pulse layer — connecting authorization delay days to patient-reported wait time and care-started-on-time — is the differentiator, not another approval-rate chart. The honest verdict as of September 2026: a prior authorization dashboard earns its budget when it changes a decision on a specific morning, for a specific payer, with a named owner. If it only produces a monthly PDF, it is reporting, not operations.

## Quick answers

### How long should a prior authorization take in 2026?

Under the federal prior authorization rules finalized in January 2024, impacted payers generally must decide expedited requests within 72 hours and standard requests within 7 calendar days. A good internal target is stricter than that ceiling, because a 6.9-day average can still hide requests sitting past 30 days. Most care networks find that tracking the 90th percentile, not the mean, keeps patients out of the backlog.

### Why did our denial rate rise even though care quality did not change?

Denial rates move with payer mix, policy changes, and workflow quality rather than clinical quality alone. A shift toward Medicaid managed care, a new payer's step-therapy rules, or resubmissions marked as new requests can change the rate overnight. Segment by payer and service line before concluding anything, and compare each segment to its own trailing six-month baseline.

### What is a reasonable prior authorization appeal overturn rate?

KFF has reported that a substantial share of Medicare Advantage and Medicaid managed care denials are later overturned, with rates ranging roughly from one in five to more than half depending on the program and state. An overturn rate above 20 percent in a service line is a signal to review documentation and escalation quality. It is not automatically bad or automatically good.

### How often should a care network refresh prior authorization metrics?

Run the queue daily, review denial reasons and aging weekly, and do a payer-level deep-dive monthly. Because appeal decisions can take 30 to 60 days, a dashboard limited to live portal status will understate the true denial burden. A quarterly trend review catches payer policy changes and staffing shifts that daily views miss.

### Can public payer dashboards give us benchmark denial rates?

KFF's analysis of federally required insurer prior authorization reporting found the published data offers little explanation of what gets approved or denied, since it is aggregated and lacks service-line and clinician detail. It is useful as a rough sanity check on timing and volume. Your own request-level records remain the best benchmark for a specific care network.

Canonical: https://getpulse.care/knowledge/what_should_a_prior_authorization_dashboard_actually_measure_in_2026.php
Markdown: https://getpulse.care/knowledge/what_should_a_prior_authorization_dashboard_actually_measure_in_2026.php/index.md