Acknowledge or decline an assignment

Every assignment you hold on a trip needs a response — you either acknowledge it or decline it. This page covers both, from the trip detail screen where they live.

Acknowledge an assignment

1. Open the trip and find your assignment row (it shows your role badge and report time).
2. Tap Acknowledge. The button reads Queued (offline) if you have no connection at that instant, then Syncing..., then Acknowledged once the server confirms it.
3. If the request fails, the button reads Retry with the error — the acknowledgment stays queued locally and the app retries it automatically; you can also tap the button again to retry immediately.

Decline an assignment

1. From the same row, tap Decline.
2. You're asked to confirm — on iOS you can optionally type a reason for dispatch; on other platforms you confirm without a reason (a reason is always optional).
3. The decline is queued the same way an acknowledgment is: Queued (offline) → Syncing... → Declined, retried automatically on failure. A declined assignment is filtered out of your Up Next card and trip-prefetch — it is treated as no longer yours.

What dispatch sees

Acknowledging or declining is not just a local status change — it updates the assignment dispatch sees on their side, immediately once it syncs. If you leave an assignment unacknowledged, dispatch can re-nudge you: a periodic scan identifies unacknowledged assignments, sends you another reminder push (and an email if push can't reach you — see notifications), and reports back to dispatch what was re-nudged and what is still outstanding. Acknowledging closes that loop for you.