Centaur · Task Queue & Diary System
A hypothetical claim is opened, a litigation status is set, and the system stamps a due date on every task in that status's workflow. This sandbox runs the actual cascade logic live so the dates can be tested before backend implementation. Change the creation date or pick a strategy and everything recomputes.
due date = anchor date + Time, counted in business days (skip Sat/Sun). US holidays are treated as normal working days.
The spreadsheet column "Days from Last Task for Role Type" is a stale label. The anchor is the previous task in the list — not the last task of the same role.
When the status is set, the opening block is stamped up front. Each task cascades off the previous one.
Completing Determine Strategy forks the workflow. The picked option creates its own tasks, anchored on the selection date.
When a task is actually completed, its dependents recompute off the real completion date — across the whole chain, not just the retained block. (Here we assume every task lands exactly on its due date.)
Only the Diary Date: Review Claim task (Do Not Engage) counts calendar days incl. weekends — its 60 is wall-clock, every other number is business days.
Inside the retained block, a few tasks anchor off a specific named task instead of the cascade: Legal Report → Medical Report; Review/Reserves → Counsel's Initial Report.