Right-of-Way Project Coordinator
WSP in the U.S. · Little Rock, AR · 1 mo ago
OTHRFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: "This Opportunity" description, "Your Impact Key Responsibilities" with subpoints, "Who You Are Required Qualifications", "About WSP". Also there is mention of locations, multiple openings, etc. There's no explicit Pay, Schedule, Benefits (though benefits mentioned in About WSP: comprehensive suite of benefits). That is specific: medical, dental, vision, disability, life, retirement savings. So we can include Benefits section. Pay not mentioned. Schedule not mentioned. Skills maybe implied but not explicit list. We could include Skills if we extract from responsibilities: project controls, scheduling, budgeting, financial recordkeeping, earned value, risk management, coordination, communication, quality control, etc. But we need to avoid filler. Better to have sections: About the role (maybe from "This Opportunity" and location), Responsibilities (from Key Responsibilities), Requirements/Qualifications (from Who You Are Required Qualifications), Benefits (from About WSP). Also maybe "About WSP" could be "About the Company" but not required. Use headings as per list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine Requirements and Qualifications into one? But they are separate headings allowed. We need to decide which to include based on content. We have both "Required Qualifications" and also maybe "Experience...". Could put Requirements heading with the bullet list of qualifications. Qualifications heading maybe duplicate; better to not create empty heading. So we include Requirements (or Qualifications) but not both. Choose Requirements. Also Skills maybe not explicit; we could skip. Benefits we have. Pay and Schedule none -> omit.
Thus output:
. Could group under subheadings? Not required; just list.
Then "Who You Are Required Qualifications"
- Experience in right-of-way coordination, project controls, or related roles supporting infrastructure or utility projects.
- Financial recordkeeping and management including but not limited to bank reconciliations, Escrow Account Balance, Reimbursements, etc.
- Strong understanding of budgeting, scheduling, and performance metrics (e.g., earned value analysis).
- Proficiency with project management and reporting tools.
- Effective communication and organizational skills; ability to manage multiple priorities.
- Familiarity with electric utility infrastructure projects is preferred.
We can list as .
Then "About WSP" paragraph about benefits etc. Benefits: "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."
We can list each benefit as .
We should not include other fluff like "WSP USA is the U.S. operating company..." etc. That's not benefits but could be About the Company but not required heading. We could include as part of About the role? Probably not needed. The instruction: include a section ONLY when posting has real, specific content for it. The About WSP paragraph is not a section heading we have (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can put the benefits under Benefits heading. The rest of About WSP description (mission, size) is not needed for any heading; we could omit as it's not under those headings. It's not required to preserve all info? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep all substantive info. If we omit the About WSP mission description, we lose substantive info. But we could incorporate it into About the role? Not appropriate. Perhaps we can create an "About the Company" section but not in allowed headings list. 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
. We'll group under
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: "This Opportunity" description, "Your Impact Key Responsibilities" with subpoints, "Who You Are Required Qualifications", "About WSP". Also there is mention of locations, multiple openings, etc. There's no explicit Pay, Schedule, Benefits (though benefits mentioned in About WSP: comprehensive suite of benefits). That is specific: medical, dental, vision, disability, life, retirement savings. So we can include Benefits section. Pay not mentioned. Schedule not mentioned. Skills maybe implied but not explicit list. We could include Skills if we extract from responsibilities: project controls, scheduling, budgeting, financial recordkeeping, earned value, risk management, coordination, communication, quality control, etc. But we need to avoid filler. Better to have sections: About the role (maybe from "This Opportunity" and location), Responsibilities (from Key Responsibilities), Requirements/Qualifications (from Who You Are Required Qualifications), Benefits (from About WSP). Also maybe "About WSP" could be "About the Company" but not required. Use headings as per list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine Requirements and Qualifications into one? But they are separate headings allowed. We need to decide which to include based on content. We have both "Required Qualifications" and also maybe "Experience...". Could put Requirements heading with the bullet list of qualifications. Qualifications heading maybe duplicate; better to not create empty heading. So we include Requirements (or Qualifications) but not both. Choose Requirements. Also Skills maybe not explicit; we could skip. Benefits we have. Pay and Schedule none -> omit.
Thus output:
About the role
... description ...
Responsibilities
- ... each bullet ...
Requirements
- ... each bullet ...
Benefits
- ... each benefit ...
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 only those headings. But we could still include other headings if needed? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are the allowed headings. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should only use those headings. So we need to fit all substantive info under those headings. The About WSP mission etc could go under About the role? Not really. Maybe we can treat "About the role" to include both role description and company overview. That might be acceptable. The About the role heading could contain description of the role and also company info. That would preserve all substantive info.
Thus About the role paragraph will include: The Right-of-Way (ROW) Coordinator supports..., Candidates can sit..., Texas..., multiple openings..., apply if you have strong experience..., plus WSP USA description: "WSP USA is the U.S. operating company of WSP, one of the world's leading engineering and professional services firms. Dedicated to serving local communities, we are engineers, planners, technical experts, strategic advisors and construction management professionals. WSP USA designs lasting solutions in the buildings, transportation, energy, water and environment markets. With more than 15,000 employees in over 300 offices across the U.S., we partner with our clients to help communities prosper. www.wsp.com WSP provides a flexible and agile workplace model while meeting client needs." That's all substantive.
We must not include the EEO boilerplate etc.
Now Benefits: list medical, dental, vision, disability, life, retirement savings.
Now we need to ensure we don't include filler like "commensurate with experience". Not present.
Now produce HTML.
Let's craft.
About the role paragraph: combine sentences.
We'll produce:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are the allowed headings. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should only use those headings. So we need to fit all substantive info under those headings. The About WSP mission etc could go under About the role? Not really. Maybe we can treat "About the role" to include both role description and company overview. That might be acceptable. The About the role heading could contain description of the role and also company info. That would preserve all substantive info.
Thus About the role paragraph will include: The Right-of-Way (ROW) Coordinator supports..., Candidates can sit..., Texas..., multiple openings..., apply if you have strong experience..., plus WSP USA description: "WSP USA is the U.S. operating company of WSP, one of the world's leading engineering and professional services firms. Dedicated to serving local communities, we are engineers, planners, technical experts, strategic advisors and construction management professionals. WSP USA designs lasting solutions in the buildings, transportation, energy, water and environment markets. With more than 15,000 employees in over 300 offices across the U.S., we partner with our clients to help communities prosper. www.wsp.com WSP provides a flexible and agile workplace model while meeting client needs." That's all substantive.
We must not include the EEO boilerplate etc.
Now Benefits: list medical, dental, vision, disability, life, retirement savings.
Now we need to ensure we don't include filler like "commensurate with experience". Not present.
Now produce HTML.
Let's craft.
About the role paragraph: combine sentences.
We'll produce:
About the role
The Right-of-Way (ROW) Coordinator supports the ROW Program Manager/Project Manager and ROW Supervisor(s)/Assistant Project Manager(s) in the planning, execution, and reporting of right-of-way and real estate acquisition projects. This role is responsible for developing and maintaining project schedules and budgets, monitoring quality control, and producing detailed performance reports for electric transmission and substation-related projects. Candidates can sit in any of our offices; Texas, Oklahoma, Arkansas, and Louisiana are considered prime locations. This opportunity has multiple openings – apply if you have strong experience in ERCOT, SPP, SWEPCO, varying voltage, and LARGE‑SCALE. WSP USA is the U.S. operating company of WSP, one of the world's leading engineering and professional services firms. Dedicated to serving local communities, we are engineers, planners, technical experts, strategic advisors and construction management professionals. WSP USA designs lasting solutions in the buildings, transportation, energy, water and environment markets. With more than 15,000 employees in over 300 offices across the U.S., we partner with our clients to help communities prosper. www.wsp.com WSP provides a flexible and agile workplace model while meeting client needs.
Now Responsibilities: list each bullet as- .
We need to ensure we capture all bullets exactly.
Let's list:
- Assist the Program Manager and ROW Supervisors in developing, monitoring, and maintaining right-of-way project schedules and budgets.
- Track and report on project milestones across survey, acquisition, and construction-related damage settlements.
- Prepare earned value reports that measure schedule and cost performance.
- Responsible for tracking and reporting on trust/escrow accounts, if applicable, including regular reconciliations, ensuring accuracy and compliance.
- Duties may include processing reimbursements, maintaining a detailed record of transactions, and monthly reporting.
- Collaborate with the team, addressing any discrepancies, and facilitate timely fund reimbursements.
- Develop accurate budgets related to right-of-way and real estate acquisition activities.
- Analyze project financials to forecast trends, identify variances, and support decision-making.
- Handle and prepare financial recordkeeping and management including but not limited to bank reconciliations, Escrow Account Balance, Reimbursements, etc.
- Prepare and issue routine project and portfolio reports, including dashboards that track key performance indicators (KPIs), production status, and risk assessments.
- Identify and communicate potential project risks and performance issues promptly.
- Serve as a liaison between project stakeholders, including ROW teams, Program Managers, and client personnel.
- Occasionally act as a single point of contact on project control matters.
- Ensure all reporting aligns with client and internal standards.
- Lead the development and monitoring of quality control processes to ensure timely and accurate project execution.
- Ensure adherence to project management best practices and ROW-specific compliance guidelines.
- Support the ROW team with additional tasks and responsibilities as required to