Planning and Delivery Manager (Owner's Representative) - Data Center Construction (Hybrid)
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content.
We have job description: includes overview (About the role), duties/responsibilities, minimum qualifications, preferred qualifications, duties and responsibilities (already listed), benefits, salary range (Pay). No explicit schedule info. So we can include About the role, Responsibilities, Requirements (maybe combine min qualifications?), Qualifications (preferred?), Skills (maybe from abilities), Benefits, Pay. Schedule not present, so omit.
We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent.
We need to format lists with - . Use
for prose.
We need to ensure we don't include boilerplate like EEO etc. Remove those paragraphs.
We need to include "Submission Requirements" maybe as part of Requirements? It's about resume requirements; could be considered part of Requirements or Qualifications? Probably part of Requirements (documents). We'll include under Requirements.
We must not include "At KALCON we are committed..." EEO boilerplate; remove.
We must not include "Submission Requirements" heading? It's not one of the allowed headings; we can embed that content under Requirements as a list.
We need to decide sections:
- About the role: summary paragraph(s) describing role.
- Responsibilities: list of duties (the Duties And Responsibilities section broken into subcategories). Could combine all duty bullet points into a single list or multiple lists under subheadings? But only allowed headings are the given ones; we cannot add custom headings like "Field Validation & Construction Planning". So we need to put all duties under Responsibilities as a list (maybe grouped but still just list items). We'll preserve all duty statements as list items.
- Requirements: Minimum Qualifications + Submission Requirements (list of resume items). Could also include "Experience may be considered in lieu of formal education." etc.
- Qualifications: Preferred Qualifications.
- Skills: maybe extract abilities like strong communication, organizational, problem-solving, ability to influence, etc. Could also include ability to maintain on-site presence, travel, etc. We'll put those under Skills.
- Benefits: list benefits.
- Pay: salary range.
We must not include sections with filler like "commensurate with experience". Not present.
We must not include Schedule.
Now craft HTML.
We need to ensure we don't duplicate content. Let's extract prose.
About the role: The first paragraph: "KALCON is seeking an experienced and field-oriented Scheduler / Planning & Delivery Manager to support the successful delivery of mission-critical data center construction projects. Acting as an extension of the Owner's Representative team, this role provides on-site schedule leadership, construction planning support, schedule validation, and delivery oversight throughout construction, commissioning, and turnover activities. The position may support projects where the client is acting as either the tenant within a third-party developed facility or as the developer delivering space for a tenant, requiring flexibility in how the role engages with project stakeholders and contractors."
We can put that in
.
Responsibilities: list all duty statements from "Duties And Responsibilities" section. Let's extract each bullet:
- Maintain an active on-site presence to validate that contractor schedules, sequencing plans, and reported progress accurately reflect field conditions and actual construction activities.
- Work directly with General Contractor schedulers, superintendents, and trade partners to evaluate construction sequencing, crew loading, workfront availability, and execution readiness.
- Walk the project regularly to identify schedule risks, coordination conflicts, access constraints, material shortages, and productivity issues before they impact project milestones.
- Provide independent feedback to project leadership regarding schedule health, field performance, and the realism of contractor planning assumptions.
- Own and maintain the owner's view of the project schedule, incorporating field observations, contractor updates, procurement activities, commissioning milestones, and project priorities.
- Review contractor Primavera P6 schedules, logic, float trends, milestone forecasts, and recovery plans to evaluate alignment with actual construction progress.
- Analyze schedule changes, delays, recovery strategies, and critical path activities to identify risks and opportunities impacting project delivery.
- Challenge schedule assumptions and progress updates that are inconsistent with field conditions or observed construction performance.
- Participate in weekly planning meetings, look-ahead reviews, contractor coordination meetings, and superintendent planning sessions to support reliable project execution.
- Coordinate construction sequencing with procurement, equipment deliveries, commissioning activities, startup events, and turnover milestones.
- Track owner-furnished equipment, vendor activities, and long-lead procurement items that may affect schedule performance and project delivery.
- Support project teams in identifying recovery opportunities and implementing mitigation strategies when schedule risks are identified.
- Align construction schedules with commissioning, startup, testing, and turnover milestones to ensure project delivery remains focused on operational readiness.
- Support integration of Level 1 through Level 5 commissioning activities into project planning and schedule coordination efforts.
- Monitor readiness for system startup, turnover, and commissioning activities and identify constraints that may affect completion dates.
- Coordinate with project controls, commissioning teams, contractors, and vendors to ensure schedule priorities support successful turnover objectives.
- Prepare weekly schedule reports, milestone updates, and risk summaries highlighting key project activities, constraints, delays, and recovery actions.
- Communicate schedule performance, emerging risks, and recommended actions to project leadership in a clear and actionable manner.
- Build effective working relationships with contractors, superintendents, vendors, consultants, and project stakeholders to promote collaboration and schedule accountability.
- Support projects operating under either tenant-representation or developer delivery models and adapt communication and coordination approaches accordingly.
We'll put each as
- .
Requirements: Minimum Qualifications bullet points:
- Bachelor's degree in Construction Management, Engineering, Architecture, Project Management, or a related field preferred. Experience may be considered in lieu of formal education.
- 5+ years of experience supporting commercial, industrial, mission-critical, manufacturing, infrastructure, or large-scale construction projects in a field-based construction, scheduling, project engineering, superintendent, construction management, or planning role
- Proven experience utilizing Primavera P6 to develop, maintain, analyze, and validate construction schedules in support of active field operations.
- Strong understanding of construction means and methods, trade sequencing, site logistics, procurement, commissioning, startup, turnover, and operational readiness activities.
- Experience working directly with General Contractors, superintendents, subcontractors, and trade partners to validate schedule assumptions, construction sequencing, manpower loading, and reported progress against actual field conditions.
- Ability to identify schedule risks, analyze critical path activities, evaluate recovery plans, and communicate schedule impacts and recommendations to project teams and leadership.
- Strong communication, organizational, and problem-solving skills with the ability to influence stakeholders, challenge assumptions, and drive accountability in a fast-paced construction environment.
- Ability to maintain a consistent on-site presence, perform routine field walks, and travel as required to support project assignments.
Also Submission Requirements: list of resume items:
- List of all Educational Achievements
- List of all Professional Licenses or Certificates
- List of Awards Received
- Detailed Employment History with each company including:
- Name & Contact Information of the firm or agency
- Start Date and End Date (Month & Year)
- Positions Held
We'll include these as list items under Requirements maybe as a sublist? But we can just add them as list items.
Qualifications: Preferred Qualifications:
- Experience supporting mission-critical, data center, hyperscale, colocation, AI infrastructure, or other technically complex construction projects.
- Experience working within an Owner's Representative, developer, tenant-representative, or owner's project management environment.
- Experience integrating construction schedules with commissioning, startup, testing, and turnover milestones.
- Familiarity with Pull Planning, Last Planner System®, Lean Construction principles, or collaborative planning methodologies.
- PSP, PMP, CCM, or similar industry certifications.
Skills: maybe we can pull out abilities not already covered: strong communication, organizational, problem-solving (already in Requirements). Ability to influence stakeholders, challenge assumptions, drive accountability (also in Requirements). Ability to maintain on-site presence, perform routine field walks, travel (also in Requirements). Might be overlapping. Could still include some like "Ability to identify schedule risks, analyze critical path activities, evaluate recovery plans, and communicate schedule impacts" (already in Requirements). Might be redundant but okay.
We could decide to not have Skills section if content overlaps heavily; but we need to include only if real specific content. We could still include Skills with items like "Strong communication, organizational, and problem-solving skills", "Ability to influence stakeholders and drive accountability", "Ability to maintain on-site presence and travel". That's specific.
Benefits: list as given.
Pay: salary range: $140,000 USD - $200,000 USD.
Now produce HTML.
We must not include any extra text outside HTML fragment.
Let's craft:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Skills
- ...
...
Benefits
- ...
...
Pay
$140,000 USD - $200,000 USD
Check that we didn't include Schedule.
Now ensure we didn't inadvertently include boilerplate like EEO etc. We removed.
Check that we preserved all substantive info: we included overview, duties, min quals, submission requirements, preferred quals, skills, benefits, pay. Did we miss any? The "Ability to maintain a consistent on-site presence, perform routine field walks, and travel as required to support project assignments." is in Requirements; we also put in Skills maybe duplicate but okay.
We also included "Experience may be considered in lieu of formal education." as part of first bullet.
We included "Strong understanding of construction means and methods, trade sequencing, site logistics, procurement, commissioning, startup, turnover, and operational readiness activities." as bullet.
We included "Experience working directly with General Contractors, superintendents, subcontractors, and trade partners to validate schedule assumptions, construction sequencing, manpower loading, and reported progress against actual field conditions."
We included "Ability to identify schedule risks, analyze critical path activities, evaluate recovery plans, and communicate schedule impacts and recommendations to project teams and leadership."
We included "Strong communication, organizational, and problem-solving skills with the ability to influence stakeholders, challenge assumptions, and drive accountability in a fast-paced construction environment."
We included "Ability to maintain a consistent on-site presence, perform routine field walks, and travel as required to support project assignments."
Now Submission Requirements bullets: we need to include them as list items.
Check that we didn't miss any duty: we included all.
Now ensure we didn't include any duplicated lines: we have some overlap between Requirements and Skills but that's okay as they are distinct sections; but we might be duplicating content (like strong communication etc). The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited but might be considered redundant. However we could avoid duplication by moving those skills to Skills only and not repeat in Requirements. But Requirements already includes those skills as part of minimum qualifications; they are substantive. If we move them to Skills only, we would lose them from Requirements. But we could keep them in Requirements and not duplicate in Skills; instead Skills could include other abilities not already captured: maybe "Ability to influence stakeholders, challenge assumptions, and drive accountability" is already in Requirements. "Ability to maintain on-site presence, perform routine field walks, and travel" also in Requirements. So Skills might be redundant. Perhaps we can omit Skills section entirely, as the skills are already covered under Requirements. The instruction: "Prefer a few substantive sections over many thin ones." So better to omit Skills if its content is already covered. Let's drop Skills section.
Thus
for prose. We need to ensure we don't include boilerplate like EEO etc. Remove those paragraphs. We need to include "Submission Requirements" maybe as part of Requirements? It's about resume requirements; could be considered part of Requirements or Qualifications? Probably part of Requirements (documents). We'll include under Requirements. We must not include "At KALCON we are committed..." EEO boilerplate; remove. We must not include "Submission Requirements" heading? It's not one of the allowed headings; we can embed that content under Requirements as a list. We need to decide sections: - About the role: summary paragraph(s) describing role. - Responsibilities: list of duties (the Duties And Responsibilities section broken into subcategories). Could combine all duty bullet points into a single list or multiple lists under subheadings? But only allowed headings are the given ones; we cannot add custom headings like "Field Validation & Construction Planning". So we need to put all duties under Responsibilities as a list (maybe grouped but still just list items). We'll preserve all duty statements as list items. - Requirements: Minimum Qualifications + Submission Requirements (list of resume items). Could also include "Experience may be considered in lieu of formal education." etc. - Qualifications: Preferred Qualifications. - Skills: maybe extract abilities like strong communication, organizational, problem-solving, ability to influence, etc. Could also include ability to maintain on-site presence, travel, etc. We'll put those under Skills. - Benefits: list benefits. - Pay: salary range. We must not include sections with filler like "commensurate with experience". Not present. We must not include Schedule. Now craft HTML. We need to ensure we don't duplicate content. Let's extract prose. About the role: The first paragraph: "KALCON is seeking an experienced and field-oriented Scheduler / Planning & Delivery Manager to support the successful delivery of mission-critical data center construction projects. Acting as an extension of the Owner's Representative team, this role provides on-site schedule leadership, construction planning support, schedule validation, and delivery oversight throughout construction, commissioning, and turnover activities. The position may support projects where the client is acting as either the tenant within a third-party developed facility or as the developer delivering space for a tenant, requiring flexibility in how the role engages with project stakeholders and contractors." We can put that in
. Responsibilities: list all duty statements from "Duties And Responsibilities" section. Let's extract each bullet: - Maintain an active on-site presence to validate that contractor schedules, sequencing plans, and reported progress accurately reflect field conditions and actual construction activities. - Work directly with General Contractor schedulers, superintendents, and trade partners to evaluate construction sequencing, crew loading, workfront availability, and execution readiness. - Walk the project regularly to identify schedule risks, coordination conflicts, access constraints, material shortages, and productivity issues before they impact project milestones. - Provide independent feedback to project leadership regarding schedule health, field performance, and the realism of contractor planning assumptions. - Own and maintain the owner's view of the project schedule, incorporating field observations, contractor updates, procurement activities, commissioning milestones, and project priorities. - Review contractor Primavera P6 schedules, logic, float trends, milestone forecasts, and recovery plans to evaluate alignment with actual construction progress. - Analyze schedule changes, delays, recovery strategies, and critical path activities to identify risks and opportunities impacting project delivery. - Challenge schedule assumptions and progress updates that are inconsistent with field conditions or observed construction performance. - Participate in weekly planning meetings, look-ahead reviews, contractor coordination meetings, and superintendent planning sessions to support reliable project execution. - Coordinate construction sequencing with procurement, equipment deliveries, commissioning activities, startup events, and turnover milestones. - Track owner-furnished equipment, vendor activities, and long-lead procurement items that may affect schedule performance and project delivery. - Support project teams in identifying recovery opportunities and implementing mitigation strategies when schedule risks are identified. - Align construction schedules with commissioning, startup, testing, and turnover milestones to ensure project delivery remains focused on operational readiness. - Support integration of Level 1 through Level 5 commissioning activities into project planning and schedule coordination efforts. - Monitor readiness for system startup, turnover, and commissioning activities and identify constraints that may affect completion dates. - Coordinate with project controls, commissioning teams, contractors, and vendors to ensure schedule priorities support successful turnover objectives. - Prepare weekly schedule reports, milestone updates, and risk summaries highlighting key project activities, constraints, delays, and recovery actions. - Communicate schedule performance, emerging risks, and recommended actions to project leadership in a clear and actionable manner. - Build effective working relationships with contractors, superintendents, vendors, consultants, and project stakeholders to promote collaboration and schedule accountability. - Support projects operating under either tenant-representation or developer delivery models and adapt communication and coordination approaches accordingly. We'll put each as
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
$140,000 USD - $200,000 USD
Check that we didn't include Schedule. Now ensure we didn't inadvertently include boilerplate like EEO etc. We removed. Check that we preserved all substantive info: we included overview, duties, min quals, submission requirements, preferred quals, skills, benefits, pay. Did we miss any? The "Ability to maintain a consistent on-site presence, perform routine field walks, and travel as required to support project assignments." is in Requirements; we also put in Skills maybe duplicate but okay. We also included "Experience may be considered in lieu of formal education." as part of first bullet. We included "Strong understanding of construction means and methods, trade sequencing, site logistics, procurement, commissioning, startup, turnover, and operational readiness activities." as bullet. We included "Experience working directly with General Contractors, superintendents, subcontractors, and trade partners to validate schedule assumptions, construction sequencing, manpower loading, and reported progress against actual field conditions." We included "Ability to identify schedule risks, analyze critical path activities, evaluate recovery plans, and communicate schedule impacts and recommendations to project teams and leadership." We included "Strong communication, organizational, and problem-solving skills with the ability to influence stakeholders, challenge assumptions, and drive accountability in a fast-paced construction environment." We included "Ability to maintain a consistent on-site presence, perform routine field walks, and travel as required to support project assignments." Now Submission Requirements bullets: we need to include them as list items. Check that we didn't miss any duty: we included all. Now ensure we didn't include any duplicated lines: we have some overlap between Requirements and Skills but that's okay as they are distinct sections; but we might be duplicating content (like strong communication etc). The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited but might be considered redundant. However we could avoid duplication by moving those skills to Skills only and not repeat in Requirements. But Requirements already includes those skills as part of minimum qualifications; they are substantive. If we move them to Skills only, we would lose them from Requirements. But we could keep them in Requirements and not duplicate in Skills; instead Skills could include other abilities not already captured: maybe "Ability to influence stakeholders, challenge assumptions, and drive accountability" is already in Requirements. "Ability to maintain on-site presence, perform routine field walks, and travel" also in Requirements. So Skills might be redundant. Perhaps we can omit Skills section entirely, as the skills are already covered under Requirements. The instruction: "Prefer a few substantive sections over many thin ones." So better to omit Skills if its content is already covered. Let's drop Skills section. Thus