Client and Stakeholder Relations
The Client and Stakeholder Relations domain tests how you define expectations, communicate, manage changes, engage affected parties, and resolve disputes without damaging the professional relationship or the project.
Core rules and concepts
- Define scope, deliverables, acceptance criteria, assumptions, exclusions, and the client's responsibilities in the agreement. Ambiguity at the start becomes a dispute at the end.
- Use a written change-order process. When requested work falls outside scope, assess cost, schedule, and technical impact before proceeding; obtain written authorization unless a safety emergency requires immediate action.
- Map stakeholders by power and interest, then build an engagement and communication plan. Identify a single point of contact for client approvals and decisions.
- Manage expectations with evidence: progress reports, decision logs, risk registers, and minutes. Do not make verbal promises that exceed the contract.
- Public and community consultation requires accessible notice, clear information, a recorded response process, and feedback that shows how input was considered.
- Resolve disputes in stages: direct negotiation, mediation, arbitration, then litigation. Preserve contemporaneous records, but prefer interest-based negotiation before positional escalation.
- Protect client confidentiality and personal data, including in shared project platforms.
Worked example
A client asks mid-project for an additional seismic analysis not listed in the scope. You estimate 40 extra hours, a two-week schedule impact, and additional software cost. The correct action is to issue a change order describing the work, price, schedule effect, and assumptions, then proceed only after written acceptance. Doing the work informally risks unpaid effort, unplanned delay, and a dispute about whether the analysis was included. If the request reveals an immediate safety concern, act first and document the urgency.
Traps that cost marks
Accepting scope creep without a change order; bypassing the client's project manager; overpromising schedule or performance; ignoring community stakeholders until approval is at risk; failing to document decisions; disclosing another client's confidential information.