Project Coordinator
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as a heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the job description.
Job Title: Project Coordinator (but we don't repeat as heading). The description includes:
- About the role: The Grid Investment Project Coordinator manages and coordinates utility infrastructure and grid investment projects that support the modernization, reliability, and expansion of electric distribution systems. This role provides comprehensive project coordination, including scheduling, document management, reporting, budget tracking, and stakeholder communication throughout the project lifecycle. Acting as a critical link between project managers, engineering teams, field personnel, contractors, and business stakeholders, the coordinator ensures that projects are delivered safely, on time, within budget, and with complete documentation integrity.
That's the "About the role" content.
- Responsibilities: a long list of bullet-like sentences separated by periods. We need to turn them into
- items.
- Essential Skills: list of bullet-like sentences (starting with "5 to 10 years of experience..." etc). Should be under Skills or Qualifications? The instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content.
We have:
- About the role (we have content)
- Responsibilities (we have content)
- Essential Skills (we have content)
- Additional Skills & Qualifications (we have content)
- Work Environment (some content)
- Job Type & Location (some content)
- Pay And Benefits (we have pay range and benefits list)
- Workplace Type (some content)
- Application Deadline (some content)
- About Actalent (boilerplate? Might be considered company description; but we need to remove EEO/equal-opportunity boilerplate etc. The "About Actalent" includes some description but also EEO statement later. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Actalent" paragraph is not exactly boilerplate but is company description; we might keep it as part of "About the role"? However the instruction says "Prefer a few substantive sections over many thin ones." We could combine About the role and About Actalent into an "About the role" or "About the company"? But the heading list includes "About the role". So we should put the role description under About the role. The company description could be considered extra but maybe we can include it under About the role as well? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the company description if it's substantive. However the heading list does not have "About the company". We could put it under About the role as additional paragraph. Or we could create a section "About the company" but not in allowed headings. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should map content to those headings. If content doesn't fit, we may need to omit or combine.
We have:
- About the role: we have description of role.
- Responsibilities: we have list.
- Skills: we have Essential Skills and Additional Skills & Qualifications (both skill-related). Could combine into Skills section.
- Qualifications: maybe we could put Essential Skills under Qualifications? But we have both Skills and Qualifications sections allowed. We could put Essential Skills under Skills, and Additional Skills & Qualifications under Qualifications? Or combine.
- Benefits: we have benefits list under Pay And Benefits.
- Pay: we have pay range.
- Schedule: we don't have explicit schedule info (like full-time, part-time, shift). There's Work Environment and Workplace Type but not schedule. So we should not create Schedule section because no specific schedule content.
- Requirements: we could put some of the essential skills as requirements? But we already have Skills section. Might be okay to omit Requirements if not distinct.
We need to avoid filler/placeholder text. Ensure we don't include sections with only generic statements like "commensurate with experience". Not present.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out:
- "Application Deadline This position is anticipated to close on Sep 23, 2026." That's application instruction? It's a date; maybe we should drop it as it's application instruction? The instruction says remove application instructions. So drop that line.
- "About Actalent ..." includes EEO statement later: "The company is an equal opportunity employer..." etc. That's EEO boilerplate; we need to remove that. Also the later paragraphs about San Francisco Fair Chance Ordinance, Massachusetts Lie Detector, Use of Artificial Intelligence (AI) etc. Those are legal/EEO boilerplate; remove.
- Also "Job Type & Location This is a Contract position based out of Calera, AL." That's not boilerplate; it's substantive about job type and location. Should we keep? Possibly under About the role or maybe we can incorporate into a short paragraph. Since we don't have a specific heading for Job Type & Location, we could fold into About the role paragraph or maybe a separate
after About the role? But we must not create new headings not in list. So we can add a
after About the role containing that info.
- "Work Environment This position is based onsite in Calera, Alabama. The role operates in a professional office environment..." That's substantive; we could incorporate into About the role or maybe a separate
after About the role.
- "Workplace Type This is a fully onsite position in Calera,AL." Duplicate of work environment; we can drop duplicate.
- "Pay And Benefits The pay range for this position is $40.00 - $45.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors. Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following: ..." That's substantive; we need Pay and Benefits sections.
We need to output HTML fragment with
headings and appropriate content.
Let's decide sections:
- About the role
: include role description, job type/location, work environment maybe.
- Responsibilities
: list of responsibilities as - .
-
Skills
: combine Essential Skills and Additional Skills & Qualifications into a list.
- Benefits
: list of benefits.
- Pay
: pay range.
We should not include Requirements or Qualifications if we already covered skills. But we could also have Qualifications section for things like "5 to 10 years of experience..." but that's skill. However we have both Skills and Qualifications allowed; we could put Essential Skills under Skills, and Additional Skills & Qualifications under Qualifications. But that may be thin. Better to combine into Skills.
We need to avoid duplication: ensure we don't repeat same bullet points.
Let's extract responsibilities list from the text:
Responsibilities section begins after "Responsibilities". The text:
"Collaborate with project managers, engineers, construction managers, and contractors to develop project execution plans, schedules, milestones, and deliverables.Coordinate activities across multiple grid investment projects that support distribution system upgrades, reliability improvements, and infrastructure investments.Serve as the primary point of contact for project teams regarding project status, schedules, documentation, and deliverables.Facilitate project meetings, track action items, and ensure commitments are completed in a timely manner.Manage and maintain all project documentation throughout the project lifecycle, ensuring records are accurate, complete, and accessible.Establish and maintain organized file structures within SharePoint, Teams, network drives, and project management platforms.Maintain version control and ensure project records meet company standards and regulatory requirements.Process, organize, and archive project scopes, design packages, construction drawings, permits, contracts, change requests, financial records, inspection reports, and project closeout documentation.Conduct periodic audits of project documentation to verify compliance with internal standards and external regulatory requirements.Coordinate document review and approval workflows among project stakeholders.Develop and maintain project schedules and milestone tracking tools to monitor progress.Monitor project progress, proactively identify schedule risks and delays, and assess potential impacts.Coordinate project updates and assist leadership with project forecasting and performance reporting.Support project status reviews and provide schedule recovery recommendations when needed.Assist with project budget monitoring, expense tracking, and financial reporting.Track project expenditures and support monthly forecasting and accrual activities.Validate invoices and supporting documentation for accuracy and compliance with contract terms.Coordinate invoice processing and reconciliation activities with contractors and internal teams, including contract administration and change management documentation.Utilize advanced Microsoft Excel to manage project data and performance metrics.Create and maintain budget tracking spreadsheets, cost forecasting models, invoice reconciliation logs, production tracking tools, resource allocation trackers, executive dashboards, and schedule performance metrics.Analyze project data to identify trends, risks, variances, and opportunities for improvement.Develop and support automated reporting and dashboard solutions using formulas, Pivot Tables, Power Query, lookup functions, and data visualization tools.Coordinate personnel, equipment, materials, and contractor resources to support project execution.Assist with procurement activities, vendor coordination, material tracking, and work package readiness.Monitor resource utilization and support workforce planning efforts.Identify project risks and collaborate with project teams to develop mitigation strategies.Support quality assurance processes to ensure project deliverables meet established standards.Assist in managing scope changes, obtaining approvals, and maintaining associated documentation.Ensure compliance with applicable utility standards, procedures, and regulatory requirements.Prepare and distribute project status reports, presentations, and executive summaries.Facilitate effective communication between engineering, communication between engineering, construction, operations, finance, and contractor teams.Communicate project progress, risks, and key decisions to stakeholders in a clear and timely manner.Support leadership with data-driven insights to inform project decision-making."
We need to split into separate items at each period that starts a new sentence (but some sentences have internal periods like "e.g."? Not present). We'll split by "." and trim.
Similarly for Essential Skills:
"5 to 10 years of experience in project coordination, project controls, construction administration, or project management support.Experience supporting utility distribution, transmission, substation, fiber, or grid investment programs.Experience managing project documentation, financial reporting, and contractor coordination.Familiarity with utility capital projects and infrastructure improvement programs.Advanced proficiency in Microsoft Excel, including Pivot Tables
for prose. Do NOT repeat job title as a heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the job description. Job Title: Project Coordinator (but we don't repeat as heading). The description includes: - About the role: The Grid Investment Project Coordinator manages and coordinates utility infrastructure and grid investment projects that support the modernization, reliability, and expansion of electric distribution systems. This role provides comprehensive project coordination, including scheduling, document management, reporting, budget tracking, and stakeholder communication throughout the project lifecycle. Acting as a critical link between project managers, engineering teams, field personnel, contractors, and business stakeholders, the coordinator ensures that projects are delivered safely, on time, within budget, and with complete documentation integrity. That's the "About the role" content. - Responsibilities: a long list of bullet-like sentences separated by periods. We need to turn them into
- items.
- Essential Skills: list of bullet-like sentences (starting with "5 to 10 years of experience..." etc). Should be under Skills or Qualifications? The instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content.
We have:
- About the role (we have content)
- Responsibilities (we have content)
- Essential Skills (we have content)
- Additional Skills & Qualifications (we have content)
- Work Environment (some content)
- Job Type & Location (some content)
- Pay And Benefits (we have pay range and benefits list)
- Workplace Type (some content)
- Application Deadline (some content)
- About Actalent (boilerplate? Might be considered company description; but we need to remove EEO/equal-opportunity boilerplate etc. The "About Actalent" includes some description but also EEO statement later. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Actalent" paragraph is not exactly boilerplate but is company description; we might keep it as part of "About the role"? However the instruction says "Prefer a few substantive sections over many thin ones." We could combine About the role and About Actalent into an "About the role" or "About the company"? But the heading list includes "About the role". So we should put the role description under About the role. The company description could be considered extra but maybe we can include it under About the role as well? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the company description if it's substantive. However the heading list does not have "About the company". We could put it under About the role as additional paragraph. Or we could create a section "About the company" but not in allowed headings. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should map content to those headings. If content doesn't fit, we may need to omit or combine. We have: - About the role: we have description of role. - Responsibilities: we have list. - Skills: we have Essential Skills and Additional Skills & Qualifications (both skill-related). Could combine into Skills section. - Qualifications: maybe we could put Essential Skills under Qualifications? But we have both Skills and Qualifications sections allowed. We could put Essential Skills under Skills, and Additional Skills & Qualifications under Qualifications? Or combine. - Benefits: we have benefits list under Pay And Benefits. - Pay: we have pay range. - Schedule: we don't have explicit schedule info (like full-time, part-time, shift). There's Work Environment and Workplace Type but not schedule. So we should not create Schedule section because no specific schedule content. - Requirements: we could put some of the essential skills as requirements? But we already have Skills section. Might be okay to omit Requirements if not distinct. We need to avoid filler/placeholder text. Ensure we don't include sections with only generic statements like "commensurate with experience". Not present. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out: - "Application Deadline This position is anticipated to close on Sep 23, 2026." That's application instruction? It's a date; maybe we should drop it as it's application instruction? The instruction says remove application instructions. So drop that line. - "About Actalent ..." includes EEO statement later: "The company is an equal opportunity employer..." etc. That's EEO boilerplate; we need to remove that. Also the later paragraphs about San Francisco Fair Chance Ordinance, Massachusetts Lie Detector, Use of Artificial Intelligence (AI) etc. Those are legal/EEO boilerplate; remove. - Also "Job Type & Location This is a Contract position based out of Calera, AL." That's not boilerplate; it's substantive about job type and location. Should we keep? Possibly under About the role or maybe we can incorporate into a short paragraph. Since we don't have a specific heading for Job Type & Location, we could fold into About the role paragraph or maybe a separate
after About the role? But we must not create new headings not in list. So we can add a
after About the role containing that info. - "Work Environment This position is based onsite in Calera, Alabama. The role operates in a professional office environment..." That's substantive; we could incorporate into About the role or maybe a separate
after About the role. - "Workplace Type This is a fully onsite position in Calera,AL." Duplicate of work environment; we can drop duplicate. - "Pay And Benefits The pay range for this position is $40.00 - $45.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors. Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following: ..." That's substantive; we need Pay and Benefits sections. We need to output HTML fragment with
headings and appropriate content. Let's decide sections: -
About the role
: include role description, job type/location, work environment maybe. -Responsibilities
: list of responsibilities as- .
-
Skills
: combine Essential Skills and Additional Skills & Qualifications into a list. -Benefits
: list of benefits. -Pay
: pay range. We should not include Requirements or Qualifications if we already covered skills. But we could also have Qualifications section for things like "5 to 10 years of experience..." but that's skill. However we have both Skills and Qualifications allowed; we could put Essential Skills under Skills, and Additional Skills & Qualifications under Qualifications. But that may be thin. Better to combine into Skills. We need to avoid duplication: ensure we don't repeat same bullet points. Let's extract responsibilities list from the text: Responsibilities section begins after "Responsibilities". The text: "Collaborate with project managers, engineers, construction managers, and contractors to develop project execution plans, schedules, milestones, and deliverables.Coordinate activities across multiple grid investment projects that support distribution system upgrades, reliability improvements, and infrastructure investments.Serve as the primary point of contact for project teams regarding project status, schedules, documentation, and deliverables.Facilitate project meetings, track action items, and ensure commitments are completed in a timely manner.Manage and maintain all project documentation throughout the project lifecycle, ensuring records are accurate, complete, and accessible.Establish and maintain organized file structures within SharePoint, Teams, network drives, and project management platforms.Maintain version control and ensure project records meet company standards and regulatory requirements.Process, organize, and archive project scopes, design packages, construction drawings, permits, contracts, change requests, financial records, inspection reports, and project closeout documentation.Conduct periodic audits of project documentation to verify compliance with internal standards and external regulatory requirements.Coordinate document review and approval workflows among project stakeholders.Develop and maintain project schedules and milestone tracking tools to monitor progress.Monitor project progress, proactively identify schedule risks and delays, and assess potential impacts.Coordinate project updates and assist leadership with project forecasting and performance reporting.Support project status reviews and provide schedule recovery recommendations when needed.Assist with project budget monitoring, expense tracking, and financial reporting.Track project expenditures and support monthly forecasting and accrual activities.Validate invoices and supporting documentation for accuracy and compliance with contract terms.Coordinate invoice processing and reconciliation activities with contractors and internal teams, including contract administration and change management documentation.Utilize advanced Microsoft Excel to manage project data and performance metrics.Create and maintain budget tracking spreadsheets, cost forecasting models, invoice reconciliation logs, production tracking tools, resource allocation trackers, executive dashboards, and schedule performance metrics.Analyze project data to identify trends, risks, variances, and opportunities for improvement.Develop and support automated reporting and dashboard solutions using formulas, Pivot Tables, Power Query, lookup functions, and data visualization tools.Coordinate personnel, equipment, materials, and contractor resources to support project execution.Assist with procurement activities, vendor coordination, material tracking, and work package readiness.Monitor resource utilization and support workforce planning efforts.Identify project risks and collaborate with project teams to develop mitigation strategies.Support quality assurance processes to ensure project deliverables meet established standards.Assist in managing scope changes, obtaining approvals, and maintaining associated documentation.Ensure compliance with applicable utility standards, procedures, and regulatory requirements.Prepare and distribute project status reports, presentations, and executive summaries.Facilitate effective communication between engineering, communication between engineering, construction, operations, finance, and contractor teams.Communicate project progress, risks, and key decisions to stakeholders in a clear and timely manner.Support leadership with data-driven insights to inform project decision-making." We need to split into separate items at each period that starts a new sentence (but some sentences have internal periods like "e.g."? Not present). We'll split by "." and trim. Similarly for Essential Skills: "5 to 10 years of experience in project coordination, project controls, construction administration, or project management support.Experience supporting utility distribution, transmission, substation, fiber, or grid investment programs.Experience managing project documentation, financial reporting, and contractor coordination.Familiarity with utility capital projects and infrastructure improvement programs.Advanced proficiency in Microsoft Excel, including Pivot Tables
- .
-