Warning signs a project is in trouble before the status turns red

The earliest warning signs a project is in trouble are changes in how people talk about the work, not changes in the numbers. Updates that used to carry a date start saying "still working on it". Decisions that took one meeting now take three. The sponsor stops calling it "our project". By the time the schedule or budget turns red, those signals have often been visible for a while.

Status reports are built from the same updates that are going vague, so a report can stay green for a long time while the people closest to the work already know it is slipping. Look for changes in how people report progress and ask one direct question about each signal every week.

Contents

• Why is status still green?
• Which warning signs matter most?
• What should you check weekly?
• How should you respond?
• Which warning signs arrive late?
• Questions about project warning signs

Why is status still green?

A project can look green because most status is self-reported and lags behind the work. A task shows "in progress" until someone changes it, a percent-complete figure is a guess, and the traffic light on a report is usually set by thresholds that only trip once a deadline or a budget line has actually moved. Nothing in that chain measures confidence, and confidence is what drops first.

A thread on r/projectmanagement asked project managers for the earliest sign of trouble before it reaches the dashboard. One of the most upvoted answers said that managing from a dashboard means reacting late: the dashboard only knows what people have told it. Another reply, half joking, said the first warning sign is a dashboard that shows everything green.

A project manager who ran enterprise reporting described an earlier warning system in the same thread. They said stakeholders usually set the amber and red thresholds for cost and schedule. They kept a second, private set a few points tighter, visible only to project managers, so they would see an indicator flip before management did. The point was to see the change first, while it could still be fixed quietly.

Which warning signs matter most?

Look for vague updates, work nobody can show, reopened decisions and changes in sponsor engagement. Project managers in the thread described these alongside the other signals below. No single sign proves failure; investigate when two or three appear together, or one keeps repeating.

1. Updates lose their dates

An update that used to say "done Thursday" now says "making progress" or "still working through it". The next week, the same words appear again.

Several project managers in the thread named this as the first thing they notice. One said they ignored it for years because nothing was technically late, and now treat a second vague update in a row as a reason to go and ask directly.

The question to ask: "If you had to put a date on it today, what would it be?"

2. Nobody shows the work

People confirm that progress is happening, but nobody links a file, a draft, a screenshot or a commit. A real piece of work in progress is easy to show. When the answer to "can I see it?" is always "soon", the work may not exist in the state people are describing.

The question to ask: "Can you share where it is now, even if it is rough?"

3. Settled decisions get reopened

A decision that used to take one conversation now takes two or three. Things agreed last month come back for another round.

One commenter described this as the moment the project's single source of truth has fractured: everyone is working from a slightly different version of what was agreed, while the plan still measures progress against the original.

The question to ask: "Which decisions did we revisit this week, and why?"

4. The sponsor's language changes

Watch for a sponsor who stops discussing benefits and starts distancing themselves from the project. One of the top answers in the thread described the shift: when things are going well, the executive sponsor talks about the benefits. When they are uncertain, it becomes "the project". When they have disengaged and are looking for someone to blame, it becomes "your project".

Others put the same signal more plainly: senior stakeholders get pulled onto other problems, replies slow down, and steering meetings get moved or skipped.

The question to ask: "When did the sponsor last make a decision about this, and what was it?"

5. Bad news moves to private messages

People stop raising problems in the group meeting and start mentioning them to you one to one. That shift means they have lost confidence that the plan is real but do not want to say so on the record. It is one of the most reliable signals because it is a behaviour change, and it rarely happens without a reason.

The question to ask: "What are you worried about that you have not said in the team meeting?"

6. Small urgent requests keep arriving

Different teams each come to you with "just one small urgent thing", and then another. Each request looks harmless. Together they usually mean the real order of work has changed and nobody has said so out loud. One aerospace project manager in the thread called this the point where you brace for impact, unless the organisation is good at saying no.

The question to ask: "If we do all of these, what moves out of this month?"

7. The team doubts what was promised

The team quietly doubts it can deliver the scope, date or price promised to the client. That doubt may first surface as a joke.

One reply in the thread put it as the team doubting they can deliver what sales sold the client, and it was one of the most upvoted answers. If the team does not believe the plan, it will not survive contact with the work.

The question to ask: "On a scale of one to five, how confident are you in this date?" Ask it privately and listen for the pause.

8. Nobody can say what done looks like

Ask three people on the project what problem it solves and what "finished" means, and you get three different answers. Several replies said this is the earliest sign of all, because it exists before any work starts. Others named a close cousin: nobody can explain the critical path, the chain of work that decides the end date.

The question to ask: "What has to be true for us to call this done?"

9. The list of assumptions is not getting shorter

