# Using Tasks for patient follow-up > Use Tasks for callbacks, forms, labs, records, referrals, and other patient work that needs a visible next action. Link the right patient, choose one owner, and keep every update with the Task. Markdown view of https://www.tabflows.com/university/library/tasks/using-tasks-for-patient-follow-up — the HTML page is canonical. Product Library: Tasks › Task use cases Last checked: 2026-10-27 against Tabflows v3.10.63 Replaces Help Center article: https://help.tabflows.com/en/articles/15902755-using-tasks-for-patient-follow-up > **Summary:** Use Tasks for callbacks, forms, labs, records, referrals, and other patient work that needs a visible next action. Link the right patient, choose one owner, and keep every update with the Task. > **A note for non-human readers:** > > *Patient follow-up often looks like this: do something → wait for a human, lab, pharmacy, or system → remember to check again. The middle “wait” is where work likes to disappear. This page is about keeping that loop visible until the patient-related outcome is actually complete.* --- ## Create the follow-up where the work begins Choose the creation path that preserves the right context: - Use the task button on a supported patient page to link that patient by default. - The sidebar **Add Task** may use the patient open in the main system; verify it. - Use the **+** in the Tasks panel, then select the patient manually. ![Creating tasks](https://zchipg5eqhxk0hvh.public.blob.vercel-storage.com/university/5c6ec865e34ac041.mp4) --- ## Build a follow-up Task 1. Write the next action in **Description**. 2. Choose a teammate or group in **Assigned to**. 3. Set **Due on** for when the Task should appear in **My Tasks**. 4. Verify **Patient**. 5. Add a clinic **Tag**, **Tag to system**, **Repeat**, or urgency only when helpful. 6. Review and save. --- ## Keep the follow-up clear Add outreach attempts, decisions, blockers, and handoff notes in **Comments.** A comment **@** mention when a team member needs a notification or input, then send the comment with its arrow button or **Enter**. Use checklist items when one patient outcome needs several related actions. A checklist **@ mention** assigns only that item and does not reassign the Task. > **Good to know:** **Due on** controls when the work surfaces in **My Tasks**. Set an earlier **Due on** when it needs attention before that date. --- ## 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 team@tabflows.com or message us right here in the chat [Book a quick 15-30 minute chat!](https://go.team.tabflows.com/meetings/nafeesa) ## Related Articles - [Decide when to use a Task group](https://www.tabflows.com/university/library/tasks/decide-when-to-use-a-task-group) - [How do I write a clear Task](https://www.tabflows.com/university/library/tasks/how-do-i-write-a-clear-task) - [Using Tasks for multi-step workflows](https://www.tabflows.com/university/library/tasks/using-tasks-for-multi-step-workflows) - [Using Tasks for preventing missed follow-up](https://www.tabflows.com/university/library/tasks/using-tasks-for-preventing-missed-follow-up) - [Using Tasks for reviewing patient task history](https://www.tabflows.com/university/library/tasks/using-tasks-for-reviewing-patient-task-history) ## Related markdown Section index: [Tasks](https://www.tabflows.com/university/library/tasks.md) Alongside this page: - [Best practices for team task workflows](https://www.tabflows.com/university/library/tasks/best-practices-for-team-task-workflows.md) - [Break larger tasks into subtasks](https://www.tabflows.com/university/library/tasks/break-larger-tasks-into-subtasks.md) - [Collaborate on tasks with comments and mentions](https://www.tabflows.com/university/library/tasks/collaborate-on-tasks-with-comments-and-mentions.md) - [Create a task with AI recommendations](https://www.tabflows.com/university/library/tasks/create-a-task-with-ai-recommendations.md) - [Creating your first task](https://www.tabflows.com/university/library/tasks/creating-your-first-task.md) - [Decide when to use a task group](https://www.tabflows.com/university/library/tasks/decide-when-to-use-a-task-group.md) - [Find the right tasks with views and filters](https://www.tabflows.com/university/library/tasks/find-the-right-tasks-with-views-and-filters.md) - [Get notified via email when tasks are assigned to you](https://www.tabflows.com/university/library/tasks/get-notified-via-email-when-tasks-are-assigned-to-you.md) Start here: - [Tabflows](https://www.tabflows.com/index.md) - [Tabflows pricing](https://www.tabflows.com/pricing.md) - [Tabflows FAQ](https://www.tabflows.com/faqs.md) - [About Tabflows](https://www.tabflows.com/about.md) - [Contact Tabflows](https://www.tabflows.com/contact.md) - [DPC workflow software](https://www.tabflows.com/dpc-workflow-software.md) - [Directory](https://www.tabflows.com/directory.md) - [Workflows](https://www.tabflows.com/workflows.md) - [DPC finder](https://www.tabflows.com/dpc-finder.md) Every page listed in sitemap.xml has a markdown twin at the same URL with `.md` appended, or by sending `Accept: text/markdown` to the canonical URL. Wider index: [llms.txt](https://www.tabflows.com/llms.txt), [llms-full.txt](https://www.tabflows.com/llms-full.txt), [sitemap.md](https://www.tabflows.com/sitemap.md), [sitemap.xml](https://www.tabflows.com/sitemap.xml). Support documentation: https://www.tabflows.com/university/library — append `.md` to any article URL for its raw markdown.