> 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/projects/reference-projects.md). # Reference: Projects ## Introduction Projects in Motion are structured containers designed to organize tasks, stages, and workflows around a specific goal. Unlike folders, which group work thematically, projects provide a framework for sequencing tasks, tracking progress, and visualizing dependencies. With stages, blockers, and multiple view options (List, Kanban, Gantt), projects give teams both flexibility and control in managing work from start to finish. #### At a Glance * **Project types** → Create regular projects for one-off initiatives or workflow templates (PWTs) for repeatable processes. * **Stages** → Organize work into sequential steps; tasks move through stages to show progress. * **Blockers** → Mark tasks or dependencies that must resolve before work continues, maintaining flow and efficiency. * **Views** → Switch between List, Kanban, and Gantt to manage tasks from different perspectives. * **Calendar integration** → Project tasks and blockers sync with the calendar, with clear visual indicators when deadlines or blockers impact scheduling. * **Flexibility** → Projects support ad hoc stages, AI-powered workflows, and cross-task dependencies, making them suitable for both structured and dynamic work. #### Conclusion Projects in Motion are structured containers that bring together tasks, stages, blockers, and views to organize work around clear goals. They provide the framework for sequencing tasks, visualizing progress, and enforcing dependencies while staying tightly integrated with your calendar. Whether built as regular projects for one-off initiatives or workflow templates for repeatable processes, projects help teams run work more consistently and efficiently. #### Key Takeaway Projects give structure to your work in Motion — stages define the flow, blockers enforce dependencies, and views provide perspective, all anchored to your calendar for execution. --- # 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/project-management/projects/reference-projects.md?ask=&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.