Overview of Project Creation Methods
You can create a project by:
Creating from a Template (fastest, most structured)
Creating from Scratch (most flexible)
Creating via automation
Each method serves a different use case - let’s break them down.
1️⃣ Create a Project from a Template
This is the recommended approach if you want to get started quickly with a predefined structure.
How it works
Click the dropdown by + Create Project
Select Create from Template
Choose a template from your Template Library
Enter a Project Name
Click Create
👉 Your project will:
Populate with phases, milestones, and tasks
Start in a Pending status
Be ready for immediate use with minimal setup
📚 Template Library
Templates are managed in your Template Library, where your team stores reusable project structures.
Use templates when:
Projects follow a repeatable process
You want consistency across teams
You need to save time on setup
✏️ Naming Your Project
When creating a project, you’ll be prompted to enter a name.
Tips:
Use clear, descriptive naming (e.g., Client Name – Project Type – Date)
Keep naming consistent across your team
💡 You can edit the project name anytime later, so don’t worry about making it perfect upfront.
2️⃣ Create a Project from Scratch
This option gives you full control to build a project from the ground up.
How it works
Click + Create Project - you'll be redirected to the new project
Enter a Project Name
Your project will:
Start empty
Be set to Pending status
Require manual setup of structure
Adding Templates After Creation
Once your project is created, you can layer in structure:
Add phases to define major stages
Add milestones to track key checkpoints
Add tasks to manage execution
This is ideal when:
You’re still defining scope
Requirements evolve over time
When to use this
Projects are unique or one-off
No existing template fits your needs
You want to design a custom workflow
3️⃣ Create Projects using Automations
You can enhance any project with automations to reduce manual work.
Examples:
Auto-assign tasks
Assign roles
Add customers and other team members
Add the correct templates for the new customer's onboarding journey!
👉 See related articles:
Automations Overview
How to Set Up Automations
✅ Best Practices
Choose the right creation method
Use templates for repeatable workflows
Use scratch for flexibility
Use hybrid when scope is evolving
Standardize naming
Keep formats consistent across projects
Include key identifiers (client, type, date)
Start with “Pending”
All projects begin in Pending - use this time to finalize setup before execution. Project invites will only send when the project is started. Additionally, users will not see Pending projects on their List view until the project has been changed to an active status.
Use templates strategically
Regularly update templates based on lessons learned
Avoid overloading templates with unnecessary tasks
Build iteratively
Don’t over-plan upfront—add detail as needed
FAQs
Why does my project start as “Pending”?
This allows you to finalize setup (tasks, owners, dates) before work begins.
Can I change the project name later?
Yes—project names are fully editable at any time.
What if I pick the wrong template?
You can:
Modify the project manually
Add/remove tasks and phases
Or create a new project if needed
Can I apply multiple templates?
Yes—you can layer templates (phases, milestones, tasks) after creation.
Should I always use templates?
We recommend that you do since templates are best for repeatable processes, but scratch projects are better for unique work.
When should I use automations?
When you notice repetitive manual steps
For project creation, and getting the project set up without any manual effort.
Pro Tips
Create a “starter template” for common projects
Keep templates lean and practical
Review and improve templates regularly (every quarter is what GUIDEcx does!)
Use automations to scale your workflows
Don’t hesitate to start simple and refine later