Ask your projects data anything. Get answers in seconds. Plexa MCP Connector is live. See it in action
/
Variations & EOTs
Variation and EOT register that lives with the head contract
Raise variations against the head contract. Track cost and time impact. Route for approval. Post to the ledger. All in one workflow.
Threshold-based approval
Under $50k CA→PM. Over $50k adds Construction Manager. Over budget adds senior sign-off.
Over-budget workflow fires alongside
When a variation pushes the code over Original Budget, senior management is notified.
Cost to revenue linked
Link a subbie variation to a head contract variation. See margin per scope change.
THE PROBLEM
A variation goes to work Monday. The client rejects it Friday. The trade already has the material on site.
Variations happen fast. Approvals happen slow. When the paperwork lags the work, the builder wears the risk: material ordered, trade paid, client hasn’t accepted.
Plexa raises the variation, calculates the cost and time impact, routes for approval, and blocks the trade from proceeding until the client has accepted. Or, if it’s a builder-risk call, records exactly who took the risk.
Portfolio variation register
Every open variation, every EOT, every builder-risk call across every project. Know the total cost exposure before month-end, not after.
FAQ
Quick answers: everything you need to know about variations and EOTs
What's the difference between subcontractor and head contract variations?
Who approves a variation?
What happens when a variation pushes a cost code over budget?
How do we reduce a subcontract value?
Can subcontractors raise their own variations?
Does linking a subbie variation to a head contract variation auto-approve it?
The AI Construction Operating System
One platform, one data model, every project. Built in Australia, for the world.
YOUR DATA, PROTECTED
Hosted on AWS Sydney with Australian data residency.
GET THE MOBILE APP
Platform
Solutions
© 2026 Plexa Pro Pty Ltd. ABN 63 668 433 136