Leasing Agent

We need to output HTML fragment with sections: About the role (maybe from Position Summary), Responsibilities, Requirements (Education And Experience, Knowledge And Skills maybe combined), Skills (maybe separate), Benefits, Pay, Schedule only if present. The posting does not mention Pay, Benefits, Schedule. So we should not include those sections. Also we should not repeat job title as heading. We need to include headings for sections that have content: About the role (Position Summary), Responsibilities, Requirements (Education And Experience + Knowledge And Skills maybe combined), Skills (maybe separate if we want). But we need to avoid thin sections. Could combine Education And Experience and Knowledge And Skills into a single "Requirements" section. Skills could be part of Requirements. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role, Responsibilities, Requirements, Skills. But we need to ensure we don't create empty sections. We have content for About the role (Position Summary). Responsibilities (list). Requirements (Education And Experience + Knowledge And Skills). Skills maybe we could extract from Knowledge And Skills (abilities). But that may be redundant. Better to have Requirements covering education/experience and knowledge/skills. Then maybe no separate Skills section. But we could still include Skills if we want, but we must not create filler. If we put Skills heading but then list abilities, that's substantive. However the knowledge and skills already includes abilities. Could split: Requirements = Education And Experience; Skills = Knowledge And Skills. That seems reasonable. Thus sections:

About the role

Position Summary text.

Responsibilities

• ...

Requirements

Education And Experience text.

Skills

• ...

(list of knowledge and skills items). We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from Education And Experience and Knowledge And Skills. For Knowledge And Skills, it's a paragraph with many sentences; we could break into list items for each ability? The instruction: Use

