SIGNED mode renders the immutable agreement_body snapshot, the frozen project info, the signer's typed name, drawn signature image and timestamps, with a tab per signature. PENDING mode renders the current active template body with an 'Awaiting signature' note in place of the signature block. A Print / Save PDF button uses the browser's print flow against a print stylesheet.
Also called: view crew contract · what did the crew sign · print crew agreement
- 1Signatures load first; if none exist, the current assignment and active agreement are loaded so the document still renders.
- 2An email deep link with autoSign jumps a crew lead straight into signing.
- 3On a successful sign the view flips optimistically to the signed document, then reconciles with the database in the background.
- 4A hasSigned guard stops a lagging read from regressing the view to pending.
Two fixes are recorded. The pending renderer: 'we still render the full agreement DOCUMENT (the current active template body) so the builder can read exactly what the crew is being asked to sign… This is the fix for the previously-blank view on unsigned assignments.' And the optimistic flip: 'Without this the view kept showing "pending" until a manual refresh because getProjectSignatures could race the insert.' The component is read-only by design — 'No write operations live here — signatures are immutable by design.'
- A blank document view for unsigned assignments
- Read-after-write races showing a stale pending state
- No export path for a signed crew agreement
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 →