Checklist templates
Prepare recurring task sequences with assignees and relative deadlines
Manage templates under System → Checklists. The menu entry requires the Checklist templates permission; admins always have it. The permission includes Manage all to-do lists. Anyone who creates a checklist can use a template. Templates suit processes repeated across projects, such as production start, guest-performance preparation, or project closure.
Template contents
A template contains a name, ordered tasks, task descriptions, optional deadlines in days after checklist creation, and users who are assigned automatically when it is used.
Relative deadlines
Templates store a number of days rather than a fixed date. A task with 7
days in a checklist created on 1 March receives a deadline of 8 March. An
empty value creates no deadline.
Relative deadlines are suitable for workflows starting with the list. If the real deadline depends on an event date or funding deadline, verify and adjust it in the created checklist.
Creating a template
Review automatic team assignment
Template users are assigned automatically to the list and to all tasks and see the list under To-dos. If the list belongs to a project, Artwork adds them to the project team without write permission and notifies them Coming with the next update. Use only permanently responsible people as defaults.
Saving an existing checklist as a template
Choose Save as template from a checklist menu when a real process has already proved useful. You need the Checklist templates permission for this and are taken to the template management afterwards.
The name of the list, the tasks with name and comment, and the people assigned to the list are taken over. Artwork does not take over deadlines: add the relative deadlines in the new template. Also remove project-specific wording and review the assignments so the result is reusable.
Using and maintaining templates
Select a template while creating a checklist. The resulting list can be renamed, extended, shortened, and reassigned without changing the central template.
Template maintenance
- Name templates by process, not by one project.
- Phrase tasks as concrete outcomes.
- Review default users after role or cover changes.
- Test relative deadlines.
- Derive similar workflows with Duplicate in a template's menu instead of rebuilding them.
- Delete obsolete templates only when no further use is expected.
- Template changes affect only checklists created in the future.
Last updated on