Instructional Coordinator

We need to output HTML fragment with headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. The posting includes: Title, Department, Campus Location, Salary Range, Work Mode, Hours Per Week, Work Schedule Position Type, Position Summary, Job Duties And Responsibilities (with subparts: Schedule, Registration, Curriculum, Loading, Contracts, Textbooks, External Collaboration, Internal Collaboration), Required Qualifications, Preferred Qualifications, plus some other info: Pay dates, benefits eligibility, residency restriction, etc. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings (none present). We must remove boilerplate like EEO, scam warning, etc. The posting includes a diversity statement and residency restriction; those are not boilerplate? They are substantive? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The diversity statement might be considered EEO/equal-opportunity boilerplate. Likely we should remove that paragraph about diversity and commitment. Also the residency restriction and work authorization statement maybe also considered legal? It's about eligibility; might be considered substantive? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. The residency restriction is not exactly EEO but could be considered eligibility requirement. Might keep? It's about employment eligibility; could be considered a requirement. However the instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". The residency restriction is a legal restriction; maybe we should drop it as legal boilerplate. But it's substantive info about where candidates must reside. Might be considered a requirement. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep eligibility info if it's substantive. However the instruction also says remove legal boilerplate. The residency restriction is a legal condition; but it's specific to the job. I'd keep it as part of Requirements or Qualifications. We need to decide sections: About the role (maybe Position Summary). Responsibilities (Job Duties And Responsibilities). Requirements (Required Qualifications). Qualifications (maybe Preferred Qualifications). Skills (maybe from Required Qualifications: communication skills, technology, etc). Benefits (mention of comprehensive benefits package). Pay (Salary Range, Pay dates). Schedule (Hours Per Week, Work Mode, Work Schedule Position Type). Also we have Department, Campus Location maybe could be included in About the role. We must not create sections with filler like "commensurate with experience". We have actual salary range, so Pay section is valid. Benefits: "comprehensive benefits package" is vague but it's stated; we can include Benefits section with that statement. Schedule: we have Hours Per Week: 40, Work Mode: full-time in-person presence, Work Schedule Position Type: Full-Time Staff, Exempt. So we can include Schedule section. We must not repeat job title as heading. So no

Instructional Coordinator

. Use

About the role

