Admissions Coordinator

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. The posting includes Position Summary (we can treat as About the role). Responsibilities (Essential Duties and Responsibilities). Minimum Qualifications and Preferred Qualifications can be combined into Requirements/Qualifications? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We need to decide which sections to include. We have content: Position Summary (About the role). Responsibilities (Enrollment & Student Support, Transcript Coordination, Student-Athlete Enrollment Support, Cross-Department Coordination, Records, Systems & Compliance). Minimum Qualifications and Preferred Qualifications (these could be Requirements or Qualifications). There's no explicit Skills section but we could infer skills from qualifications (communication, organization, etc.) but better to not create a Skills section unless there is explicit content. There's no Benefits, Pay, Schedule mentioned. So we should not include those headings. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, etc. We need to preserve all substantive information. So we need to include the Position Summary paragraph(s), the responsibilities broken down perhaps as

• for each duty. The posting has many responsibilities grouped under headings (Enrollment & Student Support, Transcript Coordination, etc.). We could treat each as a subsection but we only need to output

  for main sections. Could we include subheadings? Not required but we could keep them as

  or . The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow that pattern. Probably best to have main sections: About the role (

  About the role

  ), Responsibilities (

  Responsibilities

  ), Requirements (

  Requirements

  ) maybe split into Minimum and Preferred? Could combine. We need to use

  • for any list of duties/requirements/benefits. So under Responsibilities we should list duties as
    • . Under Requirements we should list qualifications as
      • . For Minimum and Preferred we could separate but still list. We must preserve all substantive information: that includes the details under each responsibility heading (like Enrollment & Student Support bullet points). We need to capture them as list items. We also need to include the Position Summary paragraphs (maybe two paragraphs). Use

        . We need to exclude boilerplate: Equal Employment Opportunity, ADA, Job Description Disclaimer, etc. Also exclude Physical Requirements and Work Environment? Those are substantive? They describe physical demands and work environment. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep Physical Requirements and Work Environment as content. However they are not under a specified heading list; we could include them under a section like "Working Conditions" but not in allowed headings list. But we could still include them as

        under maybe a generic section? The instruction says use

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

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections; but we could also add other headings if needed? It says "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be interpreted as we should use those headings for sections; but we could also have other sections if needed, but they gave examples. Safer to stick to those headings only. However Physical Requirements and Work Environment are substantive; we could fold them into Responsibilities or Requirements? Not ideal but maybe we can include them under Responsibilities as part of duties? They are not duties. Could create a section "Working Conditions" but not in list; risk of violating instruction. The instruction: "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but it says use

        for section headings (e.g. ...). Likely they expect us to use those headings where applicable, and not to create others like "Physical Requirements". However they also say "Prefer a few substantive sections over many thin ones." So we could incorporate Physical Requirements and Work Environment into Responsibilities or Requirements as additional bullet points? Might be okay. Alternatively we could create a section "Details" but not in list. I'd rather follow the instruction strictly: only use those headings if there is real content. So we need to decide which of those headings have content. - About the role: Position Summary -> yes. - Responsibilities: Essential Duties and Responsibilities -> yes. - Requirements: Minimum Qualifications -> yes. - Qualifications: Preferred Qualifications -> maybe we can treat as Qualifications section. But we have both Requirements and Qualifications headings; we could put Minimum under Requirements and Preferred under Qualifications. That seems reasonable. - Skills: Not explicitly listed; we could derive from qualifications but better not to create if no explicit content. The instruction: "never emit a heading followed by filler/placeholder text". If we create Skills section with no explicit content, that's filler. So omit Skills. - Benefits, Pay, Schedule: no content -> omit. Thus we will have four sections: About the role, Responsibilities, Requirements, Qualifications. Now we need to output HTML fragment only. Structure:

        About the role

        ... (position summary paragraphs)

        Responsibilities

        • ... each duty ...
        ...
        We need to capture all duties from the posting. Let's extract them. From Position Summary: we already used that. Responsibilities sections: Under "Essential Duties and Responsibilities" there are bullet-like paragraphs: - Process enrollments and review newly enrolled student files for completeness and outstanding requirements. - Conduct proactive outbound calls and follow-up with prospective and enrolled students based on assigned outreach priorities and departmental needs. - Respond to student questions regarding enrollment requirements, next steps, and start readiness. - Support recruitment and enrollment activities as needed during high-volume enrollment periods. - Track missing admissions documentation, financial aid requirements, Offer Letters, payment concerns, transcripts, and other outstanding enrollment items. - Connect students with Financial Aid, Registrar, Student Services, Athletics, or other University departments when specialized assistance is required. - Document student outreach, responses, outstanding requirements, identified barriers, and required next actions within University systems. - Monitor students from enrollment through successful completion of their first course to facilitate continuity of support and appropriate departmental handoffs. - Identify enrollment or start-readiness barriers and escalate concerns to the appropriate department or University leader. Then "Transcript Coordination": - Review newly enrolled student files to identify outstanding official transcript requirements. - Determine whether required transcripts have previously been requested and track existing requests or initiate requests in accordance with established University procedures. - Monitor Anthology and other University systems for transcript receipt and status updates. - Maintain accurate records of transcript requests, request dates, anticipated receipt dates, and completed requirements. - Follow up with institutions and students regarding delayed or outstanding transcripts. - Coordinate with the Registrar regarding transcript-related issues and escalate unresolved barriers when appropriate. - Ensure transcript-related activity and documentation are accurately maintained within University systems. Then "Student-Athlete Enrollment Support": - Review newly enrolled student-athlete files for outstanding enrollment requirements. - Conduct proactive outreach to student-athletes regarding missing documentation and required next steps. - Collaborate with Admissions and Athletics to identify and resolve enrollment-related barriers. - Monitor student-athlete file completion against established enrollment and institutional deadlines. - Escalate unresolved eligibility, documentation, or enrollment matters to the appropriate University department. Then "Cross-Department Coordination": - Serve as an operational point of coordination among Admissions, Financial Aid, Registrar, Athletics, Student Services, and other departments supporting the enrollment process. - Track students with unresolved requirements and coordinate appropriate follow-up through resolution or formal handoff. - Participate in student-status and enrollment-readiness reviews as assigned. - Track assigned action items and follow through to ensure timely resolution. - Coordinate communication across departments to reduce unnecessary duplication of student outreach. - Facilitate appropriate handoffs when continued student support or decision-making falls within another department’s area of responsibility. - Communicate recurring enrollment barriers, process gaps, or student experience concerns to Admissions leadership. - Support cross-functional process-improvement initiatives designed to strengthen enrollment, start readiness, and the student experience. Then "Records, Systems & Compliance": - Maintain accurate and timely documentation within Anthology, CRM platforms, and other University-approved systems. - Ensure student records and enrollment activities are handled in accordance with University policies and established procedures. - Maintain confidentiality of student information in accordance with FERPA and University requirements. - Follow established departmental workflows, service standards, and escalation procedures. - Support reporting and tracking related to enrollment requirements, outstanding documentation, student outreach, and start readiness. - Perform other duties as assigned. Now Requirements (Minimum Qualifications): - High school diploma or equivalent required. - Previous experience in customer service, administrative support, admissions, enrollment, student services, or a related environment. - Demonstrated experience managing detailed records, deadlines, and follow-up activities. - Strong written and verbal communication skills. - Proficiency with Microsoft Office applications and ability to learn new technology systems. - Demonstrated ability to work effectively both independently and collaboratively. - Ability to communicate professionally and confidently with students by telephone, email, and other communication channels. - Strong organizational skills with the ability to manage multiple priorities in a fast-paced environment. Qualifications (Preferred Qualifications): - Associate or bachelor’s degree from an accredited institution. - Previous experience in higher education admissions, enrollment management, student services, Registrar operations, Financial Aid, or a related area. - Experience working directly with students or prospective students. - Experience with Anthology or a comparable higher education Student Information System. - Experience using CRM, student information, document management, or workflow systems. - Experience coordinating activities or processes across multiple departments. We should not include Physical Requirements and Work Environment; but maybe we could incorporate them as a brief note under Responsibilities? However they are substantive; omitting them loses info. The instruction says preserve ALL substantive information. So we need to include them somewhere. Could we add a section "Working Conditions" but not in the list? The instruction says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are examples. It might be okay to add another heading like "Working Conditions". However they said "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That could be read as you should use h3 for those sections; but you could also use h3 for other sections if needed. The examples are just examples. So we can add a section for Physical Requirements and Work Environment, maybe combine them into a "Working Conditions" section. But we need to avoid creating sections with filler text. Physical Requirements and Work Environment have real content, so it's fine. Thus we could have sections: About the role, Responsibilities, Requirements, Qualifications, Working Conditions. But Working Conditions not in the example list; still okay. Alternatively we could fold Physical Requirements into Responsibilities as a bullet like "Physical demands: prolonged sitting, frequent computer/telephone use, ability to communicate effectively, maintain regular