How to read your workday's fragmentation
A day can be full of meetings and still be a good day, and a day with only two hours of meetings can be a terrible one — it depends on where the meetings sit. Four hours of meetings clustered in the morning leave a whole afternoon free; the same four hours scattered across the day leave no gap long enough to do real work. That is fragmentation, and it is what this analyzer measures: not just how many hours meetings take, but what shape they leave behind.
When you analyze your day here, your browser:
- Takes your day — workday start and end, then each meeting's title, start, end and type. Paste a list if it is quicker: one meeting per line, like
09:00-10:00 Team standup. - Draws the timeline — the whole day to scale, meetings in one colour, free time in another, so the shape of the day is visible at a glance: solid blocks of focus, or confetti.
- Counts what survives — the gaps of 60+ and 90+ minutes, the longest uninterrupted block, the meeting-free hours versus the usable focus hours (gaps of 30 minutes or more), and the dead time in gaps too short to use.
- Scores the fragmentation — 0 to 100 from a formula printed on the page, with an estimated context-switch count and a 23-minute refocus cost per gap after a meeting, so the invisible cost of switching is visible too.
- Shows the what-if — tick "could be async" on meetings that do not need to be live, and see the focus time and score the day would recover if they became a written update instead.
What makes this analyzer different
The pages that top the results for this search mostly ask for aggregate numbers — total hours, total meeting hours, interruptions per hour — and return a single estimated focus figure from a formula. They never see the shape of your day, so they cannot tell a clustered morning from a scattered one, and none of them show what changes if a meeting goes async. The one tool that does take individual meetings only totals their duration and flags overlaps. This page is the only free, no-install, no-account, fully client-side analyzer we found that does all four: draws the day to scale from your actual meetings, counts the focus blocks that survive, scores fragmentation with a published formula, and simulates the async what-if — with a live network-request counter so you can verify the privacy claim yourself. It runs entirely in your browser — there is no server to upload to.
When is analyzing the right choice — and when is it the wrong one?
Analyzing is right when your days feel busy but nothing deep ever gets done, and you suspect the calendar's shape — not its total hours — is the problem. A score with a short longest block and a lot of dead time is the evidence to take to a team: cluster the meetings, protect one 90-minute block, turn the status updates async. It is the wrong choice as a verdict on a single unusual day: one bad Tuesday does not mean the week is broken, so run it on a typical day, and re-run it after you change the shape.
Honest limitations
It cannot see your real calendar
A web page has no access to your calendar. The analysis comes from the meetings you enter, so a forgotten meeting makes the day look better than it is — check the list against your calendar before trusting the score.
Focus estimates are indicative
Usable and effective focus are computed from gap lengths and a published refocus average, not measured. Your own refocus time, energy and task type change what a gap is really worth.
The score is a planning aid
The 0–100 score weights meeting share, dead time, longest block and switches by fixed weights. It ranks days against each other; it is not a grade on your productivity.
It cannot judge a meeting's worth
A meeting that fragments your day can still be the most valuable hour in it. The what-if shows the time recovered, not whether the meeting should go — that judgement is yours.
Overlaps are reported, not resolved
Double-booked meetings are counted once and flagged, but the tool cannot tell which one you actually attended. Fix overlaps in your calendar, not here.
Your day lives in one browser
Meetings are stored in this browser's local storage only. Clearing browser data, or switching devices, starts the day over — export the CSV if the analysis matters.