etc. We need to preserve all substantive information. Let's extract: - Department: Science Technology Education - Campus Location: Arnold/Main Campus - Salary Range: $52,605-$65,756 - Work Mode: full-time in-person presence on campus or at alternative locations. - Hours Per Week: 40 - Work Schedule Position Type: Full-Time Staff, Exempt - Position Summary: The Instructional Coordinator ... provides instructional and administrative support to the Director of the TEACH Institute (and their designees) on matters pertaining to faculty and instruction, course offerings and scheduling, course run/cuts, teaching assignments and contracts, faculty teaching loads, preparation and maintenance of curricular and instructional documents, direct billing, data analysis of enrollment trends, and textbook management. - Job Duties And Responsibilities: broken into sections: Schedule: - Build, analyze, organize, coordinate, enter, and modify the development of the credit and non-credit schedule of classes for submission to the Office of Records and Registration. - Monitor all deadlines for schedule production and enrollment timelines to ensure the department is meeting all its obligations. - Evaluate and analyze with department chairs in scheduling effectiveness concerning times, locations, formats, past enrollment trends, and future administrative requests. - Ensure appropriate room assignments, corrections to the class file and schedule, both printed and online, and other administrative matters. - Research and resolve discrepancies. Registration: - Monitor and review program and course enrollments to make sure class offerings are sufficient. - Assist with recommendations to the Director for additional offerings or to cancel any poorly enrolled class sections. - Prepare necessary documents to get approval for cutting sections as needed on the run-cut decision date. - Work with the office staff to ensure that rosters are captured prior to sections being cut to facilitate student notification. - Analyze, develop, implement, and support procedures for new scheduling and registration initiatives. - Maintain historical records of enrollment trends. Curriculum: - Organize, coordinate, enter, and modify all EPC (Committee on Educational Policies and Curriculum) proposals for the academic calendar year; track the progress of the documents through the final approval by the EPC Committee. - Monitor all deadlines. - Evaluate and review courses and programs of study documents to ensure currency of the program descriptions, course and program learning outcomes, course descriptions, and course outlines. - Review all EPC-approved changes for the College Catalog. - Maintain historical records of curriculum changes. Loading: - Track and compare faculty instructional and non-instructional loads and schedules (including items from other AACC activities) and any other assignments related to the contractual obligations of full-time faculty assigned to the Education Department. - Generate all faculty load reports, staffing analyses, and enrollment reports as required by the Director and Dean. - Monitor all faculty teaching loads and assignments for ACA compliance. Contracts: - Assign part-time and full-time faculty to courses and any non-instructional service approved by the Dean. - Monitor and track part-time faculty lecturer rank, promotions, teaching workload reports, and determine eligibility for promotions and service awards; communicate information with the Director. - Oversee the processing and routing of all compensation documents for full-time and part-time faculty. - Serve as primary contact for questions or issues about contracts and contract approvals. Textbooks: - Manage and track all textbook orders, including direct digital access (DDA) textbooks, for assigned departments; enter information into Colleague in collaboration with the bookstore. - Monitor all deadlines. External Collaboration: - Serve as liaison between the TEACH Institute and the community. - Regularly work with teachers and staff from Anne Arundel County Public Schools. - Track and assist teachers in registering for classes and completing direct billing paperwork. Internal Collaboration: - Serve as a content expert for all systems and processes related to this position. - Monitor notifications regarding changes to any system or procedure that impacts department functions. - Alert Director, chairs, and office staff upon receipt of such notification/information. - Participate in college-wide task forces or groups to maintain currency and connections with records/registration, business office, communications, data, and IT in functions related to the position description and to support the TEACH Institute. - Regularly work with other Instructional Coordinators and administrative personnel (e.g., answering questions pertaining to contracts, payroll, loading, data management system, independent study, faculty loading, and various other procedures). Required Qualifications: - Bachelor's degree or higher - Minimum Of Two Years Of Relevant Experience - Excellent oral, written and interpersonal communication skills. - Demonstrated ability to work collaboratively with others in a team setting and a strong commitment to providing excellent customer service. - Proven ability to work with a variety of technology packages in a Windows environment, including word processing, database management, data retrieval and presentation. - Ability to work independently with attention to details and accuracy. - Demonstrated organizational skills. - Ability to deal professionally, tactfully and effectively with students, faculty, administrators, staff and the public. Preferred Qualifications: - Experience in a post-secondary setting. - Experience in K-12 education. Additional info: - Pay dates occur on the 7th and 22nd of each month. If those dates fall on a weekend, the pay date occurs on the Friday prior to the 7th and 22nd. - As an employee of the college, you are eligible for a comprehensive benefits package. - In the best interest of the College, only individuals who are residents of Maryland or one of the following states will be eligible for employment at the college: Delaware, Pennsylvania, Virginia, West Virginia or the District of Columbia. - The college will annually review this restriction and, if appropriate, expand the list of states of employment eligibility. - While we appreciate your interest ... applicants must be currently authorized to work in the U.S. on a full-time basis. Employment-based visa sponsorship (including H-1B sponsorship) is not available for any position. We need to decide what to keep. The diversity statement we can drop as EEO boilerplate. The work authorization and visa sponsorship statement maybe also legal but it's substantive about eligibility; we could keep under Requirements or a separate section like Eligibility. But we have limited section headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could incorporate eligibility into Requirements or Qualifications. The residency restriction could be part of Requirements. The work authorization could also be part of Requirements. We must not create sections with filler. So we will create sections: - About the role (include Position Summary, Department, Campus Location maybe) - Responsibilities (include all duties) - Requirements (include Required Qualifications plus eligibility info: residency, work authorization, no visa sponsorship) - Qualifications (include Preferred Qualifications) - Skills (maybe we could extract skills from Required Qualifications: communication, teamwork, tech, independent work, organizational, interpersonal. But we might avoid duplication; maybe we can omit Skills section if it's thin. The instruction: Prefer a few substantive sections over many thin ones. So we could omit Skills and fold those into Requirements. But we have to use headings only when there is real specific content. If we omit Skills, we don't output that heading. That's fine. - Benefits (comprehensive benefits package) - Pay (salary range, pay dates) - Schedule (hours per week, work mode, position type) We must not repeat job title as heading. Good. We need to output only HTML fragment, no /, no markdown. We'll produce something like:

About the role

...

For lists, use

• . We need to ensure we preserve all substantive info. Let's craft. About the role: include Position Summary, Department, Campus Location. Responsibilities: we could break into subheadings? The instruction only says use

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

  but likely we should stick to

  for sections only. Within Responsibilities we can use

  • for each duty; we could group by subcategories using

    headings? Not specified. We could just list all duties as a flat list, but that loses grouping. However we can still include subheadings as

    maybe bold? But better to keep as

    with subheading text then

    . The instruction didn't forbid using

    for prose; we can use

    for subheading like "Schedule:" then

    . That seems okay. We must not invent or summarize away detail. So we need to keep each duty verbatim. Let's extract each duty exactly as in posting. Schedule duties: - Build, analyze, organize, coordinate, enter, and modify the development of the credit and non-credit schedule of classes for submission to the Office of Records and Registration. -