Separate Recorded Clinic Waiting Time from Consultation Time — Free
A clinic visit can take an hour without an hour of clinician contact. Record three clocks once, then keep the waiting segment separate from the consultation segment before discussing scheduling or access with the practice.
The proof surface
Question-prioritising guides organize what to ask during an appointment. This strip audits what happened around one: ordered observed clocks, two elapsed segments and a pooled waiting denominator. It neither predicts queue length nor rates clinical care.
InputVisit code | check-in HH:MM | consultation start HH:MM | consultation end HH:MM; waiting-share review mark (%)
Rare deviceQuestion-prioritising guides organize what to ask during an appointment. This strip audits what happened around one: ordered observed clocks, two elapsed segments and a pooled waiting denominator. It neither predicts queue length nor rates clinical care.
Output artifactPooled observed waiting share 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: North visit | 09:10 | 09:42 | 10:02; West visit | 11:00 | 11:18 | 11:48. Waiting-share review mark (%) = 60. Pooled observed waiting share: 50 % waiting. All records are invented.
Before using the queue-time strip
Use clocks from the same local day and the same time source. Check-in means the moment you actually registered, not the appointment time printed on a reminder. Consultation start and end refer to one continuous segment you can identify; if a visit contains several separate contacts, do not pretend they form one uninterrupted consultation. Give visits anonymous codes rather than names, diagnoses or provider identifiers. The review percentage is your own discussion threshold, not a service standard. Several visits may be pooled only when you intend to compare the same recording convention. An early check-in inflates the measured waiting period without establishing a delay attributable to the clinic.
Why the flat version breaks
Averaging the printed percentages
A short visit and a long visit do not contribute equally to elapsed time. Averaging their shares can conceal where the minutes went. Use the pooled minute denominator shown in the strip; keep individual percentages for comparing recording circumstances rather than substituting their average for the total.
Calling every waiting minute lateness
Check-in can precede a booked time, and a patient can arrive late. This log contains neither scheduled appointment time nor staff explanations. Keep the word waiting literal. If your question concerns lateness, obtain the relevant booked times and discuss them separately rather than adding an accusation to the calculated share.
Joining clocks across midnight
A 23:50 check-in and 00:20 consultation start are not an ordered same-day row. They need dated observations, not a quiet correction by this tool. The parser rejects that sequence and retains your previous reading so you can return to the source without losing either the input or the useful result.
How to work the queue-time strip
Choose one observation convention
Write down what each clock means before collecting a week of visits. A consultation that starts with a nurse and finishes with a doctor may need a different log from a single practitioner contact. Keep that distinction in the anonymous visit code or your private source notes. The calculator cannot recover segments you did not observe.
Enter clocks in actual sequence
Use 24-hour HH:MM, including leading zeros. The parser requires check-in no later than start, and start no later than end; end must be later than check-in. Overnight visits are outside this single-day model. Do not repair a suspicious time by guessing an extra day, and do not enter a booked time in place of an observed clock.
Reconcile both segments before the share
Subtract check-in from start for waiting minutes, and start from end for consultation minutes. Add both segments for the visit window. Across multiple records, sum waiting minutes first and divide by the sum of visit-window minutes. That weighting gives a long visit its actual contribution instead of treating every visit as an equal-sized sample.
Take a recording question to the practice
Save the clocks and the definition of consultation alongside the share. Ask reception whether there is a better arrival convention or a useful way to record interrupted visits. A marked row is an invitation to discuss the particular segment, not evidence of negligent care or a promised improvement if an appointment is moved.
What the queue-time strip separates
Question
Before
Inspect this instead
Averaging the printed percentages
A short visit and a long visit do not contribute equally to elapsed time. Averaging their shares can conceal where the minutes went. Use the pooled minute denominator shown in the strip; keep individual percentages for comparing recording circumstances rather than substituting their average for the total.
Enter clocks in actual sequence
Calling every waiting minute lateness
Check-in can precede a booked time, and a patient can arrive late. This log contains neither scheduled appointment time nor staff explanations. Keep the word waiting literal. If your question concerns lateness, obtain the relevant booked times and discuss them separately rather than adding an accusation to the calculated share.
Reconcile both segments before the share
Joining clocks across midnight
A 23:50 check-in and 00:20 consultation start are not an ordered same-day row. They need dated observations, not a quiet correction by this tool. The parser rejects that sequence and retains your previous reading so you can return to the source without losing either the input or the useful result.
Take a recording question to the practice
This queue-time strip 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.
Observation arithmetic only: this does not diagnose, assess care quality or establish a service breach. Ask the clinic's scheduling team to confirm how interrupted or overnight visits should be recorded; discuss clinical concerns with a qualified clinician.
Data note: The queue-time strip processes Visit code | check-in HH:MM | consultation start HH:MM | consultation end HH:MM 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 paper ticker strip
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the queue-time strip 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 queue-time strip 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.
Observation arithmetic only: this does not diagnose, assess care quality or establish a service breach. Ask the clinic's scheduling team to confirm how interrupted or overnight visits should be recorded; discuss clinical concerns with a qualified clinician.
What this is built on
Method: Subtract check-in from start for waiting minutes, and start from end for consultation minutes. Add both segments for the visit window. Across multiple records, sum waiting minutes first and divide by the sum of visit-window minutes. That weighting gives a long visit its actual contribution instead of treating every visit as an equal-sized sample.
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-10-01, 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: an appointment felt like one undifferentiated hour. After: observed waiting and consultation minutes have separate, inspectable denominators.
Three worked readings, with different inputs
Sample A — typical inputs
North visit | 09:10 | 09:42 | 10:02
West visit | 11:00 | 11:18 | 11:48
North contains 32 waiting minutes and 20 consultation minutes; West contains 18 and 30. The combined visit window is 100 minutes, of which 50 are waiting. The pooled share is therefore 50%, not the average of two differently sized visit percentages. North's own share is approximately 61.538462%, so it receives the reader's 60% review mark even though the pooled share does not.
This record has seven minutes before consultation and 23 minutes in consultation. Seven divided by the full 30-minute window gives 23.333333%. Changing the consultation end changes the denominator as well as the total visit time. The result does not say whether the appointment was late: no booked appointment time has been supplied, and check-in may have been deliberately early.
Check-in and consultation begin together, so the observed waiting segment is zero. The 25-minute consultation still supplies a positive denominator. A record with all three clocks equal would be rejected instead of producing a made-up percentage. Zero waiting is an arithmetic observation, not a claim that the whole visit had no delays, because reception, procedures and checkout outside these clocks are unmeasured.
Optional AI formatting, never the calculation
Manual entry completes this queue-time strip 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 queue-time strip. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string", "string"]}], "setting": "string"}. The columns are Visit code | check-in HH:MM | consultation start HH:MM | consultation end HH:MM; the setting is Waiting-share review mark (%). 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.