Book a demo, get a 14-day free trial. →
BuildersAI

Delay register

What the job lost, why, and the record to put behind the claim.

A delay register for a project across a chosen date range, with Export and Print in the corner. Three figures read 25.5 hours lost, 3.2 working days at 8 hours a day, and 4 days affected. Underneath, chips break the total down by cause: Weather 10 hours 30 minutes, Materials 8 hours, Information 4 hours and Instruction 3 hours.

Delays get argued about at the end and recorded at the beginning, if at all. The register is where they get written down on the day they happen.

What it does

  • Record a delay while it is happening, from the phone
  • Say what caused it and what it cost the programme
  • Filed against the day in the site diary, beside that day’s photographs
  • Read the whole register for a job in one list, in a browser

Why it matters on site

An extension of time claim is only as good as its contemporaneous records. Writing the delay down on the afternoon it happened is the whole difference between a claim and an opinion.

Which plan

This is included in every plan, from £149 a month. Plans differ by how many people they seat, not by what the software does. See pricing.

How to use it

The manual page for this is in the Help Centre, and it is the same guide SiteBot reads inside the app. Read the guide.