Facilities Management Administrator

,

,

• . No divs, no classes, no inline styles, no
  . Must preserve all original content word-for-word. So we need to parse the raw text and wrap sections accordingly. We need to identify sections: "Business Unit / Division:", "Job Type Classification:", "Location - Town / City:", "About Us:", "Duties & Responsibilities:", "Skills and Competencies:", "Qualifications:". We need to keep the content exactly as given, but we can wrap each line? The instruction: Use

  for introductory paragraphs and general text. Use

  for section headers. Use

  • for list items (duties, requirements, qualifications, skills). So we need to detect list items within sections like Duties & Responsibilities (which is a block of sentences separated by periods? Actually it's paragraphs with headings inside? The Duties & Responsibilities section contains subheadings like "Financial Administration and Control", "Supplier and Contract Administration", etc. Those are not list items but could be considered headings? The instruction says use

    for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we could treat each subheading under Duties & Responsibilities as

    maybe? But they said use

    for section headers like Responsibilities etc. The Duties & Responsibilities is a section header; we could wrap that in

    . Then inside we have bullet-like paragraphs? Actually the text: "Financial Administration and Control Ensure compliance..." It's a sentence where the heading is bold? In raw text it's "Financial Administration and Control Ensure compliance...". There's no punctuation separating heading from content. It seems they intend each line like "Financial Administration and Control Ensure compliance..." as a paragraph. But we could treat each sentence as a

    . However they want list items for duties, requirements, qualifications, skills. The duties are not in bullet list format; they are sentences. But we could still wrap each duty sentence in

    inside a

    . However the instruction: "Use
    • for list items (duties, requirements, qualifications, skills)". So we need to convert the duties section into a list. Similarly skills and competencies and qualifications. Thus we need to parse the raw text and produce HTML with appropriate tags, preserving content exactly. We need to decide how to split into list items. For Duties & Responsibilities, the raw text after that heading includes multiple sentences each starting with a capitalized phrase (like "Financial Administration and Control Ensure compliance..."). There's no clear delimiter besides maybe a period after each sentence? Actually each "heading" ends before the next capitalized phrase. Eg: "Financial Administration and Control Ensure compliance with all Tsebo financial policies, procedures, and delegated authority requirements. Process supplier invoices accurately and within required deadlines. Monitor purchase orders and track site expenditure against budget. Verify completed services and supporting documentation before invoice submission. Perform monthly supplier account reconciliations and resolve discrepancies. Maintain accurate financial records and filing systems. Support audits through accurate record management and document availability. Assist with monthly reporting and expenditure analysis." That's a block of sentences. Then next heading: "Supplier and Contract Administration Manage supplier onboarding documentation and records. Maintain supplier databases and compliance documentation. Liaise with suppliers regarding invoicing, contract requirements, and service documentation. Track outstanding documentation and ensure compliance with service agreements. Support contract administration activities and maintain accurate records." etc. Thus we could treat each heading+its sentences as a list item? But the instruction says list items for duties, requirements, qualifications, skills. Could be each bullet point is a sentence? However the raw text does not have bullet characters. We could still wrap each sentence in
    • . That would preserve content word-for-word (just adding tags). That seems acceptable. Similarly for Skills and Competencies: it's a line: "Financial administration and invoice processing. CAFM system administration. Microsoft Excel reporting and data management. Supplier management and document control. Records management. Report writing. Customer service administration. Budget tracking and expenditure monitoring. Data accuracy and quality control". That's a list of phrases separated by periods. We could split by period and space? But we need to preserve content exactly; we could keep the whole block as a

      but then not using

      • . However instruction says use
        • for list items (duties, requirements, qualifications, skills). So we need to make a list. We could split by period and space, each item ending with a period. But the original text includes periods after each item except maybe last? It ends with "Data accuracy and quality control" without a period? Actually ends with "Data accuracy and quality control". No period. So we need to be careful. Qualifications: includes multiple sentences: "Qualifications Grade 12 / Matric Diploma in Administration, Finance, Accounting, Bookkeeping, Facilities Management, or a related field. Additional facilities management or customer service certifications Proficient in Microsoft Office Suite (Excel, Word, Outlook, PowerPoint). Experience using CAFM, ERP, or facilities management systems. Experience Minimum 3 years' administrative experience within Facilities Management, Property Management, Business Support Services, or a related environment. Experience processing supplier invoices and maintaining financial records. Experience working with multiple stakeholders and service providers." Again we could split by period. But we must preserve all original content word-for-word. If we split and rejoin with
        • tags, we are not altering the text inside each
        • . We just need to ensure we don't lose any punctuation or add extra spaces. We can split by ". " (period space) and then each part plus the period (except maybe last). But we need to keep the period inside the
        • . So we can keep each sentence as is, including its trailing period. For the last sentence that may not have a period, we keep it as is. Thus algorithm: For each section that should be a list, we take the raw text after the heading up to next heading or end. Then we split by ". " (period+space). For each part, if it does not already end with ".", we add "."? Actually the split removes the delimiter. So we need to add back the period for all but possibly the last if original didn't have period. Simpler: we can just replace ". " with ".
        • " and wrap with
          • and
          . But need to handle the final period. Better: we can wrap the whole block in
          • and replace ". " with ".
          • " and then ensure closing
          . If the block ends with a period, we will have an extra empty
        • at end? Let's test: Suppose text: "A. B. C." Replace ". " with ".
        • " yields "A.
        • B.
        • C." Then we wrap:
          • A.
          • B.
          • C.
          ? Actually after replacement we have "A.
        • B.
        • C." Need to add closing
        . So final:
        • A.
        • B.
        • C.
        . Works if ends with period. If ends without period, e.g., "A. B. C" (no period after C). Replace ". " yields "A.
      • B.
      • C". Then wrap:
        • A.
        • B.
        • C
        . That's missing period after C, which matches original. Good. Thus we can apply this transformation to the duties, skills, qualifications sections. For About Us: it's a paragraph(s). We'll wrap in

        . Also we have headings like "Business Unit / Division:", "Job Type Classification:", "Location - Town / City:" these are not section headers per the list but we could treat them as

        with bold? But we must preserve content. Could wrap each line in

        . Or we could treat them as

        as well. Simplify: We'll output each line as

        except for sections we convert to lists and headings we convert to

        . The headings we know: "About Us:", "Duties & Responsibilities:", "Skills and Competencies:", "Qualifications:". Also maybe "Business Unit / Division:" etc could be

        . Thus final HTML:

        Business Unit / Division: Tsebo Facilities Solutions

        But note the raw text includes line breaks. We need to preserve line breaks? The instruction: preserve ALL original content word-for-word. If we replace line breaks with nothing, we lose them. However HTML collapses whitespace; but we could keep line breaks inside

        as they are; they will be rendered as whitespace but that's okay. We should keep the line breaks exactly as they appear in the raw text. The raw text given includes line breaks after each label. We need to keep them. Thus we need to output the exact same characters, just wrapped in tags. So we need to keep line breaks. Simplify: We'll output the raw text but replace section headings with

        tags and wrap list sections accordingly, while preserving line breaks and other text. Thus we need to parse the raw text string. Let's copy the raw text exactly: Business Unit / Division: Tsebo Facilities Solutions Job Type Classification: Full Time Location - Town / City: Johannesburg About Us: Tsebo Facilities Solutions is looking for a Facilities Management Administrator to provide effective and efficient administrative, financial, and customer support services within the Facilities Management environment. The role is responsible for ensuring accurate financial administration, supplier management, document control, customer service support, and operational coordination to support service delivery excellence and enhance client satisfaction in accordance with contractual obligations and Tsebo standards As a leading African Integrated Workplace Management Solutions Provider, Tsebo Solutions Group offers clients reduced costs, risk and complexities together with increased quality, efficiency and productivity. We specialise in Catering, Facilities Management, Cleaning and Hygiene, Pest Control, Protection, Energy, Procurement, Workspace Design, Engineering, Remote Camps, and more. Developing our people – the heart of Tsebo – is the foundation of our purpose. The result is a knowledgeable workforce that is in touch with every nuance of our clients’ needs. DOWNLOAD OUR ONE-PAGER to find out more about who we are in a nutshell. Duties & Responsibilities: Financial Administration and Control Ensure compliance with all Tsebo financial policies, procedures, and delegated authority requirements. Process supplier invoices accurately and within required deadlines. Monitor purchase orders and track site expenditure against budget. Verify completed services and supporting documentation before invoice submission. Perform monthly supplier account reconciliations and resolve discrepancies. Maintain accurate financial records and filing systems. Support audits through accurate record management and document availability. Assist with monthly reporting and expenditure analysis. Supplier and Contract Administration Manage supplier onboarding documentation and records. Maintain supplier databases and compliance documentation. Liaise with suppliers regarding invoicing, contract requirements, and service documentation. Track outstanding documentation and ensure compliance with service agreements. Support contract administration activities and maintain accurate records. Operational Administration Provide administrative support to the Facilities Management team. Manage correspondence, incoming communications, and document control processes. Maintain CAFM system records and ensure data accuracy. Generate reports and administrative documentation as required. Coordinate meeting arrangements, schedules, and operational records. Support implementation of operational processes and continuous improvement initiatives. Customer Service and Stakeholder Management Deliver professional and responsive support to clients and stakeholders. Address customer enquiries and escalate unresolved issues appropriately. Monitor customer service requests and ensure timely resolution. Assist in conducting customer satisfaction surveys and feedback analysis. Build positive working relationships with clients, suppliers, and internal teams. Promote a customer-centric service culture across the site. Compliance, Governance and Systems Management Ensure compliance with company policies, health and safety requirements, and contractual obligations. Maintain confidentiality and safeguard sensitive information. Support accurate management of CAFM and related systems. Ensure all documentation is retained according to company standards. Contribute to risk management and compliance monitoring activities. Skills and Competencies: Financial administration and invoice processing. CAFM system administration. Microsoft Excel reporting and data management. Supplier management and document control. Records management. Report writing. Customer service administration. Budget tracking and expenditure monitoring. Data accuracy and quality control Qualifications: Qualifications Grade 12 / Matric Diploma in Administration, Finance, Accounting, Bookkeeping, Facilities Management, or a related field. Additional facilities management or customer service certifications Proficient in Microsoft Office Suite (Excel, Word, Outlook, PowerPoint). Experience using CAFM, ERP, or facilities management systems. Experience Minimum 3 years' administrative experience within Facilities Management, Property Management, Business Support Services, or a related environment. Experience processing supplier invoices and maintaining financial records. Experience working with multiple stakeholders and service providers. We need to preserve line breaks exactly. Thus we will produce HTML where we keep the line breaks as they are inside tags. Approach: We'll replace each heading line with

        Heading

        and keep the line break after it. For sections that should be lists, we will replace the block after heading until next heading or end with
        • ...
        using the transformation. We must ensure we don't double count headings. Let's implement manually. We'll process line by line. Lines: 1: "Business Unit / Division:" 2: "Tsebo Facilities Solutions" 3: (empty line) 4: "Job Type Classification:" 5: "Full Time" 6: (empty line) 7: "Location - Town / City:" 8: "Johannesburg" 9: (empty line) 10: "About Us:" 11: "Tsebo Facilities Solutions is looking for a Facilities Management Administrator to provide effective and efficient administrative, financial, and customer support services within the Facilities Management environment. The role is responsible for ensuring accurate financial administration, supplier management, document control, customer service support, and operational coordination to support service delivery excellence and enhance client satisfaction in accordance with contractual obligations and Tsebo standards As a leading African Integrated Workplace Management Solutions Provider, Tsebo Solutions Group offers clients reduced costs, risk and complexities together with increased quality, efficiency and productivity. We specialise in Catering, Facilities Management, Cleaning and Hygiene, Pest Control, Protection, Energy, Procurement, Workspace Design, Engineering, Remote Camps, and more. Developing our people – the heart of Tsebo – is the foundation of our purpose. The result is a knowledgeable workforce that is in touch with every nuance of our clients’ needs. DOWNLOAD OUR ONE-PAGER to find out more about who we are in a nutshell." 12: (empty line) 13: "Duties & Responsibilities:" 14: (the long block) ... We need to capture until next heading "Skills and Competencies:" line. Let's extract the duties block lines from line 14 up to before line that starts "Skills and Competencies:". Similarly skills block from after that heading until before "Qualifications:" line. Qualifications block from after that heading until end. We'll need to preserve line breaks inside those blocks as they appear (they are paragraphs with sentences separated by spaces, not line breaks). Actually the duties block is all on one line? In the raw text, after "Duties & Responsibilities:" there is a line break then the block of sentences continues without line breaks until the next heading. So it's a single line (though long). We'll keep that line as is. Thus we can treat the block as a single string (the line after heading). We'll apply the list transformation to that line. Similarly skills block is a single line. Qualifications block is also a single line (maybe multiple sentences but no line breaks). Thus we can process. Now produce HTML. We'll start with

        for lines before first heading? Actually we will output each line accordingly. Let's construct:

        Business Unit / Division: Tsebo Facilities Solutions

        But note there is an empty line after that line. We'll preserve empty lines as
        ? Actually empty line could be represented as
        but that adds empty paragraph. Might be okay. But we could just keep the line break inside

        tags? The line break is between lines; we could have

        Business Unit / Division: Tsebo Facilities Solutions

        then an empty line => we could output
        . However the instruction: If text has no clear sections, just wrap paragraphs in

        tags. Empty line is a paragraph with no content; we could output

        . That's fine. But maybe easier: we just output the raw text with headings replaced by

        and list sections replaced by

        • ...

        , and wrap everything else in

        tags preserving line breaks. However we need to avoid wrapping headings inside

        . So we need to differentiate. Simpler: We'll produce HTML where we keep the original line breaks, and we wrap each line (excluding empty lines) in

        unless it's a heading we convert to

        or it's part of a list section we convert to

        • . But list sections are multiple lines? Actually they are single line after heading; we could replace that line with the list markup. Thus algorithm: For each line: - If line matches exactly a known heading (including trailing colon), we output

          line

          . - Else if line is empty, we output
          (or maybe just a blank line? but we need to output something; we can output
          ). - Else if we are inside a list section (i.e., after a heading that indicates list, until next heading), we need to process the line as list content. But we only have one line per section; we could just when we see the heading "Duties & Responsibilities:", we set a flag to process next line as list, then after outputting the list we reset flag. Similarly for skills and qualifications. Thus we need to know when we encounter those headings. Let's implement manually in reasoning. We'll produce output sequentially. Line1: "Business Unit / Division:" -> not a list heading, output

          Business Unit / Division:

          ? But the heading ends with colon; we could keep as

          . However we might want to keep it as

          not

          . That's fine. Line2: "T