How to review a project workload snapshot fairly
A workload snapshot helps a team see the distribution of selected tasks and identify questions about capacity. It is a planning aid rather than a complete assessment of effort or performance.
Start with the right material.
- What you provide
- a loaded task table with displayed assignees and statuses.
- The intended result
- Export open-task counts by assignee without inferring effort or employee performance.
How the workflow works.
Group tasks by their supplied owner and status, keeping due dates and estimates where available. Highlight unassigned work and distinguish missing estimates from a confirmed zero effort.
What to check in the result.
Review the snapshot with the team before reallocating work. Equal task counts do not imply equal workload, and the selected project view may omit other responsibilities.
Import the CSV with a consistent delimiter and inspect text identifiers, dates and amounts before using spreadsheet totals. Keep the original file available while checking any automatic type conversion.
Learn from the worked example.
The downloadable CSV example uses these columns: Assignee, Open tasks, Interpretation. Compare a complete record with the source before sorting, combining or importing your own output.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.