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.

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.

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.

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.

Everything is recalculated once a day, outside office hours. Usage from today shows up tomorrow.

The number of people using at least one of the applications answering this need.

Someone using three applications for the same need is counted once.

Out of everyone whose activity Beamy observes, the share who need this function.

This measures the weight of the need itself, independently of the tools answering it.

How many different applications cover this same need in your company.

This is the most direct sprawl figure in the platform. Six tools for one need means six contracts, six integrations and six risk surfaces.

The share of usage on this need happening on authorized applications.

A low score here does not necessarily mean people are working around the rules. It can also mean no application has been designated as the official one for this need.

How many people use authorized applications, banned ones, or ones whose status has not been decided.

One person can use several applications with different statuses and appear in several shares.

The share of applications on this need whose status has been settled.

An application counts as qualified as soon as a status has been assigned, authorized or banned. The rest are still awaiting a decision.

The calculation covers the applications active during the period on screen, not the whole catalog.

This is your remaining work on this area. A low figure on a heavily used need is the first thing to address.

The same curve as on the Product Sheet, applied to the whole need.

It covers the last twelve months.

A need growing while the number of applications stays high signals an area where demand is rising before any rationalization has begun.

A two-way table: each row is a department of your organization, each column an application.

Each cell shows the share of that department's time going to that application over the past 90 days. The darker the cell, the more the department's usage is concentrated on that tool. The border of each column recalls the application's authorization status.

You can sort by row to see what a given department relies on, or by column to see which departments an application actually serves.

A selector changes the organizational level shown as rows, and a search field filters the columns.

A row with three or four equally dark cells: that department has standardized on nothing for this need.

A column dark on a single row: that tool is local, whatever the catalog says.

Two dark columns on different rows, for the same need: the textbook redundancy case to arbitrate.

The same mosaic as on the Product Sheet, applied to the whole need.

The size of a rectangle is the number of people concerned by this need in the department, the colour the measure you select.

This chart answers who needs this function. The departments crossed with applications, above, answers what they use to cover it. The two read together.