Project Scheduler (Sales & Estimating Phase)

We need to output HTML fragment with headings

for sections that have real content: About the role? Actually the posting includes "About KPI Solutions" (company description) and "Position Summary". Then "Key Responsibilities", "Requirements", "Preferred Qualifications", "Key Performance Indicators (KPIs)", "Benefits". Also maybe "Education", "Experience", "Technical Skills", "Core Competencies" are subparts of Requirements? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map sections accordingly. We need to preserve all substantive info, remove boilerplate (EEO etc). Remove duplicated lines. No Pay or Schedule sections unless present. There's no explicit Pay or Schedule info. So we should not create those sections. We need sections only when posting has real specific content. We have: - About KPI Solutions (company description) -> could be "About the role"? Actually "About the role" is generic; but we have company description. Could use "About KPI Solutions" as heading? 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 suggests those as examples. Probably we should use those standard headings. However we have "About KPI Solutions" which is not exactly "About the role". Might still be okay to use

About KPI Solutions

. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when applicable. But we can also use other headings if they match content? Safer to follow the pattern: Use those exact headings when we have content. For company description, maybe "About the role" is not appropriate. Could we treat "About KPI Solutions" as "About the role"? Not really. But we could still output a heading

About KPI Solutions

as it's a section heading. The instruction didn't forbid other headings, just gave examples. So it's okay. We need to avoid repeating job title as heading (not present). No Job ID. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information. Let's parse content: About KPI Solutions paragraph: description. Position Summary: paragraph. Key Responsibilities: bullet list (multiple items). We'll need to convert each bullet into