• for any list of duties/requirements/benefits. The Knowledge And Skills is not a list but a paragraph; we could keep as

  . However we could also split into list items for each ability, but that would be summarizing? It's okay to convert sentences into list items as long as we preserve all info. Safer to keep as

  for prose. But the instruction says use

  • for any list of duties/requirements/benefits. It doesn't forbid using

    for non-list content. So we can keep Knowledge And Skills as

    . Thus:

    About the role

    The primary purpose of this position is to coordinate the resident application and leasing processes. The incumbent provides customer service by answering questions, reviewing submitted forms for accuracy and completeness, and communicating status updates regarding wait lists and vacancy listings.

    Responsibilities

    • Serves as the primary contact for prospective residents.
    • Receives and responds to inquiries (telephone and in-person) from applicants, residents, landlords, and community organizations as needed.
    • Implements and coordinates the methods and procedures needed to effectively manage the leasing process and assists Property Management staff with the processing of applications.
    • Ensures compliance with Agency, department, and investor objectives; federal, state, and local statues, rules, regulations, policies, and procedures; and other guidelines.
    • Makes appropriate recommendations to improve efficiency and effectiveness.
    • Monitors existing waiting lists, ensuring compliance with relevant regulations.
    • Shows units; interviews prospective residents; assists prospective residents with completing application paperwork; and explains how information will determine applicant eligibility, rent to be charged, and unit size required according to applicable regulations.
    • Receives official applications from potential residents; interviews applicants; verifies information received; and determines housing eligibility.
    • Directs applicants in securing necessary verification and documentation of eligibility factors; and, if needed, contacts external sources for substantiation and/or clarification.
    • Assists with the verification of any information presented for eligibility or rent computation and assists with resident rent calculations or retroactive rent payments.
    • Informs applicants of eligibility decisions and provides information regarding next steps.
    • Prepares contracts, leases, and move-in packets.
    • Sends out notice of cancellation, denial or withdrawl to applicants,; processes cancellations, denials and withdrawals in the computer system.
    • Maintains accurate and complete records regarding applicant, participant, resident, and tenant/landlord information in computer system.
    • Manages data related to daily leasing activities and utilizes data tracking and reporting systems.
    • Prepares reports on the status of applications, leasing, and occupancy.
    • Prepares and maintains paper and electronic files for various programs in compliance with Agency, investor, federal, state, and local regulations, policies, and procedures.
    • Assists with special projects and supports other department activities as assigned.
    • Performs other duties as assigned.

    Requirements

    High School Diploma or GED required. Associate’s Degree or Bachelor’s Degree in Business Administration or closely related field from an accredited college or university preferred. One (1) year of leasing, clerical, or resident intake experience is required. An equivalent combination of education and experience may be considered.

    Skills

    Thorough knowledge of Agency operating policies, procedures, principles, practices, and techniques; HUD regulations pertaining to low-rent housing; and services available through local social service agencies. Thorough knowledge of leasing agreement procedures, recertification process, and uniform physical condition standards inspections. Thorough knowledge and experience in a housing assistance program or social services field. General knowledge of Landlord/Tenant Law, procurement regulations, and Fair Housing requirements. Ability to accurately and completely document in writing appropriate events and activities. Ability to read and comprehend relatively complex material. Ability to establish and maintain effective working relationships with co-workers and persons outside the Agency. Ability to communicate on the level of the listener, recognizing when information has been misunderstood, and the ability to rectify any misunderstanding as needed when explaining Agency policies and procedures. Ability to interview and counsel residents and deal effectively with situations that require tact and diplomacy, yet firmness. Capable of managing competing demands and meeting productivity standards while handling frequent change, delays, and unexpected events. Ability to prepare clear and concise narrative and statistical reports. Ability to operate appropriate Agency computer equipment and software packages. Ability to communicate clearly, concisely, orally and in writing.

    We should not include sections like Benefits, Pay, Schedule. Also we should not include Supervision Controls, Guidelines, Complexity, Scope and Effect, Personal Contacts, Physical Requirements, Work Environment, Other Requirements. Those are substantive but not requested headings. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings, but does not forbid other headings? It says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect us to use those headings only. Also they say "Prefer a few substantive sections over many thin ones." So we should omit those other sections. However we must preserve ALL substantive information; do NOT invent or summarize away detail. If we omit those sections, we lose that information. But maybe we can incorporate that information into existing sections (like Responsibilities or Requirements) without creating new headings. The instruction says we should not create headings for those unless the posting has real, specific content for it. It does not forbid including that content under other headings. So we can embed details like Supervision Controls etc. into maybe Responsibilities or Requirements as prose. But we must not lose info. However the instruction also says "Prefer a few substantive sections over many thin ones." So we could combine all extra info into a single "Additional Information" but that heading is not in the list. Better to incorporate into existing sections like Responsibilities (some are not duties) or Requirements (some are not requirements). Could create a section "Additional Details" but that's not in the allowed list; maybe it's okay but they said "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But to be safe, we could add a section "Other Information" but risk being considered not following instruction. Better to incorporate into existing sections where appropriate. We have many details: Supervision Controls, Guidelines, Complexity, Scope and Effect, Personal Contacts, Physical Requirements, Work Environment, Other Requirements. We could add a section "Additional Information" but maybe it's okay. However the instruction says "Prefer a few substantive sections over many thin ones." Adding another section may be okay if it's substantive. But they gave examples of headings; they didn't say we cannot use others. I'd lean to include a section "Additional Information" to preserve all info without making many thin sections. But we must ensure we don't create filler. The content is substantive. Alternatively we could merge all those into Responsibilities (some are not duties) or Requirements (some are not requirements). That might be awkward but doable. Given the instruction to preserve ALL substantive information, I think we should include them. I'd create a section "Additional Information" with sub-sections? But we cannot nest headings? We could just have a

    with all that info. That would be a lot of prose but okay. But the instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they gave examples. I'd stick to those headings only and embed the rest into those sections. Let's see where each fits: - Supervision Controls: could go under Responsibilities (maybe as a duty about receiving instructions). Could add a bullet: "Receives instructions from and is accountable to the Property Manager; sets priorities; brings complaints to supervisor; plans and carries out work activities with minimal supervision; work reviewed regularly for accuracy, timeliness, conformity." That's a duty. - Guidelines: could be under Responsibilities: "Performs routine duties by following established policies and procedures, applicable reference materials, published laws, regulations, handbooks, and training materials; may require guidance from supervisor for situations not covered." - Complexity: maybe under Responsibilities: "Performs routine duties following established and specific Agency policies and procedures; coordinates, integrates, and/or prioritizes tasks based on circumstances, assessment of critical issues, supervisor input, and established procedures." - Scope and Effect: maybe under Responsibilities: "Leasing Agents are key employees in the management and operation of properties; work affects residents, Agency profitability, community groups, and support agencies; successful accomplishment enhances Agency’s image and ability to meet mission." - Personal Contacts: maybe under Responsibilities: "Personal contacts are mostly with residents, prospective residents, coworkers, and outside service agencies; purposes include obtaining/providing information, planning/coordinating, advising, motivating, influencing, justifying, defending, negotiating, resolving matters." - Physical Requirements: could be under Responsibilities? Not exactly duty but could be under Requirements? Could be under Requirements as "Physical Requirements: Must be able to ..." but that's not education/experience. Could be under Requirements as a bullet. - Work Environment: maybe under Responsibilities? Not duty. Could be under Requirements as "Work Environment: ..." - Other Requirements: "Must possess a valid State of North Carolina or