Check Walking-Leg Times Against Your Hours Available
A route on a map is distance; a day on foot is minutes. Multiply each leg’s distance by the pace you actually walk, total the minutes, and compare them with the hours in the day you have left.
1 · walking leg | distance units | pace minutes per unit
FIRST-LOAD
Input is processed locally and a draft is saved automatically in this browser profile when storage is available. Reset to sample clears that draft; Pro history has its own clear button. A state link encodes your inputs in its URL: share only non-sensitive rows. Browser history, clipboard and anyone receiving the link may retain it. Optional AI use below leaves this device; it is not required.
Data note: Everything runs in this browser tab on the walk time docket: your walking leg | distance units | pace minutes per unit stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.
Perspective: Before: Cobbles, hills and photo stops change pace by minutes per kilometre. After: the walk time docket shows the working beside each named row so the reader can change the assumption and inspect the consequence.
2 · Read the walk time docket
Duration arithmetic on the distances and paces you supply. Not a route guide, fitness assessment or navigation authority; check terrain, access and transport against current maps and local advice, and match the plan to your own health needs. Elevation gain is deliberately outside this check — plan it in the ascent-time allowance tool linked in the method.
Paid layer: walk time docket print and history
one-time step · the free reading above stays complete
Free tier
- one complete walk time docket run in the app
- three samples plus unlimited article-demo runs
- unwatermarked result text and an explicit, user-triggered state link
What $4 one-time adds
- print the walk time docket with its row workings
- CSV of walk minutes and row explanations
- last five reading summaries saved in this browser profile
$4 once for repeated filing of the walk time docket, not for a better answer. Illustrative time basis: avoiding one five-minute manual reformat per saved reading; no market-price or guaranteed-savings claim.
Local history (this device)
- No saved runs yet — your first run files here.
Checkout is unavailable until a payment link is configured. The optional unlock is browser-local, profile-scoped and best-effort, not server-verified access. Clearing browser data can remove it; there is no account or cross-device recovery.
Boundary and sources
Duration arithmetic on the distances and paces you supply. Not a route guide, fitness assessment or navigation authority; check terrain, access and transport against current maps and local advice, and match the plan to your own health needs. Elevation gain is deliberately outside this check — plan it in the ascent-time allowance tool linked in the method.
- Method: The day’s window after breakfast, museum tickets and dinner reservations. Two hours of walking inside a ten-hour day is two hours, not ten.
- All sample records are invented examples. The app does not fetch measurements, policies, files or personal records.
- Google’s official pricing page, fetched 2026-09-29, lists free-tier access including AI Studio. Optional formatting only; limits and availability can change. Free-tier content may be used to improve products. Never paste private records there.
Mechanism: competence-autonomy-loop
Optional AI formatting, not calculation
For this walk time docket, use the free AI Studio interface only if available to you, with no paid API key. Manual entry completes the same workflow for free. Supply only fictional or non-sensitive notes. Review its output against the source; never paste unresolved questions into the numeric rows.
Format my non-sensitive notes for a walk time docket. Return plain rows only: walking leg | distance units | pace minutes per unit. Preserve supplied quantities exactly. Do not guess missing values; list questions separately. Do not calculate or add advice. I will check every row before pasting into the local tool.
Accepted schema: walking leg | distance units | pace minutes per unit. No AI response is executed as code.