Find Meeting Windows That Reach a Chosen Attendance Count — Free
A group can have plenty of available hours but no interval with enough people together. Enter anonymous availability codes and a minimum count to see exactly which same-day segments meet it.
The proof surface
Public-testimony timers budget one speaker’s words. This rail sweeps member availability to find simultaneous headcount windows, keeps shared endpoints explicit, and does not interpret governance or voting rules.
Inputanonymous member code | available from HH:MM | available until HH:MM; minimum simultaneous attendance count
Rare devicePublic-testimony timers budget one speaker’s words. This rail sweeps member availability to find simultaneous headcount windows, keeps shared endpoints explicit, and does not interpret governance or voting rules.
Output artifactTime reaching the chosen simultaneous count 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: Member A | 09:00 | 11:00; Member B | 10:00 | 12:00; Member C | 10:30 | 11:30. Minimum simultaneous attendance count = 3. Time reaching the chosen simultaneous count: 30 qualifying minutes. All records are invented.
Before using the attendance-window rail
Use a count agreed by the organizer, not a threshold invented from a generic quorum rule. Membership classes, remote attendance, conflicts of interest and the type of decision can affect a real organization’s requirements. This instrument intentionally does not parse those rules. One anonymous member gets one interval for the same local day; split-day availability needs a separately confirmed model rather than duplicating a person and counting them twice. The displayed rail changes at every start or finish boundary so a short bottleneck cannot disappear into an average. Keep the source availability and the eventual invitation separate: the tool cannot send a calendar invite, hold a room or turn a stated window into a commitment. It helps the organizer ask a concrete scheduling question.
Why the flat version breaks
Adding availability instead of overlapping it
Three members each free for an hour need not be free together. Only simultaneous segments contribute to the chosen headcount window.
Counting a shared endpoint as a meeting
A person leaving exactly when another arrives creates no positive-duration overlap. End-exclusive intervals keep that boundary from manufacturing a slot.
Calling the count a legal quorum
Governance rules can specify membership classes and decision types. This tool checks a chosen count only and cannot determine whether a meeting or vote is lawful.
How to work the attendance-window rail
Use anonymous unique member codes
Each code represents one person and one continuous interval. Do not paste names, contact details or reasons for absence. Duplicate codes are rejected because counting the same member twice would falsely increase simultaneous attendance.
Keep one local day and clock
Use HH:MM with start strictly before finish. Overnight or multi-zone availability is outside this form. A finish at 10:00 means unavailable from 10:00 onward; exact boundary contacts do not add meeting duration.
Inspect each count segment
The sweep collects every start and end, counts active intervals between neighboring boundaries, and includes that segment’s minutes only when the count reaches your setting. The headline sums qualifying segments without merging disjoint periods into an invented continuous slot.
Confirm the rule and the invitation
Ask the chair or organizer to confirm the applicable attendance rule, who counts and any minimum continuous meeting length. Contact the group to confirm attendance through the usual process before announcing that a decision-making meeting is valid.
What the attendance-window rail separates
Question
Before
Inspect this instead
Adding availability instead of overlapping it
Three members each free for an hour need not be free together. Only simultaneous segments contribute to the chosen headcount window.
Keep one local day and clock
Counting a shared endpoint as a meeting
A person leaving exactly when another arrives creates no positive-duration overlap. End-exclusive intervals keep that boundary from manufacturing a slot.
Inspect each count segment
Calling the count a legal quorum
Governance rules can specify membership classes and decision types. This tool checks a chosen count only and cannot determine whether a meeting or vote is lawful.
Confirm the rule and the invitation
This attendance-window rail 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.
Availability arithmetic only, not legal, governance or quorum advice. It does not verify membership eligibility, meeting notice, remote participation rules or a valid vote. Confirm the rule and proposed slot with the chair or qualified governance adviser; retain anonymous codes and obtain attendance confirmation separately.
Data note: The attendance-window rail processes anonymous member code | available from HH:MM | available until 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 attendance-window rail 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 attendance-window rail 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.
Availability arithmetic only, not legal, governance or quorum advice. It does not verify membership eligibility, meeting notice, remote participation rules or a valid vote. Confirm the rule and proposed slot with the chair or qualified governance adviser; retain anonymous codes and obtain attendance confirmation separately.
What this is built on
Method: The sweep collects every start and end, counts active intervals between neighboring boundaries, and includes that segment’s minutes only when the count reaches your setting. The headline sums qualifying segments without merging disjoint periods into an invented continuous slot.
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-09-30, 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: total available hours hid simultaneous headcount. After: each boundary segment shows who is counted anonymously, without claiming a legal quorum.
Three worked readings, with different inputs
Sample A — typical inputs
Member A | 09:00 | 11:00
Member B | 10:00 | 12:00
Member C | 10:30 | 11:30
A is available until 11:00, B begins at 10:00 and C begins at 10:30. All three are simultaneously available only from 10:30 to 11:00, a thirty-minute interval. Other displayed segments show one or two available members and contribute zero qualifying minutes. The names are anonymous sample codes, not a real committee. Reaching a count of three does not establish a legal quorum or assure that each person will attend; it only exposes the overlap in the supplied intervals.
Sample B — changed plan
Member A | 09:00 | 12:00
Member B | 10:00 | 12:00
Member C | 10:30 | 11:30
Extending A’s availability to noon lets the three-member overlap continue until C leaves at 11:30. The qualifying time grows to sixty minutes. The change is attributable to one interval, not to a different meeting rule. If several disjoint qualifying windows appear, their durations are added for the headline, but they are not one continuous meeting. Read each segment before choosing a meeting length; a total of sixty minutes split into two half-hours may not support a sixty-minute agenda.
Sample C — boundary convention
Member A | 09:00 | 10:00
Member B | 10:00 | 11:00
Member C | 10:00 | 11:00
At exactly 10:00 A’s interval ends while B and C begin. The model uses start-inclusive, end-exclusive intervals, so a shared endpoint does not create a positive-duration three-person overlap. The maximum simultaneous count is two and the qualifying total is zero. A zero result remains a visible schedule record with the insufficient segments, not an empty page. Ask about another time or a different attendance requirement through the organization’s proper process.
Optional AI formatting, never the calculation
Manual entry completes this attendance-window rail 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 attendance-window rail. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string"]}], "setting": "string"}. The columns are anonymous member code | available from HH:MM | available until HH:MM; the setting is Minimum simultaneous attendance count. 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.