How to measure employee productivity in knowledge work
To measure employee productivity, divide output by input: what a person or team delivers against the time they spend. In knowledge work, output is hard to count, so the practical approach pairs outcome measures (delivered work, quality) with time-use measures (focus time, core-tool share, idle time) and never relies on activity alone.
This guide is for managers, team leads and HR teams. It covers the formula with a worked example, why activity metrics mislead, 8 employee productivity metrics that work, how the measures change by role, how to track productivity fairly, and how Intelogos measures it. To put the numbers into a weekly or monthly report, use the free employee productivity report template.
Table of Contents
- What is employee productivity, and how do you calculate it?
- Why do activity metrics mislead?
- Which 8 employee productivity metrics work in knowledge work?
- How do you measure productivity by role?
- How do you track productivity fairly?
- How does Intelogos measure productivity?
- Frequently Asked Questions
What is employee productivity, and how do you calculate it?
Employee productivity is the output a person or team produces for each unit of input, usually an hour worked. The formula is productivity = output ÷ input, and the result only means something when you compare it with the same measure over time, or with people doing the same work.
It's the same idea the US Bureau of Labor Statistics uses for the whole economy: its labor productivity measures compare output with hours worked. Nonfarm business labor productivity rose at an annual rate of 1.4% in the second quarter of 2026 (BLS, released September 3, 2026). Inside a company, the hard part is choosing the output, because it depends on the job:
- Support: tickets resolved.
- Finance: invoices processed or accounts reconciled.
- Engineering: changes shipped to customers.
- The whole company: revenue per employee, annual revenue ÷ average headcount. For example, $12,000,000 ÷ 80 employees = $150,000 per employee. It's useful for tracking a business over the years, but it says nothing about any one person.
A worked example
A support agent resolves 320 tickets in a month and works 160 hours.
- Raw productivity: 320 ÷ 160 = 2 tickets per hour.
- Adjust for quality: 40 of those tickets were reopened because the first answer didn't solve the problem. The output that stayed solved is 320 - 40 = 280 tickets, so productivity is 280 ÷ 160 = 1.75 tickets per hour.
- Compare like with like: the next month, the same agent resolves 300 tickets in 150 hours and 15 are reopened. Productivity is (300 - 15) ÷ 150 = 285 ÷ 150 = 1.9 tickets per hour, an improvement on 1.75, even though fewer tickets were closed.
Two lessons follow. Count output that meets the quality bar, not just volume. And compare a number with the same person's or team's earlier periods, or with others in the same role: a support ticket and a code change aren't the same unit, so tickets per hour can't be compared with an engineer's output.
Why do activity metrics mislead?
Activity metrics count inputs, not results. Keystrokes, mouse movement and hours online show that a computer was in use, not that useful work got done, and they penalize the parts of knowledge work that happen away from the keyboard.
- Keystrokes measure typing. A careful two-paragraph decision memo takes fewer keystrokes than pasting text between documents all afternoon.
- Mouse movement is easy to fake. A mouse jiggler, a device or app that moves the pointer, produces steady input with no work behind it.
- Hours online reward presence. Someone who finishes the work in six focused hours looks worse than someone who stays online for ten.
- Activity falls during real work. Calls, reading, reviewing and thinking produce little input, so roles heavy in them look less "active".
People also learn to optimize whatever they're measured on. Set a target for activity and you get more activity, not more work.
Intelogos records only whether keyboard or mouse input happened, and even so its help center describes Activity of 20 to 50% as typical and healthy for most jobs. It also notes that activity near 90 to 100% for a full 8-hour day is humanly very difficult, and can be a sign that an auto-clicker or mouse jiggler is generating the input (Activity KPI). Use activity to explain a pattern, never to rank people.
Which 8 employee productivity metrics work in knowledge work?
The metrics that work combine what was delivered (outcomes and quality) with how working time was used (focus, core tools, idle time and hours). Pick two or three outcome measures and two or three time-use measures for each role, not all eight at once.
| Metric | What it measures | How to collect it |
|---|---|---|
| Goal completion | The share of agreed goals or deliverables completed on time in the period | Goals agreed at the start of the period, checked in a review or a project tracker |
| Output per hour worked | Units of finished work divided by hours worked, such as tickets or invoices per hour | Counts from the system where the work is done, divided by hours from time records |
| Quality | Rework, reopened tickets, error or adjustment rates, revision rounds, customer satisfaction | Quality reviews, the help desk or issue tracker, customer surveys |
| Cycle time | How long a unit of work takes from start to finish | Start and finish dates in the issue tracker or help desk |
| Focus time | Hours spent in uninterrupted blocks of core work, for example 60 minutes or more | Meeting-free blocks in calendars, and app usage data showing long stretches in core tools |
| Core-tool share | The share of working time spent in the tools where the role's core work happens | App and website usage data, with tools sorted into work and non-work categories for each role |
| Idle time | The share of working hours with no keyboard or mouse input | Work-time data with an idle threshold, read alongside meetings and calls |
| Hours against expected | Time worked compared with the agreed schedule, including after-hours work | Time records or work-time data compared with each person's schedule |
The value is in reading them together:
- Output per hour up, quality down: people may be rushing to hit a number.
- Hours up, focus time down: meetings and interruptions are crowding out the core work.
- Long hours, flat output: look for overload, unclear priorities or a blocker before anything else; see the signs of team burnout.
- Low core-tool share across a whole team: check how tools are categorized before you assume a behavior problem. A tool nobody has categorized yet looks like non-work time.
How do you measure productivity by role?
Use the same formula, but change the output and the core tools for each role. A support agent's core work happens in the help desk and team chat; an engineer's happens in the code editor and code repository. Measure each role against its own tools and outcomes, never against another role's.
| Role | Outcome measures | Core tools (illustrative categories) | Watch out for |
|---|---|---|---|
| Operations | Orders or requests processed, service levels met, error rate | Order management or operations system, spreadsheets, scheduling and logistics tools | Email and chat are often core coordination work here, not a distraction |
| Customer support | Tickets resolved, first-contact resolution, reopen rate, customer satisfaction | Help desk, knowledge base, team chat | Calls lower activity without lowering output |
| Finance | Days to close the month, reconciliations completed, invoice processing time, adjustments after close | Accounting system or ERP, spreadsheets, banking portals | Work peaks at month end, so compare the same point in the cycle |
| Engineering | Changes shipped, cycle time from first commit to release, defects found after release | Code editor, code repository and review tools, terminal, issue tracker | Design, review and thinking time; never count lines of code |
In practice, that means sorting tools by role: the same team chat app can be core work for support and a supporting tool for engineering. Intelogos handles this with importance categories set per department, described below.
How do you track productivity fairly?
Tell people what you measure and why before you start, judge trends over several weeks rather than single days, read every number in context, and use the data to start conversations, not to decide outcomes on its own.
- Give notice first. Say what is measured, what isn't, why and who sees it. Some states, including Connecticut, Delaware, Maine and New York, require employers to give notice before electronic monitoring (employee monitoring laws by state). The free employee monitoring policy kit includes a policy template, an acknowledgment and consent form and a state notice checklist.
- Trends over snapshots. One slow Tuesday means nothing; four weeks of falling output with rising hours means something. Compare a person with their own baseline and with others in the same role.
- Context over raw numbers. Time off, onboarding, a research-heavy project, an incident week or a run of planning meetings all change the numbers. Ask before you conclude.
- Team before individual. Start with team-level patterns, and look at individual detail when a trend or a specific concern gives you a reason.
- Let people see their own data. When employees see the same numbers as their manager, disputes get settled by looking, and people can use the data to protect their own focus time.
- Keep a person in the decision. From July 1, 2027, California's SB 947 bars employers from relying solely on an automated decision system when making a disciplinary or termination decision (California AB 1883, AB 1331 and SB 947 guide). A productivity score should start a conversation, not end one. If you use AI to draft reviews, see our guide to AI for performance reviews.
This is general information, not legal advice. Laws vary by location and change often; consult your own counsel before acting on it.
For remote and hybrid teams, see how to know if remote employees are working. If paid time regularly isn't being worked, the employee time theft guide has a sample policy clause and a fair process.
How does Intelogos measure productivity?
Intelogos measures productivity as the active work time a person spends in their role's work tools, against the time they're expected to work. You decide which tools count as work for each department with importance categories.
Intelogos is a workforce analytics platform that shows how work time is spent across apps and websites, without screenshots or keystroke logging, and lets managers ask questions about it in plain language. Intelogos doesn't take screenshots. Intelogos doesn't record what people type; it records only whether keyboard or mouse input happened.
Importance categories decide what counts as work
Every application and website Intelogos detects is assigned one of four importance categories (importance categories):
- Primary: the core tools where someone is expected to spend most of their work time. The help center recommends only 1 to 3 Primary tools per role.
- Secondary: work-related tools that support the core work, such as communication, meeting, documentation and project management tools.
- Distracting: tools not related to work, such as social media and entertainment sites.
- Neutral: the default for any tool that hasn't been categorized yet.
Primary and Secondary tools together are the "work tools". You set categories for all users first, then override them for departments whose work differs: team chat might be Secondary for most teams and Primary for a support department that lives in it all day, and a video site might be Distracting for most teams and Secondary for a marketing team that produces video. Tools left as Neutral don't count toward Engagement or Productivity, so reviewing them regularly keeps the numbers accurate.
The Productivity KPI
The help center defines Productivity as "the portion of active work minutes spent in primary and secondary tools, out of the total possible time based on how much the user is expected to work" (Productivity KPI):
Productivity = active work minutes in primary and secondary tools ÷ expected work time × 100
A minute counts as active if any second within it had keyboard or mouse input. Someone expected to work 8 hours (480 minutes) who has about 240 active minutes in primary and secondary tools has a Productivity of 240 ÷ 480 = 50%. The help center describes 40 to 60% as strong for most roles and above 60% as exceptional.
Three related KPIs fill in the picture:
- Engagement: the portion of tracked time spent in primary and secondary tools, out of the total tracked time (Engagement KPI).
- Contribution: the total number of active work minutes spent in primary and secondary tools, shown in hours and minutes (Contribution KPI).
- Availability: the portion of the day the user was working, out of the total amount of time they were expected to work (Availability KPI).
An Overall Rating combines Availability, Activity, Engagement and Productivity into one score, with weights you set for everyone, per department or per job title (Overall Rating KPI). Employees can see their own time data, or their full activity and KPIs, depending on an account-wide setting (roles and access).
These KPIs cover the time-use half of productivity. Pair them with the outcome and quality measures from your own systems, and read both as trends. Learn more about employee productivity tracking with Intelogos; plans start at $8 per license per month billed yearly (pricing).
Frequently Asked Questions
How do you calculate employee productivity?
Divide output by input: productivity = output ÷ hours worked. For example, a support agent who resolves 280 tickets that stay solved in 160 hours has a productivity of 280 ÷ 160 = 1.75 tickets per hour. Count output that meets your quality bar where you can, and compare the result with the same person's earlier periods or with others in the same role, never across different roles.
What are good metrics for measuring productivity?
Combine outcome metrics with time-use metrics. Good outcome metrics are goal completion, output per hour worked, quality (rework, errors and reopened work) and cycle time. Good time-use metrics are focus time, core-tool share, idle time and hours worked against expected hours. Avoid keystroke counts, mouse movement and hours online as measures of productivity: they show activity, not results.
How do you track the productivity of an employee?
Agree outcomes for the role, tell the employee what you'll measure and why, then review outcomes alongside work-time patterns on a regular rhythm, such as weekly or monthly. Look at trends over several weeks, read the numbers in context and discuss them with the employee before drawing conclusions. A productivity report template keeps each review consistent with the last.
What is an example of a productivity measure?
Tickets resolved per hour worked is a productivity measure for a support team; reconciliations completed per day suits a finance team, and changes shipped per sprint suits an engineering team. At company level, revenue per employee (annual revenue divided by average headcount) is a common example. In Intelogos, the Productivity KPI measures active work minutes in a role's work tools against expected work time.
Sources
- US Bureau of Labor Statistics, Productivity: labor productivity compares output with hours worked; nonfarm business labor productivity rose at a 1.4% annual rate in the second quarter of 2026 (release of September 3, 2026). Checked October 23, 2026.
- California SB 947 bill text (Chapter 859, Statutes of 2026): Labor Code section 1522(b)(1), no sole reliance on an automated decision system for disciplinary or termination decisions, operative July 1, 2027 (section 1526.7). Checked October 23, 2026.
- State monitoring notice laws: see the statutes linked in employee monitoring laws by state.
Intelogos facts come from our help center (Productivity, Engagement, Contribution, Availability, Activity and Overall Rating KPIs, importance categories, roles and access) and our pricing page.