Telehealth Workflow Checklist for Private Practice (2026 Guide)

Telehealth Workflow Checklist for Private Practice (2026 Guide)

A telehealth workflow checklist is the operational backbone of a well-run virtual care service. Without it, each clinician develops their own pre-session routine, consent gets managed inconsistently, and post-session documentation varies in quality depending on who ran the session.

This checklist covers the full telehealth session lifecycle for private practices: from booking through consent, session delivery, clinical documentation, and post-session follow-up. Use it as a configuration guide when setting up a new telehealth service, or as an audit tool to identify gaps in an existing one.

Phase 1 — At Booking

These tasks must happen automatically when a telehealth appointment is created. Manual steps at booking are the first source of missed consent and poorly prepared patients.

System tasks (automated):

• Appointment created with visit type set to "Telehealth" — not a generic appointment type
• Correct telehealth consent form package selected based on visit type and patient profile (adult / minor / new patient)
• Consent form package sent to patient's documented email or portal account
• Appointment confirmation sent to patient including: date, time, clinician name, video join link, and technical preparation instructions
• Appointment added to clinician's telehealth schedule view

Front desk tasks:

• Patient contact details verified in record — phone number current (needed for fallback call if video fails)
• For new patients: confirm patient has received confirmation and can access the join link (brief confirmation SMS or email)
• For minors: confirm guardian is documented in the record and guardian's contact is current

Owner: Receptionist / Front desk lead SLA: All booking tasks complete within 30 minutes of appointment creation

---

Phase 2 — 24 Hours Before Session

The 24-hour checkpoint is the last opportunity to resolve consent and technical issues without disrupting the session day.

System tasks (automated):

• Consent status check: has the patient completed and signed the required consent forms?
• If consent is incomplete: reminder sent to patient with direct link to incomplete forms
• If consent is still incomplete after automated reminder: front desk task created for personal follow-up

Front desk tasks:

• Review consent status for all tomorrow's telehealth appointments
• For any incomplete consent: contact patient by phone or SMS to request completion
• Confirm patient has working access to video link (for patients who flag technical concerns)
• Flag any same-day reschedule risks to clinician

Clinical preparation tasks:

• Clinician reviews patient record before tomorrow's sessions: last clinical notes, active treatment plan, pending items
• Any required pre-session materials (assessment forms, questionnaires) confirmed as received
• Interpreter or accessibility accommodation confirmed if flagged on the record

Owner: Front desk lead (consent); clinician (clinical prep) SLA: All 24-hour tasks complete by end of business day before the session

---

Phase 3 — Session Day (2 Hours Before)

System tasks (automated):

• Final consent status check — alert to front desk if still incomplete
• Same-day technical readiness reminder sent to patient: "Your session is in 2 hours. Please ensure your camera and microphone are working and you're in a quiet, private location."
• Waiting room active and accessible

Front desk tasks:

• Confirm consent is complete for all same-day telehealth appointments — escalate any gaps immediately
• Ensure clinician's session dashboard is accessible and showing today's telehealth schedule
• Confirm fallback phone number for each patient is recorded and accessible to clinician

Owner: Front desk lead SLA: All same-day prep complete 30 minutes before first session

---

Phase 4 — Session Initiation

Clinician tasks (before starting session):

• Confirm consent status in session dashboard — do not start if mandatory consent is missing without documented authorisation
• Review patient record and treatment plan notes (last 2–3 entries)
• Confirm session environment: private, good lighting, no background interruptions
• Test audio and video before admitting patient from waiting room
• Note patient's verbal confirmation that they are in a private location at session start (document in session notes)

Technical checklist:

• Camera active and patient clearly visible
• Microphone active with no echo or feedback
• Connection stable (no buffering or video artefacts)
• Screen share functional if required for this session type
• Recording notification given to patient (if session is being recorded) and patient consent confirmed verbally

Fallback protocol (if video fails within first 5 minutes):

• Attempt reconnect once
• If reconnect fails: clinician calls patient on documented phone number
• Audio-only session conducted and documented as telehealth (audio fallback)
• If phone also fails: session documented as attempted, front desk notified, reschedule offered

---

Phase 5 — During Session

Clinical documentation tasks:

• Subjective: chief complaint and history in patient's own words
• Objective: relevant clinical findings (functional assessment, reported measurements, observable factors via video)
• Assessment: clinical reasoning, working or confirmed diagnosis
• Plan: treatment actions, prescriptions, referrals, patient instructions
• Plain-language summary drafted for patient portal (if portal sharing is enabled)

Session conduct:

• Confirm patient identity at session start (name and date of birth)
• Check for any changes since last visit before proceeding with planned session content
• Clinical documentation completed or begun during session — not deferred to end of day
• Record session duration

---

