Recurring meeting: how to set it up in Google Calendar and Outlook, and how to keep its history in one place (2026)

A recurring meeting is a meeting that happens on a fixed pattern — every Monday at ten, every other Thursday, the first Tuesday of the month — and lives in the calendar as one event with a repeat rule rather than as a row of separate bookings. The calendar does the arithmetic: it creates the occurrences, invites the same people to each, and lets the organizer change one date or the whole series in one place. The weekly team meeting, the one-on-one, the stand-up, the monthly client call and the quarterly review are all recurring meetings; the thing they have in common is not the topic but the fact that nobody books them twice.

This guide is the mechanics first — what a recurring meeting is and what a series is, the five settings every one needs, how recurrence is set in Google Calendar and Outlook and how a single occurrence is moved without disturbing the rest — then a series card you can copy, and the part most recurrence guides leave out: what each occurrence leaves behind and where it goes. A recurring meeting is a series, and a series is only as useful as its memory. How often each meeting should repeat is a separate question, answered in meeting cadence; this guide assumes the rhythm is chosen and shows how to put it on the calendar so that it stays there.

What a recurring meeting is — and what it isn't

Three calendar objects get called "the meeting", and the difference decides what happens when you edit one:

Two consequences follow. A change made to the series reaches every future occurrence, so the series is where the invitee list, the hour and the link are maintained. A change made to one occurrence is an exception the calendar remembers alongside the rule, so the holiday Monday is moved to Tuesday once, and the following Monday is back on schedule without anyone doing anything.

A recurring meeting is not the same as "a meeting we have often". A weekly that is booked each week by whoever remembers has a habit but no series: no fixed slot to plan around, no one place where the invitees are kept, and a different link each time, which means a different chat and a different set of notes each time. Making it recurring is a five-minute job and it removes all three problems at once.

The five settings every recurring meeting needs

Whatever the calendar, a recurrence rule is five decisions. Most arguments about a recurring meeting are about one of them left at its default.

1. The pattern. Daily, weekly, every two weeks, monthly — or a custom rule: every third Wednesday, the last Friday of the month, weekdays only. The pattern follows how long the meeting's questions can wait, which is the cadence question; the calendar only needs the answer.
2. The day and the hour. Fixed, and chosen for the people who must be there, across their time zones. A meeting at nine in Madrid is at ten in Bucharest and at four in the morning in Bogotá; the recurrence rule repeats that mistake every week until someone edits the series.
3. The length. Set on the series, not stretched occurrence by occurrence. Thirty minutes that run to forty-five every week are a sixty-minute meeting that is lying about itself.
4. The end. Three options exist in every calendar: no end, end after a number of occurrences, end on a date. A series with no end is the default and the most common mistake — it outlives the project, the team and sometimes the company. Put the end on the series: the project's close date, the quarter's end, or a date three months out at which the series is reviewed and either renewed or deleted.
5. The link. One meeting link on the series, inherited by every occurrence. This is the setting that decides where the history goes: a link that opens the same room each time keeps that room's chat, files and notes together; a link generated per occurrence scatters them. Whether the room behind the link keeps anything from one occurrence to the next is a property of the meeting tool, and the section on tools below is about exactly that.

What the rule should not carry: the agenda. An agenda is per occurrence — items, owners, minutes — and it has its own template. The series carries the standing purpose in one sentence ("unblock this week's work and decide what we don't do"); the agenda carries what this Monday is for.

How to set up a recurring meeting in Google Calendar and Outlook

Both calendars follow the same shape, and the shape is what to remember; the labels differ by version and are on the vendors' help pages.

1. Create the event as usual. Title, date and time of the first occurrence, the people. For a meeting that will run in a video tool, put the meeting link in the event now — in the location or the description, or through the tool's calendar button if it has one — so that every occurrence inherits it.
2. Open the repeat field. It sits with the date and time and reads as "does not repeat" by default. The dropdown offers the common patterns — daily, weekly on the chosen weekday, monthly on the same day, yearly, every weekday — and a custom option.
3. Choose the pattern, or build it. The custom option asks for three things: the interval (every one, two or three weeks), the days (Tuesday and Thursday, or the second Monday), and the end — never, after a number of occurrences, or on a date. Set the end.
4. Save and send. The invitation goes out once and covers the series; invitees accept the series, and every occurrence appears in their calendars.

To change the series — a new hour, a new member, a new link — open any occurrence and, when the calendar asks, choose the whole series: the change reaches every future occurrence. To change one occurrence — move this Monday to Tuesday, shorten the one before the holiday, cancel the one during the offsite — choose this occurrence only: the calendar records the exception and leaves the rule alone. The third choice, this and all following occurrences, is the one to use when the slot changes permanently from a date onward: the past stays as it was, the future follows the new rule.

