Your QS month in Saral

Open this screen in Saral/projects/guide/qs-month

What the QS team produces today, the Saral output that replaces each format, the figures side by side where a comparison has been recorded, where each input comes from and whether Saral takes it in by itself, every output over the whole project by stage, and how the month flows from screen to screen.

You enter

Nothing here. The comparisons are recorded on the account's output-parity record; this page reads them.

Saral fills in

The formats of the monthly cycle — valuations, notices, the application, the variation account — each against its Saral output and how long Saral takes.
The side-by-side comparisons, figure by figure, where they have been recorded; 'not recorded' where they have not.
The inputs table: where each input comes from (Xero, a register, a document, typed) and whether Saral reads it unaided.
The whole-project catalogue by stage, and the chain of screens the month runs through.

It produces

The case, in the team's own formats, for moving the month into Saral — and the list of inputs still typed.

What this page is for

The team's formats are the yardstick. This page puts each one beside the Saral output meant to replace it, with the figures compared where a month has been run both ways, so the decision to switch is made on the team's own numbers rather than a description.

Inputs still typed

The Inputs tab is the honest list: for every input a format needs, where it comes from and whether Saral reads it unaided. An input still typed is the next thing to automate; the list is what the owner's rule — the machine does, a person reviews — is measured against.

Where next

Back to the Projects guide for the module as a whole, or to the Reports hub to produce any of the outputs listed.

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.