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

Feature	Regular project	Workflow template project
Purpose	One-off, custom initiative	Repeatable workflows and processes
Setup	Built from scratch each time	Predefined template with stages, tasks, blockers
Reusability	Not reusable	Can be reused or launched multiple times
AI support	Manual setup only	AI can auto-generate starter workflows

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.