Subcontracts

Keep subcontractor claims, changes, and compliance in one place

Palydin helps head contractors and subcontractors manage the monthly contract work around subcontracts: claims, assessments, compliance, variations, retention, documents, and audit history.

Palydin progress claims table showing periods, statuses, response dates, claimed values, and assessed values
Each subcontract can carry its claim periods, compliance status, variation register, retention position, and supporting documents in one reviewable file.

Projects

Clearer records for both sides of the subcontract

Subcontract claims often depend on attachments, site progress, compliance status, variation background, and prior assessments. Palydin keeps that backup with the claim.

Review subcontractor payment claims with the backup attached.
Track compliance blockers before claims move.
Keep variation status and retention visible beside the claim.

How Palydin handles it

A workflow for the full commercial day.

Setup

Create the subcontract file

Keep terms, scope, compliance requirements, retention settings, and documents together.

Claim

Run claims against the same file

Track claim periods, support, assessments, payment schedule context, and audit history.

Change

Keep changes visible

Connect variations and compliance status to the claim review process.

Palydin progress claims table showing periods, statuses, response dates, claimed values, and assessed values
Each subcontract can carry its claim periods, compliance status, variation register, retention position, and supporting documents in one reviewable file.

Common work

The repeat tasks Palydin keeps together.

01

Receive, assess, and respond to subcontractor claims.

02

Track required insurance, safety, and compliance documents.

03

Manage variation submissions and assessment reasons.

04

Keep retention deductions and releases visible.

Outcomes

What gets easier when the record is clean.

Less inbox chasing during claim assessment.
Clearer payment schedule records.
Better visibility across open subcontract issues.

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.

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.