01
Load the contract
Index the scope, key dates, retention settings, and contract documents that shape the claim.
Progress claims
Palydin helps construction teams draft progress claims from live scope, cumulative progress, retention, GST, prior assessments, and contract history. The claim is not an isolated document - it stays tied to the records both sides need to verify.

Product proof
Build the claim from the same scope and contract data your team already manages. Review every number before submission, then keep the assessment history attached to the same file.
Draft payment claims from current scope and prior claim history.
Keep retention, GST, and cumulative progress visible in the claim workflow.
Let claimant and assessor work from the same auditable contract record.
Use contract-cited answers to check dates, clauses, and supporting context.
How it works
01
Index the scope, key dates, retention settings, and contract documents that shape the claim.
02
Use live progress and prior claim data to assemble a reviewed payment claim.
03
Invite the other side when ready so assessment happens against the submitted record.
FAQ
The goal is self-serve clarity: what the page is about, what Palydin does, and where your team still reviews the output.
It should manage progress values, previous claims, current claim amounts, retention, GST, supporting documents, assessment status, and audit history. Palydin also connects claims to variations, compliance, SOPA dates, and contract documents.
Palydin is designed to replace the linked spreadsheets and email trails that usually surround payment claims. Teams can still export or share information where needed, but the working record lives in Palydin.
Yes. Palydin supports both sides of a contract, so the assessor can review the same submitted claim record instead of rebuilding the position in a separate file.
No. Palydin provides workflow, drafting, records, and deadline visibility. Teams should still use their own commercial and legal review for claim strategy and statutory requirements.
Start with one contract
Start the Pro trial, load one contract, draft a real workflow, and decide from the product surface.