When do people schedule presence?

The two distributions describe the clock hours saved in the schedule. A start in the 09:00 hour covers 09:00 through 09:59 in the account’s selected schedule time zone. The end distribution follows the same rule. We do not combine these into one nine-to-five group: that would require a separate joint count and privacy review.

Each account contributes one representative day so that a seven-day schedule does not receive more weight than a one-day schedule. We choose the earliest enabled day in the stored Sunday-to-Saturday order with valid start and end values. That is a reproducible convention, not a claim that this day is the account’s most typical day.

Idle Pilot automatically seeds a Monday-to-Friday schedule from 09:00 to 17:00 when an account is linked. Customers can change it. The snapshot does not establish whether a saved hour came from an unchanged default or a deliberate edit. A cluster around these hours is therefore compatible with default-setting bias.

This is also a selected sample of people using one presence product. It is not a survey of remote workers, a census of paid customers, or an estimate of when people are most productive. We do not infer a job role, employer policy, work location, or work effort from a saved schedule.

We considered day-by-day patterns, number of enabled days, Lunch Break configuration, and broad time-zone regions. Those distributions are withheld because at least one cell or its complement would contain fewer than ten accounts. Publishing only a large cell alongside the cohort total could reveal a small complementary count by subtraction.

Only the two broad hour distributions are released. In each, both the displayed hour group and the combined other-hours group meet the ten-account threshold. There are no account identifiers, exact minute-level schedules, employer names, workplace links, or cross-tabulations in the downloadable dataset.

A saved schedule records an intended configuration. It does not prove that an account was online at those times, that a workplace connection was valid, that a person read messages, or that work occurred. A paused schedule, an expired credential, a holiday or a provider state can make configured hours differ from observed availability.

The study does not read messages or reconstruct individual activity histories. A single snapshot cannot establish how long a setting remained in place, whether a customer changed it later, or a seasonal trend. A later snapshot would need a fresh extraction and the same privacy checks before any comparison.