📖 How to use this template

A delivery-performance scorecard: it scores every task on whether it was finished before its due date, then totals that per person. The sample is a team running an event, so you can watch the scoring work before you put your own work in.

1. Duplicate this project into your own organization (dropdown next to the project name, then Duplicate)
2. Replace the sample tasks with your own work, giving every one a due date and at least one assignee
3. Keep to one assignee per task where you can, so the totals stay comparable
4. Let the period run its course before reading the charts. This scores finished work, not a plan
5. Delete the sample tasks once you have a period of your own to look at

How the score works

KPI Point is calculated for you on every task:

A task with no due date is invisible to the scorecard. That is the main thing to watch as you add your own work.

The score is also multiplied by the number of assignees, so a task shared between two people counts double for both of them. Co-assigned work swings a total further than solo work does, in either direction, which is worth remembering before you read anyone's total as a judgement.

What the charts show

The charts live in the KPI Performance document, with notes on how to read each one. They cover KPI Point per person, task count by tag, and task count by status split by person. All three read live from whatever is in the project.

About the sample data

Every sample task was finished ahead of its due date and nothing is overdue, so the sample scores positive throughout. It shows you the mechanics, not a team in trouble. The interesting shape comes from your own data: work piling up in one status, or a total dragged down by dates that were never realistic to begin with.

The statuses

To-do → In progress → Review → Completed → Approved.

Both Completed and Approved count as finished work, so anything in either is scored on whether it beat its due date.