Projects settings

Open this screen in Saral/projects/reports/settings

Every setting the Projects module reads, on one page behind the projects.settings key. The rail groups them — coding, the Xero classification, the Data hub, the Payment Schedule layout, the CVR basis, scheduled packs, alert thresholds, the registers and lists every screen reads, the contract and commercial rules, the site method, and the document templates — and the Switchboard lists them all with their defaults and a door to the tab that owns each. Three tabs matter most before the first package is let: Applications decides how a package is paid when nobody set it; QS templates holds the account's words on every output; Subcontract documents holds the order templates, who signs and who approves changed wording.

You enter

Applications: the rungs of the payment-basis ladder (a fact, the value it must match, how such a package is paid), their order and the fallback; whether the month is prepared by itself, whether and when the CVR locks by itself, what happens when Xero shows an application paid.
QS templates: the account's party words, numbering, OHP default and client layouts; one project's overrides where it differs (issuing company, OHP, words, numbering, layouts) — blank inherits.
Subcontract documents: per contracting company the signatory and the notice address; which roles approve changed wording; your own template per kind (copy the standard, edit sections, particulars and clauses, who signs first, chase days, deed).

Saral fills in

The Switchboard: every setting, its topic, its default, whether it is changed, and whether an essential is still unset.
The standard ladder as the default: a sub-contract is valued and noticed monthly, a professional appointment is a fee account, a purchase order is paid on invoice, otherwise valuation and notice — with rule 0 (work on site 45 days or more → valuation and notice) first and not removable.
The template a project's outputs print right now — issuer, columns, OHP, numbers, layouts — and where each came from; the figures owned elsewhere (retention, the payment timetable, the issuing company's details) with a door to each.
Saral's neutral, industry-standard template for every document kind the account has not made its own.

It produces

Which packages get a month on Applications and which are paid through BillScan, on every project without its own ladder.
Consistent wording, numbering and layout on every QS output; the subcontract documents the Appointments tab issues, filled and sent through Saral Sign.

What this page is for

A new account should not be blank and an old one should not be a mystery. The rail puts every Projects setting in a named group; the Switchboard shows them all together so nothing is missed. Each value lives in one place and is read by every screen that needs it. Every rule setting ships with the industry-standard figure as its default and says so under the editor; a blank value inherits it, a changed one is marked, and Reset returns to the standard.

Applications: the ground rule the standard follows

How a package is paid is decided by how the firm was appointed, with the law as the floor: a sub-contract order, JCT or NEC particulars, a letter of intent or a short-form order → valuation and notice; a professional appointment → a fee account against deliverables; a supply-only purchase order, or no contract form and no work on site → on invoice; and, whatever the form or value, work on site of 45 days or more → valuation and notice. A package's own setting, made by a person, always wins. Only a package valued monthly gets a month on Subcontracts → Applications and a notice; one paid on invoice goes through BillScan and the payment run and must never be noticed — the ladder is how Saral tells the two apart.

Applications: the facts the rungs read, and the per-project override

The method of appointment and works on site are set on the Procurement tab's edit form and written when an order is marked signed (a supply order sets works on site to no, other orders to yes). Invoiced to is a legal company in the group; order value and cost-code prefix read the package; a rung on a fact the package does not carry simply does not match. A project paid differently from the account carries its own ladder from Subcontracts → Applications → Payment rules — the account's ladder is copied as its starting point and rule 0 stays.

QS templates: one vocabulary, one owner

A client sees the same words on every document from your account — the parties, the numbering pattern, the layout — so no output is edited by hand, and a project issued by a sister company or on a client's own layout is a few overrides rather than a different template. Retention percentages, the payment timetable and the company's name and logo are facts other settings own; this tab reads them and links to them, never holding a second copy that could drift.

Subcontract documents: templates, signatories, approvers

A template is the account's standard terms with the particulars left to be filled — a title, a subtitle and ordered sections, each a block of label-and-value particulars or numbered clauses. Each document issued on a package is that template with the package's facts in it, read through by the QS and signed through Saral Sign. A clause marked as agreed wording may be edited on the order; any other reworded clause is listed on the document and needs an approver. A group lets packages under more than one legal company, so each has its own signatory and notice address.

Team canvas: switches, and the firm's side of the fence

Every card on the Team canvas tab is a module switch, off by default, stored once per workspace. Chasers poke a colleague whose step is overdue. Smartsheet write-back sends a drawing's status back onto the firm's sheet, one cell at a time, because firms keep Smartsheet for drawings and have no Saral login. Package intake files a firm's emailed applications and documents onto its package, so “Owed by the firm” on Subcontracts can say what is still missing — and whether a missing document affects payment is your contract's rule, written in your words on the QS templates (the “what you owe us” email, and the optional paragraph on a pay less notice), never an automatic withholding.

What else is on the rail

Cost codes and the NRM1 bridge, report categories, the Sales / Cost / BS classification, the Data hub (the SharePoint folders Projects reads), the Payment Schedule's PFA layout, the CVR cost basis, scheduled packs, alert thresholds and the tender code map, the registers and lists (notice types, statuses, parties, platforms, payment-timetable and tender offsets), the contract forms, NEC, budget control, cash flow, quality and dayworks rules, the site method, subcontractor forms and numbered documents. Each is a board of cards; a setting that only changes one screen stays on that screen.

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.