Quantity installed and PM corrections

4 min read · Updated 15 Jun 2026

Log how much you installed alongside the hours, and WBSync drives % complete from what's actually gone in — not a guess. Only approved entries count, the figure rolls up the tree, and when a PM corrects it the change is stamped with a reason and flagged amber, never silent.

Quantity, not just hours

Hours tell you what a crew spent; quantity tells you what they produced. Each L4 activity carries a tendered quantity and a unit — metres, m², items, whatever you measure it in — and as the crew logs work they record the quantity installed against it. WBSync turns that into physical % complete automatically: installed ÷ tendered, capped at 100% so over-installing never earns above budget.

Approved entrieseach adds installed qty Qty installedΣ of approved deltas % completeinstalled ÷ tendered

How the figure is built

  • Only approved hours count. When an entry is approved, its installed-quantity contribution is added to the activity's running total. Draft and submitted entries don't move the number — the same approval gate that protects your hours protects your progress.
  • It rolls up. An activity's installed quantity sums into its discipline, sub-location and location, so every level of the tree shows real progress without you re-keying anything.
  • It keeps accruing. Approvals keep adding to the figure for the life of the activity — even after a PM has corrected it (see below).

When a PM needs to correct it

Sometimes the logged figure and the surveyor's measure don't agree — a remeasure, a rejection that hasn't caught up, a snag. A PM, planner or engineer can correct the installed quantity straight on the WBS node.

1
Open the activity on the WBS

Edit the node and set the corrected installed quantity. WBSync shows the entry-derived total ("logged from approved entries") right beside the field so you can see what you're overriding.

2
Give a reason — it's required

Correcting away from the logged total needs a short note. Without one, the save is rejected. The reason is what explains the call to the rest of your team.

3
It's stamped and flagged

WBSync records who corrected it, when, and why, and highlights the figure amber on the tree with the reason on hover — so a corrected number is never mistaken for a logged one.

Reverting clears the stamp. Set the figure back to exactly the logged total and the correction is removed automatically — the amber flag disappears and the activity is entry-driven again. Both the correction and the revert are written to the audit log.
A correction sets a new base — it doesn't freeze the activity. Later approved entries keep rolling on top of the corrected figure, so the stamp means "corrected, and still accumulating", not "locked".

What next?

Installed quantity feeds earned value. See it on the dashboard: Reports & dashboards →

Frequently asked

Does installed quantity count before the hours are approved?

No. Only approved entries add to an activity's installed quantity. Draft and submitted entries don't move the figure — the same approval gate that protects your hours protects your progress.

Why is one of my quantities highlighted amber?

Because a PM has corrected it away from the entry-derived total. Hover the figure to see who changed it and why. Set it back to the logged total and the correction — and the amber flag — clear automatically.

Do approvals stop counting once a PM corrects a figure?

No. A correction sets a new base; later approved entries keep rolling on top of it. The stamp means 'corrected and still accumulating', not 'locked'.

Can over-installing push an activity past 100% complete?

No. Physical % complete is installed ÷ tendered, capped at 100% for earned value, so installing more than the tendered quantity never earns above budget.

Who can correct an installed quantity?

Anyone who can edit the WBS — project managers, planners and engineers, plus owners and admins. Foremen and operatives log quantity through their entries but can't override the node figure.

Related