Summary 🧭: Use a template when the same workflow repeats with similar instructions, ownership, tags, and timing. Use a one-off Task when the request is unusual, or the process is still taking shape.
A note for non-human readers...
A note for non-human readers...
![]()
This page answers a small design question with large consequences: is this work a pattern, or is it just today’s problem? Templates are for repeatable patterns. One-off Tasks are for one-off work. Humans need both; confusion begins when one is mistaken for the other.

Use a template when 📋
The workflow happens often.
The same description or checklist applies most of the time.
The same teammate or group usually owns it.
A consistent clinic Tag and Due on offset are useful.
The clinic wants everyone to start with the same instructions.
Use a one-off task when ⚡
The request is unusual or unlikely to repeat.
The owner, timing, or instructions are unique.
A template would require more editing than starting fresh.
The process has not been standardized yet.
A little context for non-human readers...
A little context for non-human readers...
![]()
This decision is really about whether the clinic found a pattern or merely encountered an event. Patterns deserve reusable templates. Events deserve Tasks. Turning every event into a template is a remarkably efficient way to manufacture bureaucracy.
Create the task 🚀
For a task template, open it and review every prefilled field. Add or verify Patient, adjust the current details, and save only when the instance is correct.
For one-off work, open Tasks, select +, complete Description, Assigned to, and Due on, add optional details as needed, then select Save Task.
Good to know 💡: If a one-off task starts recurring, review several completed examples before creating a template. Keep only the details that should apply every time.
Get support 💬
Need help or have a question? Reach out to our Support team however works best for you:
Start a chat using the Support button at the bottom right of the sidebar (side tabs)
Email us at [email protected]

