Built Logic

See what AI can do

Put together extension of time submissions with cause, effect and evidence

We take off your hands: digging through the notices, site diaries and emails. Going through each programme too. Building the case for each delay.

You get: a draft extension of time claim. It sets out the ground in the contract you rely on. The evidence for each delay, in an appendix. It goes to your commercial manager.

Get a price for this

Or check first: Are we ready for AI?

The problem

It takes weeks to put an EOT claim together. It's all digging through emails.

How it works

  1. What comes in

    • Delay notices, events log, programmes, diaries, correspondence, weather data
  2. What AI does

    Builds an event-by-event file with evidence, drafts narrative sections and indexes appendices.

  3. What you get

    • Draft extension of time submission and evidence appendix
  4. Who signs it off

    Your planner or delay expert does the delay analysis. Your commercial manager owns the claim.

What it needs to work

  • Evidence index
  • Programme records

If those aren’t in place yet, you’ll hear that before anything gets built.

Who it’s for

  • Main contractors
  • Specialist subcontractors
  • Surveyors and cost consultants

What would this cost for your team?

Answer questions about your company and how this work runs today. You see an indicative estimate of the hours back, what that time is worth and the price when you send your details.

Get a price for this

Or check first: Are we ready for AI?

How it runs, before and after

Delay on site to extension of time submission

Before, by hand

Record the site

Spot and notify delay

Claim the time

01Turn site notes and photos into a daily diary

  • Type up voice notes
  • Sort notes and photos into sections
  • Add sign-in and weather data
  • Flag missing sections
  • Check and sign the diary

02Log hours lost to weather against the activities stopped, every day

  • Record readings and stoppages
  • Prompt site for what stopped
  • Work out hours lost
  • Flag days over the contract limit
  • Confirm the stoppages
  • Decide on notices and claims

03Spot early signs of delay in site records and raise them for an early warning

  • Read diaries, emails and minutes
  • Rate the likely impact
  • Link events to the programme
  • Check for an existing warning
  • Draft the early warning
  • Decide and sign the notice

04Draft delay notices as soon as site records show a likely delay

  • Spot a likely delay
  • Match the cause to the contract
  • Draft the notice
  • Set reminders for particulars
  • Log the notice
  • Approve and issue it

05Compile weather evidence for extension of time and compensation event claims

  • Pull the weather data
  • Apply the contract test
  • Link bad days to site stops
  • Draft the weather schedule
  • Confirm the effect on the programme
  • Decide whether to claim

This step06Put together extension of time submissions with cause, effect and evidence

  • Gather records for each event
  • Draft the narrative
  • Index the appendices
  • Do the delay analysis
  • Approve the submission

07Track liquidated damages exposure against forecast completion and extension of time status

  • Pull dates and LD rates
  • Pull the forecast completion
  • Work out exposure by scenario
  • Link it to open EoT claims
  • Decide mitigation and provisions

39tasks, all by hand

After, with automation and AI

AutomatedAI reads and draftsYour team decides

Record the site

Spot and notify delay

Claim the time

01Turn site notes and photos into a daily diary

  • AI reads and drafts: Type up voice notes
  • AI reads and drafts: Sort notes and photos into sections
  • Automated: Add sign-in and weather data
  • Automated: Flag missing sections
  • Your team decides: Check and sign the diary

Passes on: a diary for each day, from voice notes, photos and messages

02Log hours lost to weather against the activities stopped, every day

  • Automated: Record readings and stoppages
  • Automated: Prompt site for what stopped
  • Automated: Work out hours lost
  • Automated: Flag days over the contract limit
  • Your team decides: Confirm the stoppages
  • Your team decides: Decide on notices and claims

Passes on: the hours lost to the weather, set against the work that stopped

03Spot early signs of delay in site records and raise them for an early warning

  • AI reads and drafts: Read diaries, emails and minutes
  • AI reads and drafts: Rate the likely impact
  • AI reads and drafts: Link events to the programme
  • Automated: Check for an existing warning
  • AI reads and drafts: Draft the early warning
  • Your team decides: Decide and sign the notice

Passes on: early signs of delay found in the site records

