Project Coordinator (Mission Critical/Data Center)
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate.
We need to parse the job description.
Content:
- Opening: "Job Description This Opportunity kW MCE is seeking a Project Coordinator for the following kW offices: Tempe, AZ; Troy, NY; Milwaukee, WI; Houston, TX." This is location info. Could be part of About the role? Might be considered "About the role" or maybe "Location". Since we only have allowed headings, we could put location in About the role paragraph.
- "The Project Coordinator is responsible for supporting the Project Manager and project teams with administrative duties throughout the project lifecycle. They will take a proactive role assisting the Project Manager and project teams in moving the project forward and enhancing communication with the project team and Client and promoting and facilitating integration on the project."
- Then "Your Impact" bullet list: many responsibilities.
- Then "Who You Are" with Required Qualifications list.
- Then "WSP Benefits:" paragraph describing benefits.
- Then "Compensation: Expected Hourly (all locations): $29.00-$35.00" plus explanation.
- Then "About WSP" paragraph about company.
- Then "WSP provides a flexible and agile workplace model..." duplicate benefits.
- Then EEO etc boilerplate to remove.
We need to produce sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for About the role (overview). Responsibilities (the bullet list under Your Impact). Requirements (maybe the "Who You Are Required Qualifications" list). Qualifications maybe overlapping with Requirements? Could treat Requirements as the list of required qualifications (high school diploma, 5+ years experience, etc). Qualifications could be additional preferred qualifications? But we have only one list; maybe we split: Requirements = mandatory (high school diploma or GED, 5+ years experience, deadline oriented, etc). Qualifications = maybe none? But we need to include a section only if posting has real specific content. We could combine Requirements and Qualifications into one? But headings are separate; we could put Requirements as the list, and Qualifications maybe empty -> we should not include Qualifications heading if no specific content. Similarly Skills: we have MS Office, Bluebeam, Smartsheet, cloud platforms, typing skills, self-motivated, etc. Those could go under Skills.
Benefits: we have WSP Benefits paragraph.
Pay: we have compensation range.
Schedule: not mentioned; no schedule info, so we should NOT include Schedule section.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay.
We need to ensure we don't include filler like "commensurate with experience". Not present.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
Let's extract details precisely.
About the role: Should include location info and general description.
Paragraph: "kW MCE is seeking a Project Coordinator for the following kW offices: Tempe, AZ; Troy, NY; Milwaukee, WI; Houston, TX. The Project Coordinator is responsible for supporting the Project Manager and project teams with administrative duties throughout the project lifecycle. They will take a proactive role assisting the Project Manager and project teams in moving the project forward and enhancing communication with the project team and Client and promoting and facilitating integration on the project."
That's about the role.
Responsibilities: list from "Your Impact" bullet points.
Let's copy each bullet:
- Coordinate with the project team during the proposal process to ensure all deadlines are met and reviews have been completed.
- Support the project manager with internal communications and follow-up
- Maintaining project calendar including project deliverables, QC deadlines and publishing to project team.
- Assist in scheduling internal team meetings, project kick-offs, design reviews, etc
- Assist in reviewing project financial reports and communicate issues to project team
- Create and maintain project Smart Sheets and document file storage
- Assist in tracking invoices and project payments.
- Assist project manager with reviewing deliverables during project deadlines. Ensure projects are meeting all internal compliance requirements
- Assist the project team in receiving, filing, distributing, processing, tracking due dates and responding to RFI’s, submittals and responses.
- Provide support for editing and formatting of specifications.
- Assist in preparation of any materials required for project pursuit.
- Assist in processing contracts and sub-consultant contracts.
- Attend project, department and team meetings and take meeting notes. Distribute meeting notes internal and externally as required.
- Assist in generating project financial management reports.
- Assist in tracking scope changes and updating project budgets accordingly.
- Create and maintain project document file storage within the standard project directory structure.
Note some duplicates: "Create and maintain project Smart Sheets and document file storage" and later "Create and maintain project document file storage within the standard project directory structure." Both are separate but similar; we keep both as separate list items.
Requirements: list from "Who You Are Required Qualifications":
- High School Diploma or GED Required
- 5+ years experience
- Deadline oriented, ability to track and maintain and meet multiple concurrent deadlines.
- Excellent verbal, written communication and program solving skills. (Probably "problem solving")
- MS Office applications, including Word, Excel, Outlook, Power Point and others.
- Familiarity with Bluebeam is an advantage.
- Familiarity with Smartsheet is an advantage.
- Working knowledge of cloud-based file sharing platforms such as, SharePoint, ShareFile, Newforma, Dropbox, Box, etc. is an advantage.
- Strong computer and typing skills
- Self-motivated and flexible to take on new tasks and assist teams.
- Strong willingness & eager to learn
Note: Some of these could be considered skills; but we have separate Skills section. We could put the mandatory ones (HS diploma, 5+ years experience, deadline oriented, excellent communication, strong computer/typing skills, self-motivated, willingness to learn) as Requirements, and the advantageous ones (Bluebeam, Smartsheet, cloud platforms) as Skills. However the instruction: Use headings for Requirements, Qualifications, Skills. We have to decide what goes where. Since we have both Required Qualifications and also list of advantages, we could treat Requirements as the mandatory items (HS diploma, 5+ years experience, deadline oriented, excellent communication, strong computer/typing skills, self-motivated, willingness to learn). Qualifications could be the advantageous ones? But Qualifications heading usually for qualifications like education, certifications. However we already used education in Requirements. Could treat Qualifications as the advantageous ones (Bluebeam, Smartsheet, cloud platforms). Skills could be MS Office applications, etc. But we need to avoid duplication.
Better: Use Requirements for the mandatory qualifications (HS diploma, 5+ years experience, deadline oriented, excellent communication, strong computer/typing skills, self-motivated, willingness to learn). Use Skills for the technical skills: MS Office applications, Bluebeam, Smartsheet, cloud platforms, etc. Qualifications maybe not needed if no distinct content; but we have "Required Qualifications" heading in original; we could treat that as Qualifications section. However we already used Requirements for mandatory; but we could swap: Requirements = the list under "Who You Are Required Qualifications" (all items). Skills = maybe none? But we have MS Office etc which are skills. Could put them under Skills. Qualifications maybe we could omit if we already used Requirements for the list. But we need to follow the instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all; we include only those with real content. So we can include Requirements (the list of required qualifications) and Skills (the technical skills). Qualifications maybe we can omit if we feel it's redundant. However the original had "Required Qualifications" as a heading; we could map that to Qualifications section. Then Requirements could be something else like "Deadline oriented, ability to track..." but that's also part of qualifications. Hmm.
Let's think: The original sections: "Your Impact" (responsibilities), "Who You Are" (then "Required Qualifications"). So we could map:
- About the role: introductory paragraph.
- Responsibilities: Your Impact list.
- Requirements: maybe the mandatory items (HS diploma, 5+ years experience, deadline oriented, excellent communication, strong computer/typing skills, self-motivated, willingness to learn). But these are also part of Required Qualifications.
- Qualifications: maybe the advantageous items (Bluebeam, Smartsheet, cloud platforms). But they are also qualifications.
- Skills: MS Office applications, etc.
But we risk splitting the same list artificially. However the instruction: "Prefer a few substantive sections over many thin ones." So we should avoid too many thin sections. Better to combine similar items into broader sections.
Thus we could have:
- About the role (intro)
- Responsibilities (Your Impact)
- Requirements & Qualifications (combined) maybe as Requirements heading only, containing all items from "Who You Are Required Qualifications".
- Skills (maybe MS Office etc) but those are already in the list; we could keep them under Requirements as well, making a single Requirements section.
But we need to decide if we need Skills separate. Since we have MS Office etc which are skills, but they are also qualifications. Could put them under Requirements.
Thus we could have sections: About the role, Responsibilities, Requirements, Benefits, Pay.
We would omit Qualifications and Skills headings to avoid thin sections.
But the instruction says we can use those headings if we have content. It's not mandatory to use all. So we can omit Qualifications and Skills if we feel they'd be thin or duplicate.
Thus final sections: About the role, Responsibilities, Requirements, Benefits, Pay.
Check if we have any content for Schedule: none, so omit.
Now we need to ensure we preserve all substantive information. Let's list all substantive info from posting:
- Location offices: Tempe, AZ; Troy, NY; Milwaukee, WI; Houston, TX.
- Role description: supporting PM, administrative duties, proactive role, moving project forward, enhancing communication, promoting integration.
- Responsibilities list (as above).
- Required qualifications list (as above).
- Benefits description: medical, dental, vision, disability, life; retirement savings; paid sick leave; paid vacation (or other personal time); paid parental leave; paid time off for bereavement, voting, naturalization.
- Compensation: Expected Hourly (all locations): $29.00-$35.00, plus note about good faith belief, etc.
- About WSP: description of WSP USA, 15000 employees, 300 offices, markets, etc.
- Additional benefits statement duplicate: flexible workplace model, comprehensive suite benefits (medical, dental, vision, disability, life, retirement savings). This is duplicate of benefits; we should not repeat duplicate lines. We need to preserve ALL substantive information but remove duplicated lines. So we should include benefits only once, combining unique points.
Thus we need to merge benefits paragraphs: first benefits list includes medical, dental, vision, disability, life; retirement savings; paid sick leave; paid vacation (or other personal time); paid parental leave; paid time off for bereavement, voting, naturalization. Second benefits paragraph: "WSP provides a flexible and agile workplace model while meeting client needs. Employees are also afforded a comprehensive suite of benefits including medical, dental, vision, disability, life, and retirement savings focused on providing health and financial stability throughout the employee’s career." This adds flexible and agile workplace model, and repeats benefits. So we should include flexible and agile workplace model as part of benefits description, and not repeat the benefit list.
Thus benefits section should include: comprehensive suite of benefits (medical, dental,
- for any list of duties/requirements/benefits. Use
for prose. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract details precisely. About the role: Should include location info and general description. Paragraph: "kW MCE is seeking a Project Coordinator for the following kW offices: Tempe, AZ; Troy, NY; Milwaukee, WI; Houston, TX. The Project Coordinator is responsible for supporting the Project Manager and project teams with administrative duties throughout the project lifecycle. They will take a proactive role assisting the Project Manager and project teams in moving the project forward and enhancing communication with the project team and Client and promoting and facilitating integration on the project." That's about the role. Responsibilities: list from "Your Impact" bullet points. Let's copy each bullet: - Coordinate with the project team during the proposal process to ensure all deadlines are met and reviews have been completed. - Support the project manager with internal communications and follow-up - Maintaining project calendar including project deliverables, QC deadlines and publishing to project team. - Assist in scheduling internal team meetings, project kick-offs, design reviews, etc - Assist in reviewing project financial reports and communicate issues to project team - Create and maintain project Smart Sheets and document file storage - Assist in tracking invoices and project payments. - Assist project manager with reviewing deliverables during project deadlines. Ensure projects are meeting all internal compliance requirements - Assist the project team in receiving, filing, distributing, processing, tracking due dates and responding to RFI’s, submittals and responses. - Provide support for editing and formatting of specifications. - Assist in preparation of any materials required for project pursuit. - Assist in processing contracts and sub-consultant contracts. - Attend project, department and team meetings and take meeting notes. Distribute meeting notes internal and externally as required. - Assist in generating project financial management reports. - Assist in tracking scope changes and updating project budgets accordingly. - Create and maintain project document file storage within the standard project directory structure. Note some duplicates: "Create and maintain project Smart Sheets and document file storage" and later "Create and maintain project document file storage within the standard project directory structure." Both are separate but similar; we keep both as separate list items. Requirements: list from "Who You Are Required Qualifications": - High School Diploma or GED Required - 5+ years experience - Deadline oriented, ability to track and maintain and meet multiple concurrent deadlines. - Excellent verbal, written communication and program solving skills. (Probably "problem solving") - MS Office applications, including Word, Excel, Outlook, Power Point and others. - Familiarity with Bluebeam is an advantage. - Familiarity with Smartsheet is an advantage. - Working knowledge of cloud-based file sharing platforms such as, SharePoint, ShareFile, Newforma, Dropbox, Box, etc. is an advantage. - Strong computer and typing skills - Self-motivated and flexible to take on new tasks and assist teams. - Strong willingness & eager to learn Note: Some of these could be considered skills; but we have separate Skills section. We could put the mandatory ones (HS diploma, 5+ years experience, deadline oriented, excellent communication, strong computer/typing skills, self-motivated, willingness to learn) as Requirements, and the advantageous ones (Bluebeam, Smartsheet, cloud platforms) as Skills. However the instruction: Use headings for Requirements, Qualifications, Skills. We have to decide what goes where. Since we have both Required Qualifications and also list of advantages, we could treat Requirements as the mandatory items (HS diploma, 5+ years experience, deadline oriented, excellent communication, strong computer/typing skills, self-motivated, willingness to learn). Qualifications could be the advantageous ones? But Qualifications heading usually for qualifications like education, certifications. However we already used education in Requirements. Could treat Qualifications as the advantageous ones (Bluebeam, Smartsheet, cloud platforms). Skills could be MS Office applications, etc. But we need to avoid duplication. Better: Use Requirements for the mandatory qualifications (HS diploma, 5+ years experience, deadline oriented, excellent communication, strong computer/typing skills, self-motivated, willingness to learn). Use Skills for the technical skills: MS Office applications, Bluebeam, Smartsheet, cloud platforms, etc. Qualifications maybe not needed if no distinct content; but we have "Required Qualifications" heading in original; we could treat that as Qualifications section. However we already used Requirements for mandatory; but we could swap: Requirements = the list under "Who You Are Required Qualifications" (all items). Skills = maybe none? But we have MS Office etc which are skills. Could put them under Skills. Qualifications maybe we could omit if we already used Requirements for the list. But we need to follow the instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all; we include only those with real content. So we can include Requirements (the list of required qualifications) and Skills (the technical skills). Qualifications maybe we can omit if we feel it's redundant. However the original had "Required Qualifications" as a heading; we could map that to Qualifications section. Then Requirements could be something else like "Deadline oriented, ability to track..." but that's also part of qualifications. Hmm. Let's think: The original sections: "Your Impact" (responsibilities), "Who You Are" (then "Required Qualifications"). So we could map: - About the role: introductory paragraph. - Responsibilities: Your Impact list. - Requirements: maybe the mandatory items (HS diploma, 5+ years experience, deadline oriented, excellent communication, strong computer/typing skills, self-motivated, willingness to learn). But these are also part of Required Qualifications. - Qualifications: maybe the advantageous items (Bluebeam, Smartsheet, cloud platforms). But they are also qualifications. - Skills: MS Office applications, etc. But we risk splitting the same list artificially. However the instruction: "Prefer a few substantive sections over many thin ones." So we should avoid too many thin sections. Better to combine similar items into broader sections. Thus we could have: - About the role (intro) - Responsibilities (Your Impact) - Requirements & Qualifications (combined) maybe as Requirements heading only, containing all items from "Who You Are Required Qualifications". - Skills (maybe MS Office etc) but those are already in the list; we could keep them under Requirements as well, making a single Requirements section. But we need to decide if we need Skills separate. Since we have MS Office etc which are skills, but they are also qualifications. Could put them under Requirements. Thus we could have sections: About the role, Responsibilities, Requirements, Benefits, Pay. We would omit Qualifications and Skills headings to avoid thin sections. But the instruction says we can use those headings if we have content. It's not mandatory to use all. So we can omit Qualifications and Skills if we feel they'd be thin or duplicate. Thus final sections: About the role, Responsibilities, Requirements, Benefits, Pay. Check if we have any content for Schedule: none, so omit. Now we need to ensure we preserve all substantive information. Let's list all substantive info from posting: - Location offices: Tempe, AZ; Troy, NY; Milwaukee, WI; Houston, TX. - Role description: supporting PM, administrative duties, proactive role, moving project forward, enhancing communication, promoting integration. - Responsibilities list (as above). - Required qualifications list (as above). - Benefits description: medical, dental, vision, disability, life; retirement savings; paid sick leave; paid vacation (or other personal time); paid parental leave; paid time off for bereavement, voting, naturalization. - Compensation: Expected Hourly (all locations): $29.00-$35.00, plus note about good faith belief, etc. - About WSP: description of WSP USA, 15000 employees, 300 offices, markets, etc. - Additional benefits statement duplicate: flexible workplace model, comprehensive suite benefits (medical, dental, vision, disability, life, retirement savings). This is duplicate of benefits; we should not repeat duplicate lines. We need to preserve ALL substantive information but remove duplicated lines. So we should include benefits only once, combining unique points. Thus we need to merge benefits paragraphs: first benefits list includes medical, dental, vision, disability, life; retirement savings; paid sick leave; paid vacation (or other personal time); paid parental leave; paid time off for bereavement, voting, naturalization. Second benefits paragraph: "WSP provides a flexible and agile workplace model while meeting client needs. Employees are also afforded a comprehensive suite of benefits including medical, dental, vision, disability, life, and retirement savings focused on providing health and financial stability throughout the employee’s career." This adds flexible and agile workplace model, and repeats benefits. So we should include flexible and agile workplace model as part of benefits description, and not repeat the benefit list. Thus benefits section should include: comprehensive suite of benefits (medical, dental,