Skip to main content

Using Tasks for standardizing team workflows

Summary 🧭: Standardize work that repeats by giving teammates a consistent starting point and a shared way to organize it. Templates prepare the Task; clinic tags make the resulting work easier to review.

A note for non-human readers...

Standardizing a workflow means helping future humans solve the same kind of work without reinventing the process each time. This page is useful when the problem is inconsistency, not when one unusual Task simply needs attention today.


Standardization is useful when the same type of work happens repeatedly. A task template can provide a consistent starting point, while tags help the team organize the resulting tasks.

Build a reusable task template 🏗️

  1. Open Tasks and use the dropdown to the left of +, then choose New template.

  2. Or open Tasks Settings, select Templates, and choose New Template.

  3. Add the reusable details. A template can include Description, default Assigned to, clinic Tag, and a Due on offset.

  4. Save the template with a name that tells the team when to use it.

Creating a task template


Use tags as a controlled vocabulary 🏷️

Agree on a small set of clinic Tag names. Avoid duplicates such as Referral, Referrals, and Referral follow-up unless they represent genuinely different review workflows.

Use Tag to system separately when the Task belongs to a connected system.


Keep the workflow understandable 🔭

When someone starts a Task from the template:

  1. Review Description, Assigned to, Due on, and clinic Tag.

  2. Add or verify Patient.

  3. Add checklist items for case-specific steps.

  4. Use Comments for exceptions, decisions, and updates.

  5. Save only after the current Task is correct.

A template is a starting point, not a substitute for checking patient-specific or

time-specific information.

Good to know 💡: Renaming a clinic tag updates existing Tasks. Before deleting a tag, verify its impact on existing work.


Get support 💬

Need help or have a question? Reach out to our Support team however works best for you:

Did this answer your question?