Extension of time claim software that keeps every delay day on the record

Palydin keeps notices of delay and EOT claims in one register against the contract. Each claim links the notice it relies on and records days requested and granted for each separable portion, so the programme position is never rebuilt from emails.

Notices and claims share one register. Days stay with their separable portion, so nothing is added across portions.CoversNotices of delay · EOT claims · Days by portion · Assessment trail

01The problem

Days kept per portion, never added up

An extension to one separable portion says nothing about another. Palydin records requested and granted days against each portion, so the register never reports a meaningless combined total.

Without a shared record

  • A delay is noticed on site and reported in an email nobody files.
  • The notice date is argued later because nobody kept the sent version.
  • EOT claims are typed in a letter template that doesn't link the notices.
  • Days for different portions are added together in a tracker and stop meaning anything.
  • Granted days live in correspondence, away from the programme and the contract.

With Palydin

  • Issue notices of delay with the event dates and the portions affected.
  • Raise each EOT claim against the notice it relies on.
  • Record days requested and granted for each separable portion.
  • Keep the assessor's reasons and the audit history on the claim.

02How it works

From contract to audit, step by step.

  1. 01

    Notify the delay

    Record the delay event, when it started, whether it is still running, and the portions it affects. The notice date is set when the notice is created, and issuing it freezes the record.

  2. 02

    Claim the days by portion

    Raise the EOT claim against the notice it relies on and request days for each separable portion it affects.

  3. 03

    Assess and grant

    The assessor grants days for each portion against what was requested and records the reason in the assessment comment.

  4. 04

    Keep the trail

    Notices, claims, decisions, and who made them stay in the audit history for when the programme is challenged.

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. Delay event
  2. Notice of delay
  3. Separable portion
  4. EOT claim
  5. Days granted
  6. Audit

03Who it's for

Useful from either side of the contract.

Subcontractors
Give notice when the delay happens and claim the days against the right portion.
Head contractors
Assess subcontractor EOT claims and run your own against the client from the same register.
Principals
See every notice and claim with the days requested and granted for each portion.

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 EOT claim software?

Extension of time (EOT) claim software records notices of delay, the EOT claims built on them, and the days requested and granted. Palydin keeps these in one register against the contract, with each claim linked to the notice it relies on.

Does Palydin add up EOT days across separable portions?

No. Days are recorded and reported for each separable portion, because an extension to one portion doesn't move the date of another. The register counts records, not combined days.

Can Palydin track a delay that is still running?

Yes. A notice records whether the delay event has ended, is ongoing, or is not yet known, and whether the length of the delay is known when the notice is issued.

Does Palydin tell us whether an EOT is valid under our contract?

No. Palydin keeps the notices, claims, dates, and decisions on the record. Entitlement under your contract is for your team and advisers to assess.

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.