Client Relationship Manager

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. We have Position Summary (About the role). Then Primary Responsibilities (Responsibilities). Then Vendor Relationships, Plan Design..., Investment Menu Changes, Recordkeeper Conversions, Participant Support and Education, Billing and Fee Administration, Practice Operations and Projects. Those could be part of Responsibilities or separate sections? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. We need to decide which sections to include: About the role (position summary). Responsibilities (primary responsibilities and subparts). Qualifications (required and preferred). Skills maybe from qualifications? Could combine. Benefits, Pay, Schedule: not present in posting (no mention). So we should NOT include those sections because no specific content. Also Requirements maybe same as Qualifications? The list includes Requirements as a possible heading. We could put qualifications under Requirements or Qualifications. Since both are allowed, we need to decide. The posting includes "Qualifications Required" and "Preferred". Also "Performance Measures". That could be considered Requirements? But we should not invent sections like Performance Measures unless we map to something like Requirements? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include sections for which we have content: About the role, Responsibilities, Requirements (or Qualifications), Skills maybe. We have qualifications (required and preferred). We could put them under Requirements. Skills maybe not separate; we could omit Skills if no explicit skills list beyond qualifications. But we could include Skills as part of Qualifications? The instruction says prefer a few substantive sections over many thin ones. So maybe we combine Qualifications and Skills into one section called Qualifications (or Requirements). Let's choose Requirements for required qualifications, and Qualifications for preferred? But we need to avoid duplication. Better: Use Requirements for required qualifications, and Qualifications for preferred? But both headings are similar. Might be confusing. Perhaps we use Requirements for required, and Qualifications for preferred (makes sense). Then we can omit Skills. We must not include Benefits, Pay, Schedule. We must preserve all substantive information, not invent or summarize away detail. So we need to include all responsibilities details under Responsibilities. Use

• for any list of duties/requirements/benefits. For prose, use

  . So we need to decide what is list vs prose. The responsibilities have many bullet-like sentences; we can treat each as

