Adjudicate
Now
Payment & variations / Contract management

Variation records: building the notification process (NSW)

A contract-specific flow chart, notification letters and delay log helped a project team implement a reporting process.

Process implementedOutcome: We prepared the notice and reporting process. The Sydney project manager confirmed that the team had implemented it and prepared its first report.

Act and time limits

The project’s delay flowchart required a delay claim within 15 business days under clause 18.2. A statutory payment claim on a Sydney project has a separate timetable.

Building and Construction Industry Security of Payment Act 1999 (NSW) · s 17(2), (3)(c)–(e)

  • Lower scheduled amount. Apply within 10 business days after receiving the payment schedule.
  • Scheduled amount unpaid. Apply within 20 business days after the payment due date.
  • No schedule and the claim was not paid in full. Serve the notice of intention to apply within 20 business days after the payment due date. Allow 5 business days after the respondent receives the notice to provide a schedule, then apply within 10 business days after that period ends.

Read the Act

A site notebook, inspection tablet and construction records — illustrative image
AI-generated illustration of the case-study subject.

For a project in Sydney, New South Wales, we prepared a contract administration package that turned the variation provisions into steps the project team could follow. We brought together the notification steps, standard letters and a delay log.

From contract clause to site process

The project flowchart identified the notification steps, notice form, relevant periods and clause references, including the route for a disputed variation. Standard notification letters and a delay-log spreadsheet supported the process.

The aim was to make the contract's requirements usable when events occurred on site. A project team needed a consistent way to record an event, communicate it and retain the records needed to explain its consequences.

The outcome

The project manager confirmed that the team had implemented the system and prepared its first report.

What the preparation demonstrates

A useful administration system starts with the executed contract. It identifies who must act, what must be communicated and the project records that must be kept. Consistent notices and logs then provide the chronology needed to explain a variation or delay claim later.

Explore related experience

Put the evidence to work.

Tell us about the project, the disputed amount and any approaching deadline.

Discuss your claim →