Tasks span workspace, claim, and cash-job scopes with role-based assignments, due dates, and overdue flags. Bulk creation and recurring rules cover routine work. Claim-aware automation spawns the right task at teardown, supplement submission, parts arrival, and repair completion so nothing falls through between stages.
When teardown starts, tasks fire automatically: photograph hidden damage (body tech, same day), flag supplement items on the claim (estimator, same day). When a supplement is submitted to the carrier: follow up on adjuster response (estimator, 3 business days), update customer on approval window (front desk, same day). When parts arrive: mirror-match against the estimate (parts, same day), move vehicle to body stage (production manager, next morning). When repair is complete: run final QC walkthrough (QC tech, same day), schedule customer pickup (front desk, after QC). The automation matches the way the shop actually works.
Bulk task creation covers the work that applies to multiple claims at once: DRP photo compliance reviews, carrier checklist audits, month-end reconciliation. Recurring task rules cover the routine weekly and monthly work that should not need to be re-created from scratch each cycle. Tasks can be assigned to a role (all estimators) or a specific person. Due dates and overdue flags surface on the production dashboard so nothing ages without someone noticing.
Technicians and production managers run the day from the bay. The task list on mobile shows assigned work, claim context, and completion checkboxes without requiring the tech to touch a desktop. Status updates and completion timestamps sync to the claim record in real time. The production manager can see the floor from the office without walking each bay. All task data feeds into the cycle time and productivity reports.
Yes. When a supplement is submitted to the carrier, Claimory can automatically create a follow-up task assigned to the estimator with a due date of 3 business days. If the task is not completed by the due date, it surfaces as overdue on the dashboard. The estimator does not need to remember to follow up; the task does the remembering.
No. Technicians have a role-scoped view: assigned tasks, the claim context they need to complete the work, and completion checkboxes. They do not see financial data, supplement details, or billing information. The tech gets what they need to do the job; the owner controls what they can see.
Every task has a completion timestamp. Stage transitions driven by task completion feed the cycle time calculation for each claim, from intake through delivery. The cycle time report shows where time is being added at each stage so the production manager can find and fix the bottleneck.