To track project progress, compare what has actually been finished and checked with what the plan said should be finished by now, using a few simple measures such as verified tasks, milestones hit, overdue work and open blockers. The goal is not a perfect number. It is an early, honest answer to one question: are we where we expected to be, and if not, why?
Many teams think they are tracking progress when they are really tracking activity. People are busy, cards are moving, messages are flying, and the project still lands two weeks late. This guide covers seven methods that measure real progress, how to choose between them, and a short weekly routine that pulls them together. For the basics of setting up a project tracker, see what project tracking is.
Activity vs progress
Before choosing a method, it helps to separate three things that often get counted as the same:
| What you see | What it really tells you | Is it progress? |
|---|---|---|
| A task is "in progress" | Someone has started | Not yet |
| A task is marked "done" | The owner believes it's finished | Probably, but unconfirmed |
| A task is verified | Someone else checked it against the brief | Yes |
A project with forty tasks "in progress" and none verified has made very little measurable progress, however hard everyone is working. The methods below all lean toward counting finished, checked work.
The 7 methods
1. Count verified tasks against the plan
List every task in the project. Each week, count how many are verified and compare that with how many you planned to have finished by this point. If you planned to close 12 tasks by the end of week three and 7 are verified, you know you're behind, and by how much.
This works best when tasks are roughly similar in size. If one task is "pour the foundation" and another is "order paint samples," counting them equally will mislead you. Split large tasks until they are a few days of work each.
2. Track milestones by date
A milestone is a checkpoint the rest of the project depends on, such as "permit approved," "content signed off by client" or "equipment delivered." Write down five to eight milestones with target dates. At each review, mark each one as hit, at risk or missed.
Milestones are excellent for talking to clients and owners, because they're easy to understand. Their weakness is that they can hide trouble between checkpoints, so pair them with one of the task-level methods.
3. Watch the overdue list
Sort open tasks by due date and look only at the ones past due. The length of that list, and whether it is growing or shrinking week to week, is one of the simplest progress signals there is. A steady trickle of overdue tasks is normal. A list that grows every week means the plan and reality have parted ways.
4. Measure how long work sits in each stage
On a board, look at how long cards stay in each column. If tasks normally spend two days "in progress" but now wait five days in "ready for review," the bottleneck is the review step, not the people doing the work. You don't need software for this; a date written on the card when it moves is enough.
5. Keep a blocker log
A blocker is anything stopping a task from moving: a missing part, an unanswered client email, a decision nobody has made. Record each one on the task with who needs to act and by when. Count open blockers at each review. Projects rarely slip because people are slow. They slip because blocked work waits quietly.
6. Rate each workstream: on track, at risk, off track
Once a week, the owner of each part of the project gives it one of three ratings, with one sentence explaining why. "At risk: tile delivery moved to the 14th, which leaves two days for installation." This forces a judgment instead of a list of activities, and it's quick to scan across several projects.
7. Read the daily work log
A daily log is a short, written note from each person about what they did and what's stuck. It doesn't measure progress by itself, but it explains the numbers. When the overdue list jumps, the logs usually show why days before anyone raises it. Our guide to the daily work diary habit shows how to keep this to about a minute a day.
Which methods suit which project?
You don't need all seven. Pick two or three that match the kind of work.
| Project type | Best methods | Why |
|---|---|---|
| Client project with fixed delivery date | Milestones, verified tasks, on track/at risk ratings | Clear dates and easy client reporting |
| Field or site work | Verified tasks with proof, overdue list, blocker log | Work happens away from the office and must be checked |
| Internal improvement project | Overdue list, daily logs | Often competes with daily work, so slippage is common |
| Ongoing work with steady flow | Stage aging, overdue list | Spots bottlenecks rather than end dates |
| Several small projects at once | On track/at risk ratings, overdue list | Quick to scan across many projects |
How to track project progress in 15 minutes a week
Pull the methods together into one short routine. A project owner can do this alone, then share the result.
- Count verified tasks and compare with the plan for this week.
- Check milestones and mark each as hit, at risk or missed.
- Read the overdue list. For each item, decide: new date, new owner, or split it.
- Review open blockers and confirm who is clearing each one.
- Skim the week's daily logs for anything the numbers didn't explain.
- Write a three-line summary: status, biggest risk, decision needed.
Send the summary to whoever needs it. If you run a team review afterward, the summary becomes the agenda. Our guide to project tracking for teams covers the roles and check-ins around this routine.
If the same tasks slip every week, moving the due dates again isn't tracking. Cut scope, add help or change the order, and record the decision.
Common mistakes when tracking progress
- Counting started work. "In progress" feels like progress. It isn't until it's done and checked.
- Using one big percentage. A single "the project is mostly done" figure hides which part is stuck. Break it down by workstream or milestone.
- Measuring too much. If you need an afternoon to produce a status report, you'll stop producing it.
- Relying on memory in meetings. People round up. Look at the tracker, not at how everyone feels.
- Ignoring follow-ups. Many delays are tasks waiting on someone outside the team. Put a follow-up date on each one; see follow-ups that never slip.
- Never resetting the baseline. If scope changes, update the plan so you're comparing against the real target.
When simple tracking is enough
Be honest about the size of the project. A two-week job with three people may need nothing more than a shared list sorted by due date and a five-minute chat on Monday. Methods are there to give you early warning. If the project is small enough that you'd notice a problem anyway, keep it light. For tracking individual tasks rather than whole projects, see how to track tasks.
Where TaskFia fits
TaskFia supports several of these methods directly. Tasks carry an owner, due date and priority and move across Kanban boards, so overdue work is easy to spot. Finished tasks are submitted with proof and approved by a verifier, so you can count verified work rather than "done" claims. Team members keep a daily diary linked to their tasks, activity monitoring shows tasks completed, verified and overdue per person, and admins receive a weekly summary by email. Basic plans and above add task dependencies and advanced filters; Business plans and above add team dashboards and advanced reports. TaskFia does not include Gantt charts or a timeline view. See project tracking in TaskFia.
Related guides. When work runs across several steps and people, project tracking software shows where each project stands. Compare what a project management platform should include for a small team. Weighing options? Here is how to choose a project management app for a small team. New to the topic? Start with the basics of task management. See how task management software built around proof of work keeps every task on the record.
Frequently asked questions
What is the best way to track project progress?
Compare verified, finished tasks and milestones against the plan each week, and watch the overdue list and open blockers. Two or three methods used consistently beat seven used occasionally.
How do you measure the progress of a project?
Count what has been finished and checked against what you planned to have finished by now, and track whether key milestones were hit on their dates. Add on track, at risk or off track ratings for a quick overall view.
How often should project progress be reviewed?
Weekly suits most small-team projects. Short, fast projects may need a quick check every couple of days; long, steady ones can be reviewed every week or two with milestone sign-offs.
What is the difference between a milestone and a task?
A task is a piece of work one person completes. A milestone is a checkpoint, usually the completion of a group of tasks, that the rest of the project depends on.
Can I track project progress in a spreadsheet?
Yes. A row per task with owner, due date, status and a verified column covers most of these methods. It gets harder to keep current as the project and team grow.
The bottom line
Real progress is finished work that someone has checked, measured against what you expected by now. Pick two or three methods that fit the project, review them in fifteen minutes each week, and act on what they show. The earlier you see a slip, the cheaper it is to fix.