01The problem
Variations with the contract trail attached
AI-assisted drafting can start from the clause, event, and cost breakdown, but your team reviews the output. The variation remains tied to the claim and audit trail.
Without a shared record
- Scope change starts in site email or a meeting note.
- Cost support sits in a folder separate from the notice.
- Contract clause references are checked late or copied by hand.
- Approved, pending, and submitted values drift from the claim position.
- Assessment reasons disappear into comments or old attachments.
With Palydin
- Capture variations when the scope change happens.
- Tie each variation to contract clauses, cost support, and claim status.
- Keep assessment revisions and reasons visible.
- Reduce lost variations caused by email and spreadsheet drift.
02How it works
From contract to audit, step by step.
- 01
Record the variation event
Capture changed scope, contractual background, cost support, and the party raising the variation.
- 02
Tie it to contract scope
Keep the variation connected to clauses, documents, separable portions, and the original scope position.
- 03
Carry the value into claims
Keep submitted, assessed, approved, and pending variation values visible beside progress claims.
- 04
Assess with reasons
Record head contractor or principal assessment decisions, revisions, reasons, and audit history against the same file.
Every step writes to the same record
Nothing is re-keyed between stages, so the audit trail is a by-product of doing the work.
- Contract scope
- Variation event
- Variation
- Cost buildup
- Claim
- Assessment reasons
- Audit
03Who it's for
Useful from either side of the contract.
- Subcontractors
- Capture scope changes early and keep the cost, clause, and claim position connected.
- Head contractors
- Assess variation submissions with the contract basis and revision history in view.
- Principals
- See pending and approved variation exposure before it becomes a claim surprise.
04Built for Australia
Built around the records commercial teams argue over.
Palydin speaks Australian construction: progress claims, retention, GST, payment schedules and the claimant–assessor relationship between subcontractors, head contractors and principals.
Australian contract language
- Progress claims
- Claim periods, claimed-to-date values, prior assessments, supporting documents and submitted status stay together.
- GST and retention
- GST, retention deductions, held amounts and release context stay visible inside the claim workflow.
- SOPA payment schedules
- Payment schedule dates sit beside the claim, the assessment reasons, the contract terms and the audit history.
- Both sides of the contract
- Subcontractors prepare the record. Head contractors and principals assess from the same file.
Controls both sides can trust
- Audit trail
- Claim changes, assessment reasons, variation decisions and retention activity stay attached to the record.
- Access controls
- Role-based permissions keep claimant, assessor, admin, commercial and viewer work separated.
- Counterparty scoping
- External parties only see the contracts they are connected to, never the rest of the portfolio.
- Contract-cited AI
- Answers point back to the contract material, so the team can check the source before acting.
05Questions
Common questions
What is construction variation management software?
It is software for recording, drafting, submitting, assessing, and tracking scope changes. Palydin connects variations to contract clauses, costs, claim status, and audit history.
Can Palydin help draft variation notices?
Palydin supports AI-assisted drafting from the contract record. Your team reviews the draft and controls what is submitted.
Does Palydin show which variations are included in claims?
Yes. Variations can sit beside claim workflows so teams can see submitted, assessed, approved, and pending value.
Is Palydin only for subcontractor variations?
No. Subcontractors, head contractors, and principals can use Palydin to manage variation records from their side of the contract.
Put your next claim on the record.
Book a 30-minute walkthrough on one of your contracts. When it fits, we set up a project pilot on a live contract and your team judges Palydin on its own numbers.