# Concept: Meeting/Events

## Understanding Events in Motion

Your calendar is more than just empty slots — it’s the framework that holds your day together. Events in Motion represent the **fixed commitments** in your schedule: meetings, appointments, or focus blocks you want protected. They’re the anchors that Motion’s AI respects when arranging tasks.

By setting events as **Busy** or **Free**, you teach Motion how flexible your time really is. Busy events are treated as immovable, while Free events allow Motion to optimize around them. Used well, events safeguard your focus, reduce scheduling conflicts, and help tasks fit naturally into your day.

### At a Glance

* **Why events matter** → Events provide the structure that tasks adapt around, representing immovable commitments.
* **How event states work** → Busy = protected time; Free = flexible time Motion can optimize.
* **Use cases** → Mark Busy for must-attend meetings or appointments, Free for optional blocks like “lunch” or “catch-up reading.”
* **Key takeaway** → Events are the anchors of your schedule; Motion’s AI arranges tasks around them to keep your day both structured and flexible.

#### Conclusion

Events give your schedule its structure. By marking the right commitments as **Busy** and keeping flexible blocks as **Free**, you help Motion’s AI plan around what matters most. Tasks adapt dynamically, but events stay fixed — giving you both reliability and flexibility in your day.

#### Key Takeaway

Events are the anchors of your calendar — they protect your commitments while giving Motion the framework to schedule tasks intelligently.


---

# Agent Instructions: 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:

```
GET https://www.usemotion.com/help/project-management/meeting-events/concept-meeting-events.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