04Draft delay notices as soon as site records show a likely delay

  • AI reads and drafts: Spot a likely delay
  • AI reads and drafts: Match the cause to the contract
  • AI reads and drafts: Draft the notice
  • Automated: Set reminders for particulars
  • Automated: Log the notice
  • Your team decides: Approve and issue it

Passes on: a draft delay notice under the contract

05Compile weather evidence for extension of time and compensation event claims

  • Automated: Pull the weather data
  • Automated: Apply the contract test
  • AI reads and drafts: Link bad days to site stops
  • AI reads and drafts: Draft the weather schedule
  • Your team decides: Confirm the effect on the programme
  • Your team decides: Decide whether to claim

Passes on: the weather on record, set next to the limits in the contract

This step06Put together extension of time submissions with cause, effect and evidence

  • AI reads and drafts: Gather records for each event
  • AI reads and drafts: Draft the narrative
  • Automated: Index the appendices
  • Your team decides: Do the delay analysis
  • Your team decides: Approve the submission

Passes on: the EOT claim, with the cause, the effect and the records

07Track liquidated damages exposure against forecast completion and extension of time status

  • Automated: Pull dates and LD rates
  • Automated: Pull the forecast completion
  • Automated: Work out exposure by scenario
  • AI reads and drafts: Link it to open EoT claims
  • Your team decides: Decide mitigation and provisions

Ends with: the LDs at risk, set against the forecast end date

15automated14by AI10decided by your team

Before, by hand

Record the site

1Write the site diary
2Log weather downtime

Spot and notify delay

3Spot early delay signs
4Draft the delay notice

Claim the time

5Build the weather case
6Build the EoT claimThis step
7Track the LD exposure

39tasks, all by hand

After, with automation and AI

AutomatedAI reads and draftsYour team decides

Tap a step to see each task and what it passes on.

Record the site

1Write the site diary

AI reads and drafts: Type up voice notes

AI reads and drafts: Sort notes and photos into sections

Automated: Add sign-in and weather data

Automated: Flag missing sections

Your team decides: Check and sign the diary

Passes on: a diary for each day, from voice notes, photos and messages

2Log weather downtime

Automated: Record readings and stoppages

Automated: Prompt site for what stopped

Automated: Work out hours lost

Automated: Flag days over the contract limit

Your team decides: Confirm the stoppages

Your team decides: Decide on notices and claims

Passes on: the hours lost to the weather, set against the work that stopped

Spot and notify delay

3Spot early delay signs

AI reads and drafts: Read diaries, emails and minutes

AI reads and drafts: Rate the likely impact

AI reads and drafts: Link events to the programme

Automated: Check for an existing warning

AI reads and drafts: Draft the early warning

Your team decides: Decide and sign the notice

Passes on: early signs of delay found in the site records

4Draft the delay notice

AI reads and drafts: Spot a likely delay

AI reads and drafts: Match the cause to the contract

AI reads and drafts: Draft the notice

Automated: Set reminders for particulars

Automated: Log the notice

Your team decides: Approve and issue it

Passes on: a draft delay notice under the contract

Claim the time

5Build the weather case

Automated: Pull the weather data

Automated: Apply the contract test

AI reads and drafts: Link bad days to site stops

AI reads and drafts: Draft the weather schedule

Your team decides: Confirm the effect on the programme

Your team decides: Decide whether to claim

Passes on: the weather on record, set next to the limits in the contract

6Build the EoT claimThis step

AI reads and drafts: Gather records for each event

AI reads and drafts: Draft the narrative

Automated: Index the appendices

Your team decides: Do the delay analysis

Your team decides: Approve the submission

Passes on: the EOT claim, with the cause, the effect and the records

7Track the LD exposure

Automated: Pull dates and LD rates

Automated: Pull the forecast completion

Automated: Work out exposure by scenario

AI reads and drafts: Link it to open EoT claims

Your team decides: Decide mitigation and provisions

Ends with: the LDs at risk, set against the forecast end date

15automated

14by AI

10decided by your team

An example of how this workflow usually happens. We would tailor it to your company and add or remove tasks based on how you work.