Key takeaways
- Rules match a domain, app or keyword and assign a category
- The category is stored when the session is written, so history stays stable
- Productivity percent is productive time divided by active time, guarded against zero
- Scores describe patterns; they are not a performance verdict
How rules work
Each organization defines rules that pair a pattern with a match type and a category: productive, neutral or unproductive. When a session is recorded, the best matching enabled rule decides its category.
Why the category is stored
Saving the category on the session means last quarter's report does not change when you edit a rule today. Re-classifying history is possible, but only as an explicit job.
The arithmetic
Productivity percent is productive time divided by active time, times 100. If active time is zero the result is zero, never an error value or infinity.
Where it misleads
A designer in a design tool and a developer reading documentation can both look unproductive under crude rules. A score tells you where to look. It cannot tell you why, so use it to ask questions, not to rank people.