Early in a project, the list of open dependencies and assumptions should shrink week by week as questions get answered. If it stays the same length, or grows, the project is still discovering what it is. That is fine in week two and a warning in week ten.

The question to ask: "Which assumption did we close this week?"

10. The steady people start to bicker

Every team has someone who complains. The signal is when your calm, reliable people get pulled into petty arguments over small things. One commenter said that when the steady ones start sniping, it is about to get bigger. Friction rises when people feel the plan is not working and do not have a safe way to say it.

The question to ask: "What is making this week harder than it should be?"

What should you check weekly?

Review updates, open work, reopened decisions, sponsor engagement, urgent requests and unresolved assumptions. A short weekly pass catches these signals while they are still changes in tone, before they reach a report. Look at the same things at the same time each week so you can notice changes.

• Read the updates. Look for any update that had a date last week and does not this week, or repeats last week's words.
• Open the work. Pick two tasks marked in progress and look at the actual file, draft or comment thread behind them.
• Count reopened decisions. Note any decision that came back for another discussion. One is normal; a pattern is not.
• Check the sponsor. When did they last reply, attend or decide? Listen to whose project they say it is.
• Count the urgent extras. List the unplanned requests that arrived and what they displaced.
• Look at the assumptions list. Did anything get closed?
• Talk informally. One project manager in the thread spends 30 minutes every morning walking the floor, in person or online, talking to people outside formal meetings. Even once a week, a conversation with no agenda surfaces what the meeting does not.

For a small project the whole pass is short. Write down what you found, even if it is "nothing changed", so that next week you have something to compare against. Use a concise weekly reporting format to share what you found.

How should you respond?

Speak privately with the person closest to the work that week. Name the change you noticed and ask what is causing it. A warning sign is cheapest to address before it needs a steering meeting.

• Ask privately. Name what you noticed: "Your last two updates did not have a date. What is going on?" Most people will tell you if they trust that bad news will not be punished.
• Bring evidence. If someone is reluctant, point to the specific thing: a task described as nearly complete that clearly is not, or a decision that came back three times.
• Record the risk. Log it as something to watch, not an escalation. One project manager in the thread described telling the person it was being recorded as a risk to monitor. That keeps the conversation safe for them and gives the project manager a dated record if it grows.
• Share the status. Ask for the update again in the group meeting. A status stated in front of peers is harder to keep vague.
• Reward early warnings. People go quiet because they learned somewhere that bringing problems costs them. The person who raises an early warning should be visibly better off for it, every time.

If the signals have already turned into a stall, with work stopped and nobody quite sure why, the problem is different. A short plan for a stalled project is the next step, and it does not need a meeting to start.

Which warning signs arrive late?

Missed milestones, budget overruns, resignations and client escalations are late signs of a failing project. By then you are recovering, not preventing. They are worth tracking because they confirm what the early signs suggested, but a project that only watches these will always find out last.

There is one useful late signal that is easy to miss: the first missed deadline on an action item. One reply in the thread suggested calling it out the first time it happens, because someone who keeps missing small commitments is often stuck on a bigger problem they have not raised.

If you want the numbers on how often projects run late or over budget, the research on project outcomes page collects the published research. The pattern behind most of it is the same: the information existed early and did not travel.

A project tool helps with the second signal more than any other, because it puts the work itself next to the status. In Breeze, for example, each task holds its comments, files and the time logged against it, so "can I see it?" is usually answered without asking. No tool catches a sponsor drifting or a team losing faith, though. That still takes a weekly conversation.

What is the one habit to keep?

Ask about the second vague update rather than letting it pass. A project that goes red has often been telling someone for a while, in words rather than numbers. A short weekly look at those words, and a direct conversation when they change, does more than any extra report.

Questions about project warning signs

What is the earliest sign a project is in trouble?

The earliest sign is usually a change in how people talk about the work: updates that lose their dates, decisions that get reopened, or a sponsor who stops engaging. These tend to appear before the schedule or budget moves, because status reports are built from the same updates that are going vague.

Why do status reports stay green when a project is failing?

Status reports stay green because most status is self-reported and only changes when a deadline or budget line has actually moved. Nothing in a typical report measures confidence, and confidence drops first. Reading the updates themselves, rather than the traffic lights, catches the change earlier.

How often should you check for project warning signs?

Check for project warning signs once a week, at the same time, looking at the same things. Most early signals are changes, so you need last week's picture to notice them. A short pass through updates, open work, reopened decisions and the sponsor's engagement is enough for a small project.

Written by Lucas

Lucas writes content at Breeze and specializes in project management, team collaboration, and practical workflow advice. He helps small teams and growing businesses plan projects, track progress, and keep work organized by sharing clear, actionable guides.