Loss Prevention Officer Hotel
or drop it." So we can include location etc in a short p maybe. But they say "Prefer a few substantive sections over many thin ones." So we could combine location and schedule into a brief paragraph. We need sections: About the role? There's a POSITION SUMMARY. That could be "About the role" or "Position Summary". Use h3 for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content: POSITION SUMMARY (list of duties). That's responsibilities. Also PREFERRED QUALIFICATIONS (Education, etc). Also there is some descriptive about Marriott culture etc. That could be "About the role" or "About the company". But we should not invent sections without content. We have responsibilities (the bullet list). We have qualifications (preferred qualifications). We have maybe "Skills" implied? Not explicit. We have no explicit Benefits, Pay, Schedule. So we should not create those sections. Thus we will have:
About the role
maybe containing a short paragraph summarizing the role (maybe from POSITION SUMMARY first sentence). But we must preserve ALL substantive information; we cannot summarize away detail. So we need to keep the duties as list items under Responsibilities. The "About the role" could be a brief paragraph from the POSITION SUMMARY intro? But the POSITION SUMMARY is essentially a list of duties. If we create About the role with a paragraph, we might be duplicating or summarizing. Better to use "Responsibilities" section for the duties list. And maybe "About the role" could be a short paragraph describing the role (like "Patrol all areas of the property; assist guests with room access...") but that's essentially the same as responsibilities. The instruction: "Prefer a few substantive sections over many thin ones." So we could just have one section "Responsibilities" with the list. And another section "Qualifications" for preferred qualifications. Possibly also "Skills" if we can extract from the text: there are many skill-related statements like "Speak with others using clear and professional language; prepare and review written documents accurately and completely." etc. Those could be considered skills. But they are also part of responsibilities. Might be better to have "Responsibilities" and "Qualifications". Avoid thin sections. We need to preserve all substantive information: The long list of duties (many sentences). We need to put them as- items. Each duty sentence should be a list item. We must not lose any.
Similarly, the PREFERRED QUALIFICATIONS: Education: High school diploma or G.E.D. equivalent. Related Work Experience: No related work experience. Supervisory Experience: No supervisory experience. License or Certification: None. We need to preserve that exactly. Could be list items.
Also there is a paragraph about Marriott culture etc. That's substantive information about the company and maybe could be placed under "About the role" or "About the company". Since we have no explicit "About the company" heading but we could add a section "About the role" with that paragraph. However that might be considered thin if it's just a paragraph. But it's substantive. We could include it as a
under a section "About the role". That would be okay. Thus sections:
About the role
[Marriott culture paragraph...]
Responsibilities
- ...
Qualifications
- ...
? But requirement: Use
- for any list of duties/requirements/benefits. So we need to make a list. We could treat each line separated by semicolon as an item? But many items have semicolons inside.
Given the instruction to preserve all substantive information, we could keep the responsibilities as a single paragraph
but that would violate the rule to use
- for any list of duties. However the rule says: "Use
- for any list of duties/requirements/benefits, and
for prose." The POSITION SUMMARY is a list of duties, so we should use list. We can approximate by splitting at each period that is followed by a space and a capital letter (next sentence starts with capital). That will avoid splitting inside "e.g.," because after "e.g.," there is a space and lowercase "small". So not split. Good. Let's attempt to split manually. I'll go through the text and create items. 1. Patrol all areas of the property; assist guests with room access. 2. Monitor Closed Circuit Televisions, perimeter alarm system, duress alarms, and fire life safety system. 3. Lock property entrances when required. 4. Conduct daily physical hazard inspections. 5. Respond to accidents, contact EMS or administer first aid/CPR as required. 6. Assist guests/employees during emergency situations. 7. Notify appropriate individuals in the event of accidents, attacks, or other incidents. 8. Defuse guest/employee disturbances. 9. Call for outside assistance if necessary. 10. Complete incident reports to document all Security/Loss Prevention related incidents. 11. Handle all interruptions and complaints. 12. Resolve safety hazard situations. 13. Escort any unwelcome persons from the property without interrupting the orderly flow of property operation. 14. Report to scenes of vehicle accidents/thefts. 15. Call for assistance using proper code responses. 16. Complete a Loss Prevention shift summary/daily activity report. 17. Maintain confidentiality of all Security/Loss Prevention and property reports/documents; release information only to authorized individuals. 18. Conduct investigations and gather evidence. 19. Conduct interviews with relevant parties. 20. Follow
- for any list of duties/requirements/benefits, and
- for any list of duties. However the rule says: "Use
- for any list of duties/requirements/benefits. So we need to make a list. We could treat each line separated by semicolon as an item? But many items have semicolons inside.
Given the instruction to preserve all substantive information, we could keep the responsibilities as a single paragraph