The two-minute check that stops AI from turning unreviewed asks into scheduled meetings
Confirm whether an AI assistant can create calendar events, decide if that write path should stay on, and protect focus blocks before it schedules anything.

A full calendar is a debt
Managers often treat a packed calendar as evidence of demand. The cost appears later, when a recurring invite arrives before anyone has weighed the ask. The meeting itself is only the first cost. The follow-up, the context switch, and the hour that was already reserved are the rest. An assistant that can schedule on its own changes the risk. It does not remove the need to review. It makes the review step shorter.
The write path is the switch that matters
Personal Intelligence in Google's AI Mode now connects directly to Google Calendar. That connection lets the assistant add new calendar entries without requiring the user to switch applications. Calendar is the first connected app that AI Mode can use to take action for a user, not merely provide information. Calendar joined Gmail and Google Photos as the third app supported by Personal Intelligence in AI Mode. The distinction matters because a manager can read a calendar and still keep control. A manager who lets the assistant write to the calendar has changed the control model.
The write path is the decision point. A manager can still use the assistant for information and keep the schedule under manual control. The problem starts when the assistant can create entries on its own. The auto-scheduling risk is whether the manager has a review step before the entry appears in the calendar.
The write-path check belongs before the assistant gets access
The check is short enough to do before the next invite arrives. It is also the only place where the manager keeps control. If the assistant can write to the calendar, the manager must decide whether that write path stays enabled. The list below is the minimum.
- Confirm whether Google Calendar is opted in to Google Search connected apps.
- Confirm whether the assistant can create events without you switching apps.
- Decide whether that write path should stay enabled.
- Mark focus blocks busy so drafts have nowhere to land.
- Confirm whether your account is eligible, because business, enterprise, and education accounts in Google Workspace are excluded from these connected apps.
Each item exists because it addresses a failure mode. The setting and capability items address the write path. Control belongs to the manager, so the decision item stays in the middle. Focus blocks need protection, so the busy-status item comes before any scheduling help. Eligibility is last because it stops a manager from assuming the feature is available. The rollout has started in the United States, while an international rollout is planned but unscheduled.
The write path should stay enabled only if the manager can review the result quickly. If the manager cannot do that, the write path should stay off. A useful default is to keep it off until the manager has a habit of checking assistant-created entries. If the manager keeps it on, focus blocks should be protected first. The assistant should not be able to place an event in a block that is already reserved for focused work.
Unreviewed invites should be cancelled before they become recurring
Review recurring invites that arrived without a clear owner. If no one can say why the meeting exists, the meeting should end. Remove the invite when the reason, owner, or stop condition is missing. Do not let a recurring invite survive because it is easier to leave it than to end it.
When an assistant-created meeting is not worth keeping, cancel it before it becomes a recurring invite. A graceful cancel names the change, gives a reason, and offers a next step. It does not apologize for protecting focus. It does not leave the invite pending. The message can be plain: the meeting is being removed, the topic can wait, and the manager will follow up if the topic becomes urgent. If the topic still needs attention, offer a shorter format.
Focus blocks need a busy status before the assistant can place an event in them. Mark them before the next scheduling request arrives. Then close the page and leave the focus blocks in place.