> For the complete documentation index, see [llms.txt](https://www.usemotion.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.usemotion.com/help/project-management/meeting-events/reference-meeting-events/free-vs-busy-in-motion.md).

# Free vs Busy in Motion

Unlike tasks, you have direct control over whether events appear as **Free** or **Busy** in Motion. This choice impacts both how your calendar appears to others and how Motion’s AI schedules tasks around these events.

**Busy events**

* Tell Motion: *“This time is completely blocked.”*
* Motion will not schedule tasks or other events in that slot.
* Use for:
  * Must-attend meetings (client calls, team stand-ups)
  * Important presentations
  * Focus blocks where you need uninterrupted time
  * Any commitment that cannot be shifted

**Free events**

* Tell Motion: *“I have something here, but tasks can still be scheduled.”*
* The event is visible but does not block scheduling.
* Use for:
  * Optional meetings you could skip or reschedule
  * Personal placeholders (like “gym” or “errands”)
  * Background activities where multitasking is possible
  * Time you want visible but not protected

**Key rule**

* **Busy = block time. Free = visible but flexible.**
* Motion respects external calendar states, so if you mark something Free in Google, it appears Free in Motion as well.
* Booking link events are always *Busy* by default.

### Event States & Behavior

Motion respects standard calendar **event states** from connected calendars (Google, Outlook, iCloud). These states determine how events display in Motion and how they interact with task scheduling.

| Event State   | Behavior in Motion                                                                                                                                              |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Busy**      | Blocks time completely. Tasks cannot be scheduled in this slot. Default for most meetings and all booking link events.                                          |
| **Free**      | Appears on your calendar but does not block scheduling. Tasks can be placed during this time.                                                                   |
| **Tentative** | Treated as *Busy* by default (to prevent conflicts) but flagged visually to show uncertainty. If confirmed or declined externally, the state updates in Motion. |
| **Declined**  | Hidden from your active calendar view in Motion. Tasks can be scheduled in this time slot.                                                                      |

**Behavior rules**

* Motion mirrors the state of an event from the source calendar; updates made externally flow into Motion automatically.
* If an event’s state changes (e.g., Tentative → Busy, Declined → Free), Motion will adjust scheduling accordingly.
* Booking link events always create **Busy** events, even if edited later.
* Tasks never override **Busy** or **OOO** events — they shift to available time instead.

**Why it matters**\
Event states give you control over how Motion prioritizes your time. Mark events accurately (Free vs Busy vs Tentative) to keep your schedule realistic and prevent tasks from being over- or under-blocked.<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.usemotion.com/help/project-management/meeting-events/reference-meeting-events/free-vs-busy-in-motion.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.