Clicking a row in the pending assignments list opens an in-place modal showing who it's waiting on, the crew and assignment date, and any stated reason. Actions: Remind (which confirms with 'Reminder sent ✓'), 'Sign it myself (as owner)' for admins and PMs, and a two-step Delete guarded by a red confirmation.
Also called: waiting on the crew lead to sign · remind the crew · pending assignments · unsigned crew contract · who hasn't signed yet · chase the crew lead · pending acceptances
- 1The modal shows a pulsing 'Awaiting signature' indicator and the sentence naming the crew, date and lead.
- 2Remind sends a nudge and flips the button to a sent state.
- 3Sign-it-myself opens the acceptance signature flow as an owner override.
- 4Delete is manager-only and explicit that 'The project isn't deleted — you can re-assign a crew and sign the acceptance contract from the project's crew section any time. This can't be undone.'
- 5On a failed delete the modal stays open so the user can retry.
The modal exists 'so a manager never navigates away' from the queue, and the delete path is scoped to real cleanup: it 'Permanently remove[s] a pending crew-acceptance assignment from the Pending Contracts queue — for a trashed/test project, or one created in error… Hard delete; intended for PENDING (unsigned) assignments.'
- Projects blocked on an unsigned crew acceptance with no visible queue
- No way to nudge a crew lead from inside the app
- Test or erroneous pending contracts clogging the list
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →