Give the role a reliable starting point.
Share required forms, secure collection tools, access restrictions, and who reviews clinical or consent information.
Keep administrative intake forms and requests visible before the practice reviews the visit.
Book a free consultationScope, access, and coverage are agreed with your team.

Define the recurring work and the evidence your team needs to review it. These building blocks become a role-specific operating plan.
A working record with source references, current status, and the person responsible for the next step.
A focused view of missing inputs, unanswered questions, and items that need your decision.
A dated handoff that distinguishes completed work from pending review and unresolved exceptions.
Share required forms, secure collection tools, access restrictions, and who reviews clinical or consent information.
A patient returns an incomplete form with a clinical question. The assistant flags the question for staff rather than answering or completing it on the patient’s behalf.
Illustrative workflow, not a client case study.Check patient matching, form versions, and completion status without representing receipt as clinical review.
Tool familiarity is considered when defining the role. Your team approves every platform, access level, and source of truth.
Platform names describe possible working environments, not endorsements or a promise of certification.
Keep administrative intake forms and requests visible before the practice reviews the visit. The scope below connects each recurring responsibility to its source information and a checkable working record. Your team confirms the exact steps, templates, and approval limits before work starts.
Begin with the latest request and its approved source record. Check that the necessary information is present, identify the owner, and clarify conflicting details before making an update.
Working output: Form completion queue. Include the source reference, current status, and next owner when an item remains open.
Use the agreed template or checklist to carry out this task. Record what was checked and the date of the action so another team member can understand the current position.
Working output: Missing-information list. Include the source reference, current status, and next owner when an item remains open.
Keep this work connected to the wider queue. Note dependencies and unanswered questions, and use the agreed escalation route when the next step requires a decision.
Working output: Review-ready administrative record. Include the source reference, current status, and next owner when an item remains open.
Complete the task only when its agreed checks have passed. If an input is missing or an approval is pending, keep that status visible rather than treating the item as finished.
Working output: Form completion queue. Include the source reference, current status, and next owner when an item remains open.
A patient returns an incomplete form with a clinical question. The assistant flags the question for staff rather than answering or completing it on the patient’s behalf.
The agreed task is complete and the supporting information is available in your approved system. Attach or link the relevant record and identify any final reviewer before closing the item.
Review against: Check patient matching, form versions, and completion status without representing receipt as clinical review.
Name the missing information, where it was requested, and who is expected to supply it. Keep a follow-up date visible. An unanswered request should not disappear into a completed-work total.
Starting requirements: Share required forms, secure collection tools, access restrictions, and who reviews clinical or consent information.
Summarize the exception and the information already checked. Ask a specific question and route it to the authorized person. Keep the original source intact while the decision is pending.
Approval boundary: Consent validation, medical history interpretation, and clinical clearance remain with the practice.
Provide individual, approved access to the systems used for this responsibility. Share a completed example, an incomplete example, the relevant template, and a named reviewer. Sensitive working records belong in those systems, not in a public inquiry form.
Possible working environments include Secure patient portal, Your PMS, Approved form platform, Practice inbox. Tool access and familiarity are confirmed as part of the role brief.
Agree which measures are useful for this queue: completed items, items awaiting an input, age of unresolved work, and corrections requested by the reviewer. Review these together with actual examples; volume alone does not establish that work is accurate.
Set response expectations from your operating needs. Coverage, turnaround targets, and the amount of work assigned are agreed separately rather than assumed from the service name.
Share required forms, secure collection tools, access restrictions, and who reviews clinical or consent information.
Check patient matching, form versions, and completion status without representing receipt as clinical review.
Consent validation, medical history interpretation, and clinical clearance remain with the practice.
We scope the role around your approved systems, including environments such as Secure patient portal, Your PMS, Approved form platform. Access, training, and the final tool requirements are confirmed before the role begins.

Organize new-patient consultation requests around the capacity your practice releases.
Explore the service ↗
Help patients keep track of confirmed visits using your practice’s communication rules.
Explore the service ↗
Coordinate administrative follow-up after the treatment coordinator has met with a patient.
Explore the service ↗
Organize practice-directed outreach to patients who need an administrative follow-up.
Explore the service ↗Tell us where the queue slows down. We’ll discuss the scope, tools, coverage, and review points that belong in your support role.
Define the role before making a commitment.