Step 01
Capture retention terms
Set retention percentage, cap, GST treatment, separable portions, and release conditions from the contract.
Retention
Construction retention tracking software for claims, releases, and contract terms
Palydin keeps retention tracking beside progress claims, separable portions, contract terms, release timing, and the audit trail. Teams can see held amounts and upcoming release positions without maintaining a separate spreadsheet.
What this page covers
Retention heldGST contextRelease timingClaim deductions
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
Retention is calculated in the claim spreadsheet but tracked somewhere else.
02
Release dates depend on practical completion notes or calendar reminders.
03
Separable portion positions are hard to see across claims.
04
Approved releases are disconnected from the claim history.
05
The held amount is checked manually each time someone asks.
How Palydin handles it
A workflow for the full commercial day.
Step 02
Apply to each claim period
Keep retention deductions visible as progress claims are drafted, submitted, and assessed.
Step 03
Track held amounts
See retention held beside approved-to-date values, prior assessments, and claim history.
Step 04
Manage release triggers
Use practical completion, DLP dates, and separable portion records where release timing differs.
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
See held amounts and release opportunities without maintaining a private tracker.
Head contractors
Assess claims and release requests with contract terms and history in the same record.
Principals
Keep retention exposure visible across portions, claims, and contract milestones.
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.