Property Administrator

We need to output HTML fragment with headings

for sections: 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 preserve all substantive info, remove boilerplate (EEO, legal, navigation, cookie, etc). Must not create sections with filler like "commensurate with experience". Must not invent. We need to parse the posting. Let's extract sections: - About the role: The first paragraph: "StoryPoint Shaker Heights The Property Administrator will perform and/or oversee all office activities of a senior residential community. This role is responsible for maintaining an accurate reporting system of resident accounts and office processes within assigned timelines. The Property Administrator will assist the Executive Director with financial oversight of budget, department declining budgets, NOI, coverage ratio, cash flow, and loss to potential." That's about the role. - Responsibilities: There's a "Primary Responsibilities" heading in the text. Then a long list of duties. Also later "Additional duties as assigned or needed." etc. Also "Responsible for pursuing receivables/collection of outstanding unpaid rents." etc. So we can put all responsibilities under

Responsibilities

with a

• list. - Requirements: The posting includes "Required Experience Associates degree or equivalent experience 2-4 years of experience in property management Ability to write clearly and concisely Ability to effectively communicate verbally with individuals and both large and small groups. Ability to effectively work collaboratively as part of a team. Strong proficiency with Microsoft Office Applications Accounting or financial experience preferred Forecasting/projections experience preferred Administrative experience required Knowledge of Yardi Some travel may be required" That's requirements/qualifications. Could split into Requirements and Qualifications but we can combine. The instruction says we can have sections like Requirements, Qualifications, Skills. We need to decide based on content. The posting lumps them; we can put under Requirements (or Qualifications). Since they ask to prefer few substantive sections over many thin ones, we can combine into one section maybe "Requirements". But we also have Skills: maybe we can separate skills like Microsoft Office, Yardi, communication, etc. But we can also put all under Requirements. We need to avoid filler like "Some travel may be required" - that's substantive (travel). It's okay. - Benefits: The posting does not mention benefits explicitly. There's a paragraph about mission, values, vision, culture, but not explicit benefits like health insurance, PTO, etc. So we should NOT create a Benefits section because no specific content. - Pay: No mention of pay/salary. So omit. - Schedule: No explicit schedule (full-time/part-time, hours). Not mentioned. So omit. Thus we will have sections: About the role, Responsibilities, Requirements (or Qualifications). Possibly also Skills if we want to separate but we can keep within Requirements. We must not include boilerplate like "Equal Opportunity Employer", "Click on glassdoor", etc. Also remove the mission/vision paragraphs? Those are substantive? They describe culture, mission, values. Could be considered "About the company" but we don't have a section for that. The instruction says we can include sections only when posting has real specific content for it. There's no heading for "About the company" in the list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add a custom heading like "About the company". So we should omit those paragraphs (mission, values, etc.) as they don't fit allowed headings. However, we must preserve ALL substantive information; but we cannot invent headings not allowed. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, but likely we should stick to those. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could include a section like "About the role" which we have. The mission/vision content could be considered part of "About the role"? Not really. It's about the company. But we could possibly include it under "About the role" as extra description? Might be okay but could be considered not directly about the role. However, the instruction says preserve ALL substantive information; we cannot drop mission/vision if it's substantive. But we cannot create a new heading. Perhaps we can incorporate it into the "About the role" paragraph as additional context. That would preserve it while staying within allowed heading. Let's do that: after the initial role description, we can add a sentence about the company's mission, values, etc. That would be substantive and not a separate heading. Similarly, the "Connecting Seniors..." paragraph is about the company; we can incorporate into About the role. Thus About the role will contain: role description + company mission/vision/values paragraphs. Now Responsibilities: we need to list all duties from "Primary Responsibilities" onward until before "General Working Conditions". Also include the additional duties like "Maintain a positive attitude..." etc. Also "Supports the Mission, Values, and Vision..." etc. Also "Work toward continual improvement..." etc. Also "Train front office personnel..." etc. Also "Responsible for pursuing receivables..." etc. Also "Implement and conduct structured receivables collection." etc. Also "Conduct monthly general ledger review." etc. Also "Collaborate with team to forecast operations with 98% accuracy 4 months out." We need to capture all bullet-like sentences. We'll turn each sentence into a

  . Ensure we don't duplicate. Let's extract responsibilities list from the text: From "Primary Responsibilities" paragraph: - The Property Administrator assumes the Executive Director responsibilities when required. - Carry out supervisory responsibilities in accordance with the organization’s policies and applicable laws. - Directly manages front office personnel. - Function as Manager on Duty, taking a weekend rotation. - Schedule front office personnel. - Complete resident billing of monthly rental fees and other miscellaneous charges. - Collect, process, deposit and record all income, and notify residents of non-payments. - Perform month end closing procedure and ensure that reports are accurate and submitted in a timely manner. - Maintain and update the property file system on work orders, general correspondence, residents, employees, etc. - Maintain Certificates of Insurance with vendors/contractors. - Provide quality, professional service to the residents. - Enter lease renewals and move-in/move-out paperwork processing in Yardi. - Maintain and reconcile petty cash account. - Process purchase invoices on a weekly basis. - Manage budget control ledger. - Payroll administration, including pay package, termination packages, and payroll transmittals. - Maintain department expenses within budgeted parameters. - Purchase and supervise the maintenance of all office and administrative supplies and equipment. - Maintain vendor indemnification and code of conduct. - Additional duties as assigned or needed. - Maintain a positive attitude which supports team performance and productivity. - Supports the Mission, Values, and Vision of Senior Village Management. - Work toward continual improvement of the overall organization. - Train front office personnel as necessary to cover Property Administrator responsibilities. - Responsible for pursuing receivables/collection of outstanding unpaid rents. - Implement and conduct structured receivables collection. - Conduct monthly general ledger review. - Collaborate with team to forecast operations with 98% accuracy 4 months out. Also there is "General Working Conditions" later, but that's not responsibilities; it's working conditions. We could possibly include under a separate section? Not allowed headings. Could we put under About the role? Not appropriate. Could we omit? The instruction says preserve ALL substantive information. Working conditions is substantive. But we don't have a heading for it. Could we incorporate into About the role? Might be okay to add a sentence about working conditions. But the list is long; maybe we can create a section "Working Conditions" but not in allowed headings. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not an exhaustive list. However, they also say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but the examples given are those. To be safe, we should stick to those headings. But we need to preserve working conditions info. Could we incorporate into Responsibilities? Not really. Could we incorporate into About the role? Could add a sentence: "The role involves standing for long periods, occasional lifting up to 25 pounds, moderate noise level, occasional travel." That would preserve. Thus we will add working conditions details into About the role after the mission/vision. Now Requirements/Qualifications/Skills: We have required experience, education, abilities, preferred experience, knowledge of Yardi, some travel may be required (already covered). We'll create a section "Requirements" with

  • items. Let's list: - Associates degree or equivalent experience - 2-4 years of experience in property management - Ability to write clearly and concisely - Ability to effectively communicate verbally with individuals and both large and small groups - Ability to effectively work collaboratively as part of a team - Strong proficiency with Microsoft Office Applications - Accounting or financial experience preferred - Forecasting/projections experience preferred - Administrative experience required - Knowledge of Yardi - Some travel may be required (though we already mentioned travel in working conditions; but we can keep it here as requirement; but to avoid duplication we could mention only once. However, we need to preserve all info; duplication is okay but better not duplicate. We'll keep travel mention in Working Conditions only, and not repeat in Requirements. But the requirement list includes "Some travel may be required". We could note it as part of requirements but we already have it in working conditions; we could keep it there and not duplicate. However, we need to preserve the info; it's preserved in working conditions. So we can omit from requirements to avoid duplication. But we must ensure we didn't lose any other required items. Also "Ability to effectively communicate verbally with individuals and both large and small groups." That's one item. Also "Ability to effectively work collaboratively as part of a team." Also "Strong proficiency with Microsoft Office Applications" Also "Accounting or financial experience preferred" Also "Forecasting/projections experience preferred" Also "Administrative experience required" Also "Knowledge of Yardi" Also maybe "Ability to write clearly and concisely" Also "Associates degree or equivalent experience" Also "2-4 years of experience in property management" Also maybe "Ability to effectively communicate verbally with individuals and both large and small groups." Already. Also "Ability to effectively work collaboratively as part of a team." Also "Strong proficiency with Microsoft Office Applications" Also "Accounting or financial experience preferred" Also "Forecasting/projections experience preferred" Also "Administrative experience required" Also "Knowledge of Yardi" Also maybe "Ability to effectively communicate verbally with individuals and both large and small groups." Already. Also "Ability to effectively work collaboratively as part of a team." Also "Strong proficiency with Microsoft Office Applications" Ok. Now we need to ensure we didn't miss any: "Ability to write clearly and concisely" yes. Now we need to output HTML fragment. Structure:

    About the role

    ... combined paragraphs ...

    Responsibilities

    • ... each duty ...

    Requirements

    • ... each requirement ...
    We must not include empty sections. Now craft the About the role paragraph. Combine: "StoryPoint Shaker Heights The Property Administrator will perform and/or oversee all office