Engr. Muhammad Waqas Ahmed: Delay Analysis, EOT, Claims Management and Forensic Scheduling

Engr. Muhammad Waqas Ahmed — forensic delay analysis, EOT and claims management

Construction delay is rarely just a scheduling problem. It can affect completion dates, cash flow, subcontractor performance, liquidated-damages exposure, entitlement to Extension of Time (EOT), disruption costs and the commercial position of every party involved. Effective delay analysis therefore needs more than a programme printout: it requires reliable schedule logic, contemporaneous project records, contractual understanding and a defensible method of analysis.

Engr. Muhammad Waqas Ahmed strengthens BGB-360's project-controls capability as a Delay Analysis & Claims Management Specialist. He brings 16 years of field experience across oil & gas and construction projects in the UAE and Saudi Arabia and currently supports US-based projects. His work covers planning, scheduling, forensic delay analysis, EOT assessment, claims documentation and recovery planning.

Why delay analysis matters

A project may finish late for many reasons: late access, design changes, approvals, procurement constraints, subcontractor performance, rework, client instructions, resource shortages, adverse events or several overlapping causes. The challenge is to determine which events actually affected the critical path, when the impact occurred, how long it lasted, whether mitigation or recovery changed the outcome, and what the contract allows.

A credible analysis should therefore answer four practical questions:

  • What happened? Identify the relevant delay events and the factual record.
  • When did it affect the programme? Link events to schedule activities, updates and critical-path movement.
  • Who or what was responsible? Assess causation and responsibility against the available contract and evidence.
  • What is the time consequence? Quantify the effect on completion and support the appropriate EOT, recovery or claims position.

The evidence base: schedules and contemporaneous records

Delay analysis becomes substantially stronger when the programme is tested against what actually happened on the project. Typical source material can include the approved baseline programme, periodic updates, progress reports, correspondence, RFIs, instructions, submittal and approval logs, procurement records, site diaries, meeting minutes, photographs, resource information and change records.

Waqas's approach is to organize these records into a chronology, connect material events to relevant schedule activities, and test the relationship between the event, the critical path and the contractual provisions relied upon. This helps reduce unsupported narrative and creates a clearer audit trail for management review, negotiation or formal claim preparation.

Forensic schedule analysis methodologies

No single delay-analysis method is appropriate for every project. The available records, quality of the baseline and updates, contract requirements, timing of the analysis and purpose of the assessment all matter. Waqas's stated expertise includes the following established approaches:

MethodTypical analytical purpose
Time Impact Analysis (TIA)Tests the prospective or event-specific impact of a delay by inserting a modeled fragnet into an appropriate schedule update and examining its effect on completion.
Impacted As-PlannedModels identified delay events against the planned programme to assess potential impact, subject to the reliability and limitations of the baseline.
Windows AnalysisDivides the project into periods or “windows” and examines how critical paths, progress and delay causes changed over time.
As-Planned vs As-BuiltCompares planned sequencing and duration against actual performance to identify significant variance and investigate causation.
Collapsed As-Built / But-ForStarts from the as-built sequence and removes selected delay events to model the completion date that might have occurred without those events.
Critical Path Method analysisExamines schedule logic, longest/critical paths, float and changes in controlling activities to understand what governed completion.

The methodology should not be selected simply because it is familiar or produces a preferred result. AACE International's 29R-03 guidance expressly recognises that method selection and implementation depend on the contract, facts, applicable law and the availability and quality of contemporaneous records. It is a technical reference rather than a one-size-fits-all prescription.

Extension of Time (EOT): from event to entitlement

An EOT submission should do more than state that an event occurred. A structured assessment typically needs to establish the relevant contractual event, demonstrate notice and record support where required, connect the event to programme impact, consider mitigation and concurrency, and quantify the resulting effect on completion.

Waqas reviews baseline and updated programmes, progress data, correspondence and contemporaneous records to investigate critical delay, causation and responsibility. Depending on the contract and governing law, an assessment may need to distinguish between excusable and non-excusable delay, compensable and non-compensable delay, and concurrent delay.

Important: Delay analysis supports the technical and evidential assessment of time impact. Contractual entitlement and legal conclusions remain dependent on the specific contract and applicable law; legal advice should be obtained where required.

Claims management and defensible documentation

Good claims management begins before a dispute. Clear notices, consistent progress updates, structured change records and contemporaneous evidence can materially improve the quality of later analysis. BGB-360's specialist support can be scoped around:

  • delay-event chronology and causation review;
  • baseline and update programme assessment;
  • critical-path and float analysis;
  • EOT support and delay-analysis reporting;
  • claims documentation and evidence organization;
  • review of contractor, subcontractor or consultant delay positions;
  • technical support for negotiation and management decision-making.

