Skip to content

Case Studies

Ending a Legal Escalation Caused by Misreported Status

How honest, evidence-based reporting rebuilt trust after a project's true status was hidden.

Engagement
Red project rescue
Stage
Takeover after escalation to legal

The situation

We were brought in to de-escalate a project that the client had already escalated to legal.

What was really going wrong

  • The previous project lead had misreported deliverables, progress, budget used and timelines to avoid flagging the project as red.
  • That created a false picture of progress until the gaps became visible to the client.
  • Once the client saw the inconsistencies, trust collapsed and legal got involved.

How we fixed it

Step 1: Acknowledge it.

We met client leadership, acknowledged the breakdown in trust directly, reset expectations, and committed to transparent, fact-based reporting from that point on.

Step 2: Find the truth.

Internally, we established what had actually been completed versus what had been reported, validated the remaining scope, and recalculated realistic timelines and effort.

Step 3: Re-baseline and rebuild.

  • Re-baselined scope, budget and timeline with the client.
  • Increased the reporting cadence and level of detail, and removed vague status language.
  • Moved the conversation from blame to recovery by focusing on what could still be delivered under clear governance.

What we refused to allow

Any status report that couldn't be backed by evidence. The project manager's role was reset as the objective source of truth, not a buffer between the team and the client.

The results

  • Legal escalation halted

  • Re-baselined

    and stabilized under transparent governance

  • 1-year agreement

    Client signed a one-year managed services agreement

The lesson

Honest red beats false green every time. Clients forgive bad news far more readily than hidden news.

Facing something similar?