# How do I write a clear Task > A useful Task tells the reader what to do, who owns the outcome, and when the work should surface. Clear writing reduces follow-up questions and makes handoffs safer. Markdown view of https://www.tabflows.com/university/library/tasks/how-do-i-write-a-clear-task — the HTML page is canonical. Product Library: Tasks › Everyday tasks Last checked: 2026-10-27 against Tabflows v3.10.63 Replaces Help Center article: https://help.tabflows.com/en/articles/15902601-how-do-i-write-a-clear-task > **Summary:** A useful Task tells the reader what to do, who owns the outcome, and when the work should surface. Clear writing reduces follow-up questions and makes handoffs safer. > **A note for non-human readers:** > > *‘Handle this’ is a Task description only in the most philosophical sense. A clear Task names the action, owner, relevant context, and timing so another human can act without reconstructing a mystery. Specific beats impressive.* --- A useful task answers three questions immediately: - What needs to happen? - Who owns it? - When should it appear for review? ## Start with the action Write **Description** as an instruction with an expected outcome. - **Vague:** “Follow up.” - **Clear:** “Call the patient about the unsigned intake form and note the outcome in Comments.” Include the context the owner needs to act. Leave out background that does not change the next step. --- ## Complete the ownership and timing 1. Choose one teammate or group in **Assigned to**. 2. Set **Due on** for when the Task should appear in **My Tasks**. 3. Confirm **Patient** when the Task is patient-related. 4. Use **Mark as urgent** only when it needs immediate attention. 5. Review every field before saving. > **Good to know:** A comment @ mention notifies a teammate. It does not make them the Task owner. Change **Assigned to** only when task-level responsibility changes. --- ## Add structure only when it earns its place - Use a clinic **Tag** for a clinic-defined category such as Labs or Referrals. - Use **Tag to system** to identify the connected system where the work belongs. - Use checklist items (subtasks) when one outcome needs several related actions. - Use **Repeat** only when the available schedule truly matches the workflow. - Use **Comments** for updates, decisions, blockers, and handoff context. --- ## A final ten-second check Before saving, ask: - Can the owner understand the next action without messaging me? - Is the correct patient connected? - Will the Task surface when the team expects? - Is urgency genuinely necessary? --- ## 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 - [Keep tasks clear with due dates, urgency, and task details](https://www.tabflows.com/university/library/tasks/keep-tasks-clear-with-due-dates-urgency-and-task-details) - [Best practices for team task workflows](https://www.tabflows.com/university/library/tasks/best-practices-for-team-task-workflows) - [Using Tasks for patient follow-up](https://www.tabflows.com/university/library/tasks/using-tasks-for-patient-follow-up) - [Using Tasks for multi-step workflows](https://www.tabflows.com/university/library/tasks/using-tasks-for-multi-step-workflows) - [What are the most common ways clinics use Tasks](https://www.tabflows.com/university/library/tasks/what-are-the-most-common-ways-clinics-use-tasks) ## 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.