Coordinate an inquiry through administrative fit, practice-controlled eligibility decisions, required records, scheduling, payment setup, and first-appointment readiness without making the task board an EHR or clinical record.
The public downloads are plaintext. After import, readable project content is encrypted on your device, while operational metadata remains visible to the service.
Reuse is governed by the Public Template license.
Already use SealTask? Open this template in SealTask.
🪴
Complete template · v1
Private-practice client intake
Sections
5
Tasks
14
Schedule anchor
Proposed first appointment
Coordinate a client inquiry through administrative review, source-system records, scheduling, and first-appointment readiness.
Proposed first appointment: The proposed first appointment date; intake readiness is scheduled before it and record follow-up after it.
01
Inquiry
Create a neutral source-system record, assign ownership, and acknowledge next steps.
Immediately route urgency and safety signals
On receipt, if information may indicate urgent or emergency handling is needed, use the practice’s approved immediate process; do not wait for the proposed appointment or use this task board for monitoring.
Urgent priority
□ Approved immediate-response owner is alerted
□ Task board is not relied on for emergency monitoring
Create a neutral inquiry reference
Create the prospective-client record in the approved system and use only its neutral reference for task coordination here.
High priority7 days before proposed first appointment
□ Approved source-system record is created
□ Operational tasks use a neutral reference only
Assign the response owner and target
Name the person responsible for the next approved communication and record the practice response target and contingency owner.
Medium priority7 days before proposed first appointment
□ Response owner accepts the handoff
□ Response target and contingency path are set
Send approved intake expectations
Use the practice-approved channel and copy to explain the intake process, response timing, emergency boundary, and next required action.
High priority6 days before proposed first appointment
□ Communication uses the approved channel
□ Timing and emergency boundaries are included
Confirm minimum administrative inputs
Verify in the approved system that only the minimum information needed for authorized routing and scheduling review is available.
Medium priority6 days before proposed first appointment
□ Required administrative inputs are present
□ Clinical detail is not copied into operational tasks
02
Fit & boundaries
Route suitability, urgency, scope, availability, and service boundaries to authorized owners.
Route the authorized fit and scope review
Assign the inquiry to the qualified practice owner who decides scope, suitability, licensure, capacity, and any required escalation.
High priority5 days before proposed first appointment
□ Qualified decision owner is assigned
□ Decision is preserved in the approved record
Confirm service and payment boundaries
Have authorized owners confirm service format, availability, fees, payment method, and insurance or referral workflow where applicable.
Medium priority4 days before proposed first appointment
□ Service boundaries are confirmed by the owner
□ Approved payment or coverage path is confirmed
Record the intake decision and next path
Record the authoritative proceed, wait, refer, or not-accepted outcome in the approved system and assign its communication owner.
High priority3 days before proposed first appointment
□ Authoritative intake outcome is recorded
□ Next communication has an accountable owner
03
Records & scheduling
Complete approved notices, consent, payment, scheduling, and communication workflows.
Complete required notice and consent records
Route practice-approved privacy, service, communication, consent, and acknowledgement records through their authoritative system.
High priority3 days before proposed first appointment
□ Required records are routed through approved systems
□ Completion status is authoritative outside this checklist
Complete approved payment setup
Use the authorized payment or billing system to complete required setup without placing account, card, insurance, or financial details here.
Medium priority2 days before proposed first appointment
□ Setup uses the approved payment or billing system
□ Financial and coverage details stay out of tasks
Schedule the first appointment authoritatively
Confirm date, format, location or approved connection method, clinician, reminders, cancellation terms, and time zone in the scheduling system.
High priority2 days before proposed first appointment
□ Appointment is in the authoritative schedule
□ Approved practical instructions are delivered
04
First appointment
Verify practical readiness, conduct the appointment, and update authoritative records.
Verify first-appointment readiness
Confirm required administrative records, clinician assignment, room or approved connection, accessibility arrangements, and contingency path.
High priority1 day before proposed first appointment
□ Required administrative records are ready
□ Visit logistics and contingency path are ready
Complete the post-appointment record check when a visit occurs
When an appointment occurs, ask authorized owners to confirm the scheduling, payment, clinical, consent, and follow-up records required by practice procedure are current.
High priority1 day after proposed first appointment
□ Required source-system records are current
□ Outstanding follow-up has an accountable owner
Promptly complete the not-accepted closeout when applicable
Promptly after a not-accepted decision, confirm approved communication, referral information where appropriate, record disposition, and removal of unnecessary access; do not wait for the proposed appointment.
High priority
□ Authoritative communication status is recorded
□ Required record and access closeout is complete
05
Done
Verified intake work moves here after its authoritative outcome is recorded.
Completion stage — move finished work here.
Who this template is for.
Therapists, psychologists, counselors, and private-practice administrators coordinating intake operations.
Practice owners separating administrative follow-up from the EHR and clinical record.
Small practices that need consistent inquiry, scheduling, payment, consent, and first-visit readiness handoffs.
When to use it.
When a prospective client contacts the practice and an authorized intake record can be created.
Before confirming a first appointment, beginning clinical services, or requesting unnecessary sensitive information.
When administrative fit, required notices, consent, payment, scheduling, and record ownership involve several steps.
How to put it to work.
Anchor on the first appointment
Set the planning anchor to the proposed first appointment. Administrative readiness schedules backward and post-visit record checks follow it.
Use the EHR for client information
Keep identity, contact details, symptoms, diagnosis, treatment, insurance, consent, and clinical communications in the practice-approved system of record.
Let authorized owners decide
The template coordinates operational gates only. The clinician and practice owners determine suitability, urgency, consent, privacy, payment, and record requirements.
Customize before you commit.
Replace general fit, notice, consent, payment, and scheduling gates with the exact practice-approved workflows and responsible owners.
Use a neutral inquiry reference in every task and resolve the person’s identity only in the authorized clinical or administrative system.
Add insurer or referral steps only when the practice has approved systems, notices, access, and record-handling procedures for them.
Create a separate not-accepted closeout path that covers notice, referral information where appropriate, record disposition, and access removal.
Keep the system boundary clear.
SealTask coordinates administrative status only. The EHR and approved practice systems remain authoritative for identity, health information, clinical decisions, communications, consent, payment, and records.
Consent, privacy acknowledgements, intake forms, insurance, payment details, referrals, and signed practice records.
Clinical notes, assessments, care decisions, emergency actions, appointment records, and retention or disclosure evidence.
Common mistakes to avoid.
Collecting clinical detail too early
Operational routing rarely requires a clinical narrative in a task. Ask only through practice-approved channels and keep sensitive content in the authorized record.
Treating an open slot as acceptance
Calendar availability does not resolve suitability, scope, urgency, licensure, payment, consent, or practice-policy gates. Preserve the authorized decision path.
Leaving an inquiry without closeout
If the practice does not proceed, assign the approved communication, referral-information, record-handling, and access-removal actions rather than leaving status ambiguous.
Questions about this template.
What should a private-practice client intake checklist include?
It should coordinate a minimum inquiry record, response ownership, administrative and clinician-controlled fit gates, required notices and consent records, payment setup, scheduling, first-visit readiness, and accepted or not-accepted closeout.
Should symptoms, diagnosis, or treatment details go in this template?
No. Keep health and clinical information in the practice-approved EHR or other authorized system. Use this checklist for neutral operational status and accountable follow-up.
Does this template make a client suitable for the practice?
No. It only coordinates the practice’s authorized review. Qualified clinical and administrative owners must make and record suitability, urgency, scope, licensure, and referral decisions.
Is using this template enough for HIPAA or other compliance?
No. The template is not compliance or clinical advice and does not replace required agreements, policies, notices, safeguards, records, or professional review. The practice must approve every system and workflow it uses.
Build the next part of the workflow.
Related template
Law firm client intake and matter-opening checklist
Coordinate a prospective-client inquiry through firm-controlled conflict review, engagement approval, matter opening, minimum access, and a documented closeout without turning the task board into the client file.
Move a content brief through accountable drafting, factual and specialist review, final approval, publication QA, and a verified live result without making the task board the CMS.
Client-side encryption means plaintext is encrypted on the user’s device before it is sent to a service. The service receives ciphertext. Whether this creates an end-to-end or zero-knowledge boundary depends on who controls the keys and whether the provider can cause or observe decryption.
Plaintext is the readable input to encryption; ciphertext is the transformed output intended to be unreadable without the correct key. Metadata is data about a record or interaction—such as who, when, how large, or which records are related—and may remain visible even when content is ciphertext.
This disclosure covers encrypted workspace content and its server-visible metadata. The workspace-content metadata inventory is complete for the enumerated current workspace persistence and SQL models, API-response models, and SSE event models. It is not a complete privacy-data inventory and excludes account authentication, billing, security and audit, abuse-prevention, and service telemetry domains; those domains are described non-exhaustively in the privacy policy. Metadata can itself be sensitive. Attachment ciphertext size usually reveals an approximation of the original file size.