Building a Prior Authorization Team: Roles, Training, and Workflow

Walk into most specialty practices and ask who handles prior authorizations. The answer is almost always some version of "whoever isn't swamped right now." That approach costs real money — in denials, in rework, in staff burnout, in delayed patient care.

A properly structured PA team changes the math entirely. This isn't about hiring more people. It's about assigning the right responsibilities to the right roles, training them to a consistent standard, and building a workflow that doesn't fall apart when someone is out sick.

Start With Practice Size, Not an Org Chart

The right team structure depends on your volume. A solo rheumatologist processing 15 PAs per month has different needs than a five-physician gastroenterology group running 120 cases monthly.

Solo Practice or Small Group (Under 30 PAs/Month)

One dedicated billing coordinator who owns the entire PA workflow end to end. The key word is dedicated — not someone who also handles scheduling, phone triage, and claims. Splitting attention is where things fall through cracks.

The physician handles all peer-to-peer reviews directly. Keeping a simple tracking spreadsheet is sufficient at this volume.

Mid-Size Practice (30–100 PAs/Month)

This is where you need role separation. One person can't effectively manage intake, documentation, submission, follow-up, and appeals simultaneously without something slipping.

The core team at this size: a PA coordinator who owns the intake-to-submission pipeline, and a billing specialist who handles denials, appeals, and payer escalations. These can be the same person if volume is at the lower end — but the responsibilities need to be explicitly separated even if one person holds both.

Large Practice or Multi-Site Group (100+ PAs/Month)

You need a dedicated function. The MGMA benchmarks suggest one FTE per 50–60 complex PA cases per month for specialty practices. At scale, that typically breaks into three distinct roles.

The Three Core Roles (And What Each Actually Does)

PA Coordinator

This is the engine of the operation. The PA coordinator owns intake: they receive referrals or treatment orders, verify insurance, check prior auth requirements with the specific payer, gather the clinical documentation from the physician, and submit the request. They also track open cases and flag anything approaching a deadline.

What separates a good PA coordinator from a mediocre one: they know the difference between what they need to submit and what they're likely to actually be asked for. Submitting the minimum gets you denied. Submitting a well-organized packet that pre-answers the reviewer's likely objections gets you approved.

Training focus: payer portals, coverage determination databases (Micromedex, CoverMyMeds), ICD-10 coding specificity, and documentation formatting. The prior authorization certification programs from NAHAM and AAHAM offer structured training worth investing in.

Clinical Documentation Specialist

At mid-to-large practices, this role is the difference between a 65% and a 90% first-pass approval rate. The clinical documentation specialist works directly with the treating physician to ensure the medical record supports the requested treatment — before submission, not after a denial.

They know the LCD/NCD criteria for each drug and indication. They can read a chart, identify what's missing, and work with the physician to document the gaps. They aren't writing clinical notes — they're ensuring the clinical story the record tells matches what the payer needs to see.

This role requires some clinical background (an RN or experienced MA with billing exposure is the common profile) and deep familiarity with the specific drug class the practice uses most.

Appeals Specialist

Denials require a different skill set than submissions. An appeals specialist understands the administrative law framework behind the appeals process, knows how to craft a written appeal letter that references the payer's own clinical criteria, and can escalate appropriately when a peer-to-peer review is the right move.

Small practices often can't justify this as a standalone role. The same coordinator handles appeals — but should be trained specifically for it. Writing a good appeal is genuinely different from writing a good submission. One of the most useful resources for this training is the CMS Medicare appeals guidance, which covers the procedural framework that many commercial payers mirror.

The Workflow: Intake to Resolution

A reliable PA workflow has five stages. Every case should move through them in sequence, and every handoff should be explicit.

Stage 1: Intake and Benefits Verification

Triggered by a treatment order. The coordinator verifies insurance, confirms whether PA is required for the specific drug and indication, and identifies the correct submission pathway (payer portal, fax, or third-party hub like Surescripts). This stage should take under 30 minutes for any case.

Stage 2: Documentation Assembly

The clinical documentation specialist (or coordinator at smaller practices) pulls the relevant chart elements: diagnosis codes, lab values, disease activity scores, prior treatment history with documented outcomes, step therapy attempts. The goal is a documentation packet that tells the clinical story without requiring the reviewer to do any interpretive work.

