Create and finalize a meeting poll

Short answer: Offer options, collect responses, and confirm the winning time. Begin with “Choose a short list of options that the organizer can genuinely honor.” and verify the result through the public participant path.

Before you change the setup

Identify the exact organizer, event type, public link, and time zone involved before editing anything. Save the current behavior or take a screenshot so the test has a reliable before-and-after comparison.

How to complete this task

Choose a short list of options that the organizer can genuinely honor.Start with the intended outcome and the record that controls it.
Set the organizing zone and explain the decision deadline.Review every related setting before saving so one rule does not mask another.
Share the response link and watch overlap rather than first response.Keep private data and guest-facing information clearly separated.
Confirm one winning slot and notify every participant.Complete the same path an external participant will use.

Verify the participant result

Run one successful case and one edge case. Confirm the public title, local time, available choices, duration, location, confirmation, calendar file, and private management path as applicable. Then check the organizer view and any email delivery record. A saved setting is not proof that the scheduling lifecycle worked.

Troubleshoot create a meeting poll

These are the failures reported most often for this specific task, with the cause that explains each one.

Participants voted but no time works for everyone.

That is a real result, not a fault. Reopen with a wider range, split the group, or accept partial attendance and record who is missing — do not keep re-polling the same options.

Someone wants to change their response.

Ask them to reopen the same link and resubmit before you finalize. Finalize only once, because the confirmed time becomes the authoritative record.

Participants read the times differently.

The poll displays the organizer's stated time zone. When the group spans regions, put that zone in the meeting title so the reference is unmissable.

Related Meetin.gs help

Return to the Meetin.gs Help Center for the adjacent configuration guide, or send the exact event code and expected result when the documented checks do not explain the behavior.

Create and finalize a meeting poll acceptance checklist

Use the following evidence map while completing this specific task. It ties each action to an observable result so another person can repeat the setup or diagnose it without guessing.

1. Choose a short list of options that the organizer can genuinely honor.

Write down the intended result, the organizer or account that owns it, and the exact event type or public link in scope. This prevents a correct change from being applied to the wrong record.

2. Set the organizing zone and explain the decision deadline.

Inspect the related rules and dependencies before saving. Record the previous value and the new value, including the time zone, provider account, or team owner when one controls the outcome.

3. Share the response link and watch overlap rather than first response.

Review what an invitee can see and what remains private. Keep only the context needed to complete the meeting task, and make the fallback understandable when information is missing.

4. Confirm one winning slot and notify every participant.

Complete this step from a signed-out participant session. Preserve the resulting URL or event code, displayed state, message, calendar output, and any provider response needed to prove the task worked.

Evidence type	What to record
Controlling input	The account, event type, setting, public link, and time zone used in the test.
Participant result	The exact choices, context, confirmation, or error visible while signed out.
Lifecycle result	What changes after confirmation, finalization, cancellation, reschedule, or retry.
Failure boundary	The missing permission, unavailable dependency, invalid input, or conflicting rule that prevents success.
Owner	The person responsible for correcting the setting, provider connection, content, or customer communication.

Evidence type

What to record

Controlling input

The account, event type, setting, public link, and time zone used in the test.

Participant result

The exact choices, context, confirmation, or error visible while signed out.

Lifecycle result

What changes after confirmation, finalization, cancellation, reschedule, or retry.

Failure boundary

The missing permission, unavailable dependency, invalid input, or conflicting rule that prevents success.

Owner

The person responsible for correcting the setting, provider connection, content, or customer communication.

RELATED CAPABILITY

Meeting polls

Offer a concise set of options, collect availability without accounts, and confirm the strongest overlap. Meeting polls can be tested now from the homepage scheduler through confirmation and change handling.

Review scope

Create and finalize a meeting poll: frequently asked questions

Short answers to the questions organizers ask most about create a meeting poll.

How does a meeting poll work?

You propose several dates and times, share one link, and participants mark every option they can attend. You then review the overlap and finalize a single time, which is recorded and confirmed by email to participants who gave an address.

How many options should I offer?

Five to eight combinations. Too few and no overlap exists; too many and response quality collapses. Only offer options you would genuinely honor.

Can participants change their vote?

Yes, until you finalize. They reopen the same link and resubmit. Finalize once, because the confirmed time becomes the authoritative record.

What if no time works for everyone?

Treat it as information. Widen the range, split into two sessions, or proceed with the best partial overlap and record who cannot attend. Re-polling the same options rarely helps.