Skip to main content

Project Types

A Project Type is a reusable bundle of everything you need to start a new project: approval items, internal tasks, project information fields, document sets, and an optional approval-pack template. When you create a project, you pick a project type and the new project is pre-populated from it.

Project types live under Project Creation Setup → Project Types (/project-creation-setup/project-types).

The three tiers​

ApprovIQ stores configuration in three tiers. Understanding the distinction is the key to using project types well.

TierWhere it livesWhat it's for
LibraryApproval Items, Tasks, Project Information Fields, Document Sets, Approval Pack Templates (all under Project Creation Setup)Master definitions you maintain once and reuse across many project types.
Project TypeA named Project TypeSelects which library entries belong together, so you can apply them to a project in one click. A project type is a reference bundle — not a copy.
Project InstanceInside a specific projectA snapshot of the project type, created when the type is applied. From this point on, edits to the project only affect that project.

Applying a project type​

When you start a new project and choose Choose a Project Type in the wizard, ApprovIQ:

  1. Copies the project type's approval items and tasks into the project's approval list.
  2. Snapshots the project type's project information fields into the project.
  3. Snapshots the project type's document sets into the project.
  4. Runs two jobs in the background to extract information from any documents the applicant has already uploaded and to classify those documents into the project's document sets. See Creating a Project for the details.

After this snapshot:

  • Edits you make inside the project only affect that project. Moving an item, editing a description, or adding a new field stays local.
  • Edits you make in the library or the project type only affect projects you create from that point on. Existing projects are not retroactively updated.

This trade-off keeps in-flight projects stable while letting you keep improving your library.

What a project type contains​

Each project type holds references to:

  • Approval items — applicant-visible checklist entries. See Approval Items and Tasks.
  • Tasks — internal checklist entries only visible to approvers and co-approvers.
  • Project information fields — custom metadata fields (e.g. "Building Class", "DA Reference"). See Project Information Fields.
  • Document sets — categorised groups of received documents (e.g. "Relied Upon Documents"). See Document Sets.
  • Approval pack templates — a pre-filled layout for any Approval Pack you later generate from the project.

A single library entry can belong to any number of project types. Build a small library of reusable parts, then combine them into as many project types as you need.

When to create a new project type​

  • You do a recognisably different kind of project (e.g. "Class 1a Residential CC" vs "Class 5 Commercial CC").
  • The approval items, information fields, or document sets differ meaningfully between those kinds.
  • You want a second project type with a slightly different approval-pack template while sharing the same approval items.

If two project types would be nearly identical, prefer one project type and adjust the specific project after it is created.