The same timing question changes with the group.

A committee needs one shared discussion, not a collection of appointments.

In an invented adult committee, four role holders need to examine the same draft together. The organiser offers two forty-minute windows and states that the discussion concerns one draft version. Each person answers against both windows. The input is their availability for that shared task; the result the organiser needs is one candidate that can support a group discussion. Four separate appointments are not an equivalent result because the participants would not hear the same conversation.

The awkward case is a window that suits three people while the fourth has not answered. A majority count may be useful information, but it does not by itself settle whether the committee's actual arrangement allows the discussion to proceed. The writer should preserve the unanswered role and ask the responsible adult to decide what that means. This example supplies no attendance rule, quorum requirement or eligibility decision. It simply shows why the scheduling question and the group's decision process must remain distinct.

Is a group poll excessive for four people? Sometimes a short exchange is enough. The important distinction is whether the organiser is repeatedly reconciling several people against the same choices. If everyone already shares a known meeting time, another availability exercise can add work. Whenly's group-first purpose is most understandable where a real overlap question exists, rather than wherever a calendar happens to be involved.

A workshop has people, duration and preparation to reconcile.

Consider a fictional adult materials workshop with a facilitator and three colleagues. They are comparing two ninety-minute windows for a tabletop demonstration. One colleague can attend the first sixty minutes of either window but cannot stay for the full activity. That answer does not establish availability for the proposed ninety-minute session. The organiser can clarify whether a shorter activity meets the purpose, but shortening the session changes the question and should be stated before the group answers again.

Preparation creates another distinction. The facilitator may need access to the table before the participants arrive. A response about attending the workshop says nothing about whether that setup period is available. Keep the participants' discussion window separate from the resource window the organiser must arrange. The existing Whenly design includes a proposed connection from a selected time to booking; this page provides neither that connection nor a way to hold the table.

A useful manual output might say that the group prefers the afternoon window for a sixty-minute revised demonstration, with setup arrangements still open. That is a modest, actionable account. It does not imply every original requirement was met or that the equipment is reserved. The objection that these details belong elsewhere is partly right: the group need not manage the resource. The organiser still needs to know that a favourable availability count has not solved that separate dependency.

A representative is not automatically an answer for an entire team.

In a separate invented case, two adult planning teams each nominate one person for a cross-team conversation. The organiser asks those two representatives about three windows. Their answers describe the representatives' availability. They do not establish that every member of either team is free, that the teams agree on the agenda, or that either representative can make every decision discussed. A short scheduling note should name the actual group being coordinated.

This is where a broad label such as everyone can mislead. If everyone means the two invited representatives, say that. If the task requires another adult whose role has not been included in the question, the apparent overlap is incomplete for that larger task. Adding that person is a change in scope, not a correction to the arithmetic. The organiser should distinguish a missing answer from a missing participant in the original question.

The output can remain simple: both representatives have indicated the second window is available; the organiser still needs to establish whether the stated discussion can be held by those representatives alone. Nothing in this example allocates organizational authority or provides a team directory. It gives the coordinator a precise way to describe what the availability answers cover, and a clear point at which to stop claiming more.

A recurring group still needs to say which occurrence it means.

An invented adult reading group usually meets on the first afternoon of the month, but it is considering a different time for one discussion. The coordinator's question concerns that single occurrence. An available answer for the replacement window does not establish a new recurring arrangement. The manual invitation should identify whether the group is choosing one exception or changing its regular pattern. Without that distinction, two readers can supply apparently compatible answers to different questions.

The original fictional input is simple: one existing meeting needs another forty-minute window; two alternatives are under discussion; the regular pattern is otherwise outside the question. A useful output says which alternative the adults prefer for that occurrence and leaves the recurring arrangement alone. If the organiser wants to reconsider the whole pattern, that is a broader question to state separately. This example does not demonstrate a recurrence engine, calendar synchronisation or an automatic exception rule.

A recurring label can be convenient shorthand, but it is not a substitute for the occurrence being discussed. The coordinator should not rely on next time if people may interpret that phrase differently. Put enough detail in the established communication for the group to recognise the intended discussion. The example uses no actual meeting history or participant records; it illustrates the scope distinction with invented facts.

Does this belong to scheduling or simply clear writing? It belongs to both. The response is meaningful only in relation to the question. When an occurrence and a recurring pattern are confused, adding the marks accurately still produces an answer to the wrong task. Whenly's concept addresses group availability; the reader's description of the activity determines what that availability means.

Two connected conversations can require two separate choices.

In another fictional adult planning exercise, one group needs a short preparation conversation before a larger review. The organiser is tempted to collect everyone's availability in a single grid and pick the column with the most marks. But the preparation conversation includes only two adults, while the review includes four. The order also matters: the preparation needs to happen first. One undifferentiated count cannot establish both arrangements.

A clearer manual approach states each question on its own terms. The two adults compare windows for the preparation task; the four compare windows for the review, with the dependency named. If the chosen preparation window falls after the proposed review, the organiser has found a conflict to resolve. No amount of favourable availability in the review column changes that order. This is a reasoning example, not a dependency scheduler built into Whenly.

The output can preserve both pieces of progress: a suitable preparation window is identified, but the review choice still needs to follow it. Alternatively, the review may have a clear group preference while the preparation remains unresolved. The organiser should not call the entire sequence arranged until the relationship between the two is actually established through their process. A partial result is useful when its boundary is visible.

What if a reader needs several connected tasks rather than one group meeting? That is valuable scope information for an inquiry. It explains why a find-a-time concept alone may not cover the work. Describe the dependency without assuming a workflow engine, automatic calendar search or resource reservation exists. The page's family links offer context for comparing kinds of scheduling work, not a promise that this sequence can be executed here.

Some scheduling problems start after the overlap is already known.

A fixed list of workshop places is a different problem from finding a shared time. If the organiser has already set Thursday afternoon and people choose among available places, the task is allocation against existing slots. If one adviser offers individual appointments, each visitor may need only that host's availability. Whenly's group-poll concept is about choosing one time across a group. Describing the distinction helps a reader avoid treating every scheduling brand as interchangeable.

The family links identify related front doors, not evidence that a particular service is deployed or an integration is available. A sensible inquiry describes the task before choosing a label: one group needing one time, individuals choosing separate appointments, or several people filling fixed places. Include the kind of decision and the main unresolved constraint. There is no need to send a participant list to explain those differences.

If the reader's task combines these jobs, separate them in the discussion. Finding an afternoon for a group, allocating a room and filling individual places can produce three different outcomes. A well-written scope note keeps the owner of each outcome visible. These situations are useful precisely because they do not collapse every dependency into a single poll result. The current Whenly site explains that concept and its limits; it supplies no operational surface for carrying out these examples.