Admin Portal · Plan operations

Put the number where it cannot be walked past.

Plan-side administration for a Medicare Advantage organization: enrollment lifecycle, agent onboarding and approval, scope-of-appointment compliance, authorizations, correspondence, workflow and user administration, with a data-health layer that keeps every queue in view.

See the admin portal →

Admin Portal · Dashboard

Why it was built this way

Every queue in the plan, measured.

Plan operations run on queues: agents waiting for approval, applications waiting for a decision, scope-of-appointment forms waiting for a signature, tasks waiting for an owner. The admin portal counts each one, states the expected level beside the observed one, and names the owner, so the number is visible before it becomes a finding.

Agents

approval queue aged by days pending, with registry verification and bulk approval of clean files

Eligibility

every "not eligible" decision carries a recorded reason, and the share of the book is tracked against an expected level

SOA

scope-of-appointment signature status by agent, with an escalating chase for the unsigned

Accounts

dormant and never-used accounts surfaced by the data-health layer before an auditor asks

Tasks are clustered rather than listed, so a thousand near-identical alerts become a couple of dozen decisions, and the authorizations queue lives beside them with its own due dates.

Fourteen modules

What each module does.

DashboardFindings before figures: measured deviations from stated expectations.

MembersEnrolled, pending, disenrollments, not eligible with a reason required, new enrollment.

AgentsApproval queue with automated registry verification and bulk approval of clean files.

Scope of appointmentSignature status, compliance exposure by agent, an escalating chase for the unsigned.

Health risk assessmentsRoster and handoff to the Vernier HRA application.

CredentialingRoster and handoff to the Vernier Credentialing application.

AuthorizationsIntake extraction from unstructured requests, criteria triage, determinations recorded by a person.

CorrespondenceDrafting with a CMS communications and marketing pre-check before anything goes out.

TasksClustering and triage: a thousand rows become a couple of dozen decisions.

NotificationsDigested by default so it cannot become a second task backlog.

WorkflowSaved automations written from a sentence, always drafted before they run.

ReportsAsk in words; the interpretation is shown back to you before the result.

Data healthDuplicates, test records, stalled workflows, dormant accounts.

AdministrationUsers and access, FMOs, internal rates, AI activity log.

Roles that mean something

A clinical account cannot reach the agents module. A read-only account cannot change anything.

Six roles ship by default: administrator, member services, agent services, clinical, compliance and read-only. The boundaries are enforced in middleware rather than hidden in the navigation, so a clinical user is redirected away from agents, an agent-services user away from authorizations, and the read-only account cannot submit a form anywhere.

Compliance sees scope-of-appointment exposure, data health and audit trails, read-only elsewhere. Member PII does not export unlogged.

Agent approval queue in the Vernier Admin Portal

See your own queues measured.

Bring the counts you track by hand today. Bruce will show you the portal that keeps them in view.

Schedule 20 minutes →