Projects guide

Open this screen in Saral/projects/guide

The whole module as one reference: how it works as a flow of six cards, every screen on the project strip, how data flows between modules, the twenty steps from bringing a job in to close-out, the routine for each role, the set-up list, job roles and access, what Saral automates against what you type, matching your manual CVR, your workbooks mapped to Saral, and every setting. With a project picked, each step and set-up item shows where that project stands.

You enter

Nothing. Pick a project to see its status chips; pick a section to read.

Saral fills in

A status chip per step and per set-up item from head counts on the project's registers — set up, partly, not started, can't tell.
The job-roles section from the account's live role set-up beside the industry standard.
Every link, proved by a test to land on a real page and tab.

It produces

Nothing is produced here — it is reference. What to do next on a project is its Next card on the Overview.

What this page is for

A QS or PM who knows the job but not the app reads here: which screen does what, in what order the month runs, what Saral derives and what must be typed, and how to prove the figures match the workbook they used to keep. It was assembled from the pieces each build round added, into one guide with one spine.

Reference, not a to-do

Nothing in the guide asks a person to tick what Saral can see. The live chips say where a project stands; the instruction on what to do next is the Next card on the project's Overview, and the header's accent action goes there.

Matching and workbooks

Matching your manual CVR explains each reason a spreadsheet CVR built from ledger exports differs from Saral's and what to set so they agree. Your workbooks → Saral takes each workbook a QS keeps and says what is imported, what is derived, what stays typed and the check that proves the two agree.

Set-up for a new project

The Set-up section is the ordered, checkable list: the contract record, the packages, the procurement dates, the appointments, the directory, the watched folders, the application settings. With the project picked each item shows whether it is done.

Routine

The QS's month on a timeline — cut-off, applications in, valuations and notices out, the CVR lock at M+10 — and the project manager's and site's days and weeks, with who does what and how each deliverable is produced.

Roles

The industry-standard job roles (QS, commercial manager, project manager, site manager, contracts manager, planner, design manager, document controller, H&S manager and more), what each sees and changes in Projects, and the switches that narrow or widen them — generated from the account's live role set-up.

The progress strip

Every Projects route carries a progress strip — one bar per lane (design, BIM, documents, changes, site, buying, package QS, client application, programme, director, accounts): done out of total, how many ready, how many overdue. The bars are the steps of the chains that route is about (a package-month, a CAI, a drawing, an order, a hold point, the project-month), and a step is done by hand, by the submit that is its evidence, or read from the books. When one team's step is done the next team's step turns ready and they are told in the app — the bell, whose line opens the package's own canvas (/projects/canvas). Everyone sees every lane; each person marks only lanes their own role already allows. The strip over Payment Schedule and Payment Planning is read-only: those routes are untouched.

Saral Share

Saral Share is the glass wall with your subcontractors: each appointed firm can have a live board for its package. The firm opens it by a signed link (no login, no onboarding), picks its name from the contract's contacts, and uploads its drawings, revisions, applications and documents; your team comments, sets the A / B / C status and uploads its own. Both sides work in draft and see only what the other side has SUBMITTED — submit is the one event that crosses the wall, so a mistake is never seen and nothing submitted can be edited (withdraw, and the firm sees the withdrawal). The firm's submit moves the package's lane steps, pokes the holders and lands in the morning queue (Projects → Saral Share) with the overnight AI pass's suggested answers beside it: the morning's job is to read, adjust and press Submit. Your submit sets the register's status and tells the firm by one short email, at most once an hour per package. A firm that keeps its drawings in Smartsheet or drops files in the SharePoint folder is on the same board — those arrivals are submitted items of theirs. The whole feature sits behind Settings → Saral Share (off until switched on) and each package's door; with either off the board says not available, never a blank. The firm never sees money, another firm, an internal thread or a draft of yours.

The canvas

Every person working on packages opens Saral on the canvas (/projects/canvas): the project's packages drawn as boxes — size is the budget (the subcontract sum, else the CSA allowance, else the PFA budget), fill is what has been certified, colour says whether what is left will be enough (green, amber within 3 %, red over, grey with no forecast yet) — in NRM group tabs, with Budgeted / Forecast and Whole / Remaining toggles, the PFA table beneath, and 'Light for me' dimming every package not waiting on one of your lanes. Click a box and you are on that package's own canvas: the lane strip with its owners, the glass wall with the firm's submissions and the AI's draft answers ready to review and submit, and everything about the package in tabs (people, design, changes, site, money, material, firm, talk) — each reading the record its home screen keeps. A Nudge per lane pokes the lane's owner in the app and is recorded on the package's thread; never a block, never an email unless they opted in. Who lands there is an account setting (Projects → Settings → Team canvas): package roles by PERMISSION — the keys the QS, Assistant QS, Design Manager, Site Manager, Project Manager and Buyer presets hold, never a role name, Owners and Admins keeping the hub — or everyone, or off. The PFA, Payment Schedule and Payment Planning are read, never changed.

Connections

Each person signs into the systems their work lives in — Outlook, Smartsheet, Aconex — from the Connections icon (the plug) in the top-right corner of every Projects page, which opens their sign-ins at a glance and the full page at /projects/connections — never from Settings. The connection is the person's: the token is sealed against their user id and nobody else can read it, use it in the browser or see it. The data is the account's: a sheet or an Aconex project a sign-in can reach is linked once to a Saral project by anyone who may write the drawing register, and every night Saral reads it with one connection that can open it — the account's own first where an Admin entered one, then the connected people, most recently successful first — and files what it finds on the project's drawing register, Design Desk and canvas for everyone with Projects access. When nobody connected can open a source it says so, never a quiet stop. The Admin tier and the Owner see the overview on the same page: who is connected to what, what each source produced, which sources nobody can open — sources and results, never a token or a mailbox, and never a view as another person.

Where next

Your QS month in Saral (Guide → QS month) compares the team's current formats to the Saral outputs that replace them, figure by figure. How the Projects module works (Guide → Module) is every page's tour and guide as one document.

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.