Skip to content

Project templates

For the helpdesk team

A project template is a pre-written list of milestones and tasks. When you raise a new project from a template, all that structure is copied in for you to tweak — fewer blank-page moments, more consistency across the team.

  • Name + description — the kind of project this kicks off.
  • Milestones — labelled checkpoints. Each milestone has an optional target offset days — how many days from project start this milestone is due. Lets the project schedule itself once you set a start date.
  • Tasks — individual to-dos. Each task can optionally be assigned to a milestone index (0-based), grouping it under that milestone in the project view.
  • Is active — flag. Inactive templates are hidden from the picker but kept in the database.
  • New starter onboarding — milestones for Day 1, Week 1, Month 1, with tasks for each (mail account, laptop, induction booking, training sign-ups).
  • Classroom refresh — milestones for Survey, Order, Install, Sign-off, tasks per item (network sockets, projector, displays).
  • Summer device refresh — milestones for each year group cohort.

If you’re using a template once a year for the summer refresh, that’s enough. If you’re using it for every laptop returned through reception, that’s overkill — those are tickets, not projects.

Edits don’t propagate to projects already raised from the template. New projects pick up the new structure; existing ones stay as they were. If you need to push a structural change across live projects, do it manually.