• . We'll need to wrap them in
  . For each major heading (like New Client Onboarding and Implementation) we could have a

  ? Not allowed; only

  for section headings. Subheadings not specified; we could just keep as

  with bold? But we cannot add arbitrary tags besides

  ,

  • ,

    . We could use

    for headings inside responsibilities? But that would be a heading not allowed? The instruction only says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings like

    or . But to be safe, we can just use

    for prose and

    • for lists. For subheadings we could use

      ...

      . That's okay. We need to preserve all details. Let's extract responsibilities sections: Primary Responsibilities - New Client Onboarding and Implementation (with sub-bullets) - Ongoing Client Service and Relationship Management (sub-bullets) - Vendor Relationships (sub-bullets) - Plan Design and Plan Document Maintenance (sub-bullets) - Investment Menu Changes (sub-bullets) - Recordkeeper Conversions (sub-bullets) - Participant Support and Education (sub-bullets) - Billing and Fee Administration (sub-bullets) - Practice Operations and Projects (sub-bullets) We'll create a
      with each main responsibility as a
      • containing maybe nested
        for subitems? But nested lists are allowed? Not prohibited. We'll keep simple: each main responsibility as
        • and subitems as
          • inside. Now Qualifications Required: list of required items. We'll put under

            Requirements

            as
            • ...
            . Preferred: under

            Qualifications

            as
            • ...
            . Performance Measures: could be considered Requirements? But we already have Requirements and Qualifications sections. Could we add a section for Performance Measures? Not in the allowed headings list. The allowed headings list includes Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Performance Measures not listed. So we should not create a heading for it. However we need to preserve all substantive information. We could incorporate Performance Measures into Requirements or Qualifications as additional items? But they are not qualifications; they are performance metrics. Could we put them under Responsibilities? Not really. Perhaps we can put them under a

            within Responsibilities? But they are not responsibilities. The instruction says we must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include them somewhere. Since there is no allowed heading for Performance Measures, we could include them as a

            under Responsibilities? That would be misrepresenting. But maybe we can treat them as part of Requirements (since they are expectations). However the instruction says we should not invent headings; we can still include content under existing headings. So we can add a

            after the qualifications lists describing performance measures. That would preserve detail. Similarly "WHY CHOOSE HUB?" is truncated; we should remove boilerplate. The snippet ends mid-sentence; we should ignore that as boilerplate. Now we need to output only HTML fragment, no markdown fences. Let's craft. Structure:

            About the role

            ... position summary ...

            Responsibilities

            • New Client Onboarding and Implementation
              • Manage the onboarding process for new advisory clients, including Broker of Record (BOR) paperwork, advisory and consulting agreements, 408(b)(2) disclosures, vendor authorization and system access forms, and adoption of the Investment Policy Statement.
              • Develop and manage the onboarding project plan, coordinate vendor deliverables and deadlines, and provide status updates to the client.
              • Establish the ongoing service calendar for each relationship, including committee meeting cadence, compliance milestones, and the participant education schedule.
              • Coordinate the rollout of HUB's financial wellness and financial coaching program (FinPath by HUB), including implementation planning, sponsor and employee communications, ongoing promotion, and engagement reporting.
              • Support new business proposals and RFP responses for prospective retirement plan clients, including plan data compilation, vendor comparison, and preparation of client-facing materials, as directed.
            • Ongoing Client Service and Relationship Management
              • Serve as the primary point of contact for the plan sponsor on all matters relating to the retirement plan.
              • Review inbound correspondence from recordkeepers, TPAs, auditors, and other plan vendors; determine required action; resolve items directly with the vendor; and involve the client only where a sponsor decision or signature is required.
              • Escalate and track unresolved service issues with recordkeeper and TPA service teams through resolution.
              • Coordinate quarterly and annual investment review and plan committee meetings with HUB's investment team, including scheduling, agenda preparation, materials, logistics, meeting minutes, and follow-up item tracking.
              • Maintain the client fiduciary file, including meeting minutes, Investment Policy Statement, fee benchmarking documentation, plan documents, participant notices, and vendor disclosures.
              • Own the integrity of all client and plan records in Microsoft Dynamics 365 for the assigned book, including contact information, fee schedules, service agreement terms, compliance deadlines, and activity history. Records should be current, complete, and usable by any team member at any time.
            • Vendor Relationships
              • Serve as the team's primary relationship contact for assigned recordkeepers and TPAs, independent of any specific client event or service issue.
              • Attend and represent the team in recordkeeper and TPA relationship meetings, quarterly business reviews, and platform update briefings.
              • Maintain a current directory of vendor contacts across service, relationship management, and escalation, and keep team-level platform access and credentialing current.
            • Plan Design and Plan Document Maintenance
              • Maintain a working knowledge of qualified plan design sufficient to discuss design alternatives with clients and to identify circumstances in which a design change should be considered — for example, a plan consistently failing or narrowly passing nondiscrimination testing, resulting in corrective refunds to highly compensated employees.
              • Work with the plan's TPA to obtain census-based cost projections for proposed design changes, such as a safe harbor match, an increase or restructuring of the employer match, or the addition of a profit sharing or new comparability allocation, and present the results to the client.
              • Manage the plan amendment process from identification through implementation: coordinate drafting with the recordkeeper or TPA, review amendment language against the client's stated intent, obtain client execution, and confirm that the recordkeeper and TPA have implemented the change in the plan document and in their administrative systems.
              • Manage required restatements and amendments, including the SECURE 2.0 restatement cycle, through client review, sign-off, and execution.
              • Prepare and coordinate distribution of related participant notices, including safe harbor, QDIA, automatic enrollment and escalation, blackout, summary of material modifications, and annual fee disclosure notices, and document timely delivery.
              • Support the annual compliance cycle, including census collection, coordination of ADP/ACP and top-heavy testing with the TPA, communication regarding corrective distributions, contribution limit monitoring, and coordination of the Form 5500 filing and plan audit, including signature and filing deadlines.
              • Manage plan hygiene projects, including terminated participant and force-out processing, missing participant searches, uncashed check resolution, participant count and audit threshold monitoring, and ERISA/plan expense account balance monitoring.
              • Coordinate resolution of payroll and HRIS integration issues (360 and 180 file feeds) with the recordkeeper and the client's payroll team.
            • Investment Menu Changes
              • Manage the implementation of investment lineup changes recommended by HUB's investment team, including fund replacements, share class changes, mapping decisions, and re-enrollments.
              • Prepare and route required documentation and obtain all necessary client signatures.
              • Coordinate timing with the recordkeeper and issue required blackout and change notices to participants.
              • Confirm following implementation that changes processed correctly at both the fund and participant account level.
              • Document each change and its supporting rationale and approvals in the fiduciary file.
            • Recordkeeper Conversions
              • Serve as the point person for all recordkeeping conversions, participating in all calls and meetings from kickoff through post-conversion validation.
              • Manage the conversion project plan and coordinate deliverables from both the incoming and outgoing providers, including data gathering and validation, plan document and payroll setup, loan and beneficiary data, trust and asset transfer timing, blackout