Streamline task assignment, track progress, and manage team workflows efficiently
✓ Free to download · ✓ Excel 2016+ and Google Sheets · ✓ Custom version in 24h
A workflow is a set of allowed transitions, not a status column. This template records each transition with a timestamp so you can measure where work waits and who it waits on.
The actual columns, with sample rows
| A | B | C | D | E | F | G |
|---|---|---|---|---|---|---|
| 1 | Task | From | To | By | At | Wait (h) |
| 2 | T-118 | Draft | Review | A. Duval | 07-08 14:20 | 6.2 |
| 3 | T-118 | Review | Approved | M. Ferrer | 07-10 09:05 | 42.8 |
| 4 | T-119 | Draft | Review | K. Owens | 07-09 11:40 | 3.1 |
| 5 | T-119 | Review | Rework | M. Ferrer | 07-09 16:15 | 4.6 |
Why each one is written the way it is
=([@At]-MAXIFS(Trans[At],Trans[Task],[@Task],Trans[At],"<"&[@At]))*24
Hours waited in the previous state, computed from the transition log. This is the measurement a status column cannot give you.
=AVERAGEIFS(Trans[Wait (h)],Trans[From],[@State])
Average wait per state. The state with the longest wait is your bottleneck, and it is usually not the one people name.
=COUNTIFS(Trans[To],"Rework")/COUNTIFS(Trans[To],"Approved")
Rework ratio — how often work comes back. Above about 20% the problem is the brief, not the execution.
=INDEX(Trans[To],MATCH(MAX(IF(Trans[Task]=[@Task],Trans[At])),Trans[At],0))
Current state as the most recent transition, so the status can never disagree with the history.
A worked example with real numbers
A marketing team believed content production was slow. The transition log showed drafting taking 6 hours on average and approval taking 43 — one approver, batching reviews to Fridays. Moving to daily review slots cut end-to-end time from nine days to three without anyone drafting faster.
Tab by tab
| Tab | Contents |
|---|---|
| Transitions | Every state change with actor and timestamp. |
| Tasks | Task register with current state derived from transitions. |
| States | Allowed states and the transitions between them. |
| Metrics | Average wait per state and rework ratio. |
| README | The workflow diagram and the rule for logging a transition. |
What is included, and what to look at next
Specific to this workbook, not generic
Because a status tells you where something is; transitions tell you how long it took to get there. Only the second one lets you find the bottleneck.
One row per state change, which for most workflows is three or four rows per task. If that is too much, the workflow probably has too many states.
Add a data-validation rule against the allowed transition list. It will not prevent a determined user, but it catches the typos that make the metrics wrong.
"This task manager has transformed how our team works. The automated workflows and clear task tracking have improved our productivity significantly."