VariationFlow

For JCT subcontracts

Your payment periods, not the main contract's.

A JCT subcontract carries its own payment periods, usually different from the main contract above it. VariationFlow tracks your payment dates on the periods you record from your subcontract, and until you record them it will not guess, because a deadline counted on the wrong contract is worse than none.

Where JCT jobs leak

Instructions never confirmed

Changes instructed on site and never confirmed in writing are the first thing disputed at the final account.

Pay less notices nobody checked

Whether a pay less notice was on time depends on your own contract's dates. Without them, a late notice can pass as timely.

Loss and expense left too late

A claim made long after the event is harder to prove and easier to resist.

How VariationFlow handles it

  • Payment periods from your subcontract

    Enter the due date, the final date and the notice periods once, and the payment notice, pay less notice and final date are tracked for every application.

  • The Construction Act tracker

    When the pay less window closes with no valid notice, the application flags a possible notified sum, with the dates that make it so.

  • Instructions, dayworks, loss and expense

    Oral instructions, daywork records and loss and expense matters are kept on each variation, dated from when they arose.

  • A record that stands up

    Every action is timestamped and chained to the one before it, photos carry a SHA-256 fingerprint, and any variation exports as a verified audit document.

A valuation flagging a possible notified sum after the pay less window closed with no valid notice

Free for your first job.

One project and two users, to capture, price and track the variations on your first job. No card and no minimum term.