Contract & documents — the main contract

Open this screen in Saral/projects/commercial

The main-contract record for one project: who the client is, the form of contract, the sum, the dates and the retention; the letters of intent the job runs on before the contract is signed; the set-up register (particulars still to settle, securities and annexures, the named parties); and the review register that holds the clause comments and derogations, round by round. Everything downstream — the packages, the application, the notices — reads the figures held here.

You enter

The contract details: client, contract type, contract sum (or the LOI cap / PCSA fee while there is no contract), retention %, start on site, completion, payment terms, floor area and the site address.
Each letter of intent (or an import of the cap workbook) and each round of contract negotiation (import the clause comments or an issue of the derogations).
A particular's working position, owner and due date; whether a security applies and what the requirement is.

Saral fills in

The stage (LOI, contract signed, PC, final certificate) from the documents on file — a person may override it with a reason.
The LOI cap tracker: cap now, applied to date, certified, open orders, what is left and the days the letter has to run, from the letters and the application register.
Each security's status from the documents filed and the group's insurance register, with its source beside it.
The handover pack and the won-tender import, which seed the record from the tender.

It produces

The contract record every other Projects screen reads (retention, payment terms, dates).
The LOI cap request pack (Excel with formulas, PDF).
The contract set-up register and the contract review register as Excel and PDF.

What this page is for

Before any package is let, the main contract's facts have to be in one place: what was agreed with the client, on what form, for how much, and what is still open. This tab is that place. The figures it holds are read by the application (retention, payment terms), by the payment notices (due and final dates) and by every subcontract order (the main-contract dates the sub-contract sits inside).

Stage is derived, not ticked

The stage badge comes from the documents on file: a signed contract, a practical completion certificate, a final certificate. If the record is wrong, override it with a reason; the system's reading stays beside yours.

Letters of intent and the cap

A job at LOI stage lives on a run of letters. Record each one (or import the cap workbook) and the cap tracker keeps the position: what has been applied for and certified against the cap, what open orders would commit, and how long the current letter has to run. A cap request pack is prepared from the same figures.

Particulars, securities, parties

The set-up register is the contract completion checklist in Saral's shape. Particulars are the points still to settle, each with its working position, owner, due date and review rounds; closing one can write the agreed figure into the key terms. Securities (bonds, warranties, guarantees, insurances) are derived from the documents filed and the insurance register — a person may set a different status with a reason. Parties names the employer's agent and the principal designers.

The review register

Each negotiation document (clause comments, derogations, PI levels, scope review) is a register of points with a round per meeting or reply. Import a round from the spreadsheet or Word issue; the dry run shows what it would add. Status and agreed wording are per point; the Excel keeps live formulas and any round prints as a PDF in its own layout.

What is done elsewhere

Key terms, sectional completion, clause notes, the payment timetable and retention bonds have their own cards further down this tab. The budget is on Budget vs cost. The valuation sales invoice is raised by Accounts, not here.

Next screen: /projects/subcontractors

Not what you needed? Inside Saral, ask Kuku (Alt+K) — if it cannot answer, “Ask a human” sends the question to Saral support with the chat attached.