The first of two deliberate gates between an approved estimate and a live project. Until it's released, the customer's portal parks them on an 'estimate approved, finalising details' hold rather than dropping them straight into a questionnaire. Releasing stamps every link for the job, preserving the first-release time, and fires a branded 'your project details form is ready' email with a link back to their portal.
Also called: gate A · hold after approval · let them fill in the details · intake form ready
- 1The builder reviews the approved estimate and presses release.
- 2The server stamps intake_released_at on every unreleased link for the job, org-scoped.
- 3The customer's portal polls and advances itself out of the hold.
- 4A tenant-branded email goes out; the same content tokens compose the text version too, so an org that texts doesn't need a second copy of the facts.
- 5It works for both engines — keyed by job id, design id or the link itself.
An approval is not a green light on its own — the builder needs a beat to check what was actually approved before the customer starts filling in details that generate a contract. Customers are held after approving until the builder releases them to the project-info form, which also emails them that it's ready. One set of wording serves the email and the text, so a builder who turns texting on doesn't get a second copy of the same facts drifting out of step with the first.
- Approval flowing straight into contract generation with no builder review
- Manually telling every customer what the next step is
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 →