Incident Scenario: Recovering a Lost Deliverable
You are the PM leading a three-person team on the build-out of a new train station in a regulated environment. The documentation owner says the full document set was completed but accidentally deleted, causing a schedule slip.
Constraints & Assumptions
-
The documentation may include permits, safety plans, drawings, training materials, finance documents, approvals, and regulator-facing artifacts.
-
Some documents may be on the critical path and cannot be bypassed.
-
Treat the situation as blameless but audit-ready.
-
You own delivery communication and schedule rebaseline, while IT, documentation, finance, construction, and regulators may need to be involved.
Clarifying Questions to Ask
-
Which documents are missing, and which are regulatory gates?
-
Where were the documents stored and what backup/version history exists?
-
What evidence shows the documents were complete before deletion?
-
Which downstream milestones are blocked and which tasks still have float?
Part 1 - Diagnose What Happened
Walk through how you would determine whether the documents were truly complete and what was lost.
What This Part Should Cover
-
Incident containment, evidence preservation, access logs, version history, and a document inventory.
-
Completeness checks against definition of done, approvals, tickets, emails, contractor copies, and regulator submissions.
-
A content map showing expected, found, missing, and approval status.
Part 2 - Recover or Recreate
Decide whether and how to recover or recreate the documents.
What This Part Should Cover
-
Time-boxed recovery paths through recycle bins, backups, endpoints, email attachments, vendors, and forensics.
-
Parallel recreation of the minimum viable document set prioritized by critical path.
-
Decision criteria using probability of recovery, recreate duration, regulatory risk, and verification requirements.
Part 3 - Stakeholder Communication
Manage stakeholder expectations and communications.
What This Part Should Cover
-
War-room ownership, update cadence, single source of truth, and clear facts without blame.
-
Audience-specific communication for leadership, construction, finance, IT, regulators, and contractors.
-
Range-based commitments until recovery or recreation path is confirmed.
Part 4 - Rebaseline Schedule and Prevent Recurrence
Rebaseline the schedule, adjust the timeline, and define recurrence-prevention mechanisms.
What This Part Should Cover
-
Critical path analysis, scenario planning, resequencing, buffers, and new milestones.
-
Verification, compliance review, approvals, and staged submissions where possible.
-
Preventive controls such as backups, permissions, versioning, document inventory, two-person review, and completion evidence.
What a Strong Answer Covers
-
Calm incident management with evidence and auditability.
-
Parallel recovery and recreation to minimize schedule risk.
-
Clear stakeholder communication and realistic rebaseline.
-
Durable process controls after the incident.
Follow-up Questions
-
How would you handle it if the documents were never actually complete?
-
What would you tell regulators on day one?
-
When would you pause downstream work?
-
How would you decide whether to spend more time on recovery?
-
What process change would have prevented the issue?
