Google Calendar: propose a time, then confirm the organizer’s change

Use this preparation for one ordinary, non-repeating timed event in Google Calendar on a computer. Privately confirm the selected event, account, guest or organizer role, intended date/time/timezone and authority. An unresolved role or target goes back to the owner before any action.

As a guest, open the event and use arrow beside Maybe → Propose a new time, choose a day/time, then Send proposal. Proposals exclude all-day events and more than 200 guests; a count of 200 alone does not prove availability. Stop for a missing control or different scope. The optional proposal message is separate from an RSVP Add note, which is visible to all invitees. The proposal message’s audience is not established here. Google: guest instructions.

The organizer can review and optionally accept a proposal; saving changes the event to the proposed time. A guest with permission to modify the event has a separate direct-rescheduling route. Do not substitute that route for the owner’s intended proposal. Google Workspace: role distinction.

For the organizer, open the event with a proposal, choose Review proposed time under the guest list, and use Save only for the approved change. A sent proposal is not evidence this happened. Response-email settings are separate at calendar and event level. Disabling event response emails also affects third-party RSVP visibility; Google Calendar guests’ responses remain viewable. Missing email does not establish acceptance or failure. Google: organizer instructions.

Hand back unknown saved state, guest responses and notification receipt; these instructions establish none.

Evidence: three official pages checked 2026-10-05T19:38:48Z. Sixteen synthetic manual decision cases checked; no event, account, proposal, edit or notification was accessed or performed. A distinct same-controller checker reread the sources and checked sixteen author cases plus six additional reader cases; these checks supply no independent formal coverage. Recheck by 2026-11-05T19:38:48Z or after role, event scope, controls or source changes. Follows the calendar standard [current article].