To end a series without losing its past, do not delete it: deleting the series removes the past occurrences from the calendar too. Set the end date to the last occurrence that should happen, or edit this and following occurrences from the first one that should not. The past stays in the calendar, and so does whatever those occurrences linked to.

In InterMIND, recurrence is set in exactly this way, because the calendar is where it belongs: connect Google Calendar or Outlook once in Integrations, click the calendar half of New meeting or the calendar button on any meeting's row, and the calendar opens with the event pre-filled — the title, the join link and the recap link. Add the people, pick the first date and the recurrence, send. The meeting row on the Meetings page follows the dates from the calendar, including the exceptions. The one-click flow in detail, including a meeting that already met and is made recurring from its row, is in how to schedule a meeting from Google Calendar or Outlook.

A series card you can copy

One block per recurring meeting, kept where the team talks — in the channel's notes, a canvas or a pinned message — so that a new member finds the rule in words, not only in the calendar:

[Team] — [Meeting name] · series created [date] · review by [date]
Purpose: [one sentence — what every occurrence produces]
Pattern: [weekly / every two weeks / monthly] on [day] at [time, with the time zone] — [minutes]
Ends: [date, or "reviewed on" date]
Link: [one link, the same for every occurrence]
Owner: [name — changes the series, cancels an occurrence, chairs by default]
Who: [the people on the series] · Optional: [people invited to single occurrences]
Each occurrence leaves behind: [decisions, open items, the parking lot — where they are posted and by when]
History lives in: [the channel, the document, the folder — one address]
Exceptions this quarter: [holiday dates moved or cancelled, decided now]

The last two lines are the ones most series lack and the ones that cost the most: a series with no agreed address for its history is a series whose history is in whoever took notes, and a series with no exceptions decided in advance is cancelled on the morning of the holiday, when nobody can plan around it.

Four series, filled in

Weekly team meeting — weekly, Monday 10:00 CET, 30 min — ends at the quarter's end, reviewed at the quarterly
Leaves behind: decisions and open items, posted in the team channel the same day.

One-on-one — every two weeks, Wednesday 14:00 CET, 30 min — no end, reviewed when the report's role changes
Leaves behind: next steps with names and dates, visible to both. The same link every time, so both sides find the history at one address.

Client progress call — weekly during delivery, Thursday 16:00 CET, 45 min — ends on the project's close date
Leaves behind: who sends what by when, in the client's channel; the client's people are invited to the series, their occasional colleagues to single occurrences.

Monthly all-hands — first Tuesday, 12:00 CET, 45 min — no end, reviewed at the quarterly
Leaves behind: the numbers, one decision explained, every question answered or dated.

The agendas inside each of these — the items, owners and minutes — are in meeting agenda examples; the stand-up, the one-on-one and the all-hands have their own guides.

Where a recurring meeting keeps its history in the tools you already use

The calendar keeps the rule. What each occurrence produces — notes, a recap, the chat — is kept wherever the meeting tool behind the link puts it, and that differs by tool. Documented behaviour only, from the vendors' own pages; each cell names the month its fact was checked.

Read across the row for the tool your team uses, and the pattern is the same in each: the series is one event, and each occurrence leaves one document or one summary, in the language it was written or held in. The thread between occurrences — last time's open items at the start of this time — is a person's job: someone opens the previous document and reads it into the room. Where that is fine, any of the four will do and the table is the whole answer. The next section is one way the job gets done where the series needs a memory of its own, read by members who do not all read the same language.

How a series keeps its history in a channel

InterMIND is a communication space where a recurring meeting lives in a channel. The meeting link is permanent, so the room is the same every occurrence; the recurrence is set once in Google Calendar or Outlook, on an event the product pre-fills with the join link and the recap link. Whatever the pattern, the channel keeps the whole series in one place and in each member's language: the chat is translated per reader — each member types in their own language and reads the others in theirs, with the original one toggle away — and the channel keeps the recap of every past session, not only the latest, so the weekly of three weeks ago is a switch between sessions on the recap page rather than a question to the room. An ad-hoc meeting by link keeps only its latest recap, and its chat is wiped when the call ends; a series belongs in a channel.

The series card above is a note in the channel, where a new member finds it on day one. During a session, the card or the previous session's recap goes on everyone's screen next to the video tiles with Share to conference: the sharer edits it live while the room watches, and every participant reads it in their own language, with the original a toggle away. The same works for the agenda of this occurrence, drafted in the channel the day before.

When the call ends, the recap is written from the meeting itself — a summary, the action items with owners — and arrives by email to each signed-in participant, as a message in the channel and as a link in the calendar event, each member reading it in their own language rather than the one the room happened to use. Any member can edit it, every edit keeps author and revision history. For a channel's recurring meeting, the open action items of the previous session are read back when the next recap is written and judged against what was said: an item someone reported finished is marked done, anything else is marked not done with the reason in the words of the meeting, or "not discussed" — and at the start of the next session Mia names the open items and their owners, so last time's list is the first thing spoken about rather than the first thing forgotten. This part runs for selected accounts while it is being refined.

