Deliverables & approvals

Approvals are records, not vibes

Each approval is created, listed and revocable — a real object with an owner and a timestamp behind every gate.

EstiWright — Approvals
technical_proposalApproved by Dana Boss
commercial_proposalApproved by Mona Approver
techno_commercialNo approval recorded
ApprovalsAudit

A hand-built mock in the site theme, modelled on the real screen and populated with our demo tenant's data — not a screenshot. Hover to pause.

More in Deliverables & approvals

Keep going

EstiWright — The deliverable ladder
Mutual NDA docx lockedapproved
Technical Proposal docx lockedapproved
Commercial (BOQ) xlsx lockedready
Techno-Commercial pdf lockedlocked
Draft Contract docx lockedlocked

The deliverable ladder

Five artifacts, each gated on the last: NDA, technical proposal, commercial BOQ, techno-commercial, draft contract.

EstiWright — Deliverables
Technical ProposalExtract the RFP requirements first.
Commercial (BOQ)Attach a costing workbook or add materials first.
Techno-CommercialApprove the technical + commercial deliverables first.

Locked, and it tells you why

A gated rung never just greys out — it states the blocking condition in plain words.

EstiWright — POST /projects/{id}/techno-commercial
409 Conflict
detail: "locked: approve technical_proposal + commercial_proposal first"

The gate is server-side

Skipping a rung is not a UI trick to work around — the API refuses with a 409 and names what is missing.

See this on your own tender.

We'll run your RFP through the same pipeline and show you the output.