The complete guide to project monitoring

Once the work schedule has been released and the project has started, progress has to be monitored. Delivering on time and on budget means keeping track of what is actually happening rather than what was planned. Monitoring is not administration imposed on the team: it is the mechanism that lets you notice a drift while correcting it is still cheap.

Monitoring is not reporting

Reporting describes the situation to someone else; monitoring changes what the project does next. The distinction matters because it decides what you measure. A monitoring indicator that has never triggered a re-sequencing, a reallocation or a scope decision is a reporting indicator, and it should be moved to the monthly pack rather than looked at every week.

Measuring progress honestly

Progress measured as “percentage of time elapsed” tells you nothing — it advances on its own whether or not anyone works. Measure it as completed effort against planned effort, or by deliverable acceptance. The difference between the two readings is usually the first sign of trouble: effort burning faster than deliverables are accepted means the estimate, not the team, was wrong.

The pair that never lies: spent and remaining

A task reported at 80% is meaningless until you know what is left. Asking for remaining effort rather than percent complete changes the conversation: a contributor who has spent 12 days and still sees 10 days of work has told you the estimate was 15, not 22. Collected task by task, that single figure is the earliest and most reliable warning a project produces.

Comparing against a baseline

Keep a baseline of the approved plan and compare the current state against it. Variance on dates, on effort and on cost gives three independent signals; when they all point the same way, the trend is real and not a measurement artefact. Without a baseline there is no variance, only a plan that quietly rewrites itself to match reality — which is how a project arrives six weeks late having always been “on track”.

What to look at, and how often

A weekly team review handles the operational layer: tasks finished, tasks blocked, remaining effort, next week’s workload. A monthly steering committee handles the decisions the team cannot take alone: budget, scope, risks, milestone dates. Mixing the two produces a meeting that is too long for the team and too detailed for the sponsor.

Acting early, in small steps

Monitoring is only useful if it triggers decisions: re-sequencing tasks, reallocating a resource, reducing scope on a low-value item. Four small corrections spread over a quarter cost far less than one replanning exercise at the end. The projects that fail are rarely the ones that drifted; they are the ones where the drift was visible and nothing followed.

Monitoring in FoxPlan

FoxPlan computes progress from the plan and the logged time, keeps the baseline for variance analysis, and surfaces overloads and slipping tasks directly on the schedule and in the portfolio dashboards. Because the same data feeds the budget and the resource workload, a decision taken on one dimension shows its consequences on the other two immediately.