REPEATABLE DELIVERY
Start the next project with a proven sequence of work
Build reusable project structures with roles, tasks, checklists, milestones and timing. Launch a new project from a published version and assign real colleagues.
Reuse the preparation, then adapt the case
Recurring work often begins with the same questions: which steps come first, who is needed and what must be checked before delivery? A project template captures that structure once. Starting a new project does not require copying a previous customer’s working records. Instead, use a published template version, choose the new project details and adapt the resulting work to the actual engagement.
Capture a useful operating pattern
Templates can define project duration, roles, stages, milestones and tasks. Task definitions can include a description, priority, estimated minutes, checklist items, a parent task, milestone and predecessor references. Role keys describe responsibility before a particular person is selected. This lets a reusable “reviewer” role remain meaningful across engagements with different teams instead of hard-coding one colleague into every future project.
- Roles, stages and milestones
- Tasks with checklists and relationships
- Relative timing and effort estimates
Publish a version before using it
Drafting a template and using a published version are separate concerns. Project creation resolves a published template version and validates its structure and references. Existing engagements do not need to be treated as live copies that change whenever someone improves the template. Review the recurring process, publish the intended version and select that known starting point for the next delivery.
- Published version as the starting point
- Validated task, stage and role references
- Improve future work without rewriting a previous project
Map the pattern to a real project
At creation, choose the project name, owner, start, visibility and supported customer or commercial-case context. Map template roles to active colleagues. Relative task and milestone offsets become dates from the chosen start. The current business-day calculation excludes weekends; do not assume that every country’s public holidays are automatically removed. Review the dates before committing them to the customer.
- Real people mapped to template roles
- New project and customer context
- Review generated dates for local working arrangements
A concrete workflow
Describe the recurring work
Create a pattern containing the task sequence, roles, checklists and meaningful delivery checkpoints.
Review and publish
Check its relationships and wording, then publish the version the team should use.
Start the engagement
Choose the new project, start date and customer, and map role responsibilities to active colleagues.
Adapt the resulting plan
Review the created tasks and dates for the actual scope, staffing and holiday arrangements.
An illustrative working example
Example: repeating a customer onboarding
An implementation team creates an onboarding pattern with discovery, configuration, review and handover. A preparation checklist sits on the discovery task, and the reviewer role is distinct from the implementer. For the next customer, the lead selects the published version and maps the roles to the available colleagues. Generated dates provide a starting plan, which is adjusted for the customer’s availability before work begins.
Questions about this topic
Is a template just a copied task list?
It can carry more structure: roles, stages, milestones, checklists, relative timing and supported task relationships as well as titles.
Can I start from an unpublished draft?
The supported instantiation flow requires a published template version. This separates process preparation from the version used for real delivery.
Are local holidays always handled automatically?
No. The current template business-day helper skips weekends. Review public holidays and company-specific non-working days when adapting the generated dates.
Does changing the template update ongoing projects?
Do not assume live synchronization. A project is instantiated from a selected published version and then managed as its own engagement.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Asana
Workflow concept: Identify a repeatable task sequence before authoring a published project template.
Notion
Workflow concept: Review an operating checklist and map its steps to template roles.
Google Sheets
Workflow concept: Check relative dates and role mappings before instantiating the next engagement.