Description
Current Formula
score = rate * ln(total_requests + 1)
Proposed Formula
score = rate * ln(total_completed + 1)
Problem
Currently, the score calculation uses total assigned requests, not the number of tasks actually completed. This can unintentionally reward officers who were assigned many tasks but completed very few of them.
For example:
- If an officer is assigned 100 tasks
- Completes only 2
- Has a rate of 0.02
With the current formula:
With the proposed formula:
The current implementation inflates the score simply because the officer was assigned many tasks, even if they did not complete them.
Why This Change Matters
Using total_completed instead of total_requests:
- Ensures officers are rewarded based on actual productivity
- Penalizes low completion relative to workload
- Prevents score inflation due to high assignment volume
- Better reflects performance fairness
Expected Impact
- Officers who complete more tasks will benefit appropriately
- Officers assigned many tasks but completing few will no longer receive inflated scores
- Overall ranking will more accurately reflect true output
Credit to @Biruktie for identifying this inconsistency in the scoring formula.
Description
Current Formula
Proposed Formula
Problem
Currently, the score calculation uses total assigned requests, not the number of tasks actually completed. This can unintentionally reward officers who were assigned many tasks but completed very few of them.
For example:
With the current formula:
With the proposed formula:
The current implementation inflates the score simply because the officer was assigned many tasks, even if they did not complete them.
Why This Change Matters
Using
total_completedinstead oftotal_requests:Expected Impact
Credit to @Biruktie for identifying this inconsistency in the scoring formula.