Building Contract
Upload the practice's own licensed form once. Avoice pulls out the particulars that the rest of the job depends on, drafts preliminaries that match, and gives every later document the right clause to cite.
Book a demoSectional completion not stated in the uploaded form. Confirm before the first certificate.
Sums, dates, damages, retention and payment periods come straight off the executed form rather than being retyped into a spreadsheet.
A20 is written from the real contract, so the prelims describe the job actually signed instead of a generic template.
Instructions, valuations and certificates all reference the right clause numbers for the form in use.
The contract becomes data, not a dead PDF. Most practices keep the executed contract in a folder and work from memory of what it said. Avoice reads it, holds the particulars as structured fields, and shows the signed document alongside them.
| Document | Type | Status |
|---|---|---|
| JCT SBC/Q 2024 · executed | Main contract | Extracted |
| Client appointment · RIBA 2024 | Appointment | Extracted |
| Structural engineer · sub scope | Sub scope | Uploaded |
| Supplemental agreement 01 | Supplement | In review |
Avoice does not publish contract forms. The practice already licenses the form it uses. Avoice works from that upload, which keeps the licence where it belongs and means the project is administered against the version actually signed, amendments included.
Avoice will use the amended figures. Confirm each one before the first interim certificate.
One set of figures, used by everything after it. Retention percentage, valuation dates, payment periods and damages are not administrative trivia. They decide when a certificate is late and how much a late one costs. Avoice holds them once and applies them everywhere.
Every clause here traces to a particular in the uploaded contract. Change the contract and the prelims flag for update.