This is the highest-leverage stage. Getting documentation right here prevents rework at every subsequent stage. It's also where AI documentation tools have the biggest impact — assembling and formatting the clinical narrative against payer-specific criteria is exactly the kind of repetitive, high-stakes work that can be automated.

Stage 3: Submission

Electronic submission where possible — CAQH data consistently shows electronic PA processing takes 6–10 days faster than fax-based submission. The coordinator logs submission date, method, and confirmation number. Every submission gets a follow-up date set at 3 business days.

Stage 4: Tracking and Follow-Up

Open cases need active status checks — not waiting for the payer to call you. At three days with no decision, follow up. At five days, escalate. A simple tracking system (even a spreadsheet with color-coded status) prevents cases from aging unnoticed. Most practices that struggle with PA turnaround times have a tracking problem, not a submission problem.

Stage 5: Appeals

A denial isn't the end of the road. First-level appeals on biologics succeed roughly 40–60% of the time when the appeal is well-constructed. Luma's blog covers the mechanics of peer-to-peer versus written appeals — the short version is that peer-to-peers are faster but require physician time, while written appeals create a paper trail for external review if needed.

Technology Stack for the PA Function

You don't need expensive software to run a solid PA function. You need the right tools connected to each other.

At minimum: access to payer portals (most major payers have web-based portals now), a coverage determination tool like CoverMyMeds or Surescripts NetworkAlliance, and a case tracking system. The tracking system can be a spreadsheet until you're processing 50+ cases per month — at that point, something purpose-built pays for itself in visibility alone.

For documentation specifically: this is where AI tools deliver the clearest ROI. Building medical necessity letters from scratch against payer-specific criteria takes 30–45 minutes per case manually. Tools like Luma compress that to under 2 minutes by structuring the clinical data against the correct LCD/NCD criteria automatically and generating a submission-ready document. At 60 cases per month, that's 28–43 hours of staff time back per month.

KPIs for Your PA Team

You can't manage what you don't measure. Track four metrics from day one:

• First-pass approval rate: Target above 85%. Below 75% means documentation problems.
• Average turnaround time: Time from submission to decision. Benchmark is 5–7 business days for commercial payers.
• Appeal success rate: How often you win on appeal. Under 40% suggests you're appealing the wrong cases or your appeals aren't strong enough.
• Cost per PA: Total PA team cost divided by monthly case volume. Useful for evaluating whether staff or technology investments make sense.

The Mistakes That Sink PA Teams

Three design errors come up repeatedly in practices struggling with PA performance:

No clear ownership. When everyone is responsible for PA, no one is. Cases slip, follow-ups get missed, and denials sit unworked. One person or role needs to be the accountable owner of each case at each stage.

Mixing PA with general billing work. Prior authorization requires focused attention. Interrupting a coordinator mid-submission to handle a patient call or process claims is a recipe for errors. Protect PA time the same way you'd protect physician clinical time.

Skipping payer-specific training. United, Aetna, Cigna, and Humana all have meaningfully different documentation preferences, portal workflows, and escalation pathways. A coordinator trained on United's process won't automatically be effective on Cigna without specific exposure. Building payer-specific SOPs — even simple one-page reference sheets — is worth the upfront time.

The Bottom Line

Building a PA team isn't a headcount exercise. It's a workflow design exercise. Define the roles clearly, train to a consistent standard, build a workflow with explicit handoffs, measure the right things, and give the team the tools to stop spending 40 minutes on documentation that can be done in 2.

Practices that do this right achieve first-pass approval rates of 88–92%. The ones that treat PA as everyone's side job tend to hover around 65%. The difference is almost entirely structural — not clinical.

Sources: MGMA Staffing Benchmarking Reports (mgma.com); CAQH Index 2023, "Measuring the Progress of Electronic Health Care Administrative Transactions" (caqh.org); CMS Medicare Provider Appeals guidance (cms.gov); NAHAM/AAHAM prior authorization training certification resources; American Journal of Managed Care, "Prior Authorization: Current Experiences and Ways to Improve the Process."