Calendar load
Calendar load looks beyond a simple meeting count. Ten short, well-spaced meetings can be far less demanding than five meetings crammed back-to-back with no travel or thinking time between them. Useful measures of calendar load take structure into account, not just volume.
Relevant factors include the proportion of the day booked, the number of back-to-back transitions, whether meetings run into typical lunch or focus-time windows, and how much notice was given before a meeting was added. Each of these affects how manageable a day actually feels, independent of what the meetings are about.
Sloane reads calendar metadata, such as start and end times, attendee count and how recently a meeting was booked, without reading meeting titles, descriptions or content in a way that would expose sensitive detail. It compares the resulting picture of load to a person's own recent pattern.
A spike in calendar load is not automatically a problem. It becomes worth flagging when it coincides with other signals, such as reduced recovery or a run of late-night messages, or when it represents a sustained change from someone's normal working pattern rather than a single unusual day.
Related terms
- Meeting fragmentation, The extent to which a day's meetings are scattered in short, disconnected blocks rather than grouped together, leaving little usable time in between.
- Context switching, The mental cost of moving between unrelated tasks or topics, which accumulates over a day and reduces the depth and quality of thinking available for any one of them.
- Telemetry friction, Sloane's metadata-only score of how fragmented and compressed a person's working day is, built from calendar and team-tool metadata such as meeting density, after-hours activity and message timing, never message content.