Odau

Usage Signals

Who is actually using what. Every figure is counted from one row per person, per application, per day — never estimated.

No application has enough data to score utilization.

0 of 0 purchased seats were used in this period. 0 of 0 applications have no usage source connected, so they are excluded from these figures rather than counted as unused — an absence of data is not evidence of an absence of use.

Where the data points · 0 of 0 applications with a usage source · 0 scored for Usage Signal · 65 business days

Usage Source Coverage
0%
0 of 0 applications
Seats Purchased
0
across active contracts
Seats Used
0
by an active person in the period
Mean Utilization
Not Scored
no application has both a seat count and a source
Reading by week

People Using Something

No usage recorded in this period.

No usage data in this period.

Most Used

Seat utilization, highest first. 0 applications can be scored; 0 cannot and are not shown.

No application has both a seat count and a usage source.

Watchlist

Lowest seat utilization. Low use is a signal to look, not a conclusion — a seasonal tool in its quiet quarter reads the same as an abandoned one.

No application has both a seat count and a usage source.

How These Are Counted

An active user is a current employee who used the application during the period — a login plus at least one meaningful action where action data exists, and a login alone where it does not. The fallback is per application: SSO login data cannot report actions, so demanding one would report every SSO-only application as entirely unused.

Utilization is active users against purchased seats. An application without both is reported as Not Scored and excluded from every average here, rather than counted as zero.

The Usage Signal combines utilization at 40%, engagement at 35% and consistency at 25%. Thresholds are configured per organization, so a judgement against them is your threshold rather than Odau’s opinion.