Find the overlap. Keep the decision honest.

Start with times that describe the same meeting.

Imagine four adult members of an invented planning group, identified only as A, B, C and D. They need one thirty-minute discussion, not three separate meetings. Their coordinator writes three candidate windows: Tuesday 15:00 to 15:30, Thursday 15:00 to 15:30 and Friday 10:00 to 10:30, all using the same stated local time basis. These are fictional inputs, not dates available to book on this site. Giving each option a duration makes the question answerable: being free at the starting minute is not the same as being free for the discussion.

The coordinator first checks that the options describe the intended activity. A candidate that leaves no time for the actual discussion is not useful just because its opening minute fits. Likewise, a remote conversation and an in-person meeting require different preparation. Put that distinction in the question before collecting answers. A reader should not need to infer whether travel, equipment setup or a second conversation has quietly become part of the request.

Does that make a simple poll too detailed? Only include context that changes the answer. The duration, time basis and kind of meeting matter here; the group's entire history does not. Three comparable windows are easier to examine than a long list mixing different lengths and purposes. This page supplies no candidate-creation control, so writing these windows is an exercise the coordinator performs through their established process.

Three answers still need a separate place for no answer.

In the fictional Tuesday column, A and D mark available, B marks if need be, and C marks no. The count is two available, one conditional and one unavailable. On Thursday, A, B and C mark available while D marks if need be. On Friday, A, B and D mark available while C has supplied no answer. These are three different situations even though both Thursday and Friday show three available marks. Friday's missing answer must remain missing.

The phrase if need be carries useful information because it does not pretend a stretch is the same as an easy choice. It also does not require a person to explain their private circumstances to the group. The coordinator can ask whether the conditional option is workable for this particular meeting without asking for a personal account of why. A no remains a no; the design's third state does not authorise the coordinator to reinterpret an unavailable answer as a negotiable one.

A blank cell cannot be converted into no, available or conditional merely to finish the arithmetic. It might mean the person has not considered the options, has not supplied an answer or is working from another version of the question. The example establishes none of those causes. The useful output is therefore a count with an explicit missing response, not a guessed explanation for the gap.

The strongest-looking count can still leave a decision open.

Thursday has answers from all four adults and no outright unavailable mark, but it includes D's condition. Friday has three available marks and one unknown. Tuesday has a known conflict. The manual summary can say exactly that. It cannot truthfully announce that everyone is free on Friday, and it cannot describe Thursday as completely unconditional. The coordinator's next question is narrow: whether D's Thursday condition is workable, or whether C can clarify Friday. This is a human choice between unresolved questions, not an automatic winner.

If two candidates carry the same counts, the totals alone do not explain which one the group should use. A relevant constraint already established for the meeting may break the tie. A preference introduced afterwards should be identified as a new consideration rather than disguised as something the responses proved. The point of the overlap is to make the decision easier to explain. A count cannot absorb every judgment about the purpose, timing and participants of a meeting.

What if waiting for one clarification takes longer than choosing immediately? The coordinator can make a bounded choice through the group's actual arrangements, but the summary must retain the missing fact. A proposed Thursday discussion with D's condition unresolved describes a different state from a confirmed Thursday discussion. Speed does not make those sentences interchangeable. Whenly supplies no automatic follow-up or confirmation through this page.

A changed duration deserves a fresh answer, not a recycled total.

Now change one fact in the earlier fictional case: the coordinator discovers the discussion needs fifty minutes rather than thirty. The original Tuesday, Thursday and Friday marks concern the shorter windows. The old totals remain an accurate description of those original answers, but they no longer establish availability for the longer discussion. Calling the revised window the same Thursday option hides a material change. The extra twenty minutes is part of what people need to consider.

A useful manual revision note says: The discussion now needs fifty minutes. Earlier marks described thirty-minute windows. Please consider the revised end times; the earlier count is retained only as a record of the shorter question. This is authored wording for an invented situation. The page does not issue the request, track its recipients or associate an answer with a stored version. It explains why an organiser should identify the changed input before relying on the result.

