Skip to content

Dubai UTC+4

Enquire
Menu

Worked example · Falaj Tower · Sample project

Falaj Tower: one update, checked.

Falaj Tower is a residential tower of ground plus 14 floors over one basement, with its facade installed in five stages. Contract completion is 11 May 2027. At the 11 Aug 2026 update the main contractor's programme forecasts 26 May 2027, 11 working days late. This is the health check on that update.

Start with a health check

01 / Move the data date

Drag through the programme. The tower follows the record.

02 / The programme against the DCMA 14-point assessment

4 pass, 9 fail, 1 not scored.

102 activities and 117 links, tested as the update arrived. Each check shows its threshold and what the programme measured.

Sample project

  1. 01Logic9.1% · 4 of 44 incomplete tasks · threshold 5% or lessFail
  2. 02Leads1.5% · 1 of 67 links to incomplete tasks · threshold 0Fail
  3. 03Lags31.3% · 21 of 67 links to incomplete tasks · threshold 5% or lessFail
  4. 04Finish-to-start links70.1% · 47 of 67 links to incomplete tasks · threshold 90% or moreFail
  5. 05Hard constraints4.5% · 2 of 44 incomplete tasks · threshold 5% or lessPass
  6. 06High float15.9% · 7 of 44 incomplete tasks · threshold 5% or lessFail
  7. 07Negative float20.5% · 9 of 44 incomplete tasks · threshold 0Fail
  8. 08High duration2.3% · 1 of 44 incomplete tasks · threshold 5% or lessPass
  9. 09Invalid dates2 · 2 tasks · threshold 0Fail
  10. 10Resources15.9% · 7 of 44 incomplete tasks without cost or hours · threshold No threshold statedNot scored
  11. 11Missed tasks26.8% · 15 of 56 tasks due finished late or not at all · threshold 5% or lessFail
  12. 12Critical path testPass · 20-day slip on FC100 moved completion 20 days · threshold Completion moves in direct proportion to the slipPass
  13. 13Critical path length index0.947 · threshold 0.95 or moreFail
  14. 14Baseline execution index0.982 · 55 of 56 tasks due were finished · threshold 0.95 or morePass

03 / What a board would find in the registers

Three registers, read the way a board reads them.

Notices

27

  • 7 sent after the 28-day period
  • 5 unanswered, the oldest 149 days

Variations

14

  • 4 valued but not in the programme
  • 2 with no instruction on file

Extensions of time

4

  • 1 with no fragnet
  • 2 not carried into the update

04 / Ranked fixes

What comes back: each finding, its fix, ranked.

  1. 01

    7 of 27 notices sent after the 28-day period

    Check each against the notice clause and record why it went late. Add a reminder 7 days before each notice falls due.Impact high · effort low

  2. 02

    4 variations valued in the cost report with no programme assessment

    Assess time for each in the next update and link it to its register ID.Impact high · effort medium

  3. 03

    9 tasks on negative float, completion 11 working days past contract completion

    Write the recovery narrative and tie each negative-float path to a notice or a recovery action.Impact high · effort medium

  4. 04

    1 of 4 extension of time requests with no fragnet

    Build the fragnet and insert it into the update current when the event happened.Impact high · effort high

  5. 05

    4 open-ended tasks

    Add the missing successors so float on these tasks means something. Most of the high-float tasks are these open ends.Impact medium · effort low

  6. 06

    2 tasks with actual dates after the data date

    Correct the actuals before the update is issued.Impact medium · effort low

  7. 07

    15 of 56 tasks due by the data date finished late or haven't finished

    Give each a cause in the update narrative and link the causes to notices where the contract allows.Impact medium · effort low

  8. 08

    5 notices with no reply, the oldest 149 days

    Chase in writing and log the chase.Impact medium · effort low

  9. 09

    2 variations with no instruction on file

    Find the instruction or record how it was given (meeting, site walk) with the date.Impact medium · effort medium

  10. 10

    1 lead in the logic

    Split the predecessor so the successor can start from a real finish, without a lead or a lag.Impact low · effort low

  11. 11

    21 lagged links, 19 of them start-to-start in the floor cycle; 70.1% finish‑to‑start

    Split floor-cycle activities at the hand-over points so finish-to-start logic replaces the start-to-start lags.Impact low · effort medium

05 / How this was produced

Falaj Tower is a sample project.

Its programme, registers and dates come from a seeded model (seed 19650), built so the checks find what they find on real updates. No client's data is used. The same checks run on your programme in a health check.

Start here

Start with a health check.

  1. 01

    You send

    a Primavera P6 export (.xer) and your notice, variation and extension of time registers.

  2. 02

    We run

    the 14 DCMA checks, then notices, variations and extensions of time.

  3. 03

    You get back

    the findings ranked, each with its fix.

Start with a health check[email protected]Capability statement (PDF)