Progress

Open this screen in Saral/projects/progress

The monthly physical-progress assessment: a % complete per package, rolled up to cost code, so value earned (progress × budget) can be set beside the cost actually spent. Nothing unassessed is treated as zero — an empty cell means not assessed, and the headline figures are measured on assessed budget only.

You enter

A % complete per package (or per cost code where the code has no package), for the assessment month picked at the top.
A note on the record modal where the assessment needs explaining.

Saral fills in

The list of packages from the Payment schedule and the budget lines from Contract & Budget — each one appears with its own % cell.
Each package's budget (its effective PFA from the Payment schedule) and each code's agreed budget line.
Cost to date per code from the CVR's own cells — the posted Xero ledger only, group basis; no drafts, no accruals.
Value earned, the budget-weighted roll-up per code, earned minus cost, and a package already measured per CSA line on the application (read here, set there).
A key nobody re-assessed this month keeps its last figure, marked with the month it came from.
Labour this week and last from attendance — a memo, ahead of the ledger, never added to cost.

It produces

The earned-value position for the month and the behind-cost alert on the Overview's Next card when spend runs ahead of physical progress.
The percentage complete that the valuation and the client report can quote.

What this page is for

A QS's monthly judgement of how far each package has physically got, recorded once and reused: it drives value earned, it sits beside the ledger cost, and it is the progress figure quoted elsewhere. The assessment is per package because that is how the work is let; it rolls up to cost code because that is how the money is reported.

Where the rows come from

A package nominated on the Payment schedule is a row under its cost code with its effective PFA as the budget. A cost code with a budget line but no package is itself an editable row. If the list is empty, add packages on the Payment schedule or budget lines on Contract & Budget — nothing is typed here that lives elsewhere.

Reading the figures

Earned is % complete × budget. Cost to date is the posted ledger for that code on the group basis — the CVR's figure, not a second one. Earned minus cost is positive when the job is ahead of its spend. The headline tiles say how many codes are assessed, so a thin assessment never reads as a thin job.

Who can do what

Anyone with the cost-report read sees the assessment. Typing a % is the programme keeper's. A package the application already measures per CSA line is read only here and set on Valuation → Application, so there is one progress figure.

Where next

Carry the month's progress into the application on QS Valuation, check the margin on the CVR Report, and read the Programme for the dates the progress is measured against.

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.