Ascertained means calculated from evidence, not estimated. A single figure with no basis behind it invites an ascertainment of nil, and that is a perfectly defensible outcome.
Loss and expense needs a relevant matter under clause 4.21. An extension of time needs a relevant event under clause 2.29. The lists overlap and they are not the same, which is why claims arrive attached to events that cannot carry money.
QScope links every head of claim to the delay event that caused it, and says so when the event is one that buys time and nothing else. The warning appears where the claim is entered, not in a manual nobody opens.
Prolongation calculated as the tendered weekly preliminaries multiplied by the weeks of delay is a price, not a loss. The claim is for what was actually incurred over the period, evidenced from the accounts.
QScope holds the basis against each head and flags anything marked as ascertained with no basis recorded, because that is the line an assessor deletes first.
A head of loss and expense almost always arises from a delay event, and that same event usually carries an extension of time. The two are assessed under different clauses and reach different conclusions, but they share a cause.
QScope holds the delay register alongside the heads of claim, so each head points back at the event that caused it and the time award is visible next to the money.
A variation is valued for the work it adds. The cost of the disruption it causes to the rest of the works is a separate matter, claimed as loss and expense, not buried in the rate for the additional work.
QScope keeps the variation value and the loss and expense apart, and lets you set a zero retention rate on loss and expense because it is normally not subject to retention.
The ascertained loss and expense is one line on the final account, stated on its own because it is not subject to retention and the client is entitled to see it separately from the measured work.
QScope carries only the ascertained heads into the account, in the RICS order, and shows claimed and ascertained apart so the adjustment can be traced rather than accepted.
No. Ascertainment is a judgement made from evidence you hold. QScope structures the claim, links it to the cause, keeps the basis and does the arithmetic on the totals.
Because it gets claimed. It is recoverable only in limited circumstances and often not at all, and having it as its own line makes it visible rather than buried inside another head.
Where an employer risk event and a contractor risk event both delay completion, the usual position is time without money. Record the extension in the delay register and leave the head of claim unascertained, with the reasoning noted.
Normally not. QScope lets you set a zero retention rate on the relevant variation for exactly that reason.
Not your whole portfolio. One live job, one certificate. If it does not save you time the first time you use it, walk away and take your data with you.