Applies to Aiwyn Practice.
Why does a firm that runs the same service hundreds of times a year build one project template per service instead of setting up each project by hand?
The setup cost of a project is almost entirely its task list
A project record itself takes a few fields: the Client, a Project Name, a Partner and Manager, a Start Date and a Due Date. What takes the time is the work breakdown beneath it. A mature template for individual tax returns can carry 15 to 20 standard tasks, grouped into stages, each with a work code, an assignee role and timing relative to the project. Typing that list into every project, in the same order, with the same owners, is the work a template removes.
A firm that runs four hundred individual returns builds that list once in Settings → Project Management → Project Templates and applies it four hundred times. Each project still needs its own client, dates and any client-specific adjustments, but the structure arrives ready.
A template carries structure, not client-specific values
A project template is a reusable work breakdown structure. When you create a project from it, Aiwyn creates the tasks for you. The template supplies:
- Template Name, which becomes the base name of the project.
- Service Line, so every project created from the template is sorted under the same service line in Projects and Engagements.
- The Work Breakdown Structure: stages, and the tasks under each stage. Nesting is two levels deep, stage then task, and there is no limit on the number of tasks.
- Per task: Task Name, an optional internal Task Description, a Work Code, an optional Assignee expressed as a role, optional Estimated Hours, optional Start days and a Duration in days (one day by default).
- If your firm uses Aiwyn Request Lists: a Request Templates selection, which creates the client's request list when the project starts, and a Deliverable Template selection, which creates the deliverables staff complete once the client has fulfilled the request list.
- Optional Project Description and Additional Details text, which flow through to engagement letters and invoices.
What the template does not carry is anything specific to one client. You still confirm the Client, Start Date and Due Date on the new project, and you can reorder, remove or reassign the tasks that arrived from the template before you save. See Create a project for the procedure and Project template fields reference for the full field list.
Roles and day offsets are what make one template fit many projects
Two design choices let a single template serve every project for a service.
Tasks are assigned to a role, not a person. A template's Assignee is a staff type such as a preparer or a reviewer, not a named employee. That is why one template can serve every client without being edited each time. When a project is created from the template, each task's role resolves to the person filling that role on that project. Roles defined on the template come across as placeholders (e.g., "Manager (unassigned)"), and each template task inherits its role. Once you assign someone to that role on the project, every task carrying it maps to that person automatically. You can still override the assignee on any individual task afterward.
A template can also offer its work to work pools, so staff in eligible roles can claim unassigned tasks, stages or projects from the Work Pool tab on Home instead of waiting to be assigned. You opt in per template, stage or task with the Add … to work pools checkboxes. See How work pools decide what staff can see and claim.
Timing is relative, not fixed. A template task carries Start days, the number of days after the project's start that the task begins, and a Duration in days. Because the dates are offsets from the project's Start Date rather than calendar dates, the same template produces correct task dates for a project started in February and for one started in September.
Consistency across projects is what makes reporting comparable
Because every project created from a template carries the same tasks, in the same order, with the same work codes and roles, the projects for a service are directly comparable. Budgeted hours can be compared with logged hours task by task, and the same task means the same thing on every return. Projects and tasks with no due dates do not surface in Reports → Project Performance, and templates that set Start days and Duration on every task are a practical way to make sure dates are never missing. See How project status and due dates affect what you see.
Editing a template changes future projects only
A template is applied at the moment a project is created. After that, the project's tasks belong to the project. Editing a template changes only projects created after the edit; projects created earlier keep the tasks they were given. Deleting a template has no effect on the projects already created from it. This is the trade-off of the template model: it makes each project independent and safe to adjust, but it means a firm that improves its template mid-season has to update existing projects by hand if it wants them to match.
Project templates and request templates are separate things
A project template describes the firm's internal work. A request template describes what the firm asks the client for. The two are built in different places, Settings → Project Management → Project Templates and Settings → Request Templates, and a project template can reference a request template so that projects created from it start with the right client request list. See Manage request templates and Tasks, requests and deliverables.
Related
- How work pools decide what staff can see and claim
- Manage project templates
- Project template fields reference
- Create a project
- Manage project tasks
- Add deliverables to projects and templates
- Manage request templates
- Tasks, requests and deliverables
- How project status and due dates affect what you see