Communications Officer
for each section heading.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can combine similar items into prose or lists as appropriate, but must not lose detail.
We need to decide what goes where.
About the role: Could include department summary and position summary overview (mission, role). Could be a prose paragraph.
Responsibilities: list of duties: evaluating incoming calls, routing to appropriate agency 24/7, providing essential communication link, providing general info to public via phone regarding safety/security/facilities, operate/monitor alarms, confidential law enforcement databases, emergency notification apps, surveillance devices, two-way comms within IOC, work with external emergency responders via Lane Central 911 to facilitate service requests for critical life safety incidents, certify as Basic Telecommunicator via DPSST, may be assigned to unique functions: field-based/tactical communications for large campus events/special ops, maintenance/updating of notification lists and protocols, testing/exercising emergency notification procedures/systems, records and court services, community engagement programs, interface with police officers, CSOs, security officers, campus partners, external constituencies using multiple comm devices, work in fast-paced potentially stressful environment, maintain composure/professional presence while accurately gathering/giving critical info to first responders, campus leaders, public, may be required to work weekends, holidays, all shifts (Day, Swing, Graveyard). That's a lot.
Requirements: Minimum requirements: High School diploma or GED; One year experience working with public (examples: customer service, sales, info/reception, food service, other positions involving direct work with general public). Also professional competencies? Those could be Skills.
Qualifications: Preferred qualifications: one year full-time work as law enforcement dispatcher within last 5 years; one or more years experience full-time work for higher education agency performing call taking/dispatch; DPSST Basic Telecommunicator certification.
Skills: Professional competencies: experience using computers for typical work tasks (entering data into spreadsheets, document generation); possession of or ability to obtain within three months LEDS certification; advanced First Aid and CPR certification; ability to read, write, speak clearly and concisely enough to understand communications and document work effectively; ability to follow both written and verbal directions and university admin policies/procedures/guidelines; ability to prioritize and multi-task effectively in fast-paced detail-oriented environment; ability to maintain composure and work effectively in stressful situations; ability to work effectively and in a professional and respectful manner when interacting with diverse members of public; ability to provide excellent customer service while adhering to rules, regulations, safety guidelines.
Also special requirements/qualifications: must pass background assessment (personal history, criminal history, psychological evaluation and DPSST F2a medical exam); meet and maintain all CJIS background requirements; adhere to Clery Act, FERPA, mandatory reporting and Title IX reporting responsibilities; maintain strict confidentiality; complete CTO within 6 months; assessment and testing: must complete and pass written and/or video skills assessment.
These could go under Requirements or Qualifications? They are special requirements. Could be part of Requirements (maybe "Requirements" includes both minimum and special). But we already have Minimum Requirements and Preferred Qualifications. We could treat "Special Requirements/Qualifications" as part of Requirements (maybe as a subsection). However we need to avoid duplication.
We have headings: Requirements, Qualifications, Skills. We could put Minimum Requirements under Requirements, Preferred Qualifications under Qualifications, and Special Requirements under Requirements as well (maybe as a list). Or we could put Special Requirements under Requirements and keep Qualifications for Preferred only. That seems fine.
Skills: Professional competencies.
Benefits: robust benefits package including health insurance, retirement plans, paid time off. Also mention "For more information about benefits, visit our website." Could include that as prose.
Pay: Salary: $27.21 - $37.25 per hour. FTE: 1.0. Could also mention appointment type regular ongoing. But Pay section likely just salary.
Schedule: This position may be required to work weekends, holidays, and all shifts (Day, Swing, and Graveyard). Also maybe mention shift work.
We also have info about Application Review Begins October 12, 2026; Open until filled. That's metadata about application timeline; we might drop as per instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. This is minor metadata; we could drop it or include in a short p at top? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could include a short p for Application Review Begins etc. But maybe better to drop it as not essential? It's substantive? It's about timeline; maybe we keep as a short p before sections. But the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. It's not a heading; we can put it in a
before sections.
Also Special Instructions to Applicants: must submit complete application, online application, resume addressing min/pref qualifications; encouragement to apply even if not meeting all preferred qualifications; contact email fass@uoregon.edu for questions. This is also substantive; we could include as a
under maybe a heading? There's no heading for Application Instructions; we could fold into a short p after the metadata.
But we must not include application instructions? The instruction says: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we must remove application instructions. So we should drop the Special Instructions to Applicants. Also remove EEO etc. So we drop that.
Thus we keep only: Department, Classification, Appointment Type and Duration, Salary, FTE, Application Review Begins..., Department Summary, Position Summary, Special Requirements/Qualifications, Minimum Requirements, Professional Competencies, Preferred Qualifications, FLSA Exempt, Benefits info, Represented by union maybe? That's substantive? Could be included in About the role? Might be minor but we can keep as a p.
We need to preserve all substantive information; but we are told to remove application instructions. So we drop that.
Now we need to decide what to include in About the role: Could combine Department Summary and Position Summary (overview). Also maybe include Classification, Appointment Type, FTE.
But we must not create headings with filler. So we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Now we need to fill each with content.
Let's draft.
About the role (
About the role
): Provide a prose paragraph summarizing the department, mission, role. Include: Department: University of Oregon Police Department, Classification: Campus Dispatcher, Appointment Type: Regular, Ongoing, FTE: 1.0. Department Summary: Safety and Risk Services (SRS) is a unit within Finance and Administration portfolio... etc. Position Summary: The Communications Officer provides direct operational support... etc. We'll combine into a few sentences.
We must preserve all substantive info; we can't omit details like mission statements etc. But we can condense into prose while preserving meaning. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That means we cannot leave out details; we must keep all details. However we can rephrase but must not lose any detail. That's tricky: if we condense, we might lose some nuance. But we can include all details as separate sentences or bullet lists. Probably safer to keep details as bullet lists under appropriate sections rather than prose that omits.
Thus we could keep About the role as a short paragraph that includes the high-level info but we still need to include all details somewhere else. For example, department summary details could go under About the role as a list? But we said use - for any list of duties/requirements/benefits. Department summary is not a list of duties/requirements/benefits; it's descriptive prose. So we can put it in
. That's fine as long as we include all the sentences.
Thus we need to include all the sentences from Department Summary and Position Summary in the About the role section (maybe as multiple paragraphs). That will preserve all detail.
Similarly, Responsibilities section will contain all duties as a list (
- ).
Requirements section will contain minimum requirements and special requirements (background, CJIS, Clery, FERPA, confidentiality, CTO, assessment). We'll list them.
Qualifications section will contain preferred qualifications.
Skills section will contain professional competencies.
Benefits section will contain benefits package
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can combine similar items into prose or lists as appropriate, but must not lose detail. We need to decide what goes where. About the role: Could include department summary and position summary overview (mission, role). Could be a prose paragraph. Responsibilities: list of duties: evaluating incoming calls, routing to appropriate agency 24/7, providing essential communication link, providing general info to public via phone regarding safety/security/facilities, operate/monitor alarms, confidential law enforcement databases, emergency notification apps, surveillance devices, two-way comms within IOC, work with external emergency responders via Lane Central 911 to facilitate service requests for critical life safety incidents, certify as Basic Telecommunicator via DPSST, may be assigned to unique functions: field-based/tactical communications for large campus events/special ops, maintenance/updating of notification lists and protocols, testing/exercising emergency notification procedures/systems, records and court services, community engagement programs, interface with police officers, CSOs, security officers, campus partners, external constituencies using multiple comm devices, work in fast-paced potentially stressful environment, maintain composure/professional presence while accurately gathering/giving critical info to first responders, campus leaders, public, may be required to work weekends, holidays, all shifts (Day, Swing, Graveyard). That's a lot. Requirements: Minimum requirements: High School diploma or GED; One year experience working with public (examples: customer service, sales, info/reception, food service, other positions involving direct work with general public). Also professional competencies? Those could be Skills. Qualifications: Preferred qualifications: one year full-time work as law enforcement dispatcher within last 5 years; one or more years experience full-time work for higher education agency performing call taking/dispatch; DPSST Basic Telecommunicator certification. Skills: Professional competencies: experience using computers for typical work tasks (entering data into spreadsheets, document generation); possession of or ability to obtain within three months LEDS certification; advanced First Aid and CPR certification; ability to read, write, speak clearly and concisely enough to understand communications and document work effectively; ability to follow both written and verbal directions and university admin policies/procedures/guidelines; ability to prioritize and multi-task effectively in fast-paced detail-oriented environment; ability to maintain composure and work effectively in stressful situations; ability to work effectively and in a professional and respectful manner when interacting with diverse members of public; ability to provide excellent customer service while adhering to rules, regulations, safety guidelines. Also special requirements/qualifications: must pass background assessment (personal history, criminal history, psychological evaluation and DPSST F2a medical exam); meet and maintain all CJIS background requirements; adhere to Clery Act, FERPA, mandatory reporting and Title IX reporting responsibilities; maintain strict confidentiality; complete CTO within 6 months; assessment and testing: must complete and pass written and/or video skills assessment. These could go under Requirements or Qualifications? They are special requirements. Could be part of Requirements (maybe "Requirements" includes both minimum and special). But we already have Minimum Requirements and Preferred Qualifications. We could treat "Special Requirements/Qualifications" as part of Requirements (maybe as a subsection). However we need to avoid duplication. We have headings: Requirements, Qualifications, Skills. We could put Minimum Requirements under Requirements, Preferred Qualifications under Qualifications, and Special Requirements under Requirements as well (maybe as a list). Or we could put Special Requirements under Requirements and keep Qualifications for Preferred only. That seems fine. Skills: Professional competencies. Benefits: robust benefits package including health insurance, retirement plans, paid time off. Also mention "For more information about benefits, visit our website." Could include that as prose. Pay: Salary: $27.21 - $37.25 per hour. FTE: 1.0. Could also mention appointment type regular ongoing. But Pay section likely just salary. Schedule: This position may be required to work weekends, holidays, and all shifts (Day, Swing, and Graveyard). Also maybe mention shift work. We also have info about Application Review Begins October 12, 2026; Open until filled. That's metadata about application timeline; we might drop as per instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. This is minor metadata; we could drop it or include in a short p at top? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could include a short p for Application Review Begins etc. But maybe better to drop it as not essential? It's substantive? It's about timeline; maybe we keep as a short p before sections. But the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. It's not a heading; we can put it in a
before sections. Also Special Instructions to Applicants: must submit complete application, online application, resume addressing min/pref qualifications; encouragement to apply even if not meeting all preferred qualifications; contact email fass@uoregon.edu for questions. This is also substantive; we could include as a
under maybe a heading? There's no heading for Application Instructions; we could fold into a short p after the metadata. But we must not include application instructions? The instruction says: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we must remove application instructions. So we should drop the Special Instructions to Applicants. Also remove EEO etc. So we drop that. Thus we keep only: Department, Classification, Appointment Type and Duration, Salary, FTE, Application Review Begins..., Department Summary, Position Summary, Special Requirements/Qualifications, Minimum Requirements, Professional Competencies, Preferred Qualifications, FLSA Exempt, Benefits info, Represented by union maybe? That's substantive? Could be included in About the role? Might be minor but we can keep as a p. We need to preserve all substantive information; but we are told to remove application instructions. So we drop that. Now we need to decide what to include in About the role: Could combine Department Summary and Position Summary (overview). Also maybe include Classification, Appointment Type, FTE. But we must not create headings with filler. So we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Now we need to fill each with content. Let's draft. About the role (
About the role
): Provide a prose paragraph summarizing the department, mission, role. Include: Department: University of Oregon Police Department, Classification: Campus Dispatcher, Appointment Type: Regular, Ongoing, FTE: 1.0. Department Summary: Safety and Risk Services (SRS) is a unit within Finance and Administration portfolio... etc. Position Summary: The Communications Officer provides direct operational support... etc. We'll combine into a few sentences. We must preserve all substantive info; we can't omit details like mission statements etc. But we can condense into prose while preserving meaning. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That means we cannot leave out details; we must keep all details. However we can rephrase but must not lose any detail. That's tricky: if we condense, we might lose some nuance. But we can include all details as separate sentences or bullet lists. Probably safer to keep details as bullet lists under appropriate sections rather than prose that omits. Thus we could keep About the role as a short paragraph that includes the high-level info but we still need to include all details somewhere else. For example, department summary details could go under About the role as a list? But we said use- for any list of duties/requirements/benefits. Department summary is not a list of duties/requirements/benefits; it's descriptive prose. So we can put it in
. That's fine as long as we include all the sentences. Thus we need to include all the sentences from Department Summary and Position Summary in the About the role section (maybe as multiple paragraphs). That will preserve all detail. Similarly, Responsibilities section will contain all duties as a list (
- ). Requirements section will contain minimum requirements and special requirements (background, CJIS, Clery, FERPA, confidentiality, CTO, assessment). We'll list them. Qualifications section will contain preferred qualifications. Skills section will contain professional competencies. Benefits section will contain benefits package