Project templates

On the project, open the ⋯ menu in the header and choose Save as template.

Give the template a name and an optional description, then pick what to capture: Deliverables & structure, Custom fields & columns, Project settings, Country & city, Tags, and Team. Billing client is off by default so templates stay client-agnostic. Conversations and attachments are coming soon.

Actual people re-adds this project’s current members when the template is used. Role slots turns each person on the deliverables into a slot you assign later, so the structure travels without the specific people.

Under Availability, keep Organization-wide so anyone can use it on any project, or pick Only for <client> to surface it just for that billing client. The Only for option appears when the project has a billing client.

Begin a new project from Projects. The form has a Start from Template section with a Whole project picker.

Organization-wide templates always show. When you choose a billing client, that client’s templates appear in a For <client> group above the organization-wide ones; other clients’ templates stay hidden.

Picking a template prefills the project’s settings, location, currency and rate, and sets the start date to today so the deliverable dates land on real dates. Everything stays editable, and what you submit wins.

A “What this template adds” panel shows exactly what will happen before you create anything: how many custom fields are enabled, created or restored from archived, which statuses and tags are added, and how many deliverables. Nothing changes in your organization until you create the project.

When the template carries deliverables, Reset progress starts them fresh, so they do not arrive marked done: each new deliverable resets to your not-started status and its completion is cleared. Turn on Keep the template’s statuses to carry the captured statuses instead, and optionally tick specific fields to clear their values. The clear list groups fields into Progress (dropdown and multi-select) and Content (everything else, like text, dates and images); anything you leave unchecked keeps the template’s value.

If the template uses role slots, assign a real person to each one; it defaults to the person it was captured from. That person becomes a project member and the slot’s deliverables follow. Leave a slot unassigned to skip it. Create the project, and the deliverables, fields, statuses, tags and team are set up for you.

Go to Settings, then Workflow, and find the Project Templates section. Each template shows its scope (Organization-wide or For a client), its source project, and whether it is archived.

Open View contents to see everything the template captured: its deliverable tree with priorities, hours and dates, its field set, statuses, tags, team and project settings. It is read-only. Each field shows how it resolves against your current fields, so you can tell at a glance whether applying the template would enable an existing field, create a new one, or restore an archived one.

Edit a template to rename it, change its description, switch its availability between Organization-wide and a client, and rename its role slots, for example from “Sarah Bennett” to “Designer”. Renaming a slot is cosmetic: it never changes which person the slot maps to on apply. Editing a template only affects projects you create from it later; any project already created from it keeps its own copy and is never changed.

A template is a snapshot frozen at save time, so later edits to the source project do not change it. Use Update from a project to re-capture its contents from any project when you want it refreshed. After you pick a project, a preview shows exactly what the refresh replaces (deliverables added, removed or changed, plus field, status, tag, team and settings changes) before anything is saved, and only your future projects are affected.

Duplicate a template to branch a variant. Archive one to hide it from the create form without losing it, and turn on Show archived to restore it later.