How TaskRely's Performance Scoring Engine Works

Most "performance tracking" in project tools is really activity tracking - who logged in, who clicked the most. TaskRely scores the actual work instead, built entirely from data your team already generates just by using the board normally. Nothing about the formula is hidden - here's exactly how the number comes together.

The four inputs

Every member's monthly score is built from up to four pieces:

• Deadline adherence - 35%. Of the tasks you completed this month that had a due date, what share finished on time - measured against the deadline actually in effect, not necessarily the original one.
• Volume - 30%. Completed work, weighted by each task's size and priority, measured against your organization's own average that month rather than a fixed external target. It's capped at 100 - finishing far more than everyone else doesn't push this category past full marks.
• Responsiveness - 25%. How quickly you respond to things that actually need a response - an assignment, a mention, a comment aimed at you - counted only during time you were clocked in. Respond within 15 minutes and that one scores full marks; past 4 hours, it scores zero; anywhere between is a straight line down. Leave something unanswered for more than 48 hours and it scores zero too, rather than being quietly left out - ignoring a mention is never the safer option.
• Manager score - 10%. A plain 0-10 number plus a note, entered monthly by your manager or an org admin - a small, deliberate human check sitting on top of three otherwise fully automated categories.

A category with no real activity that month is left out of the average entirely, not counted as a zero - a quiet month, or a brand-new hire with nothing to measure yet, doesn't get unfairly dragged down for categories with nothing in them.

The fairness rules

A raw "did it finish on time" measurement is unfair in a bunch of predictable ways, so the engine specifically corrects for these:

• Blocked time doesn't count against you. Time a task spent flagged as blocked gets added back onto its deadline - waiting on someone else isn't your fault.
• Only approved deadline changes move the target. A quietly edited due date, never marked approved, doesn't get to help or hurt your score either way.
• Cancelled tasks don't earn or lose volume credit - nothing was actually delivered. If a manager or admin marks the cancellation an avoidable failure, it still counts as a missed deadline, just never toward volume.
• Credit goes to whoever held the task longest, not whoever happened to be assigned the moment it closed - a last-minute reassignment can't hand someone else's work to its final owner.
• A task's size locks in at the moment it's completed, not whatever it's bumped to afterward - there's no inflating volume credit retroactively.
• Approved leave excludes that time from responsiveness entirely - see leave tracking for how that connects.

When there's not enough to go on

Every score carries a confidence level alongside it - high when most categories had real data, low when more than half the weight behind it is missing, and none when there was nothing to measure at all, in which case there simply isn't a score that month. A number built on almost nothing is worse than no number, so TaskRely says so plainly instead of quietly generating one anyway.

Who can see a score

You can always see your own. Your manager can see yours. An org admin can see everyone's. A teammate on the same project as you - even a close one - can't see it at all unless they're one of those two things. This is enforced where the data lives, not just hidden in the interface. See organization roles for the full picture of who's who.

Where it shows up

The Performance page shows the full breakdown per person - the overall score, each of the four categories on their own, and a trend across recent months - never just one flattened number with nothing behind it. It's also the foundation formal review cycles are built on, where a period's scores get locked in and published to the employee once a cycle is finalized.