# Workbench stakeholder brief

Operations lead: Start each morning with orders that are already overdue and still undelivered, then inspect the hub and route. Historical late deliveries support the review but should not hide the active queue. Filter by hub, service and cohort, open an order's event timeline, and show the review cutoff and last successful data update.

Hub lead: Do not rank staff or hubs using overall rates with different service mixes. Southbay express has too little data for a stable comparison. A route note is an investigation lead, not proof of an employee's responsibility.

Security lead: Operators may read only their assigned hubs. Exports require supervisor or service permissions, checked on the server for every request together with session validity. Use the existing corporate identity service and do not add a password store. Choosing a hub in the UI does not grant access.

Delivery lead: Phase one is a read-only workbench, order evidence timeline and controlled export design. Refunds, dispatch writes and customer notifications are excluded. Integration depends on client identity, gateway and order interfaces. Estimate effort, define acceptance, failure handling and rollback. No budget, contractual response SLA, concurrency target or launch date has been agreed; list them as decisions to confirm.