Recovery planning: analysing delay before it becomes a claim

Forensic analysis is often associated with disputes, but the same project-controls discipline can be used earlier to protect project value. Waqas develops planning, scheduling and recovery solutions intended to identify emerging delay, test alternative sequences and support timely completion.

Examples include reviewing near-critical activities, assessing resource or sequence changes, comparing recovery scenarios, testing revised logic, and monitoring whether corrective actions are actually improving the forecast completion date. The objective is not merely to explain delay after the event, but to help project teams respond while options still exist.

Primavera P6 and programme quality

Primavera P6 is central to Waqas's scheduling work. However, software does not make an analysis reliable by itself. The usefulness of a P6 programme depends on the quality of its logic, calendars, constraints, progress status, relationships and update discipline. Before relying on schedule outputs, the underlying programme should therefore be checked for material weaknesses that could distort critical-path conclusions.

For clients, consultants and contractors, this means that a delay review can include both the technical schedule model and the project evidence surrounding it, rather than treating the programme as an isolated file.

AI-assisted construction analysis — with professional review

Waqas and his team have developed AI-oriented tools intended to support planning, scheduling, progress tracking, delay analysis and claims management. Their stated use cases include organizing contemporaneous records, connecting project events to schedule activities and contractual provisions, identifying emerging delay risks and evaluating recovery options.

BGB-360's position is that AI should support—not replace—professional analysis. AI-generated observations need to be checked against the source records, programme logic, contractual requirements and engineering context before they are used in a professional conclusion.

AACE and SCL reference frameworks

Waqas's professional profile identifies AACE International Recommended Practice 29R-03 and the Society of Construction Law (SCL) Delay and Disruption Protocol as reference frameworks in his approach. AACE 29R-03 provides technical principles and guidance for applying CPM scheduling in forensic schedule analysis, while the SCL Protocol provides guidance to construction parties dealing with delay and disruption and emphasises transparency of information and methodology.

AACE International Recommended Practices and the SCL Delay and Disruption Protocol are external professional references; the appropriate contractual and legal framework for any particular project must still be considered separately.

Industry contribution and experience

According to his professional profile, Waqas has 16 years of field experience, has trained 5,000+ professionals in delay analysis and claims management, and has served 20+ multinational companies as a consultant in this domain. His experience spans construction and oil & gas work in the UAE and Saudi Arabia, alongside current consulting support for US-based projects.

His professional approach emphasises collaborative technical discussion, transparent findings and defensible reporting—particularly important where multiple parties have different interpretations of the same project history.

When should a project team seek delay-analysis support?

  • Completion is slipping and the controlling cause is unclear.
  • An EOT submission or response needs programme-based substantiation.
  • There are several overlapping delay events or possible concurrency.
  • The baseline or updated programmes are being challenged.
  • A contractor, subcontractor, consultant or employer has issued a delay claim.
  • The team needs an independent technical review before negotiation.
  • Management needs recovery options rather than a retrospective explanation only.
  • Project records are extensive and need to be organized into an evidence-based chronology.

Need an independent delay, EOT or claims review?

BGB-360 can arrange an initial discussion with Engr. Muhammad Waqas Ahmed to understand the project stage, available programme records, key delay events and the type of technical support required. The first step is a scope review—not a predetermined claim conclusion.

Frequently asked questions

Can BGB-360 support an Extension of Time assessment?
Yes. The scope can include programme review, delay-event assessment, critical-path analysis, contemporaneous-record review and structured EOT support, subject to the project contract and available evidence.

Which delay-analysis method will be used?
The method depends on the purpose of the assessment, contract, project circumstances, schedule reliability and available records. The methodology should be selected for the specific case rather than applied mechanically.

Can Waqas review an existing contractor or consultant delay report?
Yes. A review can examine the underlying schedule logic, selected methodology, assumptions, records relied upon and whether the conclusions are consistent with the available project information.

Can the service be used before a formal claim exists?
Yes. Early programme and delay-risk review can help management identify critical issues, strengthen records and consider recovery options before positions become entrenched.

Does AI replace forensic schedule analysis?
No. AI can support record organization, pattern identification and analytical workflows, but professional conclusions should be grounded in verified project records, schedule logic and contractual requirements.

Does BGB-360 provide legal advice on construction claims?
No. BGB-360's delay-analysis support is technical and commercial in nature. Where legal interpretation or representation is required, the client should obtain advice from appropriately qualified legal counsel.

BGB-360 and Learn with Engr Waqas

BGB-360 also works with Waqas through its professional alliance with Learn with Engr Waqas. The collaboration connects specialist project-controls capability with BGB-360's wider accounting, finance, ERP, remote workforce and advisory network.

Need delay analysis, EOT or claims support?

Discuss your programme, delay events and available records with BGB-360.