Project types and contact processes
Projects provides two reusable process tools with different jobs:
- A Project Type standardizes how the whole project runs.
- A Contact Process collects information, checklist completion, or approvals once for each contact attached to a project.
Who can do this
Owners and Admins, and users granted Projects → Manage Project Types, can manage project types. Access to contact processes also depends on the relevant contact and workspace permissions.
Choose the right process
| Requirement | Use |
|---|---|
| Repeat the same delivery phases and responsibilities for each project | Project Type |
| Enforce an ordered set of project steps | Project Type |
| Collect answers or approvals separately for each linked contact | Contact Process |
| Start a one-off project with no reusable process | No project type in the creation wizard |
Work with Project Types
Open Projects → Project Types. The list shows the type, category, status, version, last update, and actions.
A type can be a Draft while it is being designed and Published when it is ready for the project creation wizard. Published types can be duplicated for a variation or deprecated when they should no longer be used for new work.
Build a type
- Select New type, or start from Industry packs when a suitable pack is available.
- Add one or more Stages.
- Add the steps that belong to each stage.
- For each step, define its name, instructions, assignment, and due timing.
- Assign work through a Project role when the same responsibility should be filled by different people on different projects.
- Mark a step Required to continue when later work must remain locked until it is complete.
- Use Preview to review the sequence.
- Save draft while designing; select Publish only when the process is ready to create live projects.
Due timing can be relative to the previous step. A required step acts as a completion gate, while a non-required step can allow the process to continue.
What publishing changes
Only a published type is offered in Step 2 of project creation. When selected, the project copies the type's stages, steps, board, and tabs. The type is therefore a starting blueprint; the resulting project is the team's live delivery workspace.
Work with Contact Processes
Open Projects → Contact Process. A Contact Process is filled once for each contact on any project to which it is attached.
- Select New process.
- Start a blank process, or choose a reusable template when one exists.
- Build the forms, checklists, and approvals required from or about each contact.
- Publish the process when it is ready to be reused.
This is useful when every linked participant must provide their own response. It is not a replacement for project stages: stages move the overall project forward, while a Contact Process tracks a separate completion for each contact.
Verify your work
- A Project Type remains Draft until it is deliberately published.
- The published type appears in the project creation wizard.
- A project created from the type contains the expected Stages and tabs.
- Project-role assignments are filled by the correct people on the live project.
- Required steps prevent later steps from unlocking until completion.
- A Contact Process produces a separate completion path for each linked contact.
Troubleshooting
| Issue | What to check |
|---|---|
| The type is missing during project creation | Confirm its status is Published, not Draft or deprecated. |
| A step has no owner in a live project | Confirm the referenced Project role is assigned on that project. |
| Later steps are available too early | Enable Required to continue on the gating step. |
| Contact Process list is empty | No process has been created or published yet; start a blank process. |
| Users confuse milestones with stages | Milestones organize delivery work; Stages execute the reusable Project Type process. |