How I Challenge an EOT Without Becoming Adversarial

There is a way to assess an extension-of-time submission that gets a defensible answer and keeps the working relationship intact, and there is a way that gets a fight. The difference is not how hard you push — it is what you push against.

I challenge the evidence, not the person.

I make the criteria transparent. Before I get into any specific event, the contractor knows what the assessment is testing: is the event a valid claim under the contract; is there a demonstrable effect on the critical path to the affected milestone; and are both the cause and the effect evidenced in the contemporaneous record. Those are the same three tests every event faces. When the criteria are open and consistent, a rejection is not an opinion the contractor can take personally — it is a question the submission has not yet answered.

I let the programme do the talking. The strongest challenge is not “I disagree” — it is “show me where, in the contemporaneous programme, this event delayed the driving path.” A fragnet in the update, or its absence, settles more than any amount of argument. When the analysis is done in the programme rather than in correspondence, the discussion moves from positions to evidence, and evidence is much harder to be adversarial about.

I separate the strong from the weak. A submission is rarely all good or all bad. Part of assessing it professionally is acknowledging the events that are well-founded as readily as I question the ones that are not. A reviewer who rejects everything is as unpersuasive as a contractor who claims everything — and far more likely to end up in a dispute, because they have given the other side nothing to agree with.

I ask, rather than assert. “This is wrong” invites a fight. “Help me understand how this event reached the critical path, because in the update for that window the driving path runs elsewhere” invites an answer. Framing the challenge as a genuine question is not softness; it is the fastest route to the evidence, because it gives the contractor the specific thing to demonstrate.

I keep time and money, and cause and blame, separate. Much of the heat in EOT discussions comes from conflating an assessment of what happened to the programme with an accusation about who is at fault commercially. I keep the analysis to the former. Whether an event was Employer-risk or Contractor-risk is a factual, contractual question about the delay — not a character judgement — and treating it that way takes most of the temperature out of the room.

The reason this matters beyond good manners: an adversarial assessment is a weaker assessment. Hostility makes people defend positions instead of examining evidence, it hardens the other side, and it makes the whole thing more likely to end up in a forum where it costs both parties far more. A determination reached through transparent, evidential challenge is not just more pleasant to arrive at — it is more defensible when it is tested.

The takeaway: challenge the submission hard, but challenge the evidence and the programme, not the people — with open criteria and genuine questions. That is what makes the assessment both credible and survivable. The method sits under Claims & Delay Strategy and the Director’s Playbook.