Skip to main content

Project Creation Setup

Project Creation Setup is where approvers configure everything that feeds into a new project. It's the single place you maintain your reusable building blocks and assemble them into Project Types.

Open it from the main navigation or go directly to /project-creation-setup. The landing page groups every setup area into three sections: an Import shortcut, Project Types, and your Libraries.

Each approver maintains their own library — entries are per-user, so your project types and library entries are not shared with other approvers. Applicants and collaborators do not interact with Project Creation Setup at all; they only see the projects they've been invited to.

Import from PDF

If you already have a checklist document — consent conditions, a council checklist, a scope of works — you can upload it and let ApprovIQ bootstrap a project type for you.

  1. From the Project Creation Setup landing page, click Import from PDF.
  2. Upload the PDF.
  3. The AI reads the document and extracts each requirement as an approval item.
  4. Review the result, make any edits, and save. A new project type is created from the extracted items.

Import from PDF is a shortcut; you can always create a project type manually instead.

Project Types

A project type is the unit you pick when creating a project. It bundles approval items, tasks, project information fields, document sets, and an approval-pack template together so one click populates a new project with everything it needs.

See the Project Types concept page for the mental model and Configuring a Project Type for the step-by-step workflow.

Libraries

Your libraries are the master copies of the things a project type references. Build these up once and reuse them across as many project types as you like.

Approval Items

Applicant-visible checklist items. Each item describes a document or piece of evidence the applicant must provide and can carry its own document checks and reference documents. See Approval Items and Tasks.

Tasks

Internal checklist entries that only approvers and co-approvers see. Use tasks for things you need to track but shouldn't burden the applicant with (internal reviews, follow-up phone calls, verification steps). Tasks live on the same approval list as items but are never shown to applicants or collaborators.

Project Information Fields

Custom metadata fields attached to projects — site address, DA reference, building class, or per-document fields like a "Purpose" column for each relied-upon document. See Project Information Fields.

Document Sets

Categorised groups of received documents. Each set can carry an optional AI prompt that tells ApprovIQ which documents belong in the set. See Document Sets.

Approval Pack Templates

A reusable layout for Approval Packs — heading text, body message, and which document sets to include by default. Attach one to a project type and every project created from it will offer that template when you assemble an approval pack.

Document Templates

Word-compatible mail-merge templates used to generate project documents. Drop placeholders into a template and ApprovIQ fills them in from project data when the document is generated. See Document Templates.

Library edits do not affect existing projects

All of the library areas above are snapshotted when a project type is applied. Edits you make afterwards only affect projects created from that point on — existing projects keep their own copies. This is by design: it keeps in-flight projects stable while letting you keep improving your library.