You and the LPCC open the same console, but the platform knows which chair you sit in. Five acts are reserved to you, and only you: you conduct the initial evaluation, you complete the causation determination, you sign evaluations — which generates the PR-3 / DFR — you co-sign the RFAs your therapist drafts, and you declare maximum medical improvement with its §4663 apportionment. The LPCC sees these surfaces but is redirected when they reach for them.
The dashboard is built around the truth that you have many cases and limited attention, so it opens on a single "do this next" hero card. That card surfaces the most urgent action across your whole caseload — a blocking deadline, a causation that's come due, an RFA awaiting your signature — and nothing competes with it for the top of the screen.
§4663The California Labor Code section requiring apportionment of permanent disability between industrial and non-industrial causes, which you apply at MMI.Below the hero sits your active caseload and a 30-day GAF trend, so you can see at a glance whether the people you're treating are moving in the right direction before you ever open a chart.
The hero is computed from real deadlines and queue state, not a static to-do list. If it tells you Sofia's RFA needs your signature, that is because the §4610 clock has not yet started — acting on the hero is acting on the binding thing.
The discipline this dashboard asks of you is simple: clear the hero, scan the trend, then triage the caseload. Most days, the platform has already found the one thing that, left undone, would breach a deadline or stall a patient's care.
An LPCC opens the shared console and tries to complete the causation determination on a case. What happens?