Check Activity Cancellation Slack Before Each Deadline — Free
Every booking on the itinerary carries its own cancellation clock, and the clocks run down together. Subtract the notice period and your buffer from the days remaining, and see which booking loses its free exit first.
The proof surface
Hotel cancellation checks price the exposure on a room rate. This audits the activities around the stay — tours, classes, day trips — by the days of free-cancellation slack each one still holds against its own notice period.
Why the flat version breaks
Assuming all bookings share the trip’s cancellation policy
Each supplier’s term governs its own row; the package headline governs almost none of them.
Counting working days as calendar days
Notice periods are written in calendar days unless they say otherwise.
Discovering the deadline after the charge posts
Slack is only useful while it is positive; negative slack is a decision, not a countdown.
How to work the cancellation slack stub
Tours, classes, transfers, tastings — one row per booking, including the ones paid in full where the terms still allow a refund window.
Today to the activity date. Update as the trip approaches; the slack is only true on the day it is calculated.
Forty-eight hours, seven days, fourteen days — the printed term, not the memory of it. The balloon flight’s fourteen-day term is the row that surprises people.
The stub reports slack days and holds the tightest. A balloon booked ten days out with a fourteen-day notice period is already four days past its free window once the buffer is added — that row gets a phone call today or is written off honestly.
What the cancellation slack stub replaces
| Question | Before | Visible working |
|---|---|---|
| Assuming all bookings share the trip’s cancellation policy | Each supplier’s term governs its own row; the package headline governs almost none of them. | Enter days until the activity |
| Counting working days as calendar days | Notice periods are written in calendar days unless they say otherwise. | Copy the notice period from the booking terms |
| Discovering the deadline after the charge posts | Slack is only useful while it is positive; negative slack is a decision, not a countdown. | Act on negative slack first |
A local arithmetic aid replaces hand calculation, not expert review. No paid AI service is needed.
Run it on the samples, right here
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.
Window arithmetic on the dates and notice terms you supply. Not contract interpretation, refund advice or a travel-insurance determination; confirm the binding cancellation terms with each supplier or your travel agent, and check insurance wording before assuming any cost is recoverable.
Data note: Everything runs in this browser tab on the cancellation slack stub: your booked activity | days until the activity | cancellation notice days stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.
Go deeper: the companion app files the same reading as a punched ticket stubs
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the cancellation slack stub reading, and holds your drafts on this device — one free run, then $ 4 one-time for the layer that keeps filing.
The cancellation slack stub reading is complete for free. The optional $4 layer adds print, row CSV and the last five local reading summaries; it does not add hidden answers. Checkout is not configured yet; the article demo remains unlimited.
Open the check activity cancellation slack before each deadline companionBoundary
Window arithmetic on the dates and notice terms you supply. Not contract interpretation, refund advice or a travel-insurance determination; confirm the binding cancellation terms with each supplier or your travel agent, and check insurance wording before assuming any cost is recoverable.
What this is built on
- Method: Forty-eight hours, seven days, fourteen days — the printed term, not the memory of it. The balloon flight’s fourteen-day term is the row that surprises people.
- 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.
Before: Each supplier’s term governs its own row; the package headline governs almost none of them. After: the cancellation slack stub shows the working beside each named row so the reader can change the assumption and inspect the consequence.
Optional AI formatting, not calculation
For this cancellation slack stub, 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 cancellation slack stub. Return plain rows only: booked activity | days until the activity | cancellation notice days. 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: booked activity | days until the activity | cancellation notice days. No AI response is executed as code.