Clinical reviewer hours
Spent on documentation hunting and criteria lookups instead of clinical judgment. Highly trained nurses and physicians orienting to cases instead of evaluating them.
Prior auth, concurrent, retro, appeals, and grievances on one Operating System. Documentation hunting, criteria lookups, and evidence assembly come off your clinicians' desks. Every recommendation arrives at the reviewer's queue with the time-consuming work already done.

The problem
Health plans have been trained to scale UM the same way for decades. Add headcount when volume rises. Buy a tool when a workflow breaks. Layer governance on top of fragmented systems. It made sense when volumes were predictable and regulators were patient. Neither is true anymore.
By the time it's all stood up, you don't have a UM strategy. You have a stack of vendors, a hiring pipeline that cannot keep up, and a medical director queue that grows faster than it clears.
Here's where it breaks: the model assumes UM is a staffing problem. It is a system problem that staffing has been asked to solve. Every reviewer you hire enters the same broken workflow, with the same inconsistent criteria application, and the same documentation gaps. The bottleneck moves to the next person. The administrative burden stays the same.
01
Volume rises.
PA requests, concurrent reviews, retro intake, appeals. All climbing.
02
Hire more reviewers.
Slow, expensive, and the clinical talent pool is shrinking.
03
Buy a point solution.
A tool for prior auth. Another for appeals. Another for grievances. Each with its own queue.
04
Repeat.
Every quarter. Every audit cycle. Every regulatory update.
When prior auth, concurrent review, retro, and appeals all live in separate systems, the same case gets re-evaluated three times by three different teams who cannot see each other's work. That is an operating model problem that point solutions have created and then sell you more software to manage.
The lightbulb
There is a moment when it clicks. Health plans stop asking "how do we staff up appeals?" and start asking "why is this volume here in the first place?" The answer is the same every time. Criteria are being applied inconsistently at intake. Documentation gaps are not being caught until after the recommendation has issued. And nothing in the current stack closes the loop between what gets overturned at appeal and what gets reviewed at prior auth tomorrow morning.
Engine 01
Apply criteria consistently before the recommendation issues.
Closed loop
Engine 02
Appeals, IRO, and grievances handled end-to-end with every outcome captured and routed back.
Each appeal outcome and retrospective finding feeds back to prospective review so the same gap does not repeat.
Catch documentation gaps and apply criteria consistently before the recommendation reaches your medical director. Cases arrive at the reviewer with rationale documented, criteria mapped, and evidence organized.
Requests received from provider portals, fax, EHR integrations, or direct API. Clinical documentation extracted and organized. Zero manual data entry by UM staff.
Cases prioritized by urgency, regulatory deadline, and plan type. Workload distributed across staff based on capacity and case type so reviewers get the right cases at the right time.
Medical necessity criteria, evidence guidelines, and proprietary plan criteria applied consistently. Documentation gaps identified before the case reaches your reviewer.
Standard cases prepared with full rationale documented. Denial-track cases arrive at your medical director's queue ready to issue. Complex cases surfaced with evidence already mapped to criteria.
Inpatient and outpatient stays monitored in real time. Length-of-stay criteria applied continuously as clinical status evolves. Post-acute transitions, observation validation, and SLA tracking handled within the same workflow.
Your reviewer accepts, modifies, or overrides every recommendation. The clinical judgment belongs to your team. Nothing issues without your clinician's sign-off.
Retrospective recovery
Post-service review, appeals, and grievances handled in one workflow. Every outcome captured. Every signal routed back to the front end.
Post-service documentation reviewed from intake through final disposition. Retro exception logic applied. Criteria matched. Adjudication recommendations prepared with complete supporting evidence.
First-level, second-level, and IRO coordination handled within a single workflow. Cases routed by complexity, regulatory deadline, and plan requirements.
New clinical evidence identified and analyzed against the original recommendation. Documentation gaps flagged. Criteria re-applied with full traceability.
Appeal recommendations and supporting rationale assembled. Medical directors receive cases with evidence mapped and clinical context organized for their review.
Member grievances logged, categorized, and routed with full documentation. Regulatory timelines tracked at every stage.
External review packets assembled. Communication tracked. Outcomes captured and reconciled.
Every appeal outcome and grievance resolution captured. Patterns identified. Quality and financial impacts reconciled.
Root cause of every overturned recommendation routed back to prospective review. Each appeal outcome strengthens the next intake. The system gets smarter every cycle.
Every overturned appeal teaches prospective review how criteria are being applied and where documentation gaps repeat. The two engines make each other smarter. Your current vendors cannot do this. They do not talk to each other.
Prior auth, concurrent, retro, appeals, grievances, IRO. All on one Operating System. No point-solution stitching. No reviewer toggling between four systems to evaluate one case. No queue handoffs where context gets lost.
Reviewers and medical directors see exactly how every recommendation was reached and apply their clinical judgment. The Ai Workers handle documentation extraction, criteria matching, and evidence assembly. Your team gets back to the work their training is for.
Your core admin platform stays the system of record. Provider portals stay the intake path. Nothing issues without clinical approval. No rip-and-replace. No parallel infrastructure to manage.
Health plans operate under CMS, NCQA, URAC, and state regulatory frameworks. Trust and accountability are not optional. Penguin Ai was built with governance as a structural requirement.
Every recommendation surfaces the criteria applied, the clinical data reviewed, and the reasoning behind it. Your medical directors verify, stand behind, and present every recommendation to any regulator or IRO with confidence.
Every recommendation, denial draft, and appeal action documented with clinical reasoning, criteria applied, and data sources referenced. Regulatory review-ready at all times.
Statutory and contractual timeframes tracked automatically across Medicare Advantage, Medicaid, and commercial lines. Deadlines met without manual monitoring.
Medical necessity criteria, evidence guidelines, and proprietary plan criteria applied consistently with no workarounds or manual lookups.
Penguin Ai and your clinical staff work in tandem. The Ai Workers prepare the work. Your reviewers and medical directors apply their expertise and make the call.
Every appeal outcome and reviewer override strengthens future recommendations across prospective and retrospective workflows.
The next time someone tells you the answer to your UM backlog is more reviewers or another point solution, ask what that actually delivers for members waiting on authorizations and clinicians buried in documentation this week.
UM should give your clinical staff their time back. It should give your medical directors recommendations they can stand behind. It should give your members responses at the speed of human need.