Skip to content
BIMpedia
Chapter 4 · Lesson 5 of 6Topic: Managing the work

Stakeholders and communication

Projects involve many people who need different things at different times. A short stakeholder map and a communication plan decide who hears what, how often and in what form, so coordination results reach the people who can act on them.

With Maya, information manager2 min read3 quiz questions
Skip to the quiz
  • Watch out
  • What it costs
  • Experienced readers
  • Remember
  • In BIMpedia
Mayainformation manager
Even if you do this every day, watch for this: One report for everyone is a report for no one. The PM wants status and risk on one page, discipline leads want their own issues, the client wants decisions. Same data, three views: build them from one source so the numbers always agree.

A project involves dozens of organisations and hundreds of people. They don't all need the same information: the client needs decisions, the PM needs status and risk, discipline leads need their own actions, and an authority needs specific submissions at specific times. Stakeholder management and a communication plan make sure each gets what they need.

Basics
Influence / interestApproachExample
High / highManage closelyClient, project manager
High / lowKeep satisfiedPlanning or building control authority
Low / highKeep informedFuture building users
Low / lowMonitorNeighbouring businesses

Communicating coordination

AudienceWhat they needForm
Project managerStatus, trends, risks, decisionsOne-page dashboard
Discipline leadsTheir open issues with owners and datesIssue list, BCF
ClientDecisions needed, progress at milestonesShort summary, model views
Site teamWhat's coordinated and approved to buildApproved drawings, model views by area
Story · The report nobody read
How it goes wrong

Every Friday the coordinator sends a 60-page clash report to 40 people. Nobody reads past page 3. When a big clash in the plant room causes a two-week delay, the PM says no one told them.

How it goes right

The coordinator sends a one-page summary to the PM (open, closed, overdue by discipline, top three risks), each discipline lead gets only their issues, and the plant room clash is the first line of the summary with "decision needed by Tuesday". The PM calls the meeting that day.

Mayainformation manager
Your turn. Give it about 10 min and work it out on your own before you open the model answer: that is where it sticks.
Exercise: Plan three reports 10 min

For a stage 4 coordination programme, describe the weekly report for the PM, for the MEP lead and for the client: content, length and form.

Key takeaways

  • Stakeholders are everyone affected by or able to affect the project: client, users, designers, contractors, authorities, neighbours.
  • Map them by interest and influence, and decide what each needs to know, when and how.
  • Coordination reports should be short and tailored: status and risk for the PM, actions for discipline leads, decisions for the client.
  • Use the same source for every view so the numbers never disagree.

Your notes

Related tool

Agenda, attendance, issue log, actions and minutes. Roll open issues into the next meeting.

Open Coordination Meeting Pack →

Check yourself

3 questions · 2 right to complete
  1. 1. What does the project manager usually want from a coordination report?
  2. 2. A stakeholder with high influence and low interest (for example a planning authority) should usually be…
  3. 3. Why build all reports from one data source?
0 of 3 answered
Was this page useful?