> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/reference/work-and-time-management/product/workforce-productivity/time-and-motion.md). # Time & Motion We360.ai Time & Motion — how work output (work units) is measured against productive effort, how the performance matrix and composite score are calculated, and how the monthly report and comparison wo > Feature Path: Analytics → Time & Motion · Reports → Analytics → Time & Motion Report · Email Schedules → Time & Motion Report **Time & Motion** relates the *effort* an employee puts in to the *output* they produce. Classic time-and-motion studies measured how long a unit of work takes; We360.ai does the same at organizational scale, automatically, every month. It answers questions that hours alone cannot: who delivers a lot with efficient effort, who works long hours for little output, and where a team's time is not turning into results. Everything on this page is built from three monthly numbers per employee: | Number | What it measures | Where it comes from | | ------------------- | -------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | **Effort** | Time spent working, using the time metric you choose (Productive, Online, or Active) | Tracked automatically by the agent | | **Work Units (WU)** | Output for the month | Calculated from productive hours, closed tasks, and travel distance, or uploaded manually | | **Score** | A composite 0–100 rating that combines effort, output, attendance, and other enabled metrics | Calculated from your [Employee Scoring](/reference/work-and-time-management/product/workforce-productivity/employee-scoring.md) configuration | {% hint style="info" %} Time & Motion is an early-access feature and carries a **Trial** badge in the portal. Its output cutoffs and score weights are shared with [Employee Scoring & Scorecards](/reference/work-and-time-management/product/workforce-productivity/employee-scoring.md) and configured under **Settings → Scoring**. Contact your account manager to confirm access. {% endhint %} *** ## Where you see it Time & Motion appears in three places. They read the same monthly data, so the numbers always agree. | Surface | Path | What it shows | | -------------------------------- | ------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Time & Motion page** | Sidebar → **Analytics → Time & Motion** | Two tabs: **Overview** (Performance Matrix and Productivity vs Work Output curve) and **Work Units** (per-employee table with manual work-unit entry and CSV upload) | | **Time & Motion Report** | **Reports → Analytics → Time & Motion Report** | An on-screen, downloadable monthly table per employee, filterable by team, with an optional previous-month comparison | | **Emailed Time & Motion Report** | **Reports → Email Schedules**, report type **Time & Motion Report** | The richest version: every metric column, delivered monthly, with an optional comparison period | ### Access control * **Tenant Owner:** full access to the Time & Motion page, the on-screen report, and manual work-unit editing for the whole organization. * **Team Owner / Manager:** can edit work units for the people in their own teams, but never their own. The Analytics page and Reports card are limited to Tenant Owners. * **Standard User:** no access. Their own score is visible on the **Scorecard** tab of their [User Details](/reference/work-and-time-management/user-interfaces/portal/universal-tools/user-detail.md) page. The role's **Productivity** view-access permission also applies on top of these rules. *** ## How effort is measured Effort is the time an employee spends working in the month, taken from the same tracking data that powers Activity and Productivity elsewhere in the portal. You choose the time metric on the Overview tab under **Effort metric**: | Effort metric | Counts | | ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Productive time** (default) | Time in apps and websites classified as Productive under your [Productivity Rules](/reference/work-and-time-management/product/workforce-productivity/productivity-rules.md) | | **Online time** | All time the agent recorded the employee as online | | **Active time** | Online time minus idle time | {% hint style="info" %} Whether **Productive time** includes idle moments inside a productive app depends on your **Productivity Time Source** setting under **Settings → Productivity**. With **Active** (the default), only time with keyboard or mouse input counts. With **Duration**, the whole time the productive app was in the foreground counts, idle or not. Changing this setting recalculates past months. {% endhint %} ### Working days and the daily target Effort is always judged *per working day*, so a month with fewer working days is not penalized. For each employee and month We360.ai counts: * **Working days** — days the employee's shift expected them to work. Weekly offs, holidays, and approved leave days are excluded, so leave never dilutes an employee's numbers. * **Attended days** — working days on which the employee was present (any tracked activity or a punch-in). The **daily effort target** comes from your **Settings → Productivity → Goals**: the minimum Productive, Online, or Active time per day that matches the chosen effort metric. If no goal is set, We360.ai uses **5 hours per working day**. *** ## How Work Units are calculated A **Work Unit (WU)** is the common currency for output. Each employee's calculated work units for a month are the sum of three components: ``` Work Units = Productive-hour WU + Task WU + Distance WU ``` ### 1. Productive-hour work units Productive hours convert one-to-one into work units, up to the month's target (**working days × daily target**). Hours above the target earn a bonus through the **Extra Goal-Achievement Multiplier** (default **1.3×**). ``` Target hours = working days × daily target hours Base hours = min(productive hours, target hours) Overtime hours = max(0, productive hours − target hours) Productive WU = base hours + (overtime hours × multiplier) ``` **Example:** an employee averages 8 productive hours a day against a 5-hour goal. Each day earns 5 + (3 × 1.3) = **8.9 WU**. Set the multiplier to 1.0 to remove the bonus. ### 2. Task work units Work Units also credit completed project tasks: * A task counts in the month it moved to a status in the **Closed** category. Archived tasks are ignored. * Each closed task is worth **story points × story-point multiplier**. A task with no story points uses the **Default Story Points** (default 2). The multiplier is the project's own override if set, otherwise the **Default Story-Point Multiplier** (default 5.0). * The task's work units are split among the people who worked on it, in proportion to the time each logged against the task. If nobody logged time, the units are split equally among the assignees. A task with neither logged time nor assignees earns no credit. ### 3. Distance work units For field staff, travel distance recorded through [Field Tracking](/reference/work-and-time-management/product/workforce-productivity/field-tracking.md) also earns output: kilometers travelled ÷ **Kilometers per Distance Unit** (default 5 km per WU). ### Manual work units When output is better known from outside We360.ai (sales closed, tickets resolved, pieces produced), a manager can enter **Manual Work Units** for the month: * **Inline:** on the **Work Units** tab, click **edit** in the *Manual WU* column, type the value, and **Save**. * **In bulk:** click **Download Template** to get a CSV pre-filled with every employee for the month, fill in the manual column, then **Upload CSV**. A **CSV preview** shows each row's current value, new value, notes, and any error before you **Commit**. When a manual value exists it **replaces** the calculated value for the performance matrix and the score. Both are still shown side by side in the tables, and a blue **CSV** tag marks rows that came from an upload. Nobody can edit their own work units. ### The monthly benchmark The **Monthly Work-Unit Benchmark** (**Settings → Scoring**, default **100 WU**) is the output level that counts as "high" and earns a full Work Units score. Set it to what a fully productive month of your standard employee looks like. *** ## The Overview tab ### Performance Matrix The Performance Matrix is a two-by-two grid. Every employee falls into exactly one quadrant for the period, based on two cutoffs shown in the card header (for example, `cutoffs: 100 WU · 5 h / working day`): * **Output cutoff (vertical axis):** work units at or above the monthly benchmark are *high output*. Manual work units are used when present, otherwise calculated ones. * **Effort cutoff (horizontal axis):** effort at or above the daily target multiplied by the month's working days is *high effort*. | Quadrant | Output | Effort | Reading | | -------------------------- | ------ | ------ | ----------------------------------------------- | | **Smart Performers** | High | Low | High output with efficient effort | | **Heavy Hitters** | High | High | High output, high effort. Watch for burnout. | | **Unengaged Contributors** | Low | Low | Low output, low effort. Needs engagement. | | **Strugglers** | Low | High | High effort, low output. Fix process or skills. | Below the grid a summary strip shows the number of users in the period and the percentage in each quadrant. **Period controls.** Switch between **Month** and **Quarter**, then pick the primary period and, optionally, a baseline period under **Compare … vs**. For a quarter, both cutoffs scale to the months an employee actually has data for, so someone who joined mid-quarter is judged against a proportionate target. **Default periods.** Up to the 15th of the month, the Overview compares *last month* against *the month before*. After the 15th it compares *this month* against *last month*, so the primary period always has a meaningful amount of data. **Comparison.** When a baseline is set, each quadrant card shows two bars (baseline dim, primary in colour) and a tag with the change in percentage points. Movement is measured from the earlier period to the later one, and the tag is green when the change is good for that quadrant: growth in Smart Performers or Heavy Hitters, shrinkage in Strugglers or Unengaged Contributors. ### Productivity vs Work Output curve This chart shows whether more effort is actually producing more output across the organization. * **Horizontal axis:** average effort per working day, in half-hour buckets (`Effort (hours / working day)`). * **Bars (`% of users`):** the share of employees whose average effort falls in each bucket. * **Line (`Avg output %`):** the average work output of those employees, as a percentage of the monthly benchmark. * **Benchmark** line at 100 %, and a green **High productive zone** band from 100 % to 120 % of the benchmark. A healthy organization shows the line rising with effort and most bars sitting under or near the green zone. A flat line means extra hours are not converting into output. A tall bar far right with a low line points to the Strugglers quadrant. *** ## The Work Units tab A per-employee table for one month (default: last month) with the columns **Employee · Calc. WU · Manual WU · Productive (h) · Attendance % · Score · Uploaded**. * **Calc. WU** — calculated work units as described above. * **Manual WU** — the manually entered value, editable inline. * **Productive (h)** — productive hours for the month. * **Attendance %** — attended days ÷ working days × 100. * **Score** — the composite score, colour-banded: **green** at 70 and above, **amber** from 40 to 69.9, **red** below 40. A dash means no score could be calculated. * **Uploaded** — a **CSV** tag when the manual value came from an upload. The **Recompute** button re-runs the month's calculation on demand, for example after correcting task data or changing a scoring setting. *** ## How the Score works The **Score** is the same composite 0–100 rating described on [Employee Scoring & Scorecards](/reference/work-and-time-management/product/workforce-productivity/employee-scoring.md). Each enabled metric is normalized to 0–100, then combined as a weighted average using the weights under **Settings → Scoring**. Weights are re-balanced across the enabled metrics, so disabling one does not shrink everyone's score. | Metric | Normalization | Default weight | | -------------------- | ------------------------------------------------------------------------------------- | -------------- | | **Work Units** | Work units (manual if set, otherwise calculated) ÷ monthly benchmark, capped at 100 % | 40 | | **Productive Hours** | Productive time ÷ (working days × daily target), capped at 100 % | 20 | | **Attendance %** | Used as is | 15 | | **Online Hours** | Online time ÷ (working days × daily target), capped at 100 % | 10 | | **Idle Penalty** | Inverted: 100 % minus idle time ÷ (working days × daily target) | 5 | | **Distance Units** | Distance units ÷ (working days × 2) | 10 | An employee with no enabled metric that applies to them has no score, shown as a dash. **Time-and-materials mode.** Turn off **Include calculated values in score** under **Settings → Scoring** to rate people purely on uploaded manual work units. All tracker-derived metrics are then ignored, and an employee without a manual value scores from zero. {% hint style="warning" %} Saving any change under **Settings → Scoring**, **Settings → Productivity → Goals**, or the **Productivity Time Source** recalculates every past month. Scores and quadrants update retroactively. {% endhint %} *** ## The Time & Motion Report **Reports → Analytics → Time & Motion Report** presents the monthly table on screen and as a CSV download. **Filters:** a **month picker** and a **team filter**. There is no user filter and no arbitrary date range; the report is monthly by design. The default month is *last month*. **Columns:** **Employee · Work Units · Manual Work Units · Productive Time · Attendance % · Score**. Rows are ordered by score, highest first. Productive Time is shown as hours:minutes:seconds; a dash means no value. ### Previous-month comparison Under the advanced filters, set **Compare with** to **Previous month**. The report then: 1. Fetches the same table for the month before. 2. Matches employees between the two months. 3. Adds a small arrow next to every numeric cell: **▲** with the increase in green, **▼** with the decrease in red, or **—** when the employee has no row in the previous month (a new joiner, for example). 4. Shows a banner above the table stating exactly what is compared, for example *Comparing August 2026 vs July 2026 — arrows show change from the previous month.* Arrows indicate direction only. Whether a change is good depends on the column; a rise in Work Units is good, and a fall in Attendance % is not. **CSV export** uses the same six columns, preceded by the report name, the month, and the generation timestamp. *** ## The emailed Time & Motion Report The scheduled email version (**Reports → Email Schedules → Time & Motion Report**, marked **Recommended**) carries the complete set of monthly metrics: `Employee name · Email · Employee ID · Team · Month · Working days · Attended days · Attendance % · Calculated work units · Manual work units · Productive hours · Online hours · Active hours · Idle hours · Distance (km) · Score` * **Cadence** is always **Monthly**: the underlying figures are finalized once per month, so a weekly or daily schedule would re-send the same numbers. * **Data scope** can be the entire organization, team-wise, a single team, or user-wise. * **Comparison Period (optional):** **None**, **Previous month**, or **Previous quarter**. When set, every numeric column gains a side-by-side value from the comparison period plus a **delta score** (score minus comparison score). The period is relative to each send, so a monthly schedule with *Previous month* always compares last month against the month before. * The report cannot be generated for the **current month**; pick a completed month. *** ## Data freshness Time & Motion works from monthly roll-ups of the daily tracking data, not from live events. * Daily figures for the current day are refreshed about **every hour**, and the current month's totals follow shortly after. * Late-arriving data from devices that were offline is picked up automatically for the trailing weeks, and the month is re-rolled at the start of the following month to finalize it. * Because the current month is still filling in, the on-screen and emailed reports default to (or require) a **completed month**. The Overview tab does show the in-flight month once it has enough data. * If a month looks stale, use **Recompute** on the **Work Units** tab. See also the data-freshness banner described under [Settings Center](/reference/work-and-time-management/user-interfaces/portal/settings-center.md). *** ## Edge cases | Situation | What you see | | ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Employee with no tracked activity in the month | The employee does not appear in that month's tables or quadrants at all; they are not shown as zero. | | Employee who changed teams mid-month | Attributed to the team they were in at month-end. | | Employee absent on a working day | Counts as a working day but not an attended day, lowering Attendance %. | | Approved leave, holiday, or weekly off | Not a working day; it neither helps nor hurts any metric. | | Two devices used at the same time | Time from both devices is added together, which can inflate Online and Active time. | | Task closed without story points | Uses the Default Story Points value from **Settings → Scoring**. | | More than 500 employees with comparison on | Previous-month arrows may be missing on later pages of the on-screen report; use the emailed report for the full comparison. | | Month boundaries | Months are calendar months of the employee's working days. Overnight shifts are attributed to the working day they started on when [Cross-Day Working Time](/reference/work-and-time-management/product/work-and-time-management/cross-day-working-time.md) is enabled. | *** ## Related * [Employee Scoring & Scorecards](/reference/work-and-time-management/product/workforce-productivity/employee-scoring.md) — configuring the benchmark, weights, and multipliers that Time & Motion uses. * [Productivity Rules](/reference/work-and-time-management/product/workforce-productivity/productivity-rules.md) — what counts as Productive time. * [Reports](/reference/work-and-time-management/user-interfaces/portal/universal-tools/reports.md) — the full report catalogue and email schedules. * [User Details](/reference/work-and-time-management/user-interfaces/portal/universal-tools/user-detail.md) — the per-employee Scorecard. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.we360.ai/reference/work-and-time-management/product/workforce-productivity/time-and-motion.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.