Follow-ups
Follow-ups (Operations → Follow-ups) is the cross-estimate task queue — every open follow-up in one place, so nothing waits in a single file’s detail page unnoticed. The nav link carries an overdue count pill when any are past due.
Stats
Three cards summarize the queue: Open, Overdue (warning), and Closed.
The queue
A table sorted overdue → pending → done, then by due date. Columns: task title, kind chip,
the linked estimate, carrier, ball pill, owner, due date, and status pill. Each open row
has a Done button (POST /api/followups/:id/complete); completed rows show the button disabled.
A status filter (All · Overdue · Pending · Done) narrows the list, which paginates client-side at 25 rows per page.
Where follow-ups come from
Follow-ups are created three ways:
- Automatically when an auditor revision is logged — a
respondfollow-up is generated with the computed SLA due date, plus any follow-ups a matching carrier rule produces. - Manually from a deal detail page via + Add follow-up.
- Via the API —
POST /api/estimates/:id/followups.
Completing a follow-up records a follow-through event on the estimate’s activity log.