A series is members-only. A colleague or a client who belongs on the series is added by email invitation onto a free account and reads the channel in their language. Someone who is needed for one occurrence only — a supplier for one review, a candidate for one call — joins an ad-hoc meeting by link, from a phone, without an account and at no cost, hears the meeting live in their own language and gets nothing afterwards: the account is free, and it is what makes the record reachable. The host provides the space and, on a paid plan, pays only for the members active in the previous 28 days — joined a meeting, wrote in a chat, asked Mia; a member on leave for a month keeps access and costs nothing that month, and the series they come back to is in the channel, with every session's recap.

• Open a complete recap — a real record rendered by the same code that writes yours.
• Try the live demo — no signup; speak, and hear the room translated per listener.

A recurring meeting survives every tool: somebody still has to choose the pattern, hold the slot, set the end and decide the exceptions before the holiday. What does not have to survive is the second job — finding last time's document, reading it into the room, and typing this time's up by hand, in one language, for people who read others.

FAQ

What is a recurring meeting?

A recurring meeting is a meeting scheduled as one calendar event with a repeat rule — weekly, every two weeks, monthly, or a custom pattern — so that the calendar creates each occurrence, invites the same people and carries the same link every time. The series is maintained as a whole; a single occurrence can be moved or cancelled as an exception without changing the rule.

How do I set up a recurring meeting in Outlook?

Create the event with its first date, time and invitees, open the recurrence option on the event form, choose the pattern — daily, weekly, monthly or a custom rule with an interval and days — and set how the series ends: on a date, after a number of occurrences, or never. Put the meeting link in the event before saving so every occurrence inherits it, then send; the invitation covers the series. In InterMIND, the calendar half of New meeting opens Outlook with the title, the join link and the recap link already in the event, and the recurrence is set there.

How do I make a meeting recurring in Google Calendar?

Open the event, change the repeat field next to the date from "does not repeat" to a pattern or to a custom rule, set the interval, the days and the end, and save. If the meeting already has a link, keep it in the event so that every occurrence opens the same room. From InterMIND, click the calendar button on the meeting's row: Google Calendar opens with the event pre-filled, and you pick the first date and the recurrence; a meeting that has already met can be made recurring the same way without losing its chat and recaps.

How do I change one occurrence of a recurring meeting without changing the series?

Open that occurrence and, when the calendar asks which events to change, choose this event only. The calendar records the exception — a new time, a shorter length, a cancellation — and leaves the rule alone, so the next occurrence is back on the regular slot. Choose this and following events when the slot changes permanently from a date onward, and all events when the change applies to the whole series.

How do I end a recurring meeting without deleting the past occurrences?

Do not delete the series: that removes past occurrences from the calendar as well. Edit the series and set its end date to the last occurrence that should take place, or open the first occurrence that should not happen and cancel this and following events. The past stays in the calendar with whatever each occurrence linked to.

Does a recurring meeting keep the same link for every occurrence?

In the calendar, the series carries one link and every occurrence inherits it, unless the meeting tool generates a new one per occurrence or someone edits an occurrence's link as an exception. Whether the room behind that link keeps anything from one occurrence to the next is a property of the meeting tool, not the calendar: the table in this guide lists what Teams, Zoom, Google Workspace and Slack leave behind per occurrence, and a channel in InterMIND keeps the chat and every session's recap at the same address.

What is the difference between a recurring meeting and a meeting series?

They are the same object seen from two sides. "Recurring meeting" is the meeting as the team experiences it — the weekly, the stand-up. "Series" is the calendar's name for the event with the repeat rule, as opposed to an "occurrence", one instance the rule produced. Changes are made either to the series or to an occurrence, which is why the calendar asks which one you mean.

Sources: Microsoft — Schedule a meeting in Microsoft Teams; Microsoft — Take meeting notes in Microsoft Teams; Microsoft — Recap in Microsoft Teams; Zoom — Generating meeting agenda with AI Companion; Zoom — Using Meeting Summary with AI Companion; Google Meet — Start or schedule a Google Meet video meeting; Google — Calendar & Meet settings for "Take notes for me"; Google Meet — "Take notes for me" in Google Meet; Slack — Use huddles in Slack; Slack — Meeting agenda template. Each table cell names the month its fact was checked — the earliest checked August 2026, the latest checked October 2026. The steps for setting recurrence in Google Calendar and Outlook describe the shape both calendars share; the exact labels differ by version and are on the vendors' help pages. Vendors change plans, features and language lists over time; check their pages for the current state.