Work your queue in My Work
Use My Work to manage assigned tasks, due items, and next actions without losing sight of what matters first or which claims are starting to drift.
Guide
Read reporting and performance
Use reporting to understand throughput, bottlenecks, and operational health instead of relying on anecdotal activity or whoever spoke up most recently.
Outcome
What this helps you do
Turn reporting into an operational review habit that supports better decisions and more confident workflow adjustments.
This guide is written for owners and uses real claimOS screenshots so the instructions map cleanly to the product surface.
Prerequisites
Before you start
- A workspace with enough recent activity to review trends meaningfully.
- A specific operational question about queue health, throughput, response speed, or handoff quality.
- Someone who can act on what the review uncovers.
Steps
How to do it
1Start with the question you need answered
Do not open reporting just to browse charts. Know whether you are checking volume, conversion, SLA risk, or a specific handoff problem.
2Choose the metric view that matches the decision
Pick the KPI or trend group that is most likely to explain the decision in front of you so the review stays focused on signals that can change action.
3Review the right metric group
Move to the KPI or trend view that matches the decision in front of you so you stay focused on actionable signals.
4Compare the reporting view to current operating reality
Use the live queue, claims activity, or current workload context as a reference point. Reporting is strongest when it helps explain what the team is already seeing on the ground.
5Compare what you see to daily operating reality
Metrics should explain work, not replace judgment. Use them to confirm or challenge what the team feels operationally.
6Translate the insight into one workflow adjustment
Decide what should change in routing, staffing, follow-up, or configuration before you leave the dashboard so the review actually changes behavior.
7Turn insight into one clear next adjustment
Every review cycle should end with a concrete operational change, whether that is staffing, routing, follow-up, or configuration, so the dashboard leads to behavior instead of just awareness.
8Check whether the next review cadence is clear
Good reporting habits depend on rhythm. Make sure the team knows when this metric or trend should be revisited and who is expected to own that follow-up.
If the dashboard review ends without an owner, a change, or a next review point, it will likely turn into passive observation instead of operating discipline.
Screenshots
See the workflow
Watch the paired walkthrough
Walkthrough0:56
See the same workflow in motion
A short buyer-facing walkthrough of how claimOS becomes the operating layer for launch, live claims work, evidence, communications, and reporting.
Start with the high-level buyer question: what does claimOS unify that most teams currently spread across multiple tools and private follow-up loops?
Watch related walkthroughFAQ
Common questions
Should operators work from Home or My Work first?
Use Home to orient to overall risk, then move into My Work for task-by-task execution and due-work follow-through.
How often should the queue be reviewed?
At minimum, review it at the start of the day, after major claim intake spikes, and before the team wraps work.
How often should reporting be reviewed?
Use a regular operating cadence, not occasional curiosity. A weekly review is usually the minimum for spotting drift, and faster-moving teams may need daily checks on queue health or SLA risk.
What is the mistake to avoid when looking at performance data?
Do not stop at noticing a number changed. The useful step is translating that change into one routing, staffing, follow-up, or workflow adjustment the team can actually make.
Keep Going