Site & design

The site's day-to-day registers over one project as tabs: the daily labour log by package, the design register with every drawing issue and reviewer status, drawings and specifications, outbound transmittals, the numbered question registers (RFIs, design queries, discrepancy notices), daywork sheets, plant and materials on the job, contract and delay notices, and the procedures that say where every register lives.

You enter

Labour: who worked on which package each day, own and subcontract operatives, by labour type.
Design: each drawing or document issue (S1, S2 …), each reviewer's status (A / B / C / NA) and the turnaround.
Transmittals: the drawings issued, their suitability code and the recipients.
Questions: RFIs, design queries, error and discrepancy notices, disputed comments and general notices — numbered per register.
Contract notices and notices of delay, client and subcontract, or import a delay notice from the letter.
The information required schedule (IRS), the project and subcontractor directories and the design checklist on Procedures. The DRS — information required by package — has its own page, Projects → DRS.

Saral fills in

The monthly labour summary by package and type (days; memo cost only where the project has a day rate) and the actuals the Programme's look-ahead reads.
Overdue reviews and turnaround days on the design register; the cover sheet and acknowledgement links on each transmittal; inbound transmittals read from the project's mail.
Numbering per register and the monthly Excel per register.
Plant on the job from Buying's hires and the Warehouse's kit, and the project's material requests, orders waiting for goods and skips — Buying's own records, shown here, never copied.
Where every register lives, its owner, cadence and last update, generated on Procedures.

It produces

The monthly question registers and the design register as Excel, each transmittal's cover sheet, and the labour summary.
The notices that stand behind an EOT or loss-and-expense claim, and the labour evidence behind a daywork or a disruption claim.

What this page is for

Everything the site records that is not money: labour, drawings, questions, notices, plant. These are the registers a PM keeps in separate workbooks; here they are tabs over one project, numbered and dated the same way, so the evidence for a claim or a client report is in one place.

Labour is a site record, not cost

The labour log says who was on which package each day. It is not attendance (HR holds that) and it is not cost (the ledger holds that). It feeds the look-ahead's actuals and a memo cost where the project carries a day rate, and it is the head count a daywork sheet or a disruption claim is checked against.

Design, drawings and transmittals

The design register tracks each issue through review; the drawings tab opens the drawing with markup; specifications are their own register. An outbound transmittal issues drawings with a suitability code, files its cover sheet and watches for each recipient's acknowledgement. A document controller with the design key and no cost read opens just these tabs.

Questions and notices

RFIs, design queries, discrepancy notices and disputed comments are numbered per register with a reply due date. Contract notices and notices of delay are recorded with the clause and the dates they rely on; a delay notice can be imported from the letter. The programme's EOT register and the valuation's loss and expense point back to them.

Plant and materials

Plant on the job and the project's material requests are Buying's and the Warehouse's records, read through core and shown here under their own keys — a door, not a copy. The same goes for the procedures tab, which is generated from where each register actually lives.

Where next

The site's formal registers — blockers, RAMS, permits, inspections, quality, handover and the client report — are on Site registers. Dates and the EOT register are on Programme; the daily narrative is the Site diary. The DRS (design release schedule — every package's documents, Aconex status, the client's delay and the design freeze) is its own page, Projects → DRS.

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.