A Practical Guide to PPADA Variation Compliance

Why variations become audit findings

Most variation problems are not decisions made in bad faith. They are decisions made without a clear, current picture of how much of the original contract value has already been varied.

PPADA (2015) sets limits on how far a contract can move from its original value without a fresh process. The limits are not complicated. Keeping an accurate running total across several concurrent contracts, in spreadsheets, is where things break.

If you cannot state today's cumulative variation percentage for a contract in under a minute, you are exposed.

Track cumulative value, not individual changes

A single change order of modest value looks harmless in isolation. Reviewed against the contract's cumulative position, the same change may be the one that crosses a threshold. Every variation should be recorded against the contract total, with the resulting percentage visible on the approval itself.

Approve in the order the rules expect

Variations approved after work has started are the most common finding in review. Build the sequence into the workflow: request, technical review, value check against the threshold, authorised approval, then instruction to proceed.

Keep the evidence with the decision

Each variation should carry its justification, the supporting measurement or inspection, and the identity and date of every approver. Assembled later from email, this evidence is rarely complete.

A short checklist

• Record every variation against the contract, not the task
• Show the cumulative percentage on the approval screen
• Alert the approver automatically as a threshold approaches
• Require justification and supporting evidence before submission
• Keep an unalterable log of who approved what, and when

Handled this way, variation compliance stops being an annual scramble and becomes a by-product of how work is already approved.