GratisAI career · budget the restart minutes you actually observe between tasks · local-first FREE TIER 1 Free Run Available
restart-cost receipt · till receipt with a tear-off foot

Budget the Restart Minutes You Actually Observe Between Tasks

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.

1 · switch type | observed returns | minutes to reorient per return

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.

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.

Perspective: 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.

2 · Read the restart-cost receipt

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.

Optional filing controls are a local prototype.

Checkout is unavailable. The reading above is complete; print, CSV and five local summaries are optional enhancements, not hidden answers.

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.

Boundary and sources

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.

Mechanism: competence-autonomy-loop

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.