Verbal yes, unsigned contract
The customer agreed. Nothing can be ordered, scheduled or invoiced against a handshake.
What's the leak?
The customer agreed. Nothing can be ordered, scheduled or invoiced against a handshake.
What it looks like
The customer says yes on Thursday. The contract goes out Friday. Two weeks later it's still unsigned — the spouse hasn't seen it, nobody chased, and the crew slot that was informally held has been given away twice.
Why it happens
Signature is treated as an errand rather than a lifecycle state. There's no aging clock, no named signer, and no rule for what happens when a second party is required.
What it costs
Work that isn't legally committed can't be planned against, so either capacity gets held for nothing or the job loses its place in the schedule.
How URBLD closes the leak
Sent-to-signed is a tracked state with an owner and an age. Multi-party signing has an order, reminders are automatic, and the signed artifact and its audit trail stay on the record.
Leak diagnosis
- Observed symptom
- The customer said yes, but the signed contract still isn't back days later.
- Inferred root failure
- Signature is treated as an errand rather than a tracked lifecycle state with a named signer and expiry.
- Lifecycle stage
- Contracting
- Financial or capacity consequence
- Verbal wins can't be scheduled or ordered against, so crew capacity is held for work that isn't yet legally committed.
Measure it yourself
Count of contracts in 'sent, not signed' and the age of each; share requiring more than one signer.
Practical diagnostic
List every contract sent in the last 30 days that isn't signed and note who was waiting on whom.
Recommended operating response
Track sent-to-signed as an aging state with reminders and, where more than one party signs, an explicit signing order.
Deeper explanation: Electronic signature workflow
Related Features
Related Workflows
Other leaks worth checking
See how URBLD closes every leak
One connected workflow from the first lead to the final payment.