> 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/regular-projects-vs-workflow-templates.md).

# Regular Projects vs Workflow Templates

Motion supports two types of projects: **regular projects** and **workflow template projects (PWTs)**. Both organize tasks and stages, but they serve different purposes.

**Regular Projects**

* Designed for unique or one-off initiatives.
* Created manually, with stages and tasks tailored to the specific project.
* Best suited for campaigns, launches, or initiatives that will not be repeated.
* Tasks, blockers, and stages exist only in the scope of that project.

**Workflow Template Projects (PWTs)**

* Designed for processes you repeat often (e.g., onboarding, product launches, content creation).
* Provide a reusable framework of stages, tasks, and dependencies.
* Can be launched multiple times with the same structure, saving setup time.
* Optionally enhanced with AI to generate starter workflows from short prompts.

**Key differences**

<table><thead><tr><th width="139.34765625">Feature</th><th width="263.12890625">Regular project</th><th>Workflow template project</th></tr></thead><tbody><tr><td><strong>Purpose</strong></td><td>One-off, custom initiative</td><td>Repeatable workflows and processes</td></tr><tr><td><strong>Setup</strong></td><td>Built from scratch each time</td><td>Predefined template with stages, tasks, blockers</td></tr><tr><td><strong>Reusability</strong></td><td>Not reusable</td><td>Can be reused or launched multiple times</td></tr><tr><td><strong>AI support</strong></td><td>Manual setup only</td><td>AI can auto-generate starter workflows</td></tr></tbody></table>

**Why it matters**\
Use a **regular project** when the work is unique. Use a **workflow template project** when the process will repeat and benefits from consistency, automation, and time-saving.


---

# 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/regular-projects-vs-workflow-templates.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.