Work Queues

Work Queues are per-user prioritised task lists generated from the platform's operational state. Instead of scanning ten different screens for "what do I need to do today", the queue surfaces it all in one ordered view.

Overview

Lives at /app/forwarding/work-queues. Tasks are auto-generated from platform events; you don't manually create them (though you can snooze, reassign, or mark complete).

Task types:

• Confirm booking — carrier has responded; your confirmation is needed to move the booking forward.
• Issue document — the booking is locked but the MBL / MAWB / delivery order hasn't been printed yet.
• Follow up with customer — a quote has been sent but no response for N days.
• Process customs hold — a customs declaration is held and awaits action.
• Submit post-release docs — customs docs submission overdue (we're past the 14-day grace period).
• Record POD — road trip marked delivered but no POD uploaded.
• Reconcile AP bill — a carrier invoice has arrived and is unmatched to a booking.
• Review exception — milestone out of order, unexpected carrier event, etc.

Priority ordering

Tasks are ordered by:

1. Overdue (past deadline) → red.
2. Due today → amber.
3. Due this week → grey.
4. No deadline → grey at the bottom.

Within a priority tier, tasks order by booking value (high-value first) then by age (oldest first).

Task detail

Each row shows:

• Task type icon + title.
• Source booking / customs declaration / trip (clickable).
• Age (time since task was generated).
• Deadline (if any).
• Assignee (defaults to booking's ops owner or sales owner).
• Quick-action buttons (Confirm, Snooze, Reassign, Mark Done).

Click the row to open the source record in a side panel without leaving the queue.

Snoozing

Sometimes a task is blocked on external action (waiting for the customer, the carrier, or a document). Snooze it:

• Snooze until tomorrow — re-appears next business day.
• Snooze 3 days — common for customer follow-ups.
• Snooze 1 week — for longer waits.
• Custom date — pick a specific return date.

Snoozed tasks aren't gone; they just hide from the active queue until the snooze expires.

Reassigning

If a task is on your queue but belongs to someone else (e.g. customs team picks up customs tasks from an ops user's queue), drag-to-reassign. The other user sees it on their queue immediately.

Reassigning re-sets the ownership on the source record — so if you reassign a customs task to the customs team, the customs declaration's ops owner flips too.

Auto-completion

Most task types auto-complete when the underlying condition is resolved:

• Confirm booking auto-completes when the booking transitions to confirmed.
• Issue document auto-completes when the document is generated.
• Submit post-release docs auto-completes when the customs declaration moves to docs_submitted.

You rarely need to manually mark tasks done.

Notifications

Per-user notification settings:

• Daily digest email (morning) with today's queue.
• Real-time push when a high-priority task is added (overdue or due today).
• No notifications for snoozed items.

Configure in Settings → User Preferences → Notifications.

Common pitfalls

Reports

• Queue Aging — how long tasks sit before completion, per task type.
• Overdue Trend — count of overdue tasks over time; flags process breakdowns.
• Per-user throughput — tasks completed per user per week.

All under Forwarding → Reports.