> 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/task/concept-tasks.md).
# Concept: Tasks
## Understanding Tasks in Motion
Every project, meeting, or deliverable comes down to individual tasks — the building blocks of real work. In Motion, tasks aren’t just checkboxes. They’re the **atomic unit of work** that fuels everything else: Auto-Scheduling, AI Agenda, Projects, Docs, and even AI Employees.
Clear, well-structured tasks ensure your work gets planned realistically, completed on time, and aligned with your team. The more precise and thoughtful the task, the more powerful Motion becomes.
### At a Glance
* **What they are** → Tasks are Motion’s atomic unit of work, carrying context like deadlines, priority, and effort.
* **Why they matter** → They drive scheduling, planning, and coordination across Motion. Without tasks, Motion has no data to optimize.
* **How to think about them** → Break tasks down for clarity, chunk long ones, and use templates to reduce repetition.
* **Key features** → Tasks adapt to views, appear differently on your calendar depending on state, and include feeds for team activity.
* **Lifecycle** → Active → Completed → Archived — tasks keep history clean without losing context.
* **Key takeaway** → Thoughtful tasks power Motion — the clearer the task, the smarter the system.
---
# 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/task/concept-tasks.md?ask=&goal=
```
`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.