A subcontract document — read through and send

Open this screen in Saral/projects/subcontracts/issue

The draft of one document issued on a package — a sub-contract order, letter of intent, extension, warranty request, bond, guarantee, novation or certificate — with every value filled from Saral and shown with its source. You read each section and tick it, change agreed wording where the template allows, then send it for signature through Saral Sign. Once sent, the same page is the document's record: its status, signers and the issued and signed copies.

You enter

A tick on each section once read; a changed clause where the template marks it as agreed wording (a reworded standard clause needs approval before the document can go).
A value the draft could not find — it prints as a blank line until confirmed.

Saral fills in

Every particular from the package, the contract record, the appointed tender, the account's signatories and the template; each value's origin on hover.
The pre-send checks: the firm's details against the official record, a missing signer, wording awaiting approval.
The Saral Sign envelope, its status, and the issued and signed copies filed on the package.

It produces

The document as PDF (preview), Excel (particulars with their sources, payment timetable, scope, schedules) and Word with Track Changes on for the firm to mark up.
The signed document and its certificate, filed on the package and read by the appointment checklist.

What this page is for

The account's standard terms are a template; a document is that template filled from the records of one package. This page is where a person reads what Saral filled before it leaves the building — the sum, the dates, the parties, the payment timetable, the scope — and where the signing happens.

Where the values come from

The package (code, title, cost code), the appointment (firm, bid, dates), the contract record (main-contract dates, retention, payment terms), the subcontractor register (the firm's registered details and signer), and the account's settings (who signs for us, the notice address). Hover a value for its origin. A value with no source is a blank line until someone confirms it.

Changed wording needs approval

If a standard clause is reworded on one document, the change is listed and the document cannot be sent until a person allowed to approve changed wording (Settings → Subcontract documents) has approved it. Agreed wording the template marks as editable does not need approval.

After sending

The status moves through sent, signed (or declined, voided, expired). A document unsigned past the template's chase days is flagged; a letter of intent nearing its end date is flagged on the Orders & contracts list. Only the person who sent the envelope can remind or void it in Saral Sign; everyone else sees this record and the copies.

Next screen: /projects/subcontractors/orders

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.