Skip to main content

How to verify project status: a practical checklist

A reported status is a claim. Verifying it means comparing that claim with the work itself. This checklist shows how to do it by hand for any project, using the data already in your teams' tools.

By the Tarivra team · · 8 min read

Why verify status at all

Most status reports are a person's judgment, written at a point in time. They are useful, but they lean optimistic and they lag the work. When a project turns Red close to its deadline after months of Green, the evidence was almost always in the work weeks earlier. That is a watermelon project.

Verifying status does not mean distrusting teams. It means asking the same few questions of every project and answering them from the work, so that a Green means the same thing everywhere and problems surface while there is still time to act.

Before you start

  • Define the scope. Decide which items belong to the project: an epic, a label, a parent item or a set of boards. Everything that rolls up to it counts.
  • Note the target date and the reported status. You are checking one against the other.
  • Map each tool's statuses to To do, In progress and Done. Teams name their states differently; the checks only need these three.
  • Pick a window. Four to six weeks of history is usually enough to see a trend without old data drowning it.

The seven checks

Run each check, note whether it raises a flag, then compare the flags with the reported status. The thresholds below are starting points; adjust them to your teams.

1. Schedule

Is the work finishing fast enough to make the target date?

How to check:
Count the items not yet done. Divide by the number finished per week over your window. That is the weeks of work left at the current pace. Compare it with the weeks left before the date.
Red flag:
The work left needs more weeks than remain.

2. Scope growth

How much work was added after the start?

How to check:
Compare the number of items in scope today with the number at the start, or at the last baseline.
Red flag:
Scope keeps growing week after week while the date stays the same.

3. Throughput

Is the team finishing work at a steady pace?

How to check:
Count the items moved to Done in each week of your window and look at the trend.
Red flag:
The weekly count is falling, or swings so much that no forecast holds.

4. Overdue work

How much is past its due date?

How to check:
Count open items whose due date has passed, as a share of all open items.
Red flag:
The share is growing, or includes items on the critical path.

5. Blocked work

How much is flagged or marked blocked?

How to check:
Count items flagged, labeled or in a Blocked state, and note how long each has been blocked.
Red flag:
Blocked items are piling up, or any has been blocked for more than a week.

6. Stale work

Is in-progress work sitting untouched?

How to check:
Find items In progress that have not been updated recently, for example in the last 14 days.
Red flag:
A large share of in-progress work is stale. Work that nobody touches is not moving.

7. Change health

Did recent changes fail or cause incidents?

How to check:
If the project ships through change management, look at its recent change requests: which failed, were rolled back or caused incidents, and which high-risk changes are still waiting for approval.
Red flag:
Failed changes or incidents, or high-risk changes stuck in approval close to a release.

Compare the checks with the reported status

Now put the two side by side.

  • Reported Green, no flags: the status is supported by the work.
  • Reported Green, one flag: worth watching. Note it and look again next week.
  • Reported Green, two or more flags: the status and the work disagree. Ask the team what the numbers mean before the next report, not after the deadline.
  • Reported Amber or Red, with flags: an honest status. Help the team with what they need.

The aim is a conversation based on the same facts, not a verdict. Sometimes there is a good reason behind a flag, such as a planned pause or scope that was added on purpose with a new date agreed.

Make it a habit

  • Run the same checks every week, for every project, so results can be compared.
  • Keep the history. The trend of each check matters more than any single reading.
  • Record what leaders decide when a project is off track, who owns the action, and follow it until it is done.
  • Share the checks with teams. When everyone knows what Green has to show, statuses become more honest on their own.

Doing it by hand, and doing it at scale

For one project in one tool, this checklist takes an hour or two a week with exports and a spreadsheet. Across a portfolio of programs spread over Jira, Azure DevOps, ServiceNow, GitHub and GitLab, it takes far longer, and the results are out of date by the time they are shared.

Tarivra runs these checks automatically. It reads the work in each connected tool every 15 minutes, compares it with the status each team reports and scores how well the two agree, with the evidence behind every flag.

Questions

What does it mean to verify project status?

It means checking the status a team reports against the work itself: how much is done, how fast work is finishing, how much scope was added, and what is overdue, blocked or untouched.

How often should project status be verified?

Weekly is a good rhythm for most programs. The trend over several weeks says more than any single check.

Which tools hold the evidence?

Wherever the work is tracked: usually Jira, Azure DevOps, GitHub or GitLab for delivery work, and ServiceNow for changes and incidents.

What if the checks and the reported status disagree?

Ask the team what the numbers mean. There may be a good reason, such as a planned pause. If not, agree on what changes, record the decision and follow it to done.