ℹ️ In brief: on the People sheet, weekly time is a total across every application, and the decile chart counts one person once per application. Two figures that read differently from anywhere else, and mislead until you know it.
Before you read any chart
Five rules apply to every figure and every chart on this page. Knowing them prevents the most common misreadings.
The scope changes every figure
The scope changes every figure
The scope selector at the top of the page applies to everything you see, including the headline figures. A score read on one department is not the same as the score read across the whole company, and both are correct.
Before comparing two figures, check that they were read with the same scope.
Small groups are hidden
Small groups are hidden
To protect employee privacy, Beamy never shows a result carried by fewer than seven people.
Two things can then happen. The group disappears from the chart, and a chip tells you which ones were removed. Or the whole section shows a message instead of the data.
A department missing from a chart is usually a department that is too small, not missing data.
The last period is not over
The last period is not over
On every time series, the last point covers a period that is still running. It always looks lower than the others. That is not a drop in usage.
Only monitored applications are counted
Only monitored applications are counted
An application you have archived, or one Beamy does not recognise yet, appears nowhere. If usage you expected is missing, start by checking the application status.
Data refreshes overnight
Data refreshes overnight
Everything is recalculated once a day, outside office hours. Usage from today shows up tomorrow.
Global usage metrics
Four figures and two donuts, over the period you choose: last month, 30 days or 90 days.
Unique active users
Unique active users
What you are looking at
The number of people in this scope who use at least one application.
How to read it
A person is retained as soon as they pass a real usage bar on at least one application: more than two minutes in the month, or at least two visits of half a minute.
⚠️ The same label exists on the other sheets, on a different base. Here, it counts the people active on at least one application in the domain. On the Product Sheet, the users of a single application. On the Tech sheet, the people concerned by a functional need.
Number of apps used
Number of apps used
What you are looking at
How many different applications are used in this scope.
How to read it
An application counts as soon as a single person uses it. This figure measures the breadth of the estate actually in use, not what each person uses.
⚠️ This counter also exists on the Tech sheet, on a different set. Here, it is every application used in this domain, across all needs. There, only those covering one same need.
Average weekly time per user
Average weekly time per user
What you are looking at
How long one person in this scope spends each week across all their applications.
How to read it
Do not confuse it with the weekly time on a Product Sheet: here it is the total across every application.
⚠️ Do not compare this figure with the one on the Product Sheet. Here, it is time spent across every application combined. There, it is time spent on a single one.
IT policy adherence score
IT policy adherence score
What you are looking at
The share of usage happening on applications your company has authorized.
How to read it
Each person is counted once per application they use. Someone using three authorized applications and one banned one therefore counts as three compliant usages out of four.
This measures the breadth of compliant usage, not the number of compliant people. Someone using many applications weighs more than someone using one.
⚠️ This score also exists on the Tech sheet, computed on different usage. Here, it covers all the usage of the people in the domain. There, only the usage answering one given functional need.
What should catch your eye
The score ignores intensity: a single visit weighs as much as daily use.
Access mode breakdown
Access mode breakdown
What you are looking at
How people in this scope open their applications: in the browser or with installed software, and whether these are market applications or built in-house.
How to read it
The categories do not overlap.
⚠️ This breakdown also exists on the Product Sheet. Here, it covers every way the people of the domain open their applications. There, the ways a single application is opened. Without the Desktop Agent deployed, only browser sessions are visible.
Internal and external breakdown
Internal and external breakdown
What you are looking at
Among the people in this scope, how many work for the company and how many come from outside.
How to read it
The result depends entirely on how your organization was described in Beamy.
⚠️ This breakdown also exists on the Product Sheet. Here, it covers everyone in the domain. There, the users of a single application.
What should catch your eye
A significant unknown share signals an incomplete organizational mapping. This is the one place in the platform where completing that mapping directly changes the figure shown.
User engagement evolution and distribution
Usage trends over time
Usage trends over time
What you are looking at
A curve tracking, month after month, the measure you choose for this scope.
How to read it
Five measures are available: number of active users, weekly time, IT policy adherence, number of applications, and number of applications per person. You also choose the depth: three, six or twelve months.
⚠️ The same curve exists on the other sheets, on a different set. Here, it follows one domain of the organization. On the Product Sheet, a single application. On the Tech sheet, one functional need.
What should catch your eye
Applications per person is the best sprawl indicator. If it rises while the total number of applications stays flat, the estate is not widening: people are accumulating tools.
Usage time distribution by decile
Usage time distribution by decile
What you are looking at
A ten-column chart, from the lightest usage on the left to the most intensive on the right.
How to read it
Users are sorted by time spent, then split into ten equal groups. The height of each column is the average weekly time of that group.
⚠️ On this page the ranking is done application by application, then pooled. One person can therefore appear in several columns: light on one application, intensive on another. The totals shown exceed the number of people in the group. Read this chart as a picture of usage intensity across the estate, not as a ranking of people. The same chart exists on the Product Sheet, where the ten columns rank the users of a single application.
Apps used in the last 90 days
A table of the applications actually used in this scope, with their authorization status, category, user count, weekly time, business criticality and transversality. Selecting rows launches a Guidance campaign directly on that population.
AI usage
This section is switched on per organization. If you cannot see it on your People sheets, it has not been opened for your organization yet: ask your Beamy contact.
Time distribution across the main business activities
Time distribution across the main business activities
What you are looking at
A radar chart. Each spoke is a business activity, and two areas overlap, both expressed in hours per week.
How to read it
The blue area is the time spent on the activity. The pink area is the share of that time where employees are assisted by artificial intelligence.
A spoke reads like this: this activity represents two hours a week on average, of which half an hour is AI-assisted.
At least three activities are needed for the chart to appear. A note below it tells you how many activities are shown and what share of total time the remainder represents.
Domain decomposition
Breakdown by sub-domain
Breakdown by sub-domain
What you are looking at
A mosaic of the sub-groups in this scope, alongside a table repeating the same figures.
How to read it
The size of a rectangle is the number of people in the sub-group. The colour reflects the measure you select, and the colour scale adapts to this scope only: a dark rectangle is the highest in this scope, not in the whole company.
What should catch your eye
This is where the small-group masking shows the most. Sub-groups under seven people are removed from both the mosaic and the table, and a chip at the top of the section tells you which.