Agiled Docs

Productivity reports help you review delivery health.

Project Status

Use Project Status to review projects by status and overdue count. This report is grouped by project status and does not use date filters.

Open Reports → Productivity → Project Status when you need a current portfolio snapshot. Use it to find overloaded statuses, overdue projects, and projects that need manager review.

Use Project Status for current health, not historical trend analysis. Because it does not use date filters, stale project statuses can distort the snapshot until the underlying projects are cleaned up.

Prepare the Data

Before using productivity reports in a meeting, clean obvious stale records: close completed projects, update paused work to on-hold, assign unowned tasks, and remove or archive test data. Reports are only as accurate as the project and task records underneath them.

Ask project owners to review their active projects before leadership or client meetings. A single stale owner, status, or due date can make the report look more precise than the data really is.

Task Summary

Use Task Summary to review task status, priority, and assignee mix. Use date range when you want to focus on a delivery period.

Task Summary is useful for sprint review, weekly delivery review, or checking whether work is piling up with one assignee or priority.

Use the date range to match the conversation. Weekly planning needs a different view than quarterly delivery cleanup. If the report includes too much history, old completed work can hide current risk.

How to Read Them

Look for too many blocked, overdue, or incomplete items. If a team member has too much work in one status, review assignment and priorities.

Use reports to decide where to inspect the source records. The report can show a pattern, but the project or task page is where you update stale status, missing assignee, due date, priority, or completion data.

Do not use the report as the only review surface. When a number looks wrong, open the filtered project or task list and confirm whether the data issue is status hygiene, missing due dates, old test work, or real delivery risk.

Review Workflow

Start with Project Status to understand the portfolio.
Open Task Summary for the active delivery period.
Switch to table view and sort by status, priority, or assignee fields when available.
Open the matching project or task list.
Update stale statuses and overdue work.
Export the table only after cleaning up obvious stale data.

Before a Delivery Meeting

Filter to the active portfolio, remove test projects, and check whether overdue items are truly late or simply not closed. Bring the report together with the project/task list so owners can update the underlying records during or right after the meeting.

After the meeting, rerun the report with the same filters to confirm cleanup changed the numbers. Export only after stale statuses and ownership issues have been corrected.

Questions to Ask

Which projects have no clear next action?
Which assignees have too many open tasks?
Which high-priority tasks are overdue?
Which blocked tasks have no updated blocker?
Which completed work is still sitting in active status?

Follow Up After Reports

Create cleanup tasks directly from the report review when a project needs owner updates, due-date changes, status cleanup, or scope clarification. Reports should lead to source-record fixes, not just screenshots for the meeting notes.

Project and Task Reports