See what came back — and why.
An illustrative booking change, with fictional people, observations and results. Explore the findings, their evidence and the work still to do.
Members can cancel their own unpaid court bookings
Three sentences, four checks · staging.courtline.example · as Member A and Member B, your test accounts.
- 01A signed-in member can cancel a booking from My bookings only if it is their own and still unpaid.
- 02Cancelling must release the shared slot so another member can book it straight away.
- 03 04Bookings made by someone else, and bookings already paid, show no Cancel action and cannot be cancelled.
- ENVIRONMENT
- staging.courtline.example
- ACCOUNTS
- Member A and Member B, your test accounts
- OCT 27
- Initial permission: sign in and view as Member A or Member B; cancel bookings we create as Member A; no payments.
- OCT 28
- 9:48 AM we asked whether we may create a booking as Member B for check 03; 9:55 AM you answered: “Not now. Use existing data only.”
- NOV 2
- From the report, you widened it: create and cancel unpaid bookings as Member A or Member B; payments still not permitted.
Cancellation passed. Immediate release is still unverified.
Cancellation passed. A fix improved slot availability, but immediate release is still unverified. Two other checks are unfinished. The table shows each result and its date.
Works as the issue says: cancelled from My bookings as Member A, list and response watched.
Failed on Oct 28: the slot stayed taken after the cancellation. After your fix, on Nov 3, it was free a minute later and bookable — whether it comes free straight away is not yet shown.
Not yet checked. No observation of another member’s booking was recorded.
Not yet checked: no paid booking existed, and the issue rules payments out.
Each result keeps its date. Not verified means there is not enough evidence for a verdict. Your team decides whether to release.
The records, observation by observation.
The original and the retest stay separate records. Each observation names who looked and when; opening one shows the screen or response behind it.
Own unpaid booking can be cancelled from My bookings
Oct 28 · the original run
Passed · Oct 28 · nothing open
Passed on Oct 28, 3 min 05 s. Not retested on Nov 3 — the retest covered check 02 only; the mark keeps its date so it is never read as newer than it is.
Nothing open Not retested on Nov 3; the Oct 28 result stands, with its date.
Open an observation to see the screen or response behind it.
Opened My bookings, cancelled #4471.
POST /bookings/4471/cancel → 200
{ "status": "cancelled" }Who continues on this record Nothing open Not retested on Nov 3; the Oct 28 result stands, with its date.
A cancelled slot comes free for other members
Oct 28 · the original run
- 10:02 AM · as Member ABooking #4471 cancelled from My bookings — the condition this check starts from. Open that observation in record 01
Next on this check: the Nov 3 retest, a separate record →
Failed · Oct 28
The slot stayed Unavailable to another member twenty minutes after the cancellation, and the response still named the cancelled booking as holder. Returned Oct 28, 10:31 AM, human-verified. The fix was yours to make; one retest of the same scope within 14 days is included.
Your fix, then the retest The fix was yours to make; the same-scope retest after it is a separate record, Nov 3.
Open an observation to see the screen or response behind it.
Opened the Court 2 schedule for Thu Nov 5, after a reload.
Who continues on this record Your fix, then the retest The fix was yours to make; the same-scope retest after it is a separate record, Nov 3.
Same slot, ten minutes later, page reloaded.
Who continues on this record Your fix, then the retest The fix was yours to make; the same-scope retest after it is a separate record, Nov 3.
Signed out and in again, opened the same schedule.
Who continues on this record Your fix, then the retest The fix was yours to make; the same-scope retest after it is a separate record, Nov 3.
Read the slots response behind the third observation.
GET /courts/2/slots?date=2026-11-05 → 200
{ "slot": "10:30", "status": "unavailable", "held_by": 4471 }Who continues on this record Your fix, then the retest The fix was yours to make; the same-scope retest after it is a separate record, Nov 3.
A cancelled slot comes free for other members
Nov 3 · the retest of check 02 only
← The Oct 28 original, Failed · kept apart; this retest does not change it.
Not verified · Nov 3 · ours, next
Why no conclusion: the first look came a minute after the cancellation and after a reload. The slot may have been released at once or at any point in that minute, and these observations cannot tell those apart — so “straight away” is neither shown nor contradicted. Not Passed, not Failed; the Oct 28 failure did not recur. Next, in the original scope: observe the release itself as Member B from the moment of a cancellation. Nothing is needed from you; no extra credits; 9 min 12 s, no credits, and the included retest is not used by a check that reached no result.
Ours · next Observe the release itself from the moment of a cancellation. No extra credits.
Open an observation to see the screen or response behind it.
Cancelled a new booking, #4502 — Court 2, Thu Nov 5, 10:30–11:00, unpaid, ours.
POST /bookings/4502/cancel → 200
{ "status": "cancelled" }Who continues on this record Ours · next Observe the release itself from the moment of a cancellation. No extra credits.
The release itself — not observed.
Who continues on this record Ours · next Observe the release itself from the moment of a cancellation. No extra credits.
Opened the Court 2 schedule after a reload, one minute after the cancellation.
GET /courts/2/slots?date=2026-11-05 → 200
{ "slot": "10:30", "status": "available", "held_by": null }Who continues on this record Ours · next Observe the release itself from the moment of a cancellation. No extra credits.
Booked the released slot — allowed since Nov 2.
POST /bookings → 201
{ "id": 4503, "court": 2, "slot": "10:30", "status": "booked", "paid": false }Who continues on this record Ours · next Observe the release itself from the moment of a cancellation. No extra credits.
Someone else’s booking shows no Cancel action
Oct 28 · the original run · not run
- The target check was not run on Oct 28 — no observation is claimed for it. Not retested on Nov 3.
Not verified · Oct 28 · ours, next
The target check was not run, and there is no observation proving the rule. Ours next, in the original scope: consider the existing #4466 as Member B, establish a usable route and run the check; creating a booking as Member B, allowed since Nov 2, is an additional route. Nothing is needed from you, and completing the original scope costs no extra credits.
Ours · next Establish a usable route with the permitted accounts and run the check. No extra credits.
A paid booking shows no Cancel action
Oct 28 · the original run · not run
- The target check was not run on Oct 28 — no observation is claimed for it. Not retested on Nov 3.
Not verified · Oct 28 · needs from you
The target check was not run — no observation is claimed for it. It needs a paid booking in the environment that we may use; an existing one is enough. Only if one has to be made would we also need permission for one test payment. Until then 04 stays Not verified inside the agreed scope, with its reason.
Needs from you A paid booking we may use — an existing one is enough.
Questions, permissions and follow-through.
On the issue: the panel exchange and Jira notifications
The checks, the reports, and the question with your answer live in the Checktide panel on BOOK-218. Jira received three short notifications from Checktide about this change — not the only comments in the whole issue.
Answered on Oct 28 — a past exchange; nothing is waiting. Check 03’s current facts are in record 03.
Permissions, as they stood
Oct 27 · Initial permission: sign in and view as Member A or Member B; cancel bookings we create as Member A; no payments.
Oct 28 · 9:48 AM we asked whether we may create a booking as Member B for check 03; 9:55 AM you answered: “Not now. Use existing data only.”
Nov 2 · From the report, you widened it: create and cancel unpaid bookings as Member A or Member B; payments still not permitted.
What Not verified means here
Not verified means we could not yet conclude. Sometimes there are observations and partial evidence; sometimes a condition the check needs was not available, so the check itself was not completed. Either way the reason, the agreed scope, the next step and who carries it are stated — it is never a pass, and a later stage never upgrades an earlier mark.
Continuing responsibility
Ours, next, in the original scope: observe the release itself as Member B from the moment of a cancellation. Nothing is needed from you and no extra credits.
Ours, next, in the original scope: establish a usable route with the permitted accounts — the existing #4466 as Member B first; creating a booking as Member B, allowed since Nov 2, is an additional route — and run the check. Nothing is needed from you; no extra credits.
Needs from you: a paid booking in the environment that we may use — an existing one is enough. Only if one has to be made would we also need permission for one test payment.
Credits on this example
Oct 28: 12 min 47 s on check 02 and 3 min 05 s on check 01, at $0.30 a minute billed by the second. Nov 3: 9 min 12 s, no credits — a retest of the same scope after your fix; it reached no result, so the included retest was not used. Completing the original scope on 02 and 03 costs no extra credits.
Limits of this page
The dates and timings are illustrative, not a turnaround commitment. Exploring this example does not start a verification.