Skip to main content

Change History Usage: Who Is Planning in Toolio?

Use the Usage view on the Change History page to see who saved work in the last 30 or 90 days, how often, and in which modules.

The Usage view turns Toolio's change log into a picture of your team's planning activity. Instead of a row-by-row list of edits, it shows how many people saved work in the last 30 or 90 days, how often they came back, and which modules they worked in.

Usage is available to account admins. Everything on the page is built from the same change events behind Change History, so no extra setup or integration is required.

The Usage view, with summary cards, activity charts, and the planner table

Use Cases

  • Check adoption before a business review, without asking anyone to self-report.

  • Follow up after training by seeing who has started saving work and who has not.

  • See which modules are actually used, including any module nobody has touched.

  • Compare the last 7 days against the previous 7 to catch a team going quiet.

  • Spot slow saves that are worth raising with Toolio support.

Opening Usage

  1. Go to Settings > Data Management > Change History.

  2. Click Usage in the top right of the toolbar.

  3. Click Change Log to go back to the row-by-row change list.

Pick the window with the 30 days and 90 days buttons. The dates for the selected window are shown next to them, and the window is kept in the page address, so a link to the 90-day view opens on the 90-day view. Use the refresh button to re-run the numbers without reloading the page.

The Usage toolbar and summary cards

What Usage Measures

Every figure on the page is a saved change. Toolio does not record reads, so someone who spent the period reviewing plans and reports without saving anything will not appear here.

Two more things are worth knowing before you read the numbers:

  • Toolio staff and service accounts are excluded, so these totals will not match the change log for the same period.

  • One save is one change, however much it covered. A planner who edits a single cell and a planner who runs a bulk update across thousands of cells each add one change.

Days and weeks are bucketed against your organization's working day, so a late afternoon save lands on the day the planner actually worked. Weeks start on Monday.

Summary Cards

Active Planners

The number of distinct people who saved at least one change in the window. The note underneath compares the last 7 days with the 7 days before that.

Changes Saved

Total changes in the window, with the same 7-day comparison. The chip reads flat when the change is within 5% either way, and no activity when there is nothing to compare against.

Work Sessions

A work session is a run of one person's saves with no gap longer than 30 minutes. A morning and an afternoon sitting count as two sessions, while a break to read a report or sit in a meeting does not split one. The note shows the average number of changes per session.

Weeks In Period

How many weeks the window covers. This is the denominator for the Weeks with a save column in the planner table.

Changes Saved Per Day

One column per day for the whole window. Days with no saves are shown as true zeros rather than skipped, so a quiet stretch is visible instead of being hidden by the axis. Hover a column for the weekday, the number of changes, and how many planners were active.

Active Planners Per Week

Distinct people who saved a change in each week. A hatched column means the window cuts that week short, so its total is not comparable to a full week.

Planner Activity

A table of everyone who saved work in the window. Click any column header to re-sort, type in the filter box to narrow it to a person or a group of people, and click Export to pull what you are looking at into a spreadsheet.

The Planner activity table

Column

What it shows

Planner

The person who saved the changes. A deleted user appears as User plus their id.

Changes

Total saved changes in the window.

Sessions

Work sessions in the window.

Changes / session

Changes divided by sessions, as a measure of how much gets done per sitting.

Days with a save

Days on which they saved at least one change.

Weeks with a save

Weeks in which they saved at least one change, out of Weeks in period.

Last 7d

Changes in the last 7 days of the window.

Vs prior 7d

The last 7 days against the 7 days before them.

Where they work

Up to two modules, each accounting for at least 15% of that person's changes.

Changes By Module

Every module is listed with its change count and share of the total, including any module at zero. A module nobody touched is the most useful signal on the page, so it keeps its place in the list rather than disappearing.

The modules are Assortment Plan, Allocation, Merchandise Plan, Item Plan, Buying, Models & Curves, Reporting, Notifications, Settings & Admin, and Other.

Module Mix By Planner

One stacked bar per planner, showing how their work splits across modules. Assortment Plan, Allocation, and Merchandise Plan each have their own color, and everything else is grouped into a single Other segment. Hover a segment to see the module and its change count. Bar length is comparable across rows, so the busiest planner has the longest bar.

Slowest Operations

The eight operation types with the highest average save time, so you can tell a slow save from a slow planner. Colors on the last column mark how far over the 5 second threshold an operation ran: amber once the average passes 2 seconds or any single run went over 5 seconds, and red once the average passes 10 seconds.

Click Show all to switch the card to every operation type in the window, which is the quickest way to see what your team actually spends its saves on. Click Show slowest 8 to go back.

Column

What it shows

Operation

The type of save, named the same way as the Operation column in the change log.

Runs

How many times it ran in the window.

Average

Average recorded duration.

Worst

The slowest single run.

Over 5s

How many runs went over the threshold.

FAQs

Why don't these totals match the Change History log?

Usage excludes Toolio staff and your tenant's service account, and the change log does not. The service account can out-write every person in the account, so leaving it in would make the page useless as a measure of your team's planning.

Someone planned all week but shows little or no activity. Why?

Only saves are counted. Reviewing plans, running reports, and exporting data leave no change event. A planner can also do a large amount of work in a handful of saves, which shows up as a low change count and a high Changes / session.

Do imports and API writes appear here?

Writes made with an API key appear as the API user that made them. Scheduled jobs that run as your tenant's service account are excluded, along with Toolio staff.

Why is a module showing zero?

Nobody saved anything Toolio could attribute to that module in the window. Modules stay in the list at zero on purpose, since that is often the answer you came for.

What is in "Other"?

Changes from modules without their own color in the per-planner chart, plus any operation type Toolio has not yet mapped to a module. When there are unmapped operation types, they are named in the footnote at the bottom of the page.

Can I export the tables?

Yes. Planner activity has its own Export button, and both tables are standard Toolio grids, so they also sort and export like any other grid in the product. An export follows the filter, so filter first if you only want part of the table.

Can I group the table by team?

Not today. Toolio has no team or department on a user, so the filter box on Planner activity is the way to narrow the table to the people you care about.

Why does the first or last week look short?

The window is a fixed number of days, so the weeks at either end are usually partial. Those columns are hatched in Active planners per week to keep them from reading as a real drop.

Related Articles

Did this answer your question?