Variations & claims

Every variation from instruction to certified value, with the drawing revision or RFI that caused it attached — and the delay evidence assembled as events happen, not reconstructed a year later.

  • Contracts manager
  • Planning engineer
/ops/projects/[slug]/variations
Variations & claims — the screen inside ArgAssure

On a contractor's desk. Claims are won on contemporaneous records. A verbal instruction acted on in good faith, undocumented for six months, is worth roughly nothing at arbitration — while the same instruction logged the day it was given, against the drawing that changed, is worth its full value.

What it holds

Variation register with causation

Instruction reference, date, originator, the drawing revision or RFI that caused it, the rate basis, and the state from raised through certified.

Rate derivation for new items

Star rates built from analysis on the same libraries as the tender, with every component sourced — so the employer's QS is arguing with a workings sheet, not with an assertion.

Delay event register

Each event recorded when it occurs with its cause, evidence and programme impact — the dossier an EOT submission is assembled from rather than the story told after the fact.

Into the certificate

Approved variations feed the IPC as identified lines, not as a lump "variations" figure — so partial certification is visible per variation.

What it produces

  • Variation statement with causation and rate workings
  • EOT dossier with the delay events and programme impact
  • Ageing of instructed-but-uncertified value

What it will not allow

  • A variation with no instruction reference
  • A star rate with unsourced components
  • Backdating a delay event
Hands over toIPC (02) · Programme, delay & EOT (08) · Final bill (04)

← All modules for this deskThe Contractor