Action, issue and milestone trackers: dates that work
Choose an action, issue, or milestone tracker and calculate overdue days, issue age, and baseline delay using explicit dates and completion-aware formulas.
Use an action tracker for a task someone must complete, an issue log for an existing problem someone must resolve, and a milestone tracker for a dated project outcome. Their date measures differ. A useful register labels the measure instead of calling every number “delay.”
How do you calculate overdue days for open actions?
An action needs an owner, due date, and completion date. With due date in C11, completion date in D11, and review date in B7, use =IF(OR(C11="",D11<>""),0,MAX(0,$B$7-C11)).
An open action due October 5 and reviewed October 12 is 7 calendar days overdue. An action completed October 8 is no longer overdue in this open-action measure. If you need to measure historical completion lateness, compare the actual completion date with the due date separately.
The action item tracker makes missing due dates explicit in its status column. A zero overdue count does not establish that an item is complete.
How is issue age different from days overdue?
Issue age measures time since the problem was opened. Days overdue measures time beyond its target resolution date. An issue opened October 1, targeted for October 10, and still open on October 12 has 11 days of age and 2 days overdue.
If it was resolved October 9, its recorded age stops at 8 days and its days late are zero. Use the resolution date for closed records and the fixed review date for open records. Keep ownership beside the dates so follow-up has a clear destination.
How do baseline, forecast and actual milestone dates relate?
Keep the baseline date separate from the current forecast. Once a milestone is complete, use the actual date as its current finish. Delay is current finish less baseline finish.
| Milestone | Baseline | Forecast | Actual | Current delay |
|---|---|---|---|---|
| Design signed off | October 10 | October 15 | Not complete | 5 days |
| Materials ready | November 1 | October 30 | Not complete | -2 days |
| Survey complete | October 2 | October 3 | October 1 | -1 day |
Positive values mean later than baseline. Negative values mean earlier. The milestone tracker preserves all three input dates rather than overwriting the baseline with the newest forecast.
Which project tracker rules should be agreed first?
Define what counts as completion, who enters closure dates, and whether your dates use calendar or working days. Keep the review date fixed for a report that must be reproducible. Change it deliberately for the next review.
Do not use a recorded completion date as automatic evidence of approval or quality. The date measures workflow timing; the underlying deliverable and acceptance record still matter. For scope changes, keep requested impact separate from approved impact so pending requests do not silently alter the baseline.