SAFETY COMMUNICATIONS OPERATOR

We need to produce HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate. We need to parse the posting. Key content: - Hiring Department MU Police Department (maybe minor metadata, can be in a short p) - Job Description Overview: description paragraph. - What You’ll Do: list of duties (Emergency and Non-Emergency Call Handling, Radio And Dispatch Operations, Monitoring And Security Systems, Data Entry And Incident Documentation, Customer Service And Front Desk Operations, Training And Additional Duties) - Why Join MUPD? bullet points: Impactful Work, Team Environment, Educational Incentives, Professional Growth. - Shift Standard Hours: description of schedule. - Essential Personnel Requirements: note about essential employee. - Minimum Qualifications: high school diploma or equivalent, at least two years of experience providing comparable skills, knowledge, or abilities. - Preferred Qualifications: two or more years of administrative, dispatch, or communications experience; prior public-safety, 911, or law-enforcement communications background; proficiency with computers, Microsoft Office, Outlook, and accurate typing; ability to work varying shifts, including nights, weekends, and holidays. - Anticipated Hiring Range Salary Range: $18.80 per hour- Eligible for $1.00 shift differential for evening, night shifts and weekends. Grade: GGS 006 University Title: Safety Communications Operator. - Application Deadline: Open until filled, review of applications to begin immediately. (We drop application instructions) - Sponsorship Information: Employment visa sponsorship is not available for this position. (We can drop as minor metadata? It's not required but could be in a short p.) We need sections: About the role (maybe overview), Responsibilities (What You’ll Do), Requirements (Minimum Qualifications), Qualifications (Preferred Qualifications), Skills (maybe proficiency etc), Benefits (Educational Incentives, Professional Growth?), Pay (Salary range), Schedule (Shift Standard Hours). Also maybe "Impactful Work" etc could be under Benefits or separate? But we should follow instruction: use headings for those categories only if content exists. We need to decide which sections to include. We have content for: - About the role: overview paragraph. - Responsibilities: bullet list of duties. - Requirements: Minimum Qualifications. - Qualifications: Preferred Qualifications. - Skills: maybe we can include proficiency with computers etc as Skills. - Benefits: Educational Incentives, Professional Growth, maybe also Team Environment? Could be Benefits. - Pay: Salary range with shift differential. - Schedule: Shift Standard Hours description. We also have Essential Personnel Requirements (maybe part of Requirements? Could be separate but not required heading). Could fold into Requirements paragraph. We must not create sections with filler like "commensurate with experience". We have actual content. We must not repeat job title as heading. So no

Safety Communications Operator

. We must output only HTML fragment, no /, no markdown. We need to use

for section headings,

• for any list of duties/requirements/benefits, and

  for prose. Thus each section:

  About the role

  ...

  For lists:

  Responsibilities

  • ...
  ...
  We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting. We must be careful not to lose any detail. Let's extract details. Overview paragraph: "At the University of Missouri Police Department, law enforcement is about more than just policing – it’s about building community, fostering trust, and protecting the future. Safety Communications Operators are the first point of contact for emergency and non-emergency assistance, serving as a vital communications hub for police and public safety operations. In this role, you will manage critical information flow, support officer safety, and ensure timely, accurate coordination of responses across campus. This position demands professionalism, composure, and strong decision-making in a fast-paced environment." We can keep that as About the role. Responsibilities: list each bullet with details. From posting: Emergency and Non-Emergency Call Handling: - Answer and manage multi-line phone systems, including 911, emergency, and administrative lines and transfer calls to appropriate personnel or agencies as needed. - Gather accurate information from callers, assess urgency, and prioritize requests for service. - Serve as the university’s after-hours emergency switchboard and route urgent notifications appropriately. Radio And Dispatch Operations: - Operate multi-channel police radio systems to dispatch officers, security personnel, and support units. - Track officer status, movements, and safety through continuous monitoring and documentation. - Relay real-time updates, safety alerts, and critical information to field personnel with clarity and precision. Monitoring And Security Systems: - Monitor alarms, panic systems, and campus camera feeds. - Identify suspicious, unsafe, or criminal activity and coordinate immediate response from available units. - Document building alarms and work with Facilities or after-hours maintenance when required. Data Entry And Incident Documentation: - Maintain accurate, real-time CAD (Computer-Aided Dispatch) logs for all police and security activity. - Use public-safety systems including CAD, MULES, and Rave to enter, retrieve, and verify data. - Support incident reporting and investigative needs through detailed and consistent documentation. Customer Service And Front Desk Operations: - Serve as the first point of contact for walk-in individuals requesting assistance, information, or directions. - Provide professional, courteous customer service to students, faculty, staff, and visitors. Training And Additional Duties: - May assist in training new Communications Operators. - Perform other duties as assigned to support the mission of MUPD. We need to keep all that. Requirements (Minimum Qualifications): - High school diploma or equivalent. - At least two years of experience providing comparable skills, knowledge, or abilities. Qualifications (Preferred Qualifications): - Two or more years of administrative, dispatch, or communications experience. - Prior public-safety, 911, or law-enforcement communications background. - Proficiency with computers, Microsoft Office, Outlook, and accurate typing. - Ability to work varying shifts, including nights, weekends, and holidays. Skills: Could be the proficiency with computers etc. But we already have that in Preferred Qualifications. Maybe we can separate Skills as a subsection for proficiency etc. However we must not duplicate content. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we split Preferred Qualifications into Qualifications and Skills, we need to ensure we don't lose any info. We could keep Preferred Qualifications as Qualifications, and Skills could be omitted or we could put proficiency etc under Skills. But we need to decide. Better to have sections: About the role, Responsibilities, Requirements (minimum), Qualifications (preferred), Benefits, Pay, Schedule. Skills could be part of Qualifications. But we have a heading for Skills in the list of allowed headings; we can include if we have content. We could put "Proficiency with computers, Microsoft Office, Outlook, and accurate typing." under Skills. However the Preferred Qualifications also includes that line. To avoid duplication, we could move that line to Skills and keep other preferred qualifications under Qualifications. But we must not lose any detail. Let's see: Preferred Qualifications list: - Two or more years of administrative, dispatch, or communications experience. - Prior public-safety, 911, or law-enforcement communications background. - Proficiency with computers, Microsoft Office, Outlook, and accurate typing. - Ability to work varying shifts, including nights, weekends, and holidays. We could split: Qualifications: first two items (experience, background). Skills: proficiency with computers etc. Ability to work varying shifts maybe also under Skills or Requirements? Actually ability to work varying shifts is a requirement/schedule; could be under Schedule? But we already have schedule section. However ability to work varying shifts is a qualification/requirement. We could keep it under Qualifications. But we have a separate Schedule section for shift hours. So ability to work varying shifts could be mentioned there as well, but we already have schedule details. Might be redundant but okay. Given the instruction to prefer a few substantive sections over many thin ones, maybe we keep Qualifications (Preferred) as one section containing all four bullet points. And we don't need a separate Skills section. That would reduce number of sections. Thus sections: About the role, Responsibilities, Requirements (minimum), Qualifications (preferred), Benefits, Pay, Schedule. Now Benefits: from "Why Join MUPD?" we have Impactful Work, Team Environment, Educational Incentives, Professional Growth. Those are benefits. We'll list them as bullet list. Pay: "Anticipated Hiring Range Salary Range: $18.80 per hour- Eligible for $1.00 shift differential for evening, night shifts and weekends. Grade: GGS 006 University Title: Safety Communications Operator." We need to preserve all. We'll put in

  . Schedule: "Shift Standard Hours 8-hour shifts Monday thru Friday: Days (7am-3pm), Evenings (3pm-11pm), and Midnights (11pm-7am); 12-hour shifts Weekends: Days (7am-7pm) Nights (7pm -7am). Overtime may be available/required for shift coverage, special events, and/or campus emergencies as needed." Also Essential Personnel Requirements: "As an essential university employee, may be required to work during weekends, university holidays, campus closures, severe weather events, and other emergency situations as operational needs dictate." Could be included in schedule section as note. We'll combine schedule and essential personnel requirements into Schedule section. Now we need to include minor metadata like Hiring Department MU Police Department. Could be a short p at top before sections. Not a heading. We'll include a

  with that. Also Application Deadline and Sponsorship Information we drop (boilerplate). Actually Sponsorship Information is not boilerplate but it's minor metadata; we can drop as per instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can drop Sponsorship Information entirely or put in a short p. Safer to drop. Now produce HTML. We must ensure we use proper escaping for any special characters like &, <, >. The text includes ampersand in "MU Police Department"? Actually "MU Police Department" no ampersand. There's an en dash? We'll just use hyphens. We need to preserve the bullet points exactly as in posting. Use

• for each. Let's craft. First, opening

  for hiring department:

  Hiring Department: MU Police Department.

  Then About the role:

  About the role

  At the University of Missouri Police Department, law enforcement is about more than just policing – it’s about building community, fostering trust, and protecting the future. Safety Communications Operators are the first point of contact for emergency and non-emergency assistance, serving as a vital communications hub for police and public safety operations. In this role, you will manage critical information flow, support officer safety, and ensure timely, accurate coordination of responses across campus. This position demands professionalism, composure, and strong decision-making in a fast-paced environment.

  Responsibilities:

  Responsibilities

  with each bullet. We need to keep the subheadings like "Emergency and Non-Emergency Call Handling:" as part of the li text? Could be strong? But we can just include as plain text within li. We'll produce:
  • Emergency and Non-Emergency Call Handling: Answer and manage multi-line phone systems, including 911, emergency, and administrative lines and transfer calls to appropriate personnel or agencies as needed; gather accurate information from