Terminology Guide (Productivity UseCase)
Overview
Flowace captures and classifies every hour of an employee's workday into a structured, transparent framework. From the moment an employee starts their day, all time is measured and categorised - automatically where possible, and with user input where context is needed.
At the top level, all time sits within Logged Hours, which breaks into three states: Active (on-screen work detected by the system), Away (off-device time classified by the user), and Idle (inactivity beyond a set threshold). Each of Active and Away further divides into three productivity classifications - Productive, Unproductive, and Neutral - based on how applications and activities are configured by your organisation's admin.
This document is your reference for understanding every metric Flowace reports - what it measures, how it is calculated, and what it looks like in a real workday.
Active Hours and Idle Hours are captured automatically by the system. Away Hours are manually classified by the user via a pop-up prompt on return to their device.
Terms and Definitions
Term | Definition |
|---|---|
Logged Hours | Total time in a day from the employee's first login to their last logout. This is the outermost container for all time in Flowace.Logged Hours = Active Hours + Away Hours + Idle Hours |
Active Hours | Time spent by a user actively working on their laptop or desktop. The title window and URL of every application visited is captured automatically.Active Hours = Productive (Active) + Unproductive (Active) + Neutral (Active) |
Away Hours | Time during which the user is away from their device - such as meetings, trainings, or breaks. The user manually classifies the activity type via a system pop-up on return.Away Hours = Productive (Away) + Unproductive (Away) + Neutral (Away) |
Idle Hours | Time spent idle on the system. If there is no mouse or keyboard input for 3 minutes (or as per the configured threshold), the user is automatically marked as idle. |
Productive Hours (Active) | Active screen time on applications or websites labelled as Productive by the Admin (e.g. Outlook, MS Excel, internal tools). Auto-captured. |
Unproductive Hours (Active) | Active screen time on applications or websites labelled as Unproductive by the Admin (e.g. social media, entertainment sites). Auto-captured. |
Neutral Hours (Active) | Active screen time on applications or websites not yet configured or labelled in the system - neither Productive nor Unproductive. Auto-captured. |
Productive Hours (Away) | Away-time activity manually classified by the user and configured as Productive by the Admin (e.g. client meetings, trainings). |
Unproductive Hours (Away) | Away-time activity manually classified by the user and configured as Unproductive by the Admin (e.g. lunch breaks, bio breaks, personal errands). |
Neutral Hours (Away) | Away-time activity manually classified by the user and configured as Neutral by the Admin - activities that are neither productive nor unproductive. |
Productive Hours | Total productive time across both active and away states.Productive Hours = Productive (Active) + Productive (Away) |
Unproductive Hours | Total unproductive time across both active and away states.Unproductive Hours = Unproductive (Active) + Unproductive (Away) |
Neutral Hours | Total neutral (uncategorised) time across both active and away states.Neutral Hours = Neutral (Active) + Neutral (Away) |
Date | The calendar date of the recorded entry. |
User Id | Employee ID or User ID assigned to each employee. |
User Name | Full display name of the employee. |
User Email | Email address of the employee, used for identity resolution and notifications. |
Teams | Organisational grouping(s) the user belongs to in Flowace. |
Expected Day Start | Configured start time of the employee's scheduled working day. |
Expected Shift Start | Configured start time of the assigned shift within the working day. |
Work Start Time | Actual first login time recorded by the system for the day. |
Expected Day End | Configured end time of the employee's scheduled working day. |
Expected Shift End | Configured end time of the assigned shift within the working day. |
Work End Time | Actual last logout time recorded by the system for the day. |
Expected Hours (Active) | The expected number of on-screen active hours defined for the employee's shift. |
Missing Hours (Active) | Shortfall between Expected Hours (Active) and actual Active Hours recorded for the day. Highlights shift adherence gaps.Missing Hours (Active) = Expected Hours (Active) − Active Hours |
Activity % | Ratio of Active Hours to Logged Hours. Measures on-screen engagement intensity.Activity % = Active Hours ÷ Logged Hours × 100 |
Productivity % | Ratio of Productive Hours to Logged Hours. Measures output quality relative to time on system.Productivity % = Productive Hours ÷ Logged Hours × 100 |
Logged Hrs MET % | KPI metric indicating the percentage attainment of the logged hours target set for the user or team.Logged Hrs MET % = Actual Logged Hours ÷ Target Logged Hours × 100 |
SCENARIOS
The scenarios below follow a single employee - Priya, a Customer Success Manager - through a typical Tuesday, illustrating how each time classification applies in practice.
Term | Scenario |
|---|---|
Logged Hours | Priya's laptop wakes up at 9:02 AM when she logs in, and she shuts it down at 6:18 PM. Her Logged Hours = 9 hrs 16 mins, regardless of what she did during that window. |
Active Hours | Between 9:02 AM and 12:30 PM, Priya is continuously using her laptop - switching between Salesforce, Gmail, and MS Excel. The system records all title windows and URLs. This entire 3 hrs 28 mins block is captured as Active Hours. |
Away Hours | At 1:00 PM, Priya steps away for a client call on her phone. After 10 minutes of inactivity (or as per the configured threshold), the system triggers a pop-up when she returns. She selects 'Client Meeting' - pre-configured as Productive. The 45-minute block is logged as Productive (Away). |
Idle Hours | At 3:45 PM, Priya walks to a colleague's desk and forgets to lock her screen. After 3 minutes of no input (or as per the configured threshold), the system marks her as Idle. She returns at 4:10 PM - 25 minutes are logged as Idle Hours. |
Productive Hours (Active) | From 9:02 AM to 10:30 AM, Priya is in Salesforce updating opportunity records and sending follow-up emails via Outlook - both Admin-configured as Productive. These 88 minutes contribute to Productive Hours (Active). |
Unproductive Hours (Active) | Between 11:15 AM and 11:35 AM, Priya visits a news website and a social media platform - both labelled Unproductive by the Admin. The 20 minutes are automatically captured as Unproductive Hours (Active). |
Neutral Hours (Active) | From 2:00 PM to 2:18 PM, Priya opens an internal wiki tool not yet configured by the Admin. The system captures the time but cannot classify it - the 18 minutes are recorded as Neutral Hours (Active). |
Productive Hours (Away) | At 4:15 PM, Priya joins a 30-minute training webinar away from her laptop. On returning, she selects 'Training' from the pop-up - configured as Productive. These 30 minutes add to Productive Hours (Away). |
Unproductive Hours (Away) | Priya's 45-minute lunch break at 12:30 PM is away from her device. On return, she classifies it as 'Lunch Break' - an Admin-configured Unproductive activity. This contributes to Unproductive Hours (Away). |
Neutral Hours (Away) | Priya steps away for 15 minutes at 5:30 PM and logs it as 'System Updates' on the pop-up - an activity the Admin has configured as Neutral. These 15 minutes are recorded under Neutral Hours (Away). |
Missing Hours (Active) | Priya's shift requires 7 hrs of active screen time. Her actual Active Hours = 6 hrs 02 mins. Missing Hours (Active) = 58 mins - flagging a near-full day of adherence with some gap. |
Activity % | Active Hours = 6 hrs 02 mins (362 mins), Logged Hours = 9 hrs 16 mins (556 mins). Activity % = 362 ÷ 556 × 100 = 65.1% - Priya was actively using her screen for about two-thirds of her logged time. |
Productivity % | Productive Hours = 5 hrs 43 mins (343 mins). Active + Away Hours = 8 hrs 11 mins (491 mins). Productivity % = 343 ÷ 491 × 100 = 69.9% - meaning nearly 70% of Priya's engaged time was classified as productive output. |
Priya's End-of-Day Summary
The table below shows how all classifications add up across Priya's full day.
Category | Duration | Notes |
|---|---|---|
Logged Hours | 9 hrs 16 mins | First login to last logout |
Active Hours | 6 hrs 02 mins | On-screen, URL captured |
Away Hours | 2 hrs 09 mins | User-classified via pop-up |
Idle Hours | 1 hr 05 mins | Auto-detected, no input |
Productive Hours (Active) | 4 hrs 28 mins | Salesforce, Outlook, Excel |
Unproductive Hours (Active) | 0 hrs 20 mins | News & social media sites |
Neutral Hours (Active) | 1 hr 14 mins | Unconfigured tools or tools labelled as neutral |
Productive Hours (Away) | 1 hr 15 mins | Client call + training, as an example |
Unproductive Hours (Away) | 0 hrs 45 mins | Lunch break, Bio Break, as an example |
Neutral Hours (Away) | 0 hrs 09 mins | System Update activities, as an example |
Productive Hours (Total) | 5 hrs 43 mins | Active + Away productive |
Unproductive Hours (Total) | 1 hr 05 mins | Active + Away unproductive |
Neutral Hours (Total) | 1 hr 23 mins | Active + Away neutral |
Updated on: 23/04/2026
Thank you!