In this article
1. Inventory the work arriving between visits
Start with the channels the team actually uses: patient portal, telephone messages, pharmacy requests, results, referral questions, administrative tasks, and internal consultation. Ask authorized staff to review a representative period and record aggregate counts, arrival patterns, and recurring handoffs. Keep patient information within the organization’s approved systems.
Count distinct work items where possible. One request can produce several messages, so a raw notification total may exaggerate volume while hiding the effort required to finish a task. Note the period reviewed and unusual conditions such as staff leave or an intake surge. Ask clinicians where the data miss work performed outside the visible inbox.
- What arrives, through which channel, and at what times?
- Which items are repeatedly returned or rerouted?
- Which tasks require clinical judgment, and which involve administrative coordination?
2. Assign an owner to each stage
For each common work type, name who receives it, who reviews it, who performs the next step, and who confirms completion. Clinical leaders must approve which work different roles can perform under the applicable requirements and organizational policies. A routing diagram should describe real responsibilities rather than assume that every request ultimately belongs to the PMHNP.
AHRQ’s patient-access toolkit recommends defining who handles different messages and response procedures. Use that principle to build a local responsibility map. For an appointment question, the scheduling team may own the resolution; for a clinical question, an approved pathway may involve a nurse and the responsible clinician. Make the boundaries visible.
3. Define completion and escalation
Ask the team what closes each type of task. Forwarding an item, opening it, and resolving it can represent different stages. Establish how staff confirm receipt when responsibility moves, where outstanding work remains visible, and whom they contact when the usual owner is unavailable. Clinical urgency and response expectations belong in the organization’s approved protocols.
Use fictional scenarios to test the map: a request arrives shortly before clinic closes; the assigned person is off; a message is routed twice without a resolution. Record where the process becomes uncertain. The goal is a dependable route for obtaining the appropriate response, with responsibility clear at each step.
- Owner: who is responsible now?
- Next step: what action is pending?
- Escalation: who handles a blocked or urgent issue?
- Closure: how will the team know the work is complete?
4. Put the work into the weekly schedule
Have the clinical leader and operations partner compare inbox responsibilities with the proposed PMHNP week. Account for visits, documentation, consultation, meetings, coordination, and coverage. Ask when the expected message work will occur and how the plan changes when volume differs from expectations.
AHRQ’s workflow-assessment toolkit treats clinical and administrative processes as connected. Apply that idea by looking at the entire work sequence rather than adding an unexplained inbox quota. Use your own data to test assumptions. This guide supplies no universal message count, response target, or amount of protected time that is appropriate for every PMHNP practice.
5. Plan absence coverage before it is needed
Identify what happens to incoming work on non-working days, during planned leave, and when someone is unexpectedly absent. Confirm that covering staff have the required access, clinical authority, context, and capacity. A named backup is useful only when that person knows the arrangement and can perform the assigned work.
Decide how unresolved tasks return to the regular clinician. Reconcile what has been completed, what is still pending, and which commitments have changed. Review the plan with the people who will use it, then test it with a training example. Make it clear who can adjust workload when coverage adds more work than the usual schedule allows.
6. Give candidates an inbox brief they can evaluate
Bring the decisions into recruiting as a short description: channels, task types, support roles, clinical escalation, scheduled work time, and absence coverage. Separate resources already operating from approved additions and future proposals. Invite candidates to ask where the proposed week leaves room for the work described.
A useful brief might say: “Portal and telephone requests enter a shared queue. Scheduling questions follow an administrative pathway; clinical requests follow our approved review process. The PMHNP has defined responsibility for these task types, scheduled time to complete them, and a documented coverage arrangement.” Replace each general phrase with your actual operating details before using it. Review the brief after onboarding so the role continues to reflect practice.
Sources and further reading
Sources checked October 12, 2026
- AHRQ — Be Easy To Reach: Tool 7Supports defined message responsibilities, response procedures, and patient communication. Reviewed March 2024; checked October 12, 2026.
- AHRQ — Workflow Assessment for Health IT ToolkitProvides tools for examining clinical and administrative workflows in ambulatory care. Checked October 12, 2026.