Canonical page: https://tellenze.com/guides/work-templates Work templates # Reuse a good start. Make it your own. Give repeat work a clear structure and useful checks. Create a template, review the objects it will create, then adapt the new work to this particular outcome. [Explore example setups](#template-examples)[Read the template instructions](https://tellenze.com/help/templates) - Reusable definition - Reviewed preview - New work A useful starting structure Illustrative model · A fixed template version creates new objects. Each new work item can then change independently. Choose the smallest useful structure ## A whole Project. Or just the next task. Templates need to be enabled for your installation. Members apply templates they can see where they have permission to create the resulting work. Native template types · choose the type before editing its definition Type | What it starts | Where it can be used | Project | A new Project, with reusable labels, folders, knowledge pages, milestones and work. | Workspace templates only. Choose the actual Project key, name, workflow and visibility when applying. | Milestone | A milestone and its associated work in an existing Project. | Available as a workspace or Project template. A Project template stays in its own Project. | Task | One work item or a linked structure of work in an existing Project. | Workspace Task templates can also target an eligible Team. Task definitions cannot create milestones or folders. | Administrators manage workspace templates in Admin → Templates. Administrators and the Project creator manage Milestone and Task templates in Project settings → Templates. Applying a template creates new objects; it does not update existing work with a similar title. Illustrative setups to create or adapt ## Start with a pattern your team can review. These examples are ideas for your own definitions. They are not pre-installed templates. Keep the reusable structure small, and add people, access and current decisions to the resulting work. Project · Client launch ### A repeatable launch. Start with a launch milestone, a parent Story, preparation and verification children, a Release label, and a handbook folder with one checklist page. Reusable check: verification evidence is saved and the launch owner approves the release. At application, choose the customer’s Project name, workflow and visibility. Set the people and current dates on the new work. [See a complete Project definition](https://tellenze.com/help/template-reference#example-a-reusable-launch-project) Milestone · Ready for handover ### A clear handover point. Create a milestone with linked work for the handover notes, access checks and a walkthrough. Use symbols inside the definition to connect the work to that milestone. Reusable check: the receiving team can use the instructions and knows who handles the next question. Review the target date and add current contacts after applying. [Check milestone links and fields](https://tellenze.com/help/template-reference#labels-milestones-and-knowledge) Task · Timeboxed investigation ### A useful investigation. Use the discovery work type, a clear question, timebox_hours and acceptance criteria asking for findings, evidence and a recommendation. Reusable check: explain what is known, what remains uncertain and the suggested next decision. Confirm that Discovery is enabled in the destination, then add the current sources and assignee. [Check supported work fields](https://tellenze.com/help/template-reference#work-item-fields) A small definition you can try ## A release check. With a clear finish. Choose New template, name it for your team and select Task. The editor provides a starter definition. This illustrative JSON gives one work item a purpose, completion checks and a relative due date. due_date_offset_days: 2 means two calendar days after the preview’s reference date. It includes weekends. Check the resolved date before applying. The example leaves out a stage key, so the new task uses the destination workflow’s initial stage. It carries no assignee, membership, credentials or completion history. [Read the definition reference](https://tellenze.com/help/template-reference) Illustrative Task definition · create and adapt it in your own template editor { "task": { "title": "Verify the release", "type": "task", "description": "Check the release before it reaches customers.", "acceptance_criteria": "Smoke checks pass, release notes are reviewed, and a rollback owner is identified.", "complexity": "S", "due_date_offset_days": 2 }, "labels": [] } Check that Task is allowed in your destination. Saved definitions use supported fields and valid JSON. A link to a repository does not connect it or provide credentials. Create, preview, then apply ## See the new work before you create it. Keep reusable guidance in the definition. Make choices specific to this use when applying the template or editing the new work. - 01 ### Save the reusable definition. Enter the name, description and type. Edit Definition (JSON) and choose Create template. The first saved version is fixed. - 02 ### Choose the destination. Open Preview & apply. For a Project template, supply an unused Project key, name and workflow. For other templates, choose the eligible Project or Team; Project-scoped templates already have their destination. - 03 ### Generate and inspect the preview. Choose Generate preview. Read Resolved objects, parent links, milestone membership, labels, dates and stages. For a new Project, review Project visibility too. - 04 ### Apply the reviewed objects. After a successful current preview, choose Apply … objects. Inspect the result, then add people and details for this use. A separate application creates another set of objects. Illustrative application path · each step has a different purpose Definition ### A fixed template version. The reusable structure and checks are saved together. Preview ### The exact proposed objects. The destination, workflow and relative dates resolve into concrete choices. Result ### Independently editable work. Later template versions do not change this Project, milestone or task. A rejected preview needs a compatible destination or a corrected template version. The application dialog has no stage or label mapping editor. Regenerate the preview after changing destination inputs, when it expires, or when its source changes. Current permissions are checked again when applying. Improve the next use ## Learn from the work. Save a new version. After the first use, ask which steps helped and which checks were missing. Use New version to save the improved definition. Each saved version stays fixed, and earlier work keeps its own content. Archive removes a template from normal use. An authorized manager can find it with Show archived and restore it. Existing work remains. Before making it a habit ## Check one complete use. - The scope fits.It creates only the objects this repeatable outcome needs. - The checks are useful.Someone can tell when the resulting work is ready. - Dates and access are correct.Review calendar-day offsets, workflow stages and destination visibility. - Current details are added.Set assignees, instance-specific sources and decisions on the new work. Where Required Context applies, a connected agent must receive the current required reading before a protected application. A normal source link does not replace that reading. A few useful details ## Keep reuse predictable. Are these example templates already installed? These are illustrative setups you can create or adapt. Open the template editor available in your workspace, choose the native type and check the [definition reference](https://tellenze.com/help/template-reference). This page does not install or apply a template. Will a new version update work we already created? No. Applying a template creates independent new objects. Later template edits affect a future application. Edit existing work directly when it needs to change. Can a template assign people or bring attachments and comments? Definitions do not carry assignees, membership or sharing lists, credentials, attachments, comments or completion history. Add the relevant people, access and current supporting material to the destination or resulting work. Can I apply a milestone template to a Team? Only workspace Task templates can target a Team. Milestone templates need an existing Project. Project-scoped Milestone and Task templates stay in their own Project. Can my connected agent use templates? Discover the deployed tools first. list_templates, preview_template and apply_template provide the supported path. The agent must review the exact preview and use its captured versions and hash. Current access and Required Context still apply. [Follow the agent workflow guide](https://tellenze.com/guides/agent-workflows). Put the structure to use ## A clear starting point. A result worth reviewing. Choose one useful template, inspect its first application and improve the next version from what your team learns. [Review and share the result](https://tellenze.com/guides/review-and-share-results)[Open template help](https://tellenze.com/help/templates) Keep your next step clear ## Find the guide for your next step. [Browse all guides](https://tellenze.com/guides) COME TAKE A LOOK ## A little less busy. A lot more together. Curious? Join the waitlist and see how we welcome your team. Tell us a little about your team. We’ll explain the next steps and invite you when we have capacity for your workspace. [Join waitlist](https://tellenze.com/waitlist)Start with your email. No payment needed to join.