Give each person a queue: what is assigned, what is due, what was done in the last seven days, and a light, medium, or heavy load bar.
Every gap becomes a work item with an owner.
Population health tools point to the problem. This module puts it to work. A coder works their own queue, a lead balances the team's, and both read the same productivity measures from opposite sides, with a quality figure beside every pace figure because volume alone says nothing.
What it is for
What Work List does
Give the lead the whole board: unassigned and overdue items, workload by person, department, and location, and one-click redistribution of a colleague's pending work.
Measure fairly: opportunity burn-down, closure trend with a sweep-deadline projection, active review time with idle time excluded, and rework read as a signal rather than a verdict.
The screens
The screens, in the order you would use them
- 1
My Work List
Your own queue: open, in progress, overdue, and done in the last seven days, with personal figures that describe your work and say what they will not support as a conclusion about anyone else's.
- 2
Command Center
Oversight across every list: who has what, where the load is uneven, what is overdue or unassigned, and the option to open any coder's queue exactly as they see it.
- 3
Productivity
The measures, for the organization or the team: burn-down, closure trend, work by location, contractor and staff panels, and time captured automatically with an on-screen indicator and a consent notice.
Honest numbers
What the figures count
Every figure on every screen has a definition behind it. These are the ones this module runs on.
- One opportunity
- One member, one code, one year. Everything in this module counts in that unit.
- Opportunities per day and per active hour
- Pace, two ways. Per day divides by calendar days, so leave and weekends sit in the denominator; per active hour uses captured review time with idle time excluded.
- Acceptance rate
- Of the suggestions surfaced to providers, the share accepted. Where no provider has ruled yet it shows N/A, never 0%.
- Rework rate
- Reopens capture new information and policy changes as well as genuine rework, so it is read beside pace, never alone.
What can go wrong
What this module will not let you misread
Treating a skip as a completion
A skip returns the opportunity to the pile, so the queue does not shrink. A skip with a reason is credited as finished work; a skip without one is not counted at all.
Reading volume without a quality signal
Opportunities completed says nothing on its own, which is why the product always shows a quality figure beside pace.
Comparing a coder's pace across different ranges
Short ranges are volatile and calendar days hide leave. Compare like ranges, or read the per-active-hour figure.
Where the data comes from
The work-event history, an immutable record of assignment, start, completion, skip, and reopen, plus provider decisions recorded against surfaced suggestions. The "Add to Work List" action appears wherever a decision is made in Risk IQ and Q-Track, so nothing found in an analysis stays in an analysis.
How Alara Healthcare uses it
This is the module Alara Healthcare runs its monthly cadence on: gaps assigned to coders, coordinators, and providers, closed work reappearing as a measured rate the following month, and the provider seeing how that work shows up in the visit with the patient in front of them.
Care Programs servicesQuestions people actually ask
Work List questions
I've been skipping items all morning and my queue isn't getting smaller.
A skip is not a completion. It returns the opportunity to the pile, so the queue is unchanged and the item stays counted as open. Only a completion removes it. If an item genuinely cannot be worked, record the reason with the skip: a skip with a reason is credited as finished work.
One of my coders has reopened work showing against them. Is that a mistake on their part?
Not necessarily. Reopens capture new information arriving and policy changes as well as genuine rework, so a reopen is a signal to read rather than a verdict to act on. Every productivity page states plainly what it will and will not support as a conclusion about someone else's work.
Productivity only shows my own stats. Where is the team view?
What you land on is decided by your role. A coder sees their own figures inside My Work List, a team lead sees the team view, and an organization-level role sees aggregates. Individual activity is deliberately limited to team managers. The wider view is a role change handled in Admin, not a setting on the page.
See Work List on your own file layout.
Bring a sample payer file to the demo and we will show you where it lands, what it surfaces, and who works it.