First 72 Hours: Establish Control of a Red Technology Project

When a technology project turns red, the immediate priority is to establish facts, decision authority, and containment—not to promise a recovery outcome.

Educational guidance only. This 72-hour checklist is not an Acute PMC engagement duration, a service-level agreement, a promise of stabilization, or a 24/7 emergency-response service.

The first control window

A useful first control window produces five things: a truthful baseline, a named decision owner, a controlled set of immediate risks, a decision-ready executive brief, and a clear next operating model. The sequence below is illustrative; real projects vary in pace and risk.

First 24 hours: establish authority and facts

Identify the accountable sponsor and escalation deputy. Inventory delivery evidence, upcoming obligations, decision deadlines, and present operational harm. Distinguish an active incident requiring the incumbent incident team from a troubled project requiring governance decisions. Pause nonessential scope additions until decision rights are clear.

Hours 24–48: install temporary controls

Name owners for critical dependencies. Document who can approve scope, budget, design, and deadline changes. Agree on one short evidence-based status cadence and rules for preserving artifacts. Record what remains unknown; do not turn missing evidence into a green status.

Hours 48–72: prepare a sponsor decision

Present a concise choice: continue under control, stabilize, restructure, pause, stop, or refer. Show consequences, obligations, decision owners, and the cost of waiting. Determine whether the client can receive a bounded control reset or needs ongoing delegated recovery leadership.

Which service fits?

Project Clarity supports independent diagnosis and sponsor decision-making. Project Rescue is a separately scoped stabilization and control-reset engagement when a capable receiving leader exists. Lead Recovery involves agreed delegated leadership or coordination. Severity alone does not select a service, and none guarantees recovery.

Frequently asked questions

Is this a 72-hour engagement? No. This is an educational sequence, not an offer duration.

Does Acute PMC provide 24/7 incident response? No. The client's established incident-response capability remains responsible for active incident containment.

Does the checklist promise stabilization within 72 hours or five days? No. Timing, scope, access, and responsibilities must be established in a separate engagement.

Use this checklist without hiring anyone: name a decision owner, preserve the evidence, document risks and unknowns, and bring real options to the sponsor.

For a conversation about a troubled technology project, contact Andrew.Davenport@acutepmc.com.

Acute Project Management Consulting LLC.