Subcontractor compliance software that checks the paperwork before the claim

Palydin keeps each subcontract's compliance register beside its claims. Insurances, licences, and safety certificates carry their expiry dates, subcontractors upload their own documents, and a claim can't be submitted while a required document is missing.

The register shows each requirement's status. A missing required document blocks claim submission until it is uploaded.CoversInsurances · Licences · Expiry dates · Claim gating

01The problem

Compliance checked where the money moves

A certificate of currency matters most when a claim is about to be paid. Palydin holds a claim back while a required document is outstanding, so the check happens every time, not when someone remembers.

Without a shared record

  • Certificates of currency arrive by email and are saved to a shared drive.
  • Expiry dates live in a spreadsheet someone updates when they have time.
  • A claim is assessed and paid while the public liability policy has lapsed.
  • Subcontractors are chased for the same document every month.
  • Nobody can show which version was current on the day a claim was paid.

With Palydin

  • Set required insurances, licences, and safety certificates for each subcontract.
  • Let linked subcontractors upload their own documents.
  • See what is missing or expiring before it becomes a problem.
  • Hold claim submission until required documents are in.

02How it works

From contract to audit, step by step.

  1. 01

    Set what each subcontract needs

    Add the insurances, licences, and safety certificates the trade must hold, mark which are required, and record expiry dates.

  2. 02

    Claims wait for the paperwork

    While a required document is missing, the subcontractor can't submit a claim. Once their organisation is linked to the contract, they upload it themselves, and a replaced document keeps its earlier version.

  3. 03

    See what needs attention

    Outstanding and expiring documents show up beside the claims and schedules that need action on the contract.

  4. 04

    Keep the record

    Uploads, fulfilments, and claim decisions stay in the audit history, so you can show what was current when a claim was paid.

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. Subcontract
  2. Requirement
  3. Document
  4. Expiry date
  5. Claim
  6. Audit

03Who it's for

Useful from either side of the contract.

Head contractors
Set what each trade must hold and see every subcontract's position before claims are assessed.
Subcontractors
Upload certificates to your own contract and see what is outstanding before you claim.
Principals
See compliance across every subcontract on your projects without chasing reports.

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 is subcontractor compliance software?

It tracks the documents a subcontractor must hold, such as public liability and workers compensation insurance, licences, and safety certificates, along with their expiry dates. Palydin ties that register to the subcontract's claims.

Can Palydin stop a claim when insurance is missing?

Yes. While a document marked as required is outstanding, the claim can't be submitted. The subcontractor sees what is missing and uploads it to their own contract.

Do subcontractors upload their own documents?

Yes. Once the subcontractor's organisation is linked to the contract, their team uploads documents against each requirement themselves. When a document is replaced, the earlier version is kept.

Does Palydin check whether a policy's cover is adequate?

No. Palydin tracks which documents are held, required, and expiring. Whether a policy's cover meets your contract is for your team to check.

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.