Dental recall drive Gantt chart template: staged sends and hygiene capacity
An editable Gantt chart for an annual dental recall drive: list cleaning, message approval, staged sends with response waits, extra hygiene sessions and phone follow-up, with dependencies and milestones.
What the dental recall drive gantt chart template: staged sends and hygiene capacity process is
A recall drive is a short campaign with a fixed start, run beside a full diary. The work is easy to list. The difficulty is order: the list must be clean before anything is sent, the wording must be approved before the templates are built, and the number of extra hygiene sessions depends on how many patients answer the first wave. A timeline shows those links, and it shows how much of the drive is waiting for patients to reply.
This template has five groups: Patient list, Messages, Sending waves, Chair capacity and Follow-up. It has 24 tasks and three milestones, and a total length of 31 working days in the illustrative numbers. "Set the drive goals and recall rules" (2 working days) is the only starting task, so give it a fixed Start. The list path runs "Export the overdue recall list" (1), "Clean the list of duplicates and leavers" (4) and "Check consent and contact preferences" (3), which starts 2 working days into the cleaning with a start-to-start link. "Recall list ready" is the first gate. The message path runs in parallel: "Draft the message wording" (3), "Dentist approves the wording" (2), "Build the message templates by recall type" (2) and "Messages approved".
Both gates must open before "Send wave 1 to the longest overdue" (1). Then comes the part of the plan that sets the pace: "Wave 1 response wait" (5), "Send wave 2" (1), "Wave 2 response wait" (5), "Send the final reminder" (1) and "Last responses come in" (4). Capacity is planned from the first response, not the last. "Count free recall slots" (2) runs early, and "Decide on extra hygiene sessions" (1) waits for both that count and "Wave 1 response wait". "Open the extra hygiene sessions" (3) and "Extra sessions run" (10) follow. "Book recalls as replies arrive" (12) starts 1 working day into the first wave's wait, so booking runs alongside the waves instead of after them.
Follow-up is the last group. "Phone patients who have not replied" (6) starts 2 working days into "Wave 2 response wait", so calls begin while the second wave is still coming back. "Update records for patients who moved or left" (3) follows "Last responses come in". "Count booked and attended recalls" (2) waits for the sessions, the booking, the calls and the record updates, and "Drive review held" closes the plan. Every duration is illustrative, so replace them with your own response times and session lengths. Rules for how long a patient may go between recalls, and what a message may say, differ by country and by practice, so the plan holds your durations and leaves those rules to you.
A timeline schedules the drive. It does not tell you how many patients will answer or how many hygiene hours you need. Put the numbers from your own last drive in the task names or in notes. For the visit the drive is trying to fill, see /templates/dental-recall-and-hygiene-visit-process. For how a drive is planned around waits, see /guides/recall-drive-gantt-chart.
What this flowchart covers
In this template
- Five groups, Patient list, Messages, Sending waves, Chair capacity and Follow-up, with 24 tasks and three milestones: "Recall list ready", "Messages approved" and "Drive review held".
- Three sends with response waits between them: "Send wave 1 to the longest overdue", "Send wave 2" and "Send the final reminder", each followed by a wait or the last responses.
- A capacity decision that depends on the first wave: "Decide on extra hygiene sessions" needs "Count free recall slots" and "Wave 1 response wait" before "Open the extra hygiene sessions".
- Booking and calls that start inside the waits: "Book recalls as replies arrive" and "Phone patients who have not replied" are start-to-start links, so they overlap the waves.
When to use this template
- You run a recall or reactivation drive once or twice a year and want a plan you can resize each time.
- You want to see how late the first send can go before the extra hygiene sessions no longer fit before a holiday or a quarter end.
- You need the dentist, the hygienist and the front desk to see the same order of approvals, sends and calls.
- You want to compare a two-wave drive with a three-wave one by lengthening or shortening the waits.
The plan, task by task
Every task in the chart with its length in working days and what it waits for. A dependency is a step number; SS is start-to-start, FF is finish-to-finish, and +n is a lag in working days.
| # | Task | Group | Working days | Depends on |
|---|---|---|---|---|
| 1 | Set the drive goals and recall rules | Patient list | 2 | |
| 2 | Export the overdue recall list | Patient list | 1 | 1 |
| 3 | Clean the list of duplicates and leavers | Patient list | 4 | 2 |
| 4 | Check consent and contact preferences | Patient list | 3 | 3SS+2 |
| 5 | Recall list ready | Patient list | Milestone | 3, 4 |
| 6 | Draft the message wording | Messages | 3 | 1 |
| 7 | Dentist approves the wording | Messages | 2 | 6 |
| 8 | Build the message templates by recall type | Messages | 2 | 7 |
| 9 | Messages approved | Messages | Milestone | 8 |
| 10 | Send wave 1 to the longest overdue | Sending waves | 1 | 5, 9 |
| 11 | Wave 1 response wait | Sending waves | 5 | 10 |
| 12 | Send wave 2 | Sending waves | 1 | 11 |
| 13 | Wave 2 response wait | Sending waves | 5 | 12 |
| 14 | Send the final reminder | Sending waves | 1 | 13 |
| 15 | Last responses come in | Sending waves | 4 | 14 |
| 16 | Count free recall slots | Chair capacity | 2 | 1 |
| 17 | Decide on extra hygiene sessions | Chair capacity | 1 | 11, 16 |
| 18 | Open the extra hygiene sessions | Chair capacity | 3 | 17 |
| 19 | Extra sessions run | Chair capacity | 10 | 18 |
| 20 | Book recalls as replies arrive | Chair capacity | 12 | 11SS+1 |
| 21 | Phone patients who have not replied | Follow-up | 6 | 13SS+2 |
| 22 | Update records for patients who moved or left | Follow-up | 3 | 15 |
| 23 | Count booked and attended recalls | Follow-up | 2 | 15, 19, 20, 21, 22 |
| 24 | Drive review held | Follow-up | Milestone | 23 |
How it works
Fix the start
Give "Set the drive goals and recall rules" a fixed Start on the day the drive begins. The plan starts on the earliest fixed Start and is scheduled forward, so every other date follows from it.
Set the list and message paths
Resize "Clean the list of duplicates and leavers" and "Check consent and contact preferences" to what your records need, and give the approval tasks the time your dentist actually takes. "Send wave 1 to the longest overdue" waits for both paths.
Set the response waits
Change "Wave 1 response wait" and "Wave 2 response wait" to the replies you saw in your last drive. If you send a third wave, copy a send and a wait and link them in order.
Size the extra hygiene time
Set "Count free recall slots" and "Extra sessions run" from your diary. The decision task shows the earliest date extra sessions can be opened, so check it against holidays and staff leave.
Add owners, share and export
Put the person responsible for each task in People, share the chart as a link with the team, and export a PDF or PNG for the practice meeting.
Frequently asked questions
Can the chart tell me how many patients will reply?
No. It shows the durations you enter for "Wave 1 response wait" and "Wave 2 response wait" and moves the dates after them. Use the figures from your last drive and change them when you learn more.
Does it choose how many hygiene sessions to open?
No. It places "Decide on extra hygiene sessions" after the first response wait and shows when sessions could start. The number of sessions is your decision, and you can put it in the task name.
Are there rules for how often I may contact patients?
Rules on recall messages and consent differ by country and by practice. The plan holds your durations and does not check any of them, so keep your own rules as tasks or notes.
Can I run waves in parallel for different recall types?
Yes. Copy the send and wait tasks for each type, link them from "Messages approved" and join them again before "Count booked and attended recalls".