Support for owners and contractors facing delay, an EOT request or the need for a testable recovery plan.
Detailed article
Decision before action
Visible delay is not always the contractual cause of delay
We distinguish the event, timing, affected path, concurrent delay and mitigation, then identify what the available data can support.
When is this the right engagement?
The client position and project stage determine the required depth.
Owner reviewing an EOT request
Needs method, data, cause and effect tested before a decision.
Contractor facing an impacting event
Needs notice, records and analysis consistent with the programme.
Project needing recovery
Needs past delay separated from future recovery actions.
Risks that need to become visible
We turn general concern into specific issues that can be tested and owned.
- 01
Unreliable baseline
Impact cannot be measured against incomplete baseline logic. - 02
Events without chronology
Instructions, notices and updates do not align in time. - 03
Mitigation and concurrency ignored
Analysis jumps from event to days without testing alternatives.
A scope shaped around the actual question
We do not assume one package fits every project; we select what the decision needs.
Programme examination
Baseline, updates, controlling path and data quality.
Event analysis
Cut-off, cause, responsibility and impact path.
EOT and recovery
Test requested time and mitigation or sequencing options.
How does the consultation become action?
Short stages separate diagnosis, recommendation and implementation.
- 01
Set the analysis date
Freeze the data and versions used for review. - 02
Build event register
Link every event to record, programme and notice. - 03
Test the critical path
Determine whether impact reached completion. - 04
Assess options
Defensible time and mitigation or recovery actions.
Outputs that remain useful after the meeting
Every output is tied to a decision, owner or next action.
Delay event register
Documented chronology of status, notice and evidence.
Time analysis memorandum
Method, assumptions, findings and limitations.
Action plan
Record gaps, mitigation options and update ownership.
Qatar first · GCC when relevant
Time analysis must reflect how the project is actually delivered
We account for approvals, procurement, interfaces and real working arrangements in Qatar, without carrying assumptions between GCC projects untested.
Decisions connected to this path
Contextual links to services that precede this decision or are directly affected by it.
Frequently asked questions before the consultation
Concise answers to help you decide whether this is the right engagement path.
Can delay be analysed without a baseline?
A limited diagnosis is possible, but strength depends on reconstructing credible schedule logic.
Does every delay grant an extension?
No; contract, notice, causation, impact, concurrency and mitigation must be examined.
Do you also prepare recovery plans?
Yes, where data and project decisions allow realistic alternatives to be tested.
One practical next step
Start the discussion on WhatsAppStart with the question carrying the greatest project impact
Share the project stage and current issue; we will identify the right review before agreeing scope.