# Sort every refill request by its safest next action > Every refill request sits in one of four lanes with an owner, next action and due date, so the doctor sees what needs judgment. Markdown view of https://www.tabflows.com/university/playbooks/refill-triage-board — the HTML page is canonical. [](https://www.tabflows.com/university/playbooks) 1. [Playbooks](https://www.tabflows.com/university/playbooks) 2. [Refills & Rx](https://www.tabflows.com/university/playbooks#refills-and-rx) Every refill request sits in one of four lanes with an owner, next action and due date, so the doctor sees what needs judgment. - Spruce - Elation - Saves about 5 min per refill (est.) Last checked Oct 27, 2026 against Tabflows v3.10.63 ## The situation Refill requests come in through every door. One arrives through the patient portal, one by text, one from the pharmacy, and one gets mentioned during a visit. One needs labs first, one needs a doctor's review, and one is a bigger clinical issue in disguise. The refill itself is not the problem. The problem is that each request needs a different level of attention. Some are routine, some need review, some need patient follow-up, and some should not be refilled without an appointment. Treat them all the same and the day fills with noise. ## Steps 1. **Set up four lanes as clinic Tags** Ask an Admin to create one clinic Tag for each lane in Task Settings: Routine refill, Needs clinical review, Needs patient follow-up and Blocked. Keep it to those four. 2. **Make each request a Task, whatever door it came through** Use the patient-page Task button or + in Tasks, confirm Patient, and choose its lane in the Tag field. For a text in a linked Spruce conversation, select the lightbulb and review the recommended Task before you select Save task. 3. **Give it an owner, a next action and a due date** In Description, write the safest next action, not the fastest way to clear it. In Assigned to, choose the person who should take that action, not whoever saw it first, and send anything that needs clinical review to the provider. Set Due on for when they should see it in My Tasks. 4. **Save each lane as a filter** In Tasks, filter by the lane's Tag with Status set to To do, then select Save filter and name it after the lane. The provider opens Needs clinical review, and the team works Routine refill. 5. **Move the Task when its lane changes** When a routine refill turns out to need review, change its Tag and Assigned to and add a comment saying why. Set a blocked request to Waiting while it waits on labs or an appointment, and mark it Done only when nothing is left to do. ## The outcome The doctor sees the requests that actually need judgment, and the team handles routine refills with confidence. Every request has an owner, a next action and a due date, so patients get faster answers and requests stop disappearing into the inbox. ## Ask Sidekick Sidekick is the AI assistant inside Tabflows. Hey Tabflows, list every open refill task across the clinic with its patient, owner and due date, oldest first, so we can sort each one into routine, needs clinical review, needs patient follow-up or blocked. ## In the Product Library - [Organize Tasks with clinic tags](https://www.tabflows.com/university/library/tasks/organize-tasks-with-clinic-tags) - [How do I save and reuse a task filter](https://www.tabflows.com/university/library/tasks/how-do-i-save-and-reuse-a-task-filter) - [Create a Task with AI Recommendations](https://www.tabflows.com/university/library/tasks/create-a-task-with-ai-recommendations) - [How to update, complete, reopen, or delete tasks](https://www.tabflows.com/university/library/tasks/how-to-update-complete-reopen-or-delete-tasks) - [Using Spruce with Tabflows](https://www.tabflows.com/university/library/integrations/using-spruce-with-tabflows) - [Using Elation with Tabflows](https://www.tabflows.com/university/library/integrations/using-elation-with-tabflows) [Read the full guide](https://www.tabflows.com/blog/refill-triage-board-dpc) [Open it in the Automation catalog](https://www.tabflows.com/university/automations?automation=refill-triage-board) ## Related markdown Section index: [Playbooks](https://www.tabflows.com/university/playbooks.md) Alongside this page: - [Advance directive tracking](https://www.tabflows.com/university/playbooks/advance-directive-tracking.md) - [After hours answering service](https://www.tabflows.com/university/playbooks/after-hours-answering-service.md) - [After hours message triage](https://www.tabflows.com/university/playbooks/after-hours-message-triage.md) - [Billing decline follow up](https://www.tabflows.com/university/playbooks/billing-decline-follow-up.md) - [Call follow up loop](https://www.tabflows.com/university/playbooks/call-follow-up-loop.md) - [Chronic care check ins](https://www.tabflows.com/university/playbooks/chronic-care-check-ins.md) - [Clia and compliance renewals](https://www.tabflows.com/university/playbooks/clia-and-compliance-renewals.md) - [Dea and license renewals](https://www.tabflows.com/university/playbooks/dea-and-license-renewals.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.