Participant / Employee Journey Support Map
Map the employee's experience across notices, education, plan shopping, enrollment, payment, substantiation, reimbursement, life events, renewal, and escalation.
Purpose
Map the employee's experience across notices, education, plan shopping, enrollment, payment, substantiation, reimbursement, life events, renewal, and escalation.
When to use
Use before launch, during renewal, after support spikes, or when employee experience needs a clearer support lane.
Who should use this
Employee experience owner, HR, advisor, operations lead, support team, or HRB designee.
Review boundary
This map supports employee experience design and routing. It does not replace plan documents, vendor scope, licensed support, or qualified review.
Resource sections
Pre-launch education
- Education topics and owner are listed.
- Human touch moments are identified.
- Evidence location is known.
Notice and eligibility communication
- Notice and eligibility messages are mapped.
- Source/version and delivery evidence are identified.
- Escalation path is clear.
Plan shopping support
- Plan shopping support lane is defined.
- Licensed support boundary is clear.
- Marketplace guide and verification resources are linked.
Enrollment support
- Enrollment path, deadlines, and owner are identified.
- Exchange/off-exchange questions are routed.
- Follow-up evidence is retained.
First premium/payment support
- First premium responsibility and payment-risk triggers are described.
- Finance/support escalation owner is named.
- Payment reminder evidence is retained.
Substantiation and reimbursement support
- Substantiation and reimbursement steps are mapped.
- Missing documentation and denial paths are clear.
- Evidence location is known.
Life event and coverage change support
- QLE/SEP/life event support lane is identified.
- Coverage coordination triggers are routed.
- Documentation boundaries are clear.
Renewal support
- Renewal education, contribution changes, and plan-shopping support are mapped.
- Communication timing is known.
- Feedback loop is identified.
Escalation and human touch points
- High-emotion, high-risk, Medicare, COBRA, payment, subsidy, or coverage-dispute moments are identified.
- Escalation owner is named.
- Human review checkpoint is linked.
Evidence and feedback loop
- Support notes, communications, escalation notes, and improvement items have locations.
- Feedback is routed to improvement log.
- Export or print is retained.
Evidence to retain
- Journey map export - Retain with the audit file, evidence map, or review record as applicable.
- Owner and support lane notes - Retain with the audit file, evidence map, or review record as applicable.
- Notice and communication records - Retain with the audit file, evidence map, or review record as applicable.
- Enrollment/payment support notes - Retain with the audit file, evidence map, or review record as applicable.
- Reimbursement support notes - Retain with the audit file, evidence map, or review record as applicable.
- Escalation notes - Retain with the audit file, evidence map, or review record as applicable.
- Improvement notes - Retain with the audit file, evidence map, or review record as applicable.
Evidence is not saved in this static version. Assign an owner, repeat the process consistently, review exceptions, explain the rationale, and retain copies in the employer file or local project record.
Print, Copy, or Export This Resource
No database records or server-side files are created. Use these browser-only actions to retain a local copy.
This map supports employee experience design and routing. It does not replace plan documents, vendor scope, licensed support, or qualified review.