Projects

A project is one job, and everything about that job lives inside it: posts, tasks, approvals, snagging, the calendar, the timeline, drawings, site updates, the contract with its variations and selections, and the client portal.

Creating a project

Only administrators can create projects. New project on the Projects page opens a six-step wizard: Project details, Address, Dates, Appearance, Team and Templates.

Only the project title, street address and postal code are required; everything else can be filled in later. Nothing is saved until you press Create project on the last step.

The Templates step can seed the project from a task, drawing and timeline template, one of each. Applying a template only ever adds items, so you can apply another one later from the project’s Tasks, Drawings or Timeline page.

The overview

Overview is the project’s home: the project details (photo, address, dates, category, description and team) alongside its posts, tasks, approvals and, once the project reaches Snagging, its snags. Project details are edited by administrators and each field saves as you leave it.

Completed projects are hidden from the Projects page until you tick Show completed.

Categories

A project can belong to a category - a named, coloured label your organisation defines, shown as the dot or tile next to the project wherever it appears. Administrators create them under Settings → Categories, naming each one and picking its colour. Renaming one relabels every project already on it.

A new organisation starts with none, so the category picker on a project is empty until an administrator has created some. Categories are optional: a project without one simply shows no colour.

Deleting a category leaves its projects uncategorised rather than touching them.

On the Projects page, the All categories filter next to Show completed narrows the list to one category — handy once you’ve renamed one to mean something, like filtering to “Renovation” across a long list of jobs.

Project statuses

A project is Active, Snagging or Completed, set from the header by an administrator. Moving to Snagging is the handover point: the Snagging tab appears on the project and in the client portal, and outstanding defects are tracked there as snag items.

Marking a project completed asks you to confirm first.

Completing a project makes everything on it read-only. Nothing is deleted, and an administrator can set it back to Active at any time, confirming again on the way back. Completing also sets the date your client’s portal access ends, three months on.

The handover date

Once a project has started, moving an already-set handover date later asks Why is it moving? with two answers: Delayed keeps the original date as the baseline, so the project reads as delayed once the new date is past it, while Additional scope added rebaselines to the new date. Either way you can add a status note your client sees.

Bringing the date earlier, or changing it before the project starts, just saves.

Risk briefings

Risk briefing in the project header asks NavantoAI to read across the whole project, from the handover date and timeline through to open tasks and snags, and write up where the risk is. Opening the panel shows the latest briefing, shared by the whole team; anyone can regenerate it an hour after the last one, and completed projects do not offer briefings.

Deleting a project

Only administrators can delete a project, and it cannot be undone. Deleting takes the project’s client portal logins with it, so those clients lose their accounts and can no longer sign in. If the job is simply finished, mark it completed instead; that keeps everything and is reversible.