Skip to content
getgriddy.ai/blog/best-team-status-fields-for-project-trackers
Excel & Sheets

Best Team Status Fields for Project Trackers

A project tracker works better when status fields are simple, unambiguous, and tied to real review decisions. Here's a practical status set most teams can use.

·5 min read

Reviewed by Griddy

Updated for current Excel and Google Sheets workflows, with examples chosen to map back to real spreadsheet tasks rather than abstract formula syntax.

Most project trackers do not fail because they are missing columns. They fail because the status field stops meaning anything.

If every row is labeled Active, In motion, Ongoing, or some other vague status, the sheet becomes hard to scan and even harder to trust.

The simplest status set that works

Most teams can run a useful tracker with these five statuses:

  • Not started
  • In progress
  • Waiting
  • Blocked
  • Done

That is enough to separate work that has not begun, work that is moving, work waiting on someone else, work stuck, and work completed.

A project tracker template becomes much easier to review when each status implies a real next decision.

What each status should mean

StatusWhen to use it
Not startedWork is defined but nobody has begun execution
In progressSomeone is actively working on it
WaitingThe work is paused for an external response, approval, or scheduled event
BlockedProgress cannot continue because something critical is missing
DoneThe work is complete and no more action is required

The important part is not the label itself. The important part is that the team uses the same meaning every time.

Avoid status labels that hide the problem

Weak status labels usually sound busy but say very little:

  • Active
  • Pending
  • Open
  • In motion
  • Monitoring

Those labels can mean three different things depending on who updated the row. That is how trackers become noisy.

If the team cannot act differently based on the status, the label probably is not useful.

Separate status from health

A good tracker often uses two fields:

  • Status for workflow state
  • Health for confidence or risk

Example:

  • Status = In progress
  • Health = At risk

That is much more informative than trying to force one column to express progress, urgency, and risk all at once.

This is especially useful in OKR trackers and larger execution sheets where work can be moving but still look shaky.

Add one optional review status only if you really need it

Some teams need a sixth state like Needs review or Ready for review.

That can be useful when approvals matter, but only add it if review is a real operational step that repeatedly affects timelines. Otherwise it becomes one more label people use inconsistently.

TIP

If you add a status, define the exact rule that moves a row into and out of it. If you cannot define the rule in one sentence, do not add the status.

The status field should drive weekly review

A useful review usually sorts the tracker like this:

  1. Blocked
  2. Waiting
  3. In progress
  4. Not started
  5. Done

That order helps the team talk about risk and stalled work first instead of wasting time admiring completed rows.

It also pairs well with a Gantt chart when timeline planning sits beside the execution tracker.

The Griddy way

Teams often know their status field is bad, but they do not know how to simplify it without losing context.

"Replace these vague project statuses with a cleaner set, split health into a separate column, and flag every blocked item at the top"

Griddy can normalize the labels, restructure the tracker, and make the weekly review easier to run.

Skip the manual work

Describe it. Griddy does it.

Instead of writing this formula yourself, just tell Griddy what you need in plain English. Works in Excel and Google Sheets.

Use this on real templates

Clean up the status field before the tracker gets noisy

Simple, unambiguous status labels make project review easier and keep execution sheets from turning into vague activity logs.

Project Management