The coordinator can preserve progress without pretending the longer meeting is settled. For example, Thursday may remain a plausible candidate because no one rejected its original start, while its revised end remains unconfirmed. Plausible is the accurate word. A previous available mark is not evidence that another twenty minutes fits. The same reasoning applies if the meeting changes location or gains a preparation requirement that affects the person's answer.

What if the change seems too small to justify asking again? The relevant question is whether it changes what people agreed they could do. A wording correction that clarifies the same window is different from an extension of that window. The example establishes no threshold for making that judgment automatically. The organiser should state the actual change and preserve the uncertainty it creates, rather than relying on a familiar candidate label to suggest that nothing important changed.

No clean overlap is a result worth keeping.

A second fictional exercise offers two windows to three adults. In the first window, A and B are available and C is unavailable. In the second, B and C are available and A is unavailable. Every person has answered, and neither candidate works for all three. There is no missing mark to chase and no arithmetic error to repair. The manual output is a known conflict in each candidate. A scheduling explanation should be able to stop at that result without manufacturing a winning time.

The organiser has several possible questions to examine through the group's actual arrangements: whether different windows are possible, whether the discussion can be shorter, or whether the purpose really requires all three adults together. Each changes a different part of the original task. Moving to a new date changes the candidates. Shortening the discussion changes the duration. Changing the participants changes the group. None is merely a different way of adding the same marks.

The useful next note names the selected change and keeps its consequence visible. We have no common window among the two proposed options, so I am asking about two different windows is clear. Everyone is nearly available makes the conflict sound smaller without resolving it. The page does not supply an automatic search across calendars, infer another person's free time or negotiate a substitute group. Its role here is to make the unresolved choice understandable.

The objection that a poll should always end with a winner confuses a successful collection of answers with a successful meeting arrangement. Sometimes the answers show that the original proposal cannot satisfy its own requirement. Preserving that result saves the organiser from acting on a false conclusion. A good stopping point is not a failed explanation; it is an explanation that keeps the decision within the facts supplied.

A chosen time is not a room held against another booking.

Suppose the adults eventually agree on Thursday. That settles their intended meeting window in this invented example. It does not establish that a room, a piece of equipment or any other limited resource is reserved. The existing Whenly description separates its planned poll-to-booking connection from the shared booking floor described by the family. That connection is not a working Whenly surface. A reader should not leave this page believing the illustrated choice has created a booking.

The coordinator's useful handoff names the agreed window and the outstanding resource check separately: the group has chosen Thursday 15:00 to 15:30; the room arrangement still needs confirmation through the process that actually controls it. If that check fails, the response is a real constraint to revisit, not a reason to pretend the earlier group decision never happened. Keeping both facts helps explain why another option must be considered.

The result of this walkthrough is a legible decision note, not stored availability, a booked room, a calendar event or a sent reminder. It identifies the question asked, the response states used, the missing facts and the difference between a group preference and a resource hold. The mechanism page examines these parts separately; the getting-started page helps frame an inquiry without promising a poll or a booking in return.

End with a status note that survives outside the grid.

A final note is useful because the next person may never see the earlier marks. In the first exercise, imagine that the adults have clarified the conditional answer and agreed on the original Thursday window. The coordinator can write: The group has agreed on Thursday, 15:00 to 15:30, for the stated discussion. The room arrangement remains open. That note identifies the outcome and the remaining dependency without requiring the reader to reconstruct every intermediate count.

If the room is later confirmed through the organisation's actual process, the coordinator can update that part of the note with the basis for the confirmation. The earlier availability answers still do not prove the resource action. Likewise, recording the time in an established calendar is a separate action from deciding on it. The current Whenly page performs none of those actions and provides no delivery or receipt evidence for the written notice.

A useful final reread checks three nouns: the group, the window and the activity. Are they the same ones the answers described? Then check the verbs. Preferred is not booked; proposed is not confirmed; written is not sent. This small review catches a common source of confusion: a careful sequence of decisions being flattened into an overly confident closing sentence. The output remains an honest account of the particular work actually established.