Almost every project failure I've been called in to help untangle had warning signs months before it became a crisis. Nobody missed them because they were subtle — they missed them because they'd become normal. A schedule slip becomes routine. A vague status update becomes the way updates are always written. By the time the red flag is impossible to ignore, the project usually has far fewer good options left than it did when the flag first appeared.
Here are ten of the signals experienced PMs learn to catch early — and what to do about each one the moment you notice it.
Scope creep disguised as "small changes"
Individually, each ask sounds reasonable — "just one more field," "a quick tweak to the report." Collectively, they add weeks of unbudgeted work with no formal change request behind them.
Watch for: change requests happening in hallway conversations or chat threads instead of your change log.Sponsor disengagement
When the executive sponsor stops attending steering meetings or delegates every decision downward, the project has lost its air cover — and its ability to get fast decisions when it matters.
Watch for: sponsor sending a deputy to three consecutive checkpoint meetings.Status reports that are always green
Real projects have friction. A status report with no ambers, ever, usually means problems are being managed out of view rather than actually resolved — until they can't be hidden anymore.
Watch for: identical "on track" language reused week after week with no specifics.A stale or missing RAID log
If nobody can tell you when the risk register was last updated, risks aren't being actively managed — they're being logged once and forgotten.
Watch for: risks with no owner, no review date, or no change in status for over a month.Key-person dependency
One engineer, one analyst, one vendor contact who's the only person who understands a critical piece. Their laptop, their leave request, or their resignation becomes a single point of project failure.
Watch for: "only Raj knows how that integration works" said more than once.Requirements that keep "evolving" without change control
Requirements should firm up as a project progresses. If they're still shifting materially close to delivery — and nobody's tracking it as scope change — the team is building against a moving target with no visibility into the cost of that movement.
Watch for: the phrase "we'll just adjust as we go" replacing a documented baseline.Silence in meetings
A team that raises no concerns, asks no hard questions, and agrees with every plan isn't necessarily aligned — it may be a team that's stopped feeling safe enough to flag problems.
Watch for: concerns surfacing in 1:1s that were never raised in the group setting.Vendor delays surfaced only at the milestone
Third-party dependencies that are "on track" every week until the delivery date arrives and suddenly aren't. This usually means the vendor relationship has no early-warning checkpoint built in.
Watch for: vendor updates that only ever restate the original delivery date, with no interim proof of progress.Nobody can define what success looks like
If you ask three stakeholders how they'll know the project succeeded and get three different answers, the project doesn't have a scope problem — it has an alignment problem that scope issues are just a symptom of.
Watch for: success criteria that exist only in the original charter and haven't been revisited since.Schedule optimism — "we'll catch up later"
Early delays get waved off because there's "buffer later in the plan." That buffer rarely survives contact with the next delay, and by the final phase there's no slack left to absorb anything.
Watch for: a project plan where every slipped task borrows time from a phase that hasn't started yet.Not avoid these situations entirely — every project runs into some of them. The difference is treating each flag as a prompt to ask a direct question immediately, rather than letting it become the new normal. A red flag caught in week 3 is a conversation. The same flag caught in week 12 is a crisis.
These ten are a starting point, not the full list. The free PM Red Flags Guide goes deeper — 25 early-warning signs across scope, schedule, team health, and stakeholder management, built from real project patterns rather than textbook theory.