Skip to main content

Configuring a Project Type

This walkthrough builds a project type from scratch, assuming you've already started populating your libraries. If you haven't, work through Project Creation Setup first so you have some approval items, tasks, fields, and document sets to select from.

If you'd rather bootstrap a project type from a checklist PDF, jump to Import from PDF instead.

1. Create the project type​

  1. Go to Project Creation Setup → Project Types.
  2. Click + Add.
  3. Enter a descriptive name (e.g. Class 1a Residential CC).
  4. Optionally add a description — it's shown to approvers picking a type in the project wizard.

Save. The new type appears in the list on the left.

2. Attach approval items and tasks​

With the project type selected:

  1. Tick the approval items from your library that this type should include. These are the applicant-visible checklist entries.
  2. Tick the tasks that should be included. Tasks only appear for approvers and co-approvers, not for applicants or collaborators.
  3. For any item or task where you want additional context that only applies when this project type is used (e.g. a regulation reference), expand the item and add a project-type-specific description. At project-creation time, the project-type-specific description is composed with the base description.

3. Attach project information fields​

Tick the fields that this project type should carry. Remember:

  • Fields without a document-set binding are project-level (one value per project).
  • Fields with a document-set binding are per-document — they require the linked document set to also be part of this project type. See the next step.

4. Attach document sets​

Tick the document sets you want to include. If any of the fields you ticked in step 3 are linked to a document set, make sure that document set is ticked too — otherwise the per-document values will have nowhere to live.

Each document set you attach will be automatically populated on the project via its AI prompt (if one exists on the library definition) — or manually, if you prefer. See Setting up Document Sets.

5. Attach an approval pack template (optional)​

If you have an approval pack template under Project Creation Setup → Approval Pack Templates, you can link one to the project type so every project created from this type has its heading, body, and default document sets pre-filled when you go to build a pack. See Approval Packs.

6. Try it on a test project​

The fastest way to verify a project type is to create a throwaway project from it:

  1. Go to New Project.
  2. Choose Choose a Project Type as the creation method.
  3. Pick the project type you just built.
  4. Proceed through the wizard.

Check that the project's approval list contains the expected items and tasks, that the project information fields are present, and that each document set appears (empty, ready to be populated). Delete the test project when you're done.

Editing a project type later​

Edits to a project type do not affect existing projects. They only affect projects you create from the type after the edit. If you need to pull a library change into an existing project, edit the project directly — its copy is independent from that point on.