You need an answer about a design change. Someone gives you a name. That person refers you to someone else, who tells you the person you actually need left the project three months ago.
Meanwhile, the work is waiting.
A current project organisation chart should make it easy to find the person you need.
On a large project, finding the right person can take longer than getting the answer. It is particularly frustrating when you have just joined the team and don’t yet know who anyone is.
Problem: Your Team Does Not Know Who to Contact
People Waste Time Finding the Right Person
I once joined a project and wasted nearly the whole first day trying to find the right person to discuss the program stream I had been asked to control. I was told to talk with the design manager, but when I searched and asked around I found three different people with that title all on different sections of the project, none of which were clearly identified anywhere I could find.
A project can have plenty of capable people and still waste time because nobody can easily see who does what.
A new engineer may not know who coordinates design reviews. A contractor may not know who receives their program updates. A project administrator may be unsure who should review an invoice before it goes for approval.
People ask around, search old emails, or send questions to several people hoping that someone will respond. Sometimes everyone assumes someone else is dealing with the request.
This wastes time for the person asking and for everyone interrupted along the way. It also increases the chance that important information goes to the wrong person, or never reaches the person who needs it.
The Company Chart Does Not Show the Project Team
Your company may already have an organisation chart. That does not necessarily tell people how your project works.
A designer might report to an engineering manager in the company structure but work under a design manager on your project. A commissioning specialist might support several projects. Contractors and consultants may be essential members of your team without appearing on the company chart at all.
The company chart shows the business structure. Your team needs to see the project structure.
An Outdated or Inaccessible Chart Does Not Help
Even where a project organisation chart exists, it may have been prepared for the tender and never updated. It can still show people who have moved to another project, changed roles, or left the company.
Access can be another problem. I have worked in a company where viewing organisation charts depended on access to a business system that some contractors and secondees could not use. People working within the organisation could not easily see who was responsible for what.
A chart needs to be accurate and available to the people who need it. Otherwise, they are back to asking around.
Solution: Create and Maintain a Project Organisation Chart
Show the People and Roles Used by the Project
Prepare a project organisation chart early, once the main roles and reporting arrangements are understood. Refine it as the team develops.
Focus on the staff, contractors and consultants needed to deliver your project. Depending on its size, this might include:
- Project sponsor or project director.
- Project manager.
- Design manager and discipline leads.
- Construction or site manager.
- Project controls, procurement and contract administration roles.
- Quality, safety and environmental support.
- Commissioning and operational handover roles.
- Key contractor and consultant representatives.
A small project may only need a few boxes. On a large project, use an overview showing the main teams, with separate charts for the detail within each team.
Include key client and operations contacts where they help explain how the project works. Show them in clearly labelled groups so readers do not mistake a working relationship for a reporting line.
Do not fill the chart with unrelated company departments. The purpose is to help someone understand this project.
Use Project Roles as Well as Names
Each box should show the project role and the person filling it. Where several organisations are involved, include the organisation name as well.
A name on its own means little to someone who has just joined. A role on its own leaves them searching for the person doing it.
Use the role the person actually performs on the project. Their company job title may be “Senior Engineer”, but their project role might be “Design Manager”. That distinction matters when someone needs a design decision.
If one person fills several roles, show that clearly. If a required role is vacant, identify it as vacant and state who is covering it in the meantime. An empty box should prompt a resource discussion rather than leave everyone assuming the work is covered.
Explain Reporting and Communication Relationships
Make it clear who reports to whom for project work. Where necessary, distinguish project reporting from line management or technical support.
You can use solid and dashed lines, but include a short legend explaining what they mean. Do not expect everyone to interpret them the same way.
For example, an electrical engineer may receive project priorities through the design manager while receiving technical guidance from the electrical discipline lead. The chart and supporting role description should make those arrangements understandable.
Also make the authorised client contact clear. As discussed in Why You Need a Single Decision Maker in Client Communication, important commitments about scope, cost and schedule need clear decision arrangements.
This should still allow people to speak directly about routine technical matters within their agreed responsibilities. A chart should make communication easier, rather than require every question to pass through several managers.
Connect the Chart to Responsibilities and Authority
A chart helps people identify the relevant role. It does not explain every task that role must perform, or establish what that person can approve.
Support it with short role descriptions and, where useful, a responsibility assignment matrix such as a RACI. This identifies who is responsible, accountable, consulted and informed for particular activities or deliverables. The Association for Project Management has a useful example of why RACI matters.
For example, the design manager might coordinate a drawing package, a discipline lead might review the technical work, and the client’s authorised representative might accept the deliverable. Those are different responsibilities.
Make sure the arrangements agree with the project’s contracts, delegations and approval procedures. Placing someone higher on the chart does not automatically give them authority to approve expenditure or instruct a variation.
Refer also to 5 Reasons Why Clear Project Roles and Responsibilities are Important. The chart and role descriptions should support each other.
Include Contact Details That People Can Use
Ideally, include work email addresses and phone numbers in the chart so people can contact the right person immediately.
If this makes a large chart difficult to read, link each role or name to a shared project contact list instead. That list should use the same role names and remain consistent with the chart.
Include location or usual work days where these affect availability. For key roles, identify who covers absences and how to reach them.
Use work contact details appropriate for the intended audience. An internal chart may contain more detail than the version distributed to external parties. Make sure each version gives its readers a practical way to contact the people they need.
Make It Part of Induction and Handover
Put a link to the current chart somewhere obvious, such as the project workspace and the project management plan. Include it in the project summary given to new team members.
Check that contractors, consultants and other intended users can actually open it. A link is not useful if it leads to an access request that nobody processes.
During induction, explain where the new team member fits, who they report to, who reviews their work and who they can ask for help. Introduce the main people they will work with. The chart supports those introductions.
When a project manager changes, review the chart as part of the formal handover meeting. Agree when the incoming manager takes responsibility and update the project systems accordingly. The outgoing manager should not remain listed as the current manager simply because nobody changed the document.
Give Someone Responsibility for Keeping It Current
Assign an owner to maintain the chart and contact list. The project manager remains responsible for making sure the project structure is correct, even if a project administrator or team leads maintain the details.
Update it when someone joins, leaves, changes roles or becomes an acting replacement. Review it when the project moves between phases, because the team needed for design may be different from the team needed for construction or commissioning.
Show a revision date and keep one clearly identified current version. Archive old versions so they remain available as records without being mistaken for today’s team.
Where possible, generate the chart and contact list from shared project team data. This follows the same principle as Automate Project Management Where Possible: avoid repeatedly copying information between documents.
However, a company staff directory will not necessarily show who is assigned to your project. Someone still needs to maintain project roles, contractor contacts and reporting relationships. Automation helps when the underlying information is correct.
Lesson: Make It Easy to Find the Right Person
Create a project organisation chart that shows who is working on your project, what roles they perform and how the team fits together.
Make it easy to access, include usable contact details, and keep it current as people and responsibilities change. Support it with clear role descriptions and approval arrangements.
A good Project Organisation Chart will:
- Help with assigning responsibilities
- Help new team members identify the roles of the rest of the team and who to talk to for their tasks.
- Make communication between team members easier.
A good test is to give it to someone who has just joined the project. Can they work out who to contact for their next task without having to ask you?
If they can, your chart is doing something useful.



