Site registers

Open this screen in Saral/projects/site-registers

The site team's registers over one project, grouped by job: Site & programme (locations, blockers, the package tracker, holes and voids, long-lead items, acceleration, statutory approvals), Safety & environment (RAMS and plans, permits to work, inspections, the weekly H&S pack, observations, environment and waste), Quality (ITPs and NCRs, commissioning), Handover & defects (snagging and handover, close-out, the defects period) and Client (the monthly client report, the client portal).

You enter

The location hierarchy — buildings, levels and rooms — that every other register hangs off.
Blockers, holes and voids, long-lead items and their order-by dates, acceleration requests, statutory consents.
RAMS per package and their approval; permits to work and their issue; H&S inspections and observations; environmental readings and waste.
ITP hold points and NCRs; commissioning tests and certificates; snags per room and area handovers; defects after practical completion; the close-out pack items.
The monthly client report narrative, and what the client team may see on the portal.

Saral fills in

The weekly H&S pack drawn from the week's records — permits, inspections, observations, the accident book — ready for sign-off.
The snag list per room from the location hierarchy, and whole-site handover once every area is signed.
The client report's figures from the registers: progress, programme, variations, H&S, the month's photos.
Statutory consents that block work and are not yet in hand, raised on the Overview.
Each register's Excel and PDF from the same rows.

It produces

Permits, RAMS approvals, the weekly H&S pack, inspection records, the NCR and snag registers, the commissioning certificates — the H&S file and O&M evidence at close-out.
The monthly client progress report and the client portal view.
The practical completion pack and the defects-period record.

What this page is for

The site manager's registers — the ones that used to be eighteen tabs in a workbook — grouped by the job they do. The page is one project at a time; the group tabs and the rail pick the register; every register is its own table with its own export. Nothing here is money: the money views of the same project are on the workspace strip above.

Site & programme

Locations are the spine: set out buildings, levels and rooms before anything else. Blockers record what is stopping work; the package tracker sets weekly targets per package; holes and voids carry their inspections; long-lead items carry the date they must be ordered by; acceleration records requests and approvals; statutory approvals track planning, building control and licences, and a consent flagged as blocking work is raised on the Overview until it is in hand.

Blocker register and the team canvas

The Blocker register (Site & programme) is the tracker the site team used to keep in a spreadsheet: a blocker, an abortive work, an information need or an access need — its package, room, who must clear it, when it was raised, when it is due, its status, its photos and the CAI it links to. Each row is a blocker chain on the team canvas: raising it marks the chain's first step, Route names the lane that must clear it and pokes that lane in-app (the named person is for display — any holder of the lane's key may clear it), and Clear closes the chain. Abortive works carry a cost estimate and are a filter chip, not a second register. Copy agenda produces the weekly meeting's list — open and overdue blockers by lane, with each lane's ready steps — as text or a Word file. Excel and PDF follow the team's column order.

Hold points (QHP)

Hold points (Quality) is a view, not a second record: every HOLD point on the project's ITPs, by the room it was inspected at and the ITP's trade, with its drawing, status, inspector, date and photo count — the QHP tracker drawn from the Quality register rather than retyped. An ITP carries no room of its own, so the room is where the check was recorded, and a point never inspected is listed under 'Not yet inspected' rather than lost. Pass and Fail here post the same check the ITPs & NCRs register posts: Pass releases the point and the canvas's QA chain sees it; Fail raises an NCR. The Room × trade view counts released over total per cell; the export is in the QHP layout.

Safety & environment

RAMS are per package and need the approver's sign-off. Permits and inspections are money-free registers a site-only seat can keep. Observations cover safety, quality and environment. The weekly H&S pack is drawn from the week's records and signed off on the permits key. An accident or near miss is reported into HR's accident book through its own door — one record, in HR.

Quality, handover and defects

ITPs hold the witness points; NCRs are raised, evidenced and closed. Commissioning records systems, tests and certificates. Snagging is the one snag list, per room, and an area handover is signed when its snags are closed; whole-site handover follows. Close-out assembles the PC pack and the H&S file; the Defects period register runs from practical completion to the defects date.

Client

The client report is the monthly progress report: its figures come from the registers and the commercial record, the narrative is yours, and it files under the project when issued. The client portal is the QS's door to the client team — what they may see — on the commercial key.

Who can do what

Reading needs the cost-report read, except the money-free registers: a seat with the site-safety key opens Permits, Inspections, the H&S pack and Observations; the RAMS approver opens RAMS. Editing is the site-manage key (PM, Contracts Manager), RAMS approval its own key, and every register renders read only without it.

Where next

The handover and defects records close the job: the final account is produced from the CVR Report once the project reaches the completed stage, and lessons are recorded on Contract & Budget. The daily narrative behind these registers is the Site diary.

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.