Step 01
Record the variation event
Capture changed scope, contractual background, cost support, and the party raising the variation.
Variations
Construction variation management software that keeps scope changes connected
Palydin helps teams capture, draft, review, assess, and audit variations against the contract record. Scope changes stay connected to clauses, cost breakdowns, claims, and the history behind each decision.
What this page covers
Variation registerClaim impactAssessment reasonsAudit trail
Australian contract admin context
Built around the records commercial teams actually argue over.
Palydin uses Australian construction language in the product: progress claims, retention, GST, payment schedules, and the claimant/assessor relationship between subcontractors, head contractors, and principals.
Progress claims
Claim periods, claimed-to-date values, prior assessments, supporting documents, and submitted status stay together.
GST and retention
Keep GST, retention deductions, held amounts, and release context visible inside the claim workflow.
SOPA/payment schedules
Track payment schedule context beside the claim, assessment reasons, contract terms, and audit history.
Both sides of the contract
Subcontractors can prepare the record. Head contractors and principals can assess from the same file.
The broken current workflow
The old process hides the facts in the gaps.
Search pages should name the real construction workflow problem: separate files, separate assessments, and no reliable shared record.
01
Scope change starts in site email or a meeting note.
02
Cost support sits in a folder separate from the notice.
03
Contract clause references are checked late or copied by hand.
04
Approved, pending, and submitted values drift from the claim position.
05
Assessment reasons disappear into comments or old attachments.
How Palydin handles it
A workflow for the full commercial day.
Step 02
Tie it to contract scope
Keep the variation connected to clauses, documents, separable portions, and the original scope position.
Step 03
Carry the value into claims
Keep submitted, assessed, approved, and pending variation values visible beside progress claims.
Step 04
Assess with reasons
Record head contractor or principal assessment decisions, revisions, reasons, and audit history against the same file.
Connected records
The claim is not the system. The contract record is.
This is the Palydin difference: the workflow stays connected to the records that explain and defend it.
Where Palydin fits
Keep every claim and its backup together.
Some tools help you send a claim. Big project systems try to manage the whole job. Palydin sits between them: it keeps claims, variations, retention, documents, assessments, and history in one place.
Claim and payment schedule tools
They help send the claim
Useful for getting a claim or payment schedule out, but the backup often stays in emails, spreadsheets, folders, and separate trackers.
Palydin
It keeps the full story with it
Claims, variations, retention, documents, assessments, SOPA dates, and history stay together, so anyone reviewing the claim can see what it is based on.
Broad project platforms
They try to run the whole job
Useful for large teams, but often too much if the problem is monthly claim and contract work. Palydin stays focused on that repeat workflow.
Operational trust
Proof in the workflow, not in a badge.
The trust story is practical: who saw what, what changed, which source supported the answer, and which contract record holds the history.
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 workflows separated.
Counterparty scoping
External parties only work inside the contracts they are connected to, not the whole project portfolio.
Contract-cited AI
Answers point back to contract material so teams can check the source before acting.
Role relevance
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.
FAQ
Direct answers for search visitors.
Start with one contract
Verify the workflow before you talk to sales.
Start the Pro trial, load one contract, draft a real workflow, and decide from the product surface.