What goes wrong today
Templates are usually set once at hire and never revisited, so they encode assumptions about visit mix that stopped being true years ago. The symptom is a provider who runs late every day while another has gaps.
Utilisation
Provider Schedule Templates
The grid that decides how many patients a provider can actually see.
The grid that decides how many patients a provider can actually see.
Templates are usually set once at hire and never revisited, so they encode assumptions about visit mix that stopped being true years ago. The symptom is a provider who runs late every day while another has gaps.
What good looks like
Templates reviewed against the visit mix actually booked, rather than the mix assumed when the template was written.
- Actual visit mix compared against template assumptions
- Duration reality-checked against recorded visit lengths
- Buffer placed where overruns actually occur
- Changes reviewed on a cadence, not once
What to measure
Agree these before changing anything, so the effect is visible rather than argued about.
- Provider running-late minutes per session
- Template utilisation by slot type
- Variance between assumed and actual visit duration
Where we stand: We don't solve this
We do not do template analytics. This is a practice-management reporting job — your PM system is the right tool.
Rollout checklist
- Document how this is handled today, and by whom.
- Put a number on the hours or dollars involved.
- Decide which cases must always reach a person.
- Agree the metrics you will judge success on.
Frequently asked questions
Do you solve this today?
We do not do template analytics. This is a practice-management reporting job — your PM system is the right tool.
How do we know if this is our biggest gap?
The Front Desk Opportunity Scan ranks this against every other area using your own volumes.
Keep going on MedReception.ai
MedFrontDesk.ai is the playbook library. MedReception.ai is the platform that runs it.