Project Administrator

We need to output HTML fragment with headings

for sections: About the role? Actually the posting has "Position Summary", "Responsibilities", "Qualifications", "Skills Preferred". Also there is a note about salary range and benefits. According to rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map sections accordingly. We have Position Summary (maybe "About the role"). Responsibilities. Qualifications. Skills Preferred (maybe "Skills"). Also there is a note about salary range and benefits: "Note: The salary range is $$55 to $75k based on education and experience. This is in addition to a generous benefits package and bonus structure." So we have Pay and Benefits sections. Should we include Schedule? Not present. So we include Pay and Benefits sections only if posting actually states them. It does state salary range and benefits package. So we include Pay and Benefits. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, etc. Also remove "We are a Affirmative Action/Equal Opportunity Employer..." and the note about Know Your Rights. Also remove "Skills Preferred" list formatting? We need to convert list items to

• . The "Skills Preferred" includes lines like "00 - Project Management00 - Problem Solving00 - PlanGrid00 - ESTIMATING00 - Budgeting / Cost Management00 - Blue Print Comprehension". That seems weird formatting: likely each skill separated by "00 -". We need to preserve all substantive information; we should not invent or summarize away detail. So we need to parse that line into separate items. The line: "Skills Preferred 00 - Project Management00 - Problem Solving00 - PlanGrid00 - ESTIMATING00 - Budgeting / Cost Management00 - Blue Print Comprehension". Probably each skill is prefixed by "00 -". So we can split on "00 -" and ignore empty first. So items: Project Management, Problem Solving, PlanGrid, ESTIMATING, Budgeting / Cost Management, Blue Print Comprehension. Also there is "Behaviors Preferred" list after that: "Team Player: Works well as a member of a groupEnthusiastic: Shows intense and eager enjoyment and interestDetail Oriented: Capable of carrying out a given task with all details necessary to get the task done wellDedicated: Devoted to a task or purpose with loyalty or integrity". This seems like behaviors. Should we include under Skills? Possibly separate section? The rules only list certain headings; but we could include under Skills or maybe create a separate section? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says "include a section ONLY when the posting has real, specific content for it". It gives examples but not exhaustive. However we should prefer a few substantive sections over many thin ones. Could combine Behaviors under Skills or maybe under Qualifications? But Qualifications already covers experience/education. Behaviors are separate. Might be better to include a "Behaviors" section? Not in examples but could be okay. However to keep few sections, we could incorporate behaviors into Skills section as bullet points. But they are not skills; they are behaviors. Might be okay to have a separate "Behaviors" heading? The instruction didn't forbid, but said use those examples. Safer to stick to given headings. Could place behaviors under Skills as bullet points, but label them? Might be confusing. Perhaps we can include a "Behaviors" section with

  Behaviors

  . Since it's specific content. The instruction didn't forbid other headings; it just gave examples. I'd include Behaviors. Now we need to output only HTML fragment, no /, no markdown fences. We need to preserve all substantive information from Responsibilities, Qualifications, etc. Also include the Position Summary as About the role. Let's extract Position Summary paragraph: "The Project Administrator will be a key figure in facilitating efficient project operations, maintaining effective communication channels, and ensuring the overall success of our projects. This role requires a detail-oriented individual with excellent organizational skills and a proactive approach to problem-solving." We'll put that in

  under

  About the role

  . Responsibilities: a long list. We need to convert each bullet (separated by line breaks) into
  • . The responsibilities are given as sentences separated by line breaks? In the text they are separated by line breaks but not bullet points. We'll treat each sentence as a list item. Let's list responsibilities: - Estimating Support: Establish and manage temporary holding folders for incoming potential bids, ensuring bid documents are correctly categorized and distributed. - Create dedicated bidding folders for each project, effectively organizing bidding files in accordance with project specifications. - Initiate PlanGrid projects and OST bids for respective projects, ensuring accurate and efficient project setup. - Upload drawing sheets to relevant platforms and coordinate the procurement of physical copies of drawings. - Project Manager Support: Facilitate the routing of RFIs, Submittals, Shop Drawings, Schedules, and other project-related documents, incorporating markups into designated drawing sheets. - Maintain the RFI Log by updating information promptly and accurately. - Issue and document EWA (Extra Work Authorization) numbers for designated projects, maintaining thorough email documentation for directed extra work. - Collaborate with the team to price EWAs, inputting data into the system, and ensuring timely completion, including sub-tickets. - Input priced Change Order Requests (CORs) into the system, supported by accurate backup documentation; create approved field copies for project foremen's reference. - Assemble COR customer pending logs using COINs exported reports and a predefined spreadsheet template, distributing to the projects PM by the established deadline. - Utilize PlanGrid and OneNote to overlay new drawing sets for awarded projects, ensuring updated information is accessible to all stakeholders. - Update project cost codes within COINs as needed. - Coordinate Hold Harmless Agreements (HHAs) by communicating requirements to subcontractors, verifying received documents, and managing the approval process. - Construction Manager | Field Support: Collaborate with relevant teams for verification of employment, direct deposit, and wage changes. - Assist with the completion of weekly checklists and envelope stuffing. - Maintain accurate employee information, certifications, and training records using the UKG system. - Admin Support: Provide general administrative support to the team as required. - Future Tasks: Collaborate in assembling project submittal packages for newly awarded projects. - Create project submittal transmittals for attic stock and project samples, ensuring proper labeling and distribution. - Compile paint shop drawings using OST software/functions for customer and internal use. - Create and manage AJ Meeting Minutes for specified projects' weekly internal meetings. - Update Project Status Reports "Hotlist" for specific projects. We need to keep all that. Qualifications: list of bullet points. We'll convert each line to
  • . Qualifications lines: - Experience & Education Actually the heading "Experience & Education" then list. But we can treat each bullet after that as list items. List: - Proven experience as a Project Administrator, Project Coordinator, or in a similar role within the construction or related industry. - Familiarity with project management principles, methodologies, and documentation processes. - Excellent organizational skills with meticulous attention to detail. - Exceptional communication skills, both written and verbal, to effectively collaborate with cross-functional teams, subcontractors, and clients. - Strong problem-solving abilities with a proactive and solution-oriented mindset. - Ability to prioritize tasks and manage multiple projects simultaneously, meeting deadlines consistently. - Proficiency in Microsoft Office Suite (Word, Excel, PowerPoint, Outlook). - High degree of integrity, professionalism, and discretion when handling sensitive information. - Strong interpersonal skills with the ability to foster positive working relationships with team members and stakeholders. - Adaptability to evolving project needs and a willingness to take on new challenges. - A commitment to maintaining accurate records and documentation throughout projects. - Previous experience in the construction industry is a plus. Also there is a sentence: "The above describes the essential content of and requirements for proficient performance in the position and is not meant to be all-inclusive." That's boilerplate? Might be considered generic; but it's substantive? It's a disclaimer. Might be considered boilerplate; but it's not EEO. It's a generic statement. Might be okay to keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not exactly those; it's a description of the content. Might be okay to keep as part of Qualifications? It's not a requirement. Could be considered filler. Safer to omit? It's not a requirement but it's describing the content. I'd keep it as a paragraph under Qualifications maybe. But we need to preserve ALL substantive information; not invent or summarize away detail. This line is substantive? It says the above describes essential content and is not all-inclusive. That's meta. Might be considered boilerplate but not explicitly listed. I'd keep it as a

    after the list. Now Skills Preferred: we have list of skills and behaviors. We'll create

    Skills

    with
    • for each skill. Skills list: Project Management, Problem Solving, PlanGrid, ESTIMATING, Budgeting / Cost Management, Blue Print Comprehension. Behaviors: we could either include under Skills or separate

      Behaviors

      . Let's do separate Behaviors. Behaviors list: - Team Player: Works well as a member of a group - Enthusiastic: Shows intense and eager enjoyment and interest - Detail Oriented: Capable of carrying out a given task with all details necessary to get the task done well - Dedicated: Devoted to a task or purpose with loyalty or integrity Now Pay: we have salary range: "$$55 to $75k based on education and experience." The double dollar sign maybe a typo; we should preserve as "$55 to $75k based on education and experience." Actually it's "$$55 to $75k". We'll keep exactly as given? Probably preserve "$$55 to $75k based on education and experience." We'll output that in a

      under

      Pay

      . Benefits: "This is in addition to a generous benefits package and bonus structure." We'll put that under

      Benefits

      as a

      . Now we need to ensure we don't include empty sections. Now produce HTML:

      About the role

      The Project Administrator will be a key figure in facilitating efficient project operations, maintaining effective communication channels, and ensuring the overall success of our projects. This role requires a detail-oriented individual with excellent organizational skills and a proactive approach to problem-solving.

      Responsibilities

      • Estimating Support: Establish and manage temporary holding folders for incoming potential bids, ensuring bid documents are correctly categorized and distributed.
      • Create dedicated bidding folders for each project, effectively organizing bidding files in accordance with project specifications.
      • Initiate PlanGrid projects and OST bids for respective projects, ensuring accurate and efficient project setup.
      • Upload drawing sheets to relevant platforms and coordinate the procurement of physical copies of drawings.
      • Project Manager Support: Facilitate the routing of RFIs, Submittals, Shop Drawings, Schedules, and other project-related documents, incorporating markups into designated drawing sheets.
      • Maintain the RFI Log by updating information promptly and accurately.
      • Issue and document EWA (Extra Work Authorization) numbers for designated projects, maintaining thorough email documentation for directed extra work.
      • Collaborate with the team to