Workday Fragmentation Analyzer: see how meetings chop up your day.

Enter your workday and its meetings and get a timeline of focus blocks vs fragmented time — your longest uninterrupted stretch, a 0–100 fragmentation score, and how much focus time you would recover if some meetings went async.

  • Your day never leaves the device
  • Timeline of focus blocks vs meetings
  • Fragmentation score, formula shown
  • Async what-if + CSV export

Map your day

Start with your workday hours, then add the meetings in it. Estimate roughly; the analysis is a planning aid, not a measurement.

An 8-hour workday.

Add a meeting

Or paste a list

Your meetings

No meetings yet. Add your first meeting above — or load the sample day below to see a finished analysis first.

    Add meetings, then press Analyze my day. Everything stays in your browser. Nothing is uploaded.

    No meetings yet. Everything stays on this device. A sample day is available below if you want to see a finished analysis first.

    Privacy you can verify, not just trust

    Calendar apps want to read your real schedule and store it on their servers. This one can't: it is a web page, and a web page cannot see your calendar at all — it only ever sees the meetings you type or paste. Your day is stored in your browser's local storage on this device. Your day never leaves the device — the only third-party requests are the site's own analytics, which count page views — and it uploads nothing, ever. There is no server to send it to. Don't take our word for it:

    New cross-origin requests during use: 0
    1. Press F12 to open developer tools, then the Network tab.
    2. Add a meeting and analyze your day above. Watch: apart from the site's analytics, nothing new is requested — no uploads, and no meeting data ever leaves your device.
    3. Extra credit: disconnect your internet after this page loads — adding meetings and analyzing still work.

    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:

    1. 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.
    2. 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.
    3. 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.
    4. 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.
    5. 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.

    Frequently asked questions

    Does this tool read my real calendar?

    No — it cannot. A web page has no access to your calendar, so this tool is a planning aid built from the meetings you type or paste yourself: each meeting's title, start and end time, and optional type. The timeline, focus blocks, score and what-if figures are computed from those entries only, and they are labelled as estimates everywhere they appear.

    How is the fragmentation score worked out?

    The score runs 0 to 100 (higher means more fragmented) and the formula is shown on the page: 100 times (0.4 times the share of the day spent in meetings, plus 0.3 times the share spent in gaps under 30 minutes, plus 0.2 times one minus the longest focus block divided by 90 minutes, plus 0.1 times the estimated context switches divided by 16). Below 30 is Low, 30 to 54 Moderate, 55 to 74 High, and 75 or above Severe.

    What counts as usable focus time?

    Usable focus time is the sum of the gaps between meetings that last 30 minutes or more. Gaps under 30 minutes are dead time: too short to start real deep work, so they do not count — a day with six 20-minute gaps has two hours of meeting-free time but zero usable focus time. The page shows both figures separately so you can see the difference.

    Where does the 23-minute refocus cost come from?

    It comes from research by Gloria Mark at the University of California, Irvine, who found people took an average of 23 minutes and 15 seconds to return to a task after an interruption. The tool subtracts 23 minutes from each gap that follows a meeting (capped at the gap's own length) to estimate effective focus time. It is an estimate built from that published average, not a measurement of you — your own refocus time may be shorter or longer.

    How does the 'could be async' what-if work?

    Tick 'could be async' on any meeting and the what-if view recomputes the whole day with those meetings removed: the usable and effective focus time recovered, the new longest block, and the new fragmentation score. It shows what the day would look like if those meetings became a written update or a recording instead — it does not cancel anything for you.

    What if two meetings overlap?

    Overlapping meetings are counted once for the totals — their union, so the same minutes are never counted twice — and the overlap is flagged on the page. The timeline merges them into a single busy segment with both titles shown. If you are double-booked, fix the calendar; this tool only reports what you entered.

    Is my day uploaded anywhere?

    No. Your workday and meetings live in your browser's local storage on this device only — your day never leaves the device, and the only third-party requests are the site's own analytics, which count page views. You can verify it yourself with the network-request counter in the privacy section below the analyzer. Clearing your browser data wipes the day; export the CSV if you want to keep it.

    What does this tool NOT do?

    It does not read your calendar, measure how you actually spend your time, or change any meeting — it draws the shape of the day you describe and estimates what survives it. It cannot tell whether a meeting was worth having, and it does not work across devices. The score and the focus estimates are planning aids from the times you enter, not measurements of your work.