Construction progress claims software connected to the contract behind the claim

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.

Each line is claimed on top of what was assessed last period, so the summary from gross claim to total payable adds up from the grid.CoversProgress claims · Retention / GST · SOPA schedules · Head contractor review

01The problem

Claim math without spreadsheet drift

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.

Without a shared record

  • Spreadsheet claim assembled from copied progress data and old claim periods.
  • GST, retention, and previous assessment values checked by formula instead of record.
  • Emailed PDF submission with attachments split across threads.
  • Head contractor assessment rebuilt in a separate workbook.
  • Payment schedule reasons and audit history depend on file names, inbox search, and memory.

With Palydin

  • 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.

02How it works

From contract to audit, step by step.

  1. 01

    Start with contract scope

    Use the schedule of works, approved variations, contract terms, and documents as the basis for the claim.

  2. 02

    Open the claim period

    Create the next progress claim against the same contract record, with claim numbering and period context kept in sequence.

  3. 03

    Carry prior assessments forward

    Bring previous approved amounts, rejected amounts, reasons, and claim-to-date values into the current claim.

  4. 04

    Apply retention and GST

    Keep retention deductions, GST, held amounts, and adjusted contract value visible before submission.

  5. 05

    Issue and audit the assessment

    Support head contractor review, payment schedule reasons, and audit history from the same submitted record.

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.

  1. Contract scope
  2. Claim period
  3. Prior assessment
  4. Retention / GST
  5. Payment schedule
  6. Audit

03Who it's for

Useful from either side of the contract.

Subcontractors
Draft claims from live progress, keep retention visible, and submit a cleaner record.
Head contractors
Review submitted claims against scope, variations, prior assessments, and compliance context.
Principals
See the basis of the payment claim without waiting for a rebuilt summary pack.

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 should construction progress claims software include?

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.

Does Palydin replace payment claim spreadsheets?

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.

Can assessors use Palydin too?

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.

Does Palydin provide legal advice on payment claims?

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.

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.