When the customer has signed but the builder has not, the footer renders a centred card: a check chip, 'Your signature is recorded', and the line 'Your builder is finalizing the agreement. We'll email you the moment it's fully signed, and your project dashboard will unlock.' The document's own signature grid still shows the builder side as 'Pending builder counter-signature'.
Also called: only my signature showing · waiting for the builder to sign · contract half signed
- 1The branch keys on counter_signed_at being null while customer_signed_at is set.
- 2The in-document builder block renders an empty signature rule with the pending caption, because the document must be honest.
- 3The footer explains the state in the customer's language rather than repeating the grid.
- 4The promised email is real — the counter-sign automation sends a tenant-branded 'your contract is fully signed' message.
The comment is unusually candid about the UX read: 'Showing the half-filled signature grid here reads as an unsettling "only my signature" state. Instead reassure the customer their signature is captured and the builder is finalizing — the dashboard unlocks once it's fully executed.'
- Anxious customers after signing
- A UI that reads as an error when it's just a normal waiting state
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 →