Budget the Restart Minutes You Actually Observe Between Tasks — Free
Some task changes take an observable pause before you can resume. Count those returns and enter your own reorientation estimate to make a small, inspectable time budget—without importing a universal “lost focus” statistic.
The proof surface
Standup drift tools compare meetings with their booked length. This receipt isolates reorientation after task changes, using observed counts and times; it does not measure meetings, diagnose attention or score productivity.
Inputswitch type | observed returns | minutes to reorient per return; working minutes in the day being modeled
Rare deviceStandup drift tools compare meetings with their booked length. This receipt isolates reorientation after task changes, using observed counts and times; it does not measure meetings, diagnose attention or score productivity.
Output artifactTotal observed restart budget with row-by-row context
Cost$0 local calculation · no card, paid key, subscription or signup · proposed filing price is not for sale
Sample, not your facts: Illustrative inputs: Inbox returns | 7 | 3.5; Chat detours | 4 | 2. Working minutes in the day being modeled = 420. Total observed restart budget: 32.5 restart minutes. All records are invented.
Before using the restart-cost receipt
Use a lightweight observation period, not surveillance. A private tally beside a work block is enough: note a return event, estimate when you were ready to continue, then stop recording. You do not need message contents, colleague names, health information or an explanation of why someone contacted you. Separate helpful collaboration from the mechanics of returning to the original task. A handoff can be worthwhile even when it has a restart cost. The useful question is whether your plan has room for that cost, not whether interruptions are morally bad. If the result looks surprising, first check that the same event has not appeared as both an inbox return and a chat detour. This is a planning ledger built from your own observations, not a model of cognition.
Why the flat version breaks
Counting the same return in two categories
An inbox message received through chat can still be one detour. Mutually exclusive categories matter more than a detailed list of communication channels.
Including the whole conversation as restart time
Actual collaboration is work, not automatically overhead. Measure the return-to-task pause separately if that is the quantity you want to budget.
Turning a personal tally into a ranking
Different roles require different responsiveness. The receipt cannot compare employees fairly, diagnose an attention condition or prove that a communication policy improved outcomes.
How to work the restart-cost receipt
Define a return event
Count the moment you resume the original activity after leaving it, not every notification that appears. Pick categories that do not overlap. Two messages handled during one detour may create one return, while reopening a draft repeatedly may create several.
Observe rather than import a statistic
Enter minutes to reorient from your own notes or a deliberately labeled estimate. The number is not supplied by the app. Avoid tracking other people without consent or storing message contents; aggregate categories can express the same budget.
Multiply and show the share
Restart minutes for a category equal return count times minutes per return. Add the categories once, then divide by the entered working-day minutes to show the share. The result keeps the category working beside the total so a duplicated event can be found.
Review the plan, not the person
A total larger than the working day signals incompatible or overlapping inputs and flags all rows for review. Otherwise, decide whether the schedule needs room for reorientation. Ask your manager about communication expectations before changing availability or response practices.
What the restart-cost receipt separates
Question
Before
Inspect this instead
Counting the same return in two categories
An inbox message received through chat can still be one detour. Mutually exclusive categories matter more than a detailed list of communication channels.
Observe rather than import a statistic
Including the whole conversation as restart time
Actual collaboration is work, not automatically overhead. Measure the return-to-task pause separately if that is the quantity you want to budget.
Multiply and show the share
Turning a personal tally into a ranking
Different roles require different responsiveness. The receipt cannot compare employees fairly, diagnose an attention condition or prove that a communication policy improved outcomes.
Review the plan, not the person
This restart-cost receipt replaces a manual count or calculation, not source verification or the responsible person’s review.
Run it on the samples, right here
FIRST-LOAD
HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.
Observed-time arithmetic only, not neuroscience, mental-health advice or an employee productivity score. It does not estimate a universal switching penalty or the value of collaboration. Keep observations voluntary and non-sensitive; discuss role-specific communication requirements with the relevant manager rather than using this tally to assess people.
Data note: The restart-cost receipt processes switch type | observed returns | minutes to reorient per return locally. Starter/sample selection and Run compute in this tab; no input is sent by the calculator. A local draft may be saved; explicit state-link sharing or optional external AI formatting can disclose inputs. Use non-sensitive labels.
Go deeper: the companion app files the same reading as a till receipt with a tear-off foot
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the restart-cost receipt reading, and holds your drafts on this device — one complete free app run; the proposed $4 one-time filing layer is not for sale.
The restart-cost receipt answer stays complete for free. The proposed $4 one-time filing layer adds row CSV, print and five local reading summaries, not hidden answers. Checkout is unavailable; the article demo remains unlimited.
Observed-time arithmetic only, not neuroscience, mental-health advice or an employee productivity score. It does not estimate a universal switching penalty or the value of collaboration. Keep observations voluntary and non-sensitive; discuss role-specific communication requirements with the relevant manager rather than using this tally to assess people.
What this is built on
Method: Restart minutes for a category equal return count times minutes per return. Add the categories once, then divide by the entered working-day minutes to show the share. The result keeps the category working beside the total so a duplicated event can be found.
All sample records, dates, quantities and labels are invented. No outside policy, contract, rate, clock offset, measurement or accessibility standard is represented as verified.
Google’s official pricing documentation, fetched 2026-09-30, says AI Studio is free in available regions. Optional formatting may require a Google account; manual local entry requires none. Limits can change and free-tier content may be used to improve products. Do not send private records.
Before: reorientation was mixed into a vague impression of a busy day. After: counted returns and observed minutes form an explicit budget, not a productivity rating.
Three worked readings, with different inputs
Sample A — typical inputs
Inbox returns | 7 | 3.5
Chat detours | 4 | 2
Setting: Working minutes in the day being modeled = 420. Expected summary: 32.5 restart minutes.
Seven inbox returns at three and a half minutes contribute 24.5 minutes. Four chat detours at two minutes contribute another eight, for 32.5 minutes of observed restart work. That is about 7.74 percent of a 420-minute day. These are invented measurements, not a claim that email or chat usually has this effect. The ledger counts reorientation only; time spent actually answering a message is a separate activity and must not be hidden inside both categories.
Sample B — changed plan
Inbox returns | 3 | 2
Chat detours | 2 | 1.5
Setting: Working minutes in the day being modeled = 420. Expected summary: 9 restart minutes.
The alternate observation has fewer returns and shorter restart periods: six minutes plus three minutes equals nine. Comparing it with the first sample is a way to inspect assumptions, not evidence that batching messages saved 23.5 minutes. The days could have had different tasks, urgency or complexity. If you try a change, observe the same kinds of work over comparable days and preserve the communication obligations that matter to your role.
Setting: Working minutes in the day being modeled = 420. Expected summary: 0 restart minutes.
No return events contribute no restart minutes, even if a typical return would take four minutes. One explicitly measured zero-minute reorientation also contributes zero. Blank or negative times are not accepted as zero. A zero reading does not prove perfect focus or a better employee; it says only that the entries supplied no measured restart budget. Missed messages, collaborative value and the effort inside the primary task remain outside the ledger.
Optional AI formatting, never the calculation
Manual entry completes this restart-cost receipt for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.
Format only these fictional or non-sensitive notes for a restart-cost receipt. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string"]}], "setting": "string"}. The columns are switch type | observed returns | minutes to reorient per return; the setting is Working minutes in the day being modeled. Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.
An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.