OpenConstruction Academy
Sign in / Register
EN

Theory before task 3 · 9 min

Root cause, preventive action and the programme

Root cause, and what it does to the programme

After this lecture you can

  1. Find a root cause that is a process step, not a person.
  2. Write a preventive action that changes that step before the next pour.
  3. Count a delay in working days across weekends and a bank holiday.
1 / 3

Ask why until you reach a step you can change

The gang poured because the pump arrived. The pump arrived because the concrete was booked on Thursday. It was booked before the steel was finished because the plant needs 48 hours. Nothing tied the booking to the release of H2. That last answer is a step in the process, and the preventive action changes it: no pour confirmed with the plant until H2 is signed and the Supervisor told. Quality management standards such as ISO 9001 (clause 10.2) ask for exactly this: correct the nonconformity, find its cause, act so it does not recur.

Example. A good root cause suggests its own preventive action. 'Operatives careless' suggests nothing that will stop the roof slab repeating it.
Why was FS1 poured without H2?the pump arrived
Why did the pump arrive?booked Thursday
Why booked before the steel was done?48 h plant notice
Why could it run without H2?no gate on the booking
2 / 3

A delay is counted in working days

Programmes run in working days. To measure a delay, find the new start date first, then count the working days between the planned start and the new one. Weekends do not count, and neither does a bank holiday: nobody planned to work on it, so it is not lost.

Example. Under NEC4 Option B a delay caused by the Contractor's own Defect is not a compensation event; it is the Contractor's to absorb.
Planned startTuesday, week 1
AcceptanceFriday, week 2
Monday, week 3bank holiday
New startTuesday, week 3
Common mistake

Blaming the gang

'Operatives ignored the ITP' is the commonest root cause on an NCR, and the least useful. People did what the booking told them. Write the cause as the step that let the work run, and the preventive action as the change to that step.

Example. Root cause: concrete booked with no link to the H2 release. Preventive action: booking confirmed only against a signed H2.

Counting the delay

Different numbers from your task: the calendar shown above.

Not to scale
The problem
  • Planned start Tuesday of week 1. Accepted Friday of week 2; work starts the next working day. Monday of week 3 is a bank holiday.
Step 1 of 3

Week 1

Working days from the planned Tuesday to the end of week 1, not counting the Tuesday?

3 days.

Step 2 of 3

Week 2

Working days in week 2?

5 days.

Step 3 of 3

Delay

Working days from the planned start to the new start on Tuesday of week 3?

3 + 5 + 1 = 9 working days.

In short. New start first, then working days between, holidays skipped.

Check yourself

Question 1 of 3

Which root cause leads to a useful preventive action?

  • It blames people and changes no step.

  • Right. The preventive action writes itself: no booking confirmed without a signed H2.

  • Weather is a circumstance, not a cause you can change.

Question 2 of 3

Who bears a delay caused by correcting the Contractor's own Defect under NEC4 Option B?

  • No clause 60.1 event covers the Contractor's own Defect.

  • Right.

  • A search that finds a Defect is at the Contractor's cost.

Question 3 of 3

Planned start Monday; work can start on Thursday of the following week. No holidays. How many working days are lost?

Five days in week 1 and three in week 2: 8 working days.

Read the source

Free official texts. The lecture cites clause numbers and puts the rules in its own words.