A template captures a project's structure — its views, task lists, milestones, and labels — so you can spin up a new project that starts organized instead of empty. Templates are available on the Pro and Enterprise plans.
Create a template from an existing project
Open the project you want to turn into a template.
Click the project menu and select Save as template.
Name the template — for example, Client onboarding — and choose whether to include existing task assignees or leave them blank.
Click Save.
Templates are saved at the team level, so any Owner, Admin, or Member on that team can use them.
Start a project from a template
From a team, click New project.
Select From template instead of starting blank.
Pick a template and give the new project its own name.
Click Create project.
What a template includes
Included | Not included |
Views and their default groupings | Time tracking history |
Task lists, subtasks, and labels | Status update history |
Milestones, shifted relative to the new project's start date | Comments on tasks |
Custom fields | File attachments |
Note: Examply ships a handful of starter templates — Client onboarding, Sprint planning, and Product launch — under New project → From template → Examply templates.
Managing templates
A team's templates live under Team settings → Templates, where an Owner or Admin can rename, reorder, or delete them. Deleting a template doesn't affect any project already created from it — those projects keep running normally.
Updating a template doesn't retroactively change projects made from it earlier. If a client-services team refines its onboarding process, saving a fresh project as the new template keeps the old one available until it's deleted, so any project already in flight isn't disrupted.
A few templates worth building
Product teams tend to get the most value from a Sprint planning template with a two-week Timeline already blocked out and label placeholders for Bug, Feature, and Tech debt. Client-services teams do better with a Client onboarding template that includes a fixed set of milestones — kickoff call, requirements sign-off, first delivery — since those rarely change from client to client.
Templates work best when they're kept a little sparse rather than fully detailed — a handful of placeholder tasks with clear names beats twenty tasks that need renaming for every new client.
Tip: Build one solid template per recurring project type rather than one per client — you can rename it and adjust dates for each new project after creating it.