> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/ai/filing-recurring-meetings.md).

# Filing Recurring Meetings

File a recurring Outlook or Google Calendar meeting once, and every future occurrence lands in the same Organization and Project automatically.

### Overview

Many meetings repeat: weekly standups, internal syncs, recurring customer check-ins. When a recurring meeting comes in from Outlook or Google Calendar and you set its Organization or Project, Transform asks how far that change should reach. Choose to apply it to future occurrences, and every later meeting in the series is filed the same way without anyone touching it again.

This is especially useful for **internal meetings**. [Interactions Routing](https://help.transform.ai/organizations-and-projects/interactions-routing.md) ignores your own company's domains, so a meeting with only your team on it is never routed. Filing the series once sends every future occurrence to the right internal Organization and Project, with no routing setup needed.

### Key Concepts

* **Recurring meeting**: a meeting synced from a repeating event in Outlook or Google Calendar. It shows a repeat icon next to its title (hover it to see **This meeting repeats**). Meetings created inside Transform are never part of a series.
* **Series-level fields**: the fields Transform owns, which can be applied across a series: **Organization** and **Project**, **Internal only**, **Restricted to attendees**, and the meeting **type**.
* **Calendar-owned fields**: title, description, time, meeting link, and attendees come from your calendar. Edits to these apply to one occurrence only and never prompt.

### How It Works

{% stepper %}
{% step %}

### Edit a series-level field

On a recurring meeting, change its Organization or Project (or another series-level field). Nothing is saved yet.
{% endstep %}

{% step %}

### Choose which meetings to update

An **Edit recurring meeting** prompt asks which meetings to update:

* **This meeting**: only this occurrence changes.
* **This and following meetings**: this occurrence and every later one change. Earlier meetings stay as they are.
* **All meetings in the series**: every occurrence changes, past and future.

Select **Update** to apply. Closing the prompt cancels the edit and leaves the meeting unchanged.
{% endstep %}

{% step %}

### Future occurrences follow automatically

With **This and following meetings** or **All meetings in the series**, Transform remembers the values for the series. Occurrences that sync in later, including dates your calendar adds as the series continues, are created already filed in that Organization and Project.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Only the fields you changed are applied to the other occurrences. Setting the Project across a series does not touch each occurrence's Internal only or Restricted to attendees settings, and vice versa.
{% endhint %}

### Series You Filed One Meeting at a Time

If a series was never updated with the prompt, Transform still looks at its existing occurrences when a new one syncs. When every existing occurrence agrees on a value (for example, they are all in the same Organization), the new occurrence is filed the same way. When they disagree, the new occurrence takes its normal default, so a deliberate exception is never copied over.

### How It Fits With Interactions Routing

When a new occurrence syncs, Transform decides where it lands in this order:

1. A calendar sync that targets a specific Organization or Project keeps that target.
2. The values you set for the series with the prompt.
3. The values every existing occurrence agrees on.
4. [Interactions Routing](https://help.transform.ai/organizations-and-projects/interactions-routing.md) by attendee email domain.
5. Default settings.

Because series values come before routing, they also override routing's defaults. For example, if you set a series to not be internal-only, new occurrences arrive that way even if routing would have made them internal-only.

### Setup Steps

{% stepper %}
{% step %}

### Find your recurring meetings

Open **Meetings**. Recurring meetings show a repeat icon next to their title. You can also add the recurrence column or filter on it to list only recurring meetings.
{% endstep %}

{% step %}

### Set the Organization and Project

On one occurrence of the series, set the **Organization** and **Project**. For internal meetings, pick your internal Organization and the relevant internal Project.
{% endstep %}

{% step %}

### Apply it to the series

In the **Edit recurring meeting** prompt, choose **This and following meetings** (or **All meetings in the series** to also re-file past occurrences), then select **Update**.
{% endstep %}
{% endstepper %}

### Best Practices

* File each recurring internal meeting once, the first time it shows up, instead of re-filing it every week.
* Use **This and following meetings** when the series moved to a new Project, so past meetings stay where they were.
* Use **All meetings in the series** to clean up a series that was filed inconsistently.
* Keep Interactions Routing for customer meetings and use series filing for internal ones.

### Things to Know

* **Bulk edits don't prompt.** Changing the Organization or Project on several selected meetings at once updates each selected row only, because a selection can span several series.
* **Later series-wide edits win.** An occurrence you changed with **This meeting** is overwritten by a later series-wide edit to the same field.
* **Permissions are checked per meeting.** Occurrences you can't edit are skipped; the rest are still updated.
* **Calendar series splits start fresh.** If you change a series' schedule "from this date onward" in Outlook or Google Calendar, the calendar may create a new series. Its occurrences arrive with defaults; file one of them with the prompt to set up the new series.

### Troubleshooting

| Symptom                                           | Likely cause                                                                                                   |
| ------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| No prompt appears when I change the Project       | The meeting isn't recurring (no repeat icon), it was created in Transform, or you edited several rows at once. |
| No prompt appears when I change the title or time | These fields belong to your calendar and are edited per occurrence only.                                       |
| A new occurrence landed somewhere else            | The calendar sync targets a specific Organization or Project, or the series was split in your calendar.        |
| Some occurrences weren't updated                  | You don't have edit access to those meetings.                                                                  |

### Summary

File a recurring meeting once and choose **This and following meetings**: every future occurrence lands in the same Organization and Project automatically. It's the simplest way to keep internal meetings organized without Interactions Routing.

Related:

* [Interactions Routing](https://help.transform.ai/organizations-and-projects/interactions-routing.md)
* [Capturing Meetings Automatically](https://help.transform.ai/ai/capturing-meetings-automatically.md)
* [Managing Meeting History](https://help.transform.ai/ai/managing-meeting-history.md)
* [Meeting Notetaker](https://help.transform.ai/ai/meeting-notetaker.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.transform.ai/ai/filing-recurring-meetings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
