What are project types?
Project types are labels that categorize projects by:- Service offering — Financial planning, tax prep, insurance review
- Engagement type — Onboarding, annual review, ad-hoc request
- Workflow category — Client service vs internal operations
Default project types
Slant includes common project types:| Type | Description |
|---|---|
| Financial Plan | Comprehensive financial planning engagement |
| Annual Review | Yearly client review process |
| Onboarding | New client setup and paperwork |
| Tax Preparation | Tax return preparation |
| General | Uncategorized projects |
Create a project type
Enter details
Configure the project type:
- Name — Display name
- Description — What this type represents
- Color — Visual identifier
- Icon — Optional icon
Set defaults
Optionally set default values:
- Default milestones
- Default assignee rules
- Estimated duration
Configure project type details
Basic information
| Field | Description |
|---|---|
| Name | How the type appears in lists and dropdowns |
| Description | Explanation of when to use this type |
| Color | Color coding for visual identification |
| Icon | Optional icon for quick recognition |
Default milestones
Pre-configure milestones for the project type:Add milestones
Define default milestones:
- Milestone name
- Relative due date (e.g., “Day 7”)
- Description
Default tasks
Set tasks that are created automatically:Assign project types
When creating a project
Change existing project type
Changing a project’s type doesn’t add or remove milestones/tasks. It only changes the categorization.
Edit project types
Editing a project type updates future projects but doesn’t change existing ones.
Archive project types
Remove unused types from the active list:Archived types
- Don’t appear in dropdown menus
- Existing projects keep their type
- Can be restored if needed
Restore archived type
Filter and report by type
Filter projects
Project type reporting
Use project types for analysis:- How many financial plans are in progress?
- Average time to complete each project type?
- Which types have the most overdue milestones?
Project types vs templates
Both help standardize projects:| Feature | Project types | Project templates |
|---|---|---|
| Purpose | Categorization | Full project setup |
| Contains | Default structure | Complete configuration |
| Usage | Selected when creating | Applied when creating |
| Flexibility | Sets category, defaults optional | Creates exact copy |
- You need to categorize projects
- Defaults are helpful but flexible
- Reporting by category matters
- You need identical project setups
- Every task must be included
- Consistency is critical
Best practices
Keep types meaningful
Create types that:- Represent distinct service offerings
- Are mutually exclusive
- Aid in reporting and analysis
Don’t over-categorize
Too many types cause confusion:- Aim for 5-10 types
- Combine similar types
- Use tags for additional detail
Review periodically
Assess your project types:- Which types are used most?
- Are any unused?
- Should types be consolidated?
Coordinate with team
Ensure everyone understands:- What each type means
- When to use each type
- How types affect reporting
Troubleshooting
Type not appearing
Check:- Type isn’t archived
- You have permission to create projects
- Filter isn’t hiding it
Wrong defaults applied
Verify:- Correct type is selected
- Default settings are configured correctly
- Existing projects aren’t affected by type changes