• . The responsibilities are grouped under headings like "Proposal and Bid Schedule Development", "Schedule Analysis and Risk Assessment", etc. Those could be subheadings? But instruction only says use

  for section headings (like Responsibilities). Could we also use

  for subheadings? Not specified. Safer to keep them as part of the list? But we need to preserve structure. Could treat each responsibility group as a

  maybe, but not required. Could just list all responsibilities as a flat list, but that loses grouping. However we must preserve ALL substantive information; grouping is substantive. We could keep subheadings as

  or . Since not prohibited, we can use

  for subheadings inside the responsibilities section. The instruction only mandates

  for section headings; doesn't forbid other heading levels. So we can use

  for sub-sections. Similarly Requirements: includes Education, Experience, Technical Skills, Core Competencies, Preferred Qualifications (maybe separate). Also Key Performance Indicators (KPIs) separate section. Benefits: list. We need to remove boilerplate: EEO statement at end. Also remove duplicated lines: none. Let's craft HTML. Structure:

  About KPI Solutions

  ...

  Position Summary

  ...

  Key Responsibilities

  Proposal and Bid Schedule Development

  • Develop detailed proposal schedules for new business opportunities.
  • Create project execution schedules based on scope, estimates, historical performance data, and resource availability.
  • Develop schedule narratives and milestone plans to support customer proposals and bid submissions.
  • Collaborate with Estimating and Operations teams to determine logical activity sequencing and project durations.
  • Establish project milestones, critical path activities, and major deliverables.

  Schedule Analysis and Risk Assessment

  • Perform Critical Path Method (CPM) analysis on proposal schedules.
  • Identify schedule risks, constraints, assumptions, and opportunities.
  • Conduct schedule sensitivity and what-if analyses to support bid strategy decisions.
  • Evaluate customer-required schedules and recommend achievable alternatives when necessary.
  • Assess schedule impacts associated with scope, resource, procurement, and construction assumptions.

  Estimating and Cost Integration

  • Support estimating teams by aligning schedule assumptions with labor and cost estimates.
  • Develop schedule-driven resource forecasts and manpower loading curves.
  • Assist in evaluating schedule acceleration or compression scenarios.
  • Provide schedule input for contingency and risk assessments.
  • Support development of cash flow projections and execution timelines.

  Stakeholder Collaboration

  • Partner with Business Development, Proposal Managers, Estimators, Engineers, Procurement, and Operations personnel.
  • Participate in proposal reviews, strategy meetings, and bid development sessions.
  • Present schedule assumptions, risks, and recommendations to leadership and customers as required.
  • Support customer discussions regarding project execution strategies and milestone commitments.

  Schedule Governance and Standards

  • Ensure schedules comply with company scheduling standards, PMO guidelines, and customer requirements.
  • Maintain schedule templates, historical schedule databases, and best practices.
  • Support continuous improvement initiatives related to scheduling processes and tools.
  • Assist with schedule audits and schedule quality assessments.

  Transition to Project Execution

  • Support project handoff activities from Sales and Estimating to Project Management and Project Controls teams.
  • Ensure approved proposal schedules are effectively transitioned into execution schedules.
  • Document assumptions, risks, and schedule basis of estimate information for project teams.

  Requirements

  Education

  Bachelor's Degree in Engineering, Construction Management, Project Management, Business Administration, Operations Management, or a related field. Equivalent combination of education and relevant experience may be considered.

  Experience

  3+ years of project scheduling, project controls, estimating support, or project planning experience. Experience supporting proposals, bids, capital projects, manufacturing projects, engineering projects, construction projects, or EPC projects preferred. Experience developing schedules during project initiation, proposal, or estimating phases strongly preferred.

  Technical Skills

  • Advanced proficiency in Microsoft Project/Primavera P6.
  • Strong Microsoft Excel skills, including data analysis and reporting.
  • Understanding of: Work Breakdown Structures (WBS), Critical Path Method (CPM), Resource Loading, Project Lifecycle Management, Schedule Risk Analysis, Cost and Schedule Integration, Baseline Schedule Development, Proposal and Bid Processes.

  Core Competencies

  • Strong analytical and problem-solving skills
  • Excellent organizational and planning abilities
  • Ability to interpret technical scopes of work
  • Strong communication and presentation skills
  • Attention to detail
  • Collaboration and stakeholder management
  • Strategic thinking
  • Ability to manage multiple proposals simultaneously
  • Risk identification and mitigation planning

  Preferred Qualifications

  • PMI Scheduling Professional (PMI-SP) Certification
  • Project Management Professional (PMP) Certification
  • AACE Planning & Scheduling Professional (PSP) Certification
  • Experience working within a PMO, Project Controls, Engineering, Manufacturing, Construction, or EPC environment
  • Knowledge of schedule risk assessment and Monte Carlo analysis tools

  Key Performance Indicators (KPIs)

  • On-time completion of proposal schedules
  • Accuracy of project duration forecasts
  • Schedule quality and compliance scores
  • Identification and mitigation of schedule risks
  • Proposal support responsiveness
  • Successful transition of schedules into project execution
  • Stakeholder satisfaction

  Benefits

  • Medical Insurance
  • Dental Insurance
  • Vision Insurance
  • Health Care Concierge Service
  • 401(k) Retirement Plan (Pre-tax & Roth)
  • Company paid Basic Life Insurance, Short-Term Disability & Long-Term Disability
  • Voluntary Life & AD&D Insurance
  • Voluntary Accident, Critical Illness & Hospital Indemnity Insurance
  • Pet Insurance
  • Milk Stork Program
  • Wellness Program with gift card redemption and wellness challenges
  • Paid Time Off (Vacation, Sick & 10 Holidays)
  • Training & Development

  We should ensure no extra blank lines? It's fine. Check for any boilerplate removed: EEO statement removed. Also removed "KPI Solutions provides equal employment opportunity..." etc. Check for duplicated lines: none. Check for any content inadvertently omitted: The "Position Summary" paragraph we captured. Let's verify original: "Position Summary The Project Scheduler is responsible for developing, analyzing, and maintaining project schedules during the sales, estimating, and proposal development phases of the project lifecycle. This role partners closely with Business Development, Estimating, Engineering, Operations, and Project Management teams to develop realistic execution schedules that support bid strategies, customer proposals, resource planning, and project delivery commitments. The Project Scheduler plays a critical role in identifying schedule risks and opportunities, validating project timelines, and ensuring that proposed schedules align with organizational capabilities and customer requirements. The ideal candidate possesses strong scheduling expertise, analytical skills, and the ability to collaborate across multiple functions in a fast-paced proposal environment." We need to preserve that exactly. We'll put in

  . Now "About KPI Solutions" paragraph: "KPI Solutions is a national supply chain consulting and warehouse automation systems integrator, helping some of the biggest names in e-commerce, retail, and distribution move product faster and smarter. Formed in 2021 through the combination of Kuecker Logistics Group, PULSE Integration, and QC Software, KPI brings together decades of material handling and systems integration experience — rooted in material handling integration dating back to 1971. From initial design through go-live and ongoing support, KPI delivers engineered solutions that blend automated technologies (MHE, robotics, conveyor, ASRS, AMR/AGV) with intelligent warehouse execution software to optimize productivity, increase fulfillment speed, and build operational resilience for clients." We'll put that in

  . Check that we didn't miss any details like "Key Responsibilities" subheadings text: we captured all bullet points. Check "Requirements" subheadings: Education, Experience, Technical Skills, Core Competencies. Did we miss any