> 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/time-management/auto-scheduling/reference-auto-scheduling/what-auto-scheduling-considers.md).

# What Auto-Scheduling considers

#### What Parameters Motion Considers when Auto-Scheduling

Auto-Scheduling evaluates task metadata and calendar context to determine where work fits. The following parameters are used in scheduling:

<table data-header-hidden><thead><tr><th width="139.203125">Parameter</th><th width="274.234375">Details </th><th>Type of Task</th></tr></thead><tbody><tr><td>Parameter</td><td>Details</td><td>Type of Task</td></tr><tr><td><strong>Start date</strong></td><td>The earliest date a task is allowed to begin. Tasks will not be scheduled before this point, even if time is available.</td><td>Flexible tasks (to control when they can enter the schedule); recurring tasks (defines first occurrence).</td></tr><tr><td><strong>Duration</strong></td><td>The total estimated time required to complete the task. You can set duration into chunks, Auto-Scheduling will schedule each chunk into multiple scheduled sessions</td><td>All tasks; especially long tasks that need to be split or carefully placed.</td></tr><tr><td><strong>Deadline</strong></td><td>The latest time a task must be completed. Auto-Scheduling prioritizes tasks with sooner deadlines.</td><td>Hard-deadline tasks (e.g., compliance, submissions). Flexible tasks without deadlines may be delayed.</td></tr><tr><td><strong>Priority</strong></td><td>Defines the relative importance of a task. Higher-priority tasks are placed earlier or in better time slots.</td><td>ASAP tasks (highest), High/Medium/Low tasks.</td></tr><tr><td><strong>Chunking</strong></td><td>Long tasks may be split into smaller time blocks to fit into available calendar gaps, while still respecting total duration and effort.</td><td>Min chunks for each time the task is scheduled.</td></tr><tr><td><strong>Schedules &#x26; breaks</strong></td><td>Motion respects the user’s defined working hours and built-in breaks, only placing tasks during available time.</td><td><p>Work vs. personal tasks (depends on custom schedules like Workday 9–5 vs. Weekend schedule).</p><p>Breaks in between tasks so you aren't working back to back.</p></td></tr><tr><td><strong>Calendar events</strong></td><td>Fixed meetings, personal events, and custom time blocks are treated as unavailable time if set as a 'Busy' event and bypassed by Auto-Scheduling.</td><td>Fixed-time tasks (meetings, calls) and all other tasks must work around these.</td></tr><tr><td><strong>Recurring</strong></td><td>Defines whether a task is one-time or recurring. Recurring tasks can be pushed within their recurrence window but must follow repeat rules.</td><td>Recurring tasks (e.g., daily standup notes, weekly reporting).</td></tr></tbody></table>


---

# 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://www.usemotion.com/help/time-management/auto-scheduling/reference-auto-scheduling/what-auto-scheduling-considers.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.