Phase 6 — Post-Session (Same Day)

Clinician tasks:

• SOAP note completed and marked as ready for review (or auto-published if policy permits)
• Any prescriptions, referrals, or follow-up appointments initiated
• Patient instructions confirmed in Plan section — ready for portal publication
• Follow-up type selected: routine check-in / structured monitoring / none required
• If follow-up required: follow-up type (SMS / portal / structured form) and timing configured

System tasks (automated):

• Post-session summary sent to patient (Plan → patient instructions section)
• Follow-up scheduled based on clinician selection
• Appointment marked as completed in scheduling system
• Invoice generated from appointment and clinical service record

Administrative tasks:

• Invoice reviewed and sent to patient
• Any insurance billing forms submitted if applicable
• Post-session clinical notes completed and saved to patient record

Owner: Clinician (documentation); front desk (invoice, billing) SLA: SOAP note complete within 4 hours of session. Invoice sent within 1 business day.

---

Phase 7 — Follow-Up

Automated follow-up (configured at session close):

• Routine check-in: SMS or portal message, 48–72 hours post-session
• Post-procedure or clinical monitoring: structured form, 24 hours post-session
• High-risk follow-up: clinician call, within 12 hours

Follow-up response handling:

• Response reviewed by care coordinator or clinician (by category)
• Escalation thresholds checked: high pain score, symptom report, non-response
• Clinical escalation actioned within defined SLA if threshold is met
• Non-response after 2 attempts: flagged for next appointment discussion

---

Exception Management

Document all exceptions — don't manage them verbally:

Exception type	Protocol	Owner	Documentation required
Consent missing at session start	Escalate to front desk lead; session may proceed only with manager override + reason code	Manager / front desk lead	Override logged with reason; note in patient record
Video failure	One reconnect attempt; fallback to phone audio; reschedule if both fail	Clinician	Session log updated; front desk notified
Patient in crisis during session	Follow crisis protocol; emergency services contacted if warranted; session documented as emergency	Clinician	Clinical note; incident report
Consent declined	Clinical decision on whether session proceeds; patient decision documented	Clinician / manager	Patient record + clinical rationale

Setting Up in Tregovia

Tregovia's Telehealth module (EUR 15/month) automates the booking, consent, session, and follow-up stages of this checklist:

• Consent auto-triggered at appointment creation; status tracked through session dashboard
• 24-hour and 2-hour automated patient reminders with join link
• Clinician session dashboard: consent status, patient record, SOAP note, and session controls in one view
• Post-session summary auto-sent; follow-up configured from session close
• Invoice auto-generated from appointment and service record

Pricing: Telehealth module EUR 15/month. Base plan EUR 47/month (up to 2 staff, up to 100 clients (extra users EUR 10/month per 5 seats)). 14-day free trial.

FAQ

Which phase causes the most operational problems in telehealth?

Phase 1 — booking — because problems created at booking compound through every subsequent phase. A consent form sent to the wrong address, a join link not included in the confirmation, or a guardian not identified for a minor patient all require correction under time pressure on session day. Automating the booking phase correctly eliminates the majority of same-day telehealth exceptions.

How should private practices handle patients who repeatedly fail to complete consent before sessions?

After two sessions where consent was incomplete at the 24-hour checkpoint, add a personal call to the booking confirmation workflow for that patient. Some patients need a direct conversation to understand why consent forms are required — not another automated email. A brief call from the front desk ("I'm calling to make sure you received the forms for your upcoming session — it only takes a few minutes and we can't start without them") is more effective than additional automated reminders.

Should the SOAP note be completed during or after the telehealth session?

Begin it during the session; complete and review it within four hours of the session. Notes begun during the session are more accurate — the clinician captures the patient's exact words in the Subjective section, and the clinical reasoning in the Assessment is fresh. Notes completed from memory several hours later are less precise. Telehealth practice management software that surfaces the SOAP note template alongside the video session makes concurrent documentation natural rather than distracting.

What evidence should be retained for a telehealth session audit?

Consent records (with version, signer, timestamp, and viewing time), the SOAP note linked to the appointment, any prescriptions or referrals issued, the invoice, session duration and start/end time, and any exception records (consent override, video fallback, clinical escalation). If the session was recorded, the recording retention period and access log. Together, these records allow a complete reconstruction of the session for any clinical audit, insurance review, or regulatory enquiry.

How often should the checklist be reviewed?

Quarterly — and immediately after any exception that reveals a gap in the existing checklist. A patient who connects to a session without completing consent because the system sent the form to a legacy email address is a checklist failure. A clinician who conducted an audio-only session without documenting it as a telehealth fallback is a checklist failure. Each exception is a signal to tighten the relevant checklist phase. The checklist should be a living document, not a one-time configuration.