The customer-facing contract data includes counter_signer_name, counter_signed_at and counter_signature_image, rendered into the document's Signatures block under 'Builder — <company>'. The same fields drive the fully-signed footer state and gate the portal dashboard's agreement tile.
Also called: builder signature on customer copy · fully executed · both signatures
- 1The public contract endpoint selects both signature blocks.
- 2The document renders the builder block with the drawn signature, name and date once counter_signed_at exists.
- 3The dashboard tile only appears when the contract is fully executed, so 'a customer-signed-only contract never offers a half-executed PDF'.
Two fixes converge here. On the customer side: 'Added 2026-— before that the customer side only ever displayed their own signature, so a counter-signed contract looked the same as a still-pending one.' On the endpoint: 'Prior SELECT omitted the counter_* columns, which made the modal stale-render "Pending" for the counter-signature even after the admin had counter-signed seconds earlier.'
- Executed contracts indistinguishable from pending ones on the customer's copy
- A stale 'Pending' counter-signature caused by a missing column in the read
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 →