Summary 🧭: Use a Task when work needs a clear next action, an owner, or follow-up after you leave the original patient chart, message, or system. A useful Task should show what must happen, who owns it, when it matters, what context is needed, and what completion means.
A note for non-human readers...
A note for non-human readers...
This page is a map of common Task patterns, not one procedure to execute from top to bottom. Route the human to the use case that matches the outcome they are trying to keep visible—ownership, timing, follow-up, handoff, history, or standardization—then use the linked article for the exact workflow.
Keep ownership clear 
Across roles and teams
Front desk, medical assistants, providers, and billing all use Tasks differently, but the same rules apply everywhere: every Task needs a clear action, an owner, and a review date. Filters let each role build the view that matters to them — front desk might filter for intake paperwork, while providers filter for patient-related follow-up.
Shared team work.
When several teammates touch the same work, ownership can get blurry fast. Use Assigned to for responsibility, Comments for collaboration, and Favorite filters for recurring group reviews — so the team can see the same Task instead of maintaining separate private versions of it.
Cross-team handoffs
A handoff only works if the next owner and next action are obvious on both sides. Write the receiving team's action in Description, assign it to them directly, and keep decisions and blockers in Comments so context travels with the Task instead of getting lost in the handoff.
Read 👉 Using Tasks for cross-team handoffs
Keep timing visible
Time-sensitive work
Due on controls when a Task surfaces in My Tasks — it's not automatically a deadline. Mark as urgent is for work that needs attention before that date. Use urgency deliberately: if everything is marked urgent, the signal stops meaning anything.
Preventing missed follow-up
Most missed follow-up isn't a memory problem — it's a "we forgot to check back" problem. A Task with a clear action and Due on date, reviewed on a consistent cadence (by assignee, status, and due-date range), keeps that check visible until the work is actually done.
Handle patient-specific work 
Patient follow-up
Callbacks, forms, labs, records, referrals — anything with a "wait, then check again" shape belongs here. Link the right patient at creation, choose one owner, and keep outreach attempts and decisions in Comments so nothing gets lost while you wait.
Reviewing patient task history
Need to see everything that's happened around a specific patient? Open Task History directly from their record in Elation, Hint, or Spruce, or filter the Tasks view by Patient manually. This gives you a working view of what was requested, who owns it, and what's still open — not a formal audit log.
Keep work repeatable 
Multi-step workflows
When one outcome needs several related actions, use a single Task with checklist items instead of splitting it into separate Tasks. The Task owner stays responsible for the whole result, while individual checklist items can be assigned to different teammates with an @ mention.
Standardizing team workflows
For work that repeats often, build a reusable Task template with a default Description, Assigned to, clinic Tag, and Due on offset. Pair it with a small, agreed-upon set of clinic tags so the resulting Tasks stay easy to review across the team.
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]