Patient Recall Tracker.
Move overdue patients from due to booked with a simple recall pipeline.
About this template
Every practice has a list of patients overdue for their next cleaning, adjustment, or follow-up, usually buried in the PMS. This tracker turns it into a pipeline with columns for due, contacted, scheduled, and seen, plus recall interval, days overdue, and contact attempts on every card. Filter by how overdue someone is and log each touch so nobody falls through.
The live demo ships with sample data: About 80 recall records with coded patient IDs, recall intervals of 3, 6, and 12 months, contact attempt logs, and a realistic spread across pipeline stages. No PHI.
The prompt behind this template
This is the exact description the Prized agent built it from. Yours can be one sentence: the agent fills in the rest, and you refine from there.
Show the full prompt
Build a patient recall pipeline for Brightside Dental, a two dentist, three hygienist practice in Tucson, used by the front desk to move overdue patients from due to booked so nobody falls through. Layout. A summary strip of four chips: patients due (34), overdue more than 90 days (12), scheduled this month (14), and average contact attempts before booking (2.3). The hero is a four column board: Due, Contacted, Scheduled, and Seen, each column header showing its card count. Every card carries a coded patient ID like PT-2031, the recall type (hygiene cleaning, perio maintenance, or exam), an interval badge for 3, 6, or 12 months, a days overdue badge (green under 30, amber 30 to 90, red over 90), the contact attempt count, and the last touch date. Above the board sit filter chips for overdue bucket (all, under 30, 30 to 90, 90 plus) and recall type. Clicking a card opens a side sheet with the patient's recall details, a chronological contact log showing date, channel (call, text, email), and outcome, plus a form to log a new touch and a control to move the card to the next stage. Data. Seed about 80 recall records spread as 34 Due, 21 Contacted, 14 Scheduled, and 11 Seen, with intervals of 3 months for perio maintenance, 6 months for hygiene cleanings, and 12 months for exams, and due dates producing overdue values from 5 to 160 days. Seed about 60 contact attempt log entries attached mostly to Contacted and Scheduled cards, mixing calls, texts, and emails with outcomes like left voicemail, replied, and booked. Coded patient IDs only, no names, no PHI. Plant the story: a red cluster of 12 twelve month exam recalls sits more than 90 days overdue in the Due column with zero contact attempts, exactly the patients slipping through the cracks. Behavior. Days overdue is computed from each record's due date relative to today, and the summary chips are computed from the board. Cards sort inside each column by days overdue descending. Logging a touch stamps today's date and increments the attempt count. Visual identity. Use a slate blue accent for primary actions, column headers, and active filters on a clean light neutral base, calm and clinical, letting the amber and red overdue badges do the warning work.
More like this
All templatesAppointment No-Show Tracker
See where no-shows cluster by provider, weekday, and visit type, and fix the schedule.
Provider Schedule Planner
A color coded weekly grid of provider slots with live utilization percentages.
Fitness Class Profitability Calculator
Know each class's breakeven headcount before it earns a slot on the schedule.
