Replace spreadsheets, email threads, and PDF folders with one linked record — scope to audit, for claimant and assessor.

01The product






01 / 06
Start each progress claim from contract scope, prior assessments, retention, GST, and claim-to-date values.
02One contract, one file
Palydin connects the moving parts behind each claim — original scope, previous assessments, variations, retention, payment schedules and decision history — so your team always knows what was claimed, assessed and why.
The WBS, approved variations, separable portions, documents, and contract terms behind the claim.
The monthly progress position, claim-to-date values, attachments, and submission status.
Previously assessed amounts, reasons, rejected values, and what needs to carry forward.
Deductions, GST treatment, held amounts, caps, and release context beside the claim math.
SOPA timing, assessment reasons, communication context, and schedule status in one place.
Who changed what, when it moved, why it was assessed, and which source supports the record.
03Where Palydin fits
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
Useful for getting a claim or payment schedule out, but the backup often stays in emails, spreadsheets, folders, and separate trackers.
Palydin
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
Useful for large teams, but often too much if the problem is monthly claim and contract work. Palydin stays focused on that repeat workflow.
Built for Australian construction
04Workflows
05Built for every side of the contract
Subcontractors
Submit cleaner claims and stop losing variations in email.
Build progress claims from live scope, track retention, capture variations the day they happen, and keep every submission tied back to the contract.
Head Contractors
Assess claims from the same numbers your contractors submitted.
Review progress, variations, compliance, retention, and audit history in one workspace instead of reconciling PDFs, spreadsheets, and email threads.
Principals
See the commercial position before it becomes a dispute.
Track submitted claims, payment schedules, contract obligations, SOPA dates, and assessment history with a clear audit trail across every contract.
06Traceable answers
Palydin keeps answers tied to the underlying contract record, so your team can trace sources, review changes, manage access and defend decisions later.
Claim changes, assessment reasons, variation decisions, and retention activity stay attached to the record.
External parties only work inside the contracts they are connected to, not the whole project portfolio.
Commercial, assessor, claimant, admin, and viewer roles keep workflow permissions aligned to the job.
Contract documents and supporting files are stored as project records instead of scattered email attachments.
Answers point back to the contract material so teams can check the source before relying on the output.
Pricing
Full Pro access for 28 days, then $39 per seat per month. Use the trial to load a contract, build a claim, test contract-cited answers, and decide from the workflow itself.
Pro
No charge today. First charge after the 28-day trial unless cancelled before it ends.
FAQ
What Palydin does, how it handles claims, variations, retention and SOPA dates, and how pricing works. Still unsure? Book a walkthrough.
Get started
Book a 30-minute walkthrough. We’ll load one of your contracts and show the platform in action against your own numbers.
Walkthrough checklist
Bring one contract, one recent claim, and one variation. We’ll show the contract record, the claim math, the variation link, and the audit trail.
Prefer email? [email protected]
Pick a date
Mon–Fri, from 3 days out. Times shown in Brisbane (AEST).
Start the 28-day Pro trial, load a live contract, and decide from the workflow itself.