Interior projects are delivered through temporary networks of clients, designers, consultants, contractors, suppliers, regulators, users and specialist trades. Their interests are often different: a client may prioritise cost and brand expression, an occupier may prioritise comfort, a contractor may prioritise buildability and programme certainty, and an authority may prioritise safety and compliance. Project success therefore depends not only on design and cost control, but also on how people are identified, involved, informed and given authority to decide.
Stakeholder, team and communication management is the organised practice of understanding interests, allocating decision rights, coordinating professional work, resolving disagreement and preserving an accurate record of project instructions. In interior project management, communication is also a control mechanism. An unclear instruction can become a variation; a missing approval can delay procurement; an undocumented decision can produce a dispute.
This chapter treats communication as part of governance rather than as an informal administrative activity. It explains how to map stakeholder influence and requirements, establish decision structures, lead multidisciplinary teams and meetings, manage expectations and conflict, and maintain reliable reports and document-control records.
Learning Objectives
By the end of this chapter, the learner should be able to:
Identify stakeholders and analyse their interests, influence, impact and information requirements.
Construct a practical stakeholder engagement and communication plan.
Define governance arrangements, escalation routes and decision rights.
Lead multidisciplinary teams, meetings and design coordination activities.
Distinguish positions from underlying interests and apply appropriate negotiation and conflict-management methods.
Prepare accurate reports, instructions, registers and document-control records.
Evaluate ethical, legal, cultural and technological issues in project communication.
1. Stakeholders in Interior Projects
A stakeholder is any person, group or organisation that can affect a project, is affected by it, or perceives itself to be affected by it. This definition is broader than the contract parties. For example, a neighbouring tenant, accessibility representative, facilities manager or future maintenance team may not sign the main contract but may significantly affect project acceptance and long-term performance.
Stakeholders can be classified in several ways:
Internal and external: The client’s project team is internal to the client organisation; planning authorities, suppliers and neighbours are external.
Primary and secondary: Primary stakeholders are directly involved in delivery or use; secondary stakeholders influence reputation, compliance or community acceptance.
Contractual and non-contractual: A contractor has contractual duties, while an end user may have legitimate requirements without being a contracting party.
Current and future: Operations, maintenance and replacement teams should be considered before construction is complete.
A stakeholder requirement is not automatically a project requirement. It must be tested against the brief, statutory obligations, budget, programme, technical feasibility and approved governance process. A useful requirements record identifies the source, rationale, priority, acceptance criterion, owner and verification method.
Stakeholder attributes
Four attributes are particularly useful:
Power or influence: ability to approve, fund, regulate, delay or change the project.
Interest: degree to which the stakeholder cares about the outcome or is affected by it.
Impact: potential consequence of the project for the stakeholder or of the stakeholder for the project.
Attitude: support, neutrality, uncertainty or opposition.
Influence is not always the same as organisational seniority. A specialist subcontractor may have modest formal authority but high practical influence if only that firm can produce a critical bespoke element.
2. Stakeholder Analysis and Engagement
Stakeholder analysis should begin during initiation and be updated when the design, procurement strategy, project team or external environment changes. A typical process is:
Identify stakeholders from the brief, contract, drawings, approvals, risk register and site knowledge.
Record interests, requirements, influence, attitude and likely impacts.
Assess the consequences of engagement failure.
Determine the information each stakeholder needs, when it is needed and through which channel.
Assign an engagement owner.
Review the analysis at stage gates and after major changes.
A power-interest matrix is a useful starting point, but it should not be treated as a mechanical rule. A low-power user group may still provide essential usability evidence, while a high-power client executive may need only concise exception reporting rather than daily design detail.
Figure: A power-interest matrix supports differentiated stakeholder engagement; the categories must be interpreted in project context.
Communication and engagement plan
A communication plan should specify the audience, purpose, content, format, frequency, sender, recipient, approval route and record location. Communication should be proportionate. A client board may require a fortnightly dashboard showing decisions, risks, cost and programme variance, while a site supervisor needs current drawings, method information and approved instructions.
Communication channels include meetings, design workshops, formal letters, email, project information platforms, dashboards, site briefings and inspections. Channel choice should reflect urgency, complexity, confidentiality and the need for evidence. A verbal conversation can resolve an issue quickly, but a consequential instruction should be confirmed in writing.
A communication is effective only when the receiver understands and can act on it. The sender should therefore use clear language, identify action owners and deadlines, distinguish fact from assumption, and invite confirmation for high-risk matters. Cultural and linguistic differences require particular care: avoid unexplained idioms, confirm understanding and provide accessible formats where necessary.
3. Governance and Decision Rights
Governance is the system by which a project is directed, controlled and held accountable. It answers four questions:
Who may make each type of decision?
What information and recommendation are required?
What limits apply to delegated authority?
How is the decision recorded, communicated and reviewed?
Good governance prevents two opposite failures. Centralisation failure occurs when every minor issue waits for senior approval. Uncontrolled delegation occurs when team members make commitments without authority. A decision-rights schedule should match authority to competence, accountability and risk.
Decision categories
Typical decisions include:
brief and scope approval;
design-stage approval;
budget allocation and contingency use;
procurement and supplier selection;
technical substitutions;
programme resequencing;
health, safety and compliance matters;
variations and claims;
completion and handover acceptance.
A responsibility assignment matrix, often called a RACI matrix, can clarify roles. Responsible means performing the work; Accountable means owning the outcome and approving it; Consulted means providing required input; Informed means receiving the decision or status. Each important activity should normally have one accountable role, even if several people are responsible or consulted.
Activity
Client sponsor
Project manager
Interior designer
Cost consultant
Contractor
Authority
Approve brief
A
R
C
C
I
I
Coordinate design information
I
A
R
C
C
I
Approve cost plan
A
R
C
R
C
I
Approve construction method
I
C
C
I
A/R
C
Approve statutory compliance
I
C
C
I
R
A
Accept completed works
A
R
C
C
R
I
The table is illustrative; actual roles depend on the appointment contracts and jurisdiction. RACI does not replace a contract, delegation instrument or professional duty.
Decision records and escalation
A decision record should include a unique identifier, date, issue, options considered, recommendation, decision, decision-maker, assumptions, cost and programme consequences, conditions, required actions and communication list. Escalation should be based on thresholds such as safety risk, budget exposure, delay, contractual liability or reputational consequence—not merely on personal disagreement.
A practical escalation path is: attempt resolution at working level; refer unresolved or high-risk matters to the project manager; escalate outside delegated limits to the client or steering group; seek specialist, legal or regulatory advice where required. Escalation is not failure. It is a control when used early and with adequate evidence.
4. Leading Multidisciplinary Teams
Interior delivery teams combine different professional languages and priorities. Designers discuss concept, proportion and material expression; engineers focus on performance and coordination; cost managers focus on value and exposure; contractors focus on sequence, means and methods; suppliers focus on manufacturability and lead time. Effective leadership creates a shared project purpose without suppressing legitimate professional challenge.
Important team conditions include:
a clear brief and definition of success;
agreed roles, interfaces and deliverables;
psychological safety to raise errors and risks;
timely access to current information;
respect for professional competence;
visible decisions and fair allocation of accountability;
mechanisms for learning and corrective action.
Teams commonly develop through stages of orientation, disagreement, norm formation and effective performance. The manager should not assume that conflict indicates dysfunction: constructive challenge can expose design omissions or cost risk. The relevant test is whether disagreement is evidence-based, respectful and directed toward project objectives.
Meetings as production activities
A meeting is valuable when it produces understanding, decisions, assigned actions or controlled escalation. Before the meeting, define its purpose, invite only necessary participants, circulate an agenda and identify required information. During the meeting, confirm the objective, distinguish information from decisions, control time, test assumptions and record actions. After the meeting, issue minutes promptly, assign owners and due dates, and track closure.
A useful agenda for a design coordination meeting is:
approval of previous minutes and outstanding actions;
safety, compliance and access constraints;
design interfaces and unresolved clashes;
procurement, samples and long-lead items;
cost and change implications;
programme and dependencies;
decisions required;
action review and next meeting.
Minutes should not be a transcript. They should provide an auditable account of material matters. Any participant who believes the minutes are inaccurate should identify the disputed entry promptly; the project manager should preserve both the correction and the reason for it where necessary.
5. Managing Expectations, Conflict and Negotiation
Expectation management begins with explicit statements of scope, quality, budget, programme, assumptions, exclusions and approval gates. Many disputes arise from an expectation that was never made explicit. A good manager communicates uncertainty rather than promising certainty that the project cannot support.
Conflict diagnosis
Conflict may concern:
Facts: What has occurred or what condition exists?
Interests: What does each party need or fear?
Values: What principles or standards are being defended?
Process: Who should decide and how?
Relationships: Is trust or respect damaged?
Resources: How should limited money, time or access be allocated?
The visible position—“we will not accept this finish”—may conceal an interest such as maintainability, brand consistency or fear of future liability. Separating people from the problem, identifying interests and using objective criteria can turn positional conflict into problem solving.
Negotiation
Negotiation should be prepared rather than improvised. Establish the desired outcome, minimum acceptable outcome, authority limit, evidence, alternatives and consequences of no agreement. Separate negotiable variables: price, scope, time, quality, payment, access, warranties and risk allocation. Avoid trading away safety, legal compliance or professional integrity merely to reach agreement.
A principled approach involves:
defining the problem jointly;
identifying each party’s interests;
generating several options before evaluating them;
applying objective standards such as the brief, contract, regulations, benchmark data or technical evidence;
documenting the agreement, assumptions and remaining risks.
If direct negotiation fails, structured mediation, senior review, dispute adjudication or formal contractual procedures may be appropriate. The applicable contract and jurisdiction determine the formal route.
6. Reports, Instructions and Document Control
Project records must enable a competent person to reconstruct what was known, decided, instructed and delivered. Document control is therefore a management discipline, not merely filing.
Core registers
Common registers include:
stakeholder and communication register;
decision and approval register;
request-for-information register;
change and variation register;
risk and issue register;
submittal and sample register;
drawing and specification register;
action and meeting register;
transmittal and correspondence register;
non-conformance and inspection register.
Each register requires an owner, defined fields, update frequency and review status. Duplicate unofficial spreadsheets should be avoided because they create competing versions of the truth.
Document identification
A controlled document normally carries a project identifier, discipline, document type, sequential number, revision, status, date, author, checker, approver and distribution information. Status labels must be meaningful: for example, “for coordination,” “for approval,” “for construction” and “superseded.” A revision cloud or change description should explain material changes where appropriate.
The controlled workflow is generally:
create or receive the document;
check format, completeness and metadata;
review technically and commercially as required;
approve or reject with comments;
issue through the authorised platform or transmittal;
record recipients and status;
archive superseded versions while preventing accidental use;
retain the final record according to contractual, legal and organisational requirements.
A document-control system must protect authenticity, availability, confidentiality and traceability. Access rights should follow role and need. Sensitive commercial, personal or security information should not be distributed casually.
Instructions and reports
A formal instruction should state the instruction number, date, issuer and authority, description, affected documents, required action, timing, cost or programme implications, response required and distribution. If the financial effect is unknown, that uncertainty should be stated; the instruction should not imply approval of an unpriced variation unless authorised.
A project report should separate:
status: what has happened;
forecast: what is expected;
variance: difference from the approved baseline;
cause: why the variance exists;
impact: consequence for cost, time, quality, safety or operations;
response: action, owner and due date.
Reports should avoid optimistic language that conceals exposure. “On track” should be supported by defined milestones and evidence. Where information is incomplete, label it as provisional and identify the date for confirmation.
7. Ethical, Legal and Professional Considerations
Communication management has ethical dimensions. Professionals must not knowingly misrepresent progress, conceal defects, manipulate records or present unverified assumptions as facts. Conflicts of interest should be declared and managed. Gifts, hospitality and supplier relationships must comply with organisational policy and applicable law.
Confidentiality and data protection are important when drawings, access plans, personal information, pricing and security-sensitive information are shared. Records should be retained only as required and accessed only by authorised personnel. Accessibility also matters: information should be understandable and available to participants with relevant communication needs.
The project manager must distinguish an instruction from advice, a recommendation from approval, and a meeting discussion from a contractual commitment. Professional appointments and local regulations may impose specific duties regarding health and safety, building compliance, accessibility, fire performance and record retention. When in doubt, obtain qualified legal, regulatory or technical advice rather than relying on informal interpretation.
8. Digital Collaboration and Artificial Intelligence
Common data environments and project collaboration platforms can improve version control, searchable records, workflow visibility and remote coordination. Their benefits depend on disciplined naming, permissions, metadata, approval workflows, backup and user training. A platform does not automatically create a reliable record if participants continue to issue uncontrolled attachments through private channels.
Artificial intelligence may assist with meeting transcription, action extraction, document classification, risk prompts and draft reports. However, AI-generated content can omit context, misidentify speakers, reproduce bias or invent confident but unsupported statements. A qualified person must verify minutes, instructions, design information and compliance interpretations before issue. Confidential project information should not be entered into an AI service unless contractual, organisational and data-protection requirements permit it. AI should support accountability, not replace the authorised decision-maker.
9. Illustrative Case: Retail Interior Fit-Out
Background
A fictional project involves the fit-out of a 1,200 m² flagship retail store in an occupied shopping centre. The client wants a distinctive interior open for a fixed seasonal launch. The landlord controls delivery access and noisy working hours. The designer has specified bespoke timber displays, while the contractor has identified a long manufacturing lead time. The facilities team is concerned about maintainability and fire-alarm interfaces.
Problem
At a coordination meeting, the client’s brand representative requests a revised display layout. The change appears visually minor but affects lighting, power, sprinkler coordination, joinery quantities and procurement. The contractor argues that the change will delay opening; the designer argues that the original intent must be protected. The meeting ends without a recorded decision, and different drawing revisions are later circulated.
Analysis
Stakeholder mapping shows high power and high interest for the client sponsor, project manager, landlord and contractor. The brand representative has high interest and strong influence over acceptance but limited authority to approve cost. The facilities team has moderate formal power but high impact on handover. The key risks are uncontrolled scope change, ambiguous authority, revision confusion and an untested programme assumption.
The project team reviews the RACI schedule and finds that the brand representative is consulted on design but is not accountable for budget or programme approval. The project manager asks the designer and contractor to prepare coordinated options. The cost consultant prices each option, while the programme manager assesses procurement and installation effects.
Approach and solution
A controlled change request is issued with a unique identifier. It describes the requested outcome, affected drawings, assumptions and decision deadline. Three options are prepared: retain the design, revise the layout using available components, or approve the bespoke revision with a stated cost and time effect. The client sponsor, not the brand representative, approves the selected option within delegated authority.
The decision is recorded in the decision register and communicated through an approved transmittal. The drawing register marks the previous issue as superseded. The meeting minutes identify actions for lighting, sprinklers, joinery, landlord access and facilities review. The contractor receives a formal instruction only after the client’s approval and commercial authority are confirmed.
Outcome
The client selects the available-component option. It preserves the principal visual intent, avoids the long manufacturing lead time and reduces coordination risk. The facilities manager accepts the maintenance access arrangement after a mock-up review. The project opens on the planned date, although the change consumes part of the design contingency.
Learning points
Aesthetic changes may have significant technical and commercial consequences.
Influence does not equal approval authority.
Options and evidence improve negotiation more effectively than positional argument.
A decision is incomplete until it is recorded, communicated and reflected in controlled documents.
Early facilities involvement can prevent late acceptance problems.
10. Best-Practice Checklist
Before a project stage begins, confirm that:
stakeholders and affected users have been identified;
requirements have owners and acceptance criteria;
decision rights and escalation thresholds are understood;
the communication plan matches stakeholder needs;
current drawings and specifications are accessible;
meeting agendas identify decisions required;
actions, risks and changes are tracked to closure;
instructions are issued only by authorised persons;
reports distinguish actual status from forecast;
superseded information cannot be mistaken for current information;
confidentiality, accessibility and data-protection requirements are addressed;
AI-assisted outputs, if used, have been human-verified.
Chapter Summary
Stakeholder, team and communication management is central to interior project and cost management because project outcomes are produced through relationships, decisions and information flows. Stakeholders should be identified and analysed according to influence, interest, impact and attitude, then engaged through a proportionate communication plan. Governance clarifies authority, accountability, consultation and escalation; RACI matrices and decision registers help prevent both delay and unauthorised commitments.
Multidisciplinary leadership requires a shared purpose, clear interfaces, respectful challenge and disciplined meetings. Conflict should be diagnosed by its facts, interests, process and relationship dimensions. Principled negotiation uses evidence, objective criteria and documented agreements. Reliable reports, instructions, registers and revision control create traceability and protect the project from ambiguity and dispute. Digital platforms and AI can improve coordination, but only when supported by permissions, verification, professional judgement and ethical controls.
Key Terms
Stakeholder: A person or organisation that can affect, is affected by, or perceives itself affected by a project.
Stakeholder analysis: Systematic assessment of stakeholder interests, influence, impact, attitude and requirements.
Power-interest matrix: A framework for classifying stakeholders according to influence and level of interest.
Engagement plan: A plan defining how, when and by whom stakeholders will be informed and involved.
Governance: The system of direction, control, accountability and decision-making applied to a project.
Decision right: Authorised power to make a defined type of project decision.
Escalation: Referral of an issue to a higher authority or specialist route when limits or risks require it.
RACI: A responsibility matrix identifying Responsible, Accountable, Consulted and Informed roles.
Multidisciplinary team: A team comprising different professional or technical disciplines.
Psychological safety: A team condition in which people can raise concerns or mistakes without unreasonable fear of humiliation or retaliation.
Meeting action: A defined task assigned to an owner with a due date and expected output.
Conflict of interest: A situation in which personal or external interests could improperly influence professional judgement.
Negotiation: A structured process through which parties seek agreement on issues involving different interests.
Change request: A controlled proposal to alter approved scope, design, cost, programme or other baseline.
Instruction: An authorised direction requiring project action.
Document control: Processes that identify, review, issue, revise, distribute and archive project information.
Transmittal: A recorded issue of documents or information to identified recipients.
Superseded document: A previous version that is no longer authorised for current use.
Common data environment: An organised digital platform or workflow for managing shared project information.
Decision register: A controlled record of material project decisions, authority, rationale and consequences.
Review Questions
Short Answer Questions
What is the difference between stakeholder influence and stakeholder interest?
Why should a communication plan identify both the sender and the record location?
Define the four roles represented by RACI.
What information should a formal project instruction contain?
Why must AI-generated meeting minutes be human-verified?
Long Answer Questions
Explain how a power-interest matrix can support stakeholder engagement on an interior fit-out project. Discuss its limitations.
Describe how governance and decision rights can reduce both project delay and unauthorised commitments.
Explain the role of meeting preparation, facilitation, minutes and action tracking in multidisciplinary coordination.
Compare positional bargaining with principled negotiation in the management of a design change.
Discuss how document control contributes to cost, programme, quality and dispute management.
Analytical / Application Questions
A client’s marketing director requests a late material substitution directly from the contractor. Analyse the authority, cost, programme and document-control issues, and propose a controlled response.
A design team claims that a contractor is obstructive, while the contractor claims that the design is incomplete. Develop a conflict-diagnosis and negotiation plan using interests, evidence and objective criteria.
Design drawings, meeting minutes and site instructions show different revisions of a reception desk. Explain how you would investigate the discrepancy, establish the authorised information, assess project impact and prevent recurrence.
Multiple Choice Questions with Answers
Question 1
Which stakeholder attribute describes the ability to approve, fund, regulate or delay a project?
A. Interest
B. Influence
C. Attitude
D. Accessibility
Correct Answer: B. Influence
Question 2
In a RACI matrix, who owns the outcome and approves the work?
A. Responsible
B. Accountable
C. Consulted
D. Informed
Correct Answer: B. Accountable
Question 3
Which document most directly records options considered, the decision-maker and the consequences of a project decision?
A. Decision register entry
B. Site attendance sheet
C. Supplier brochure
D. Uncontrolled sketch
Correct Answer: A. Decision register entry
Question 4
What is the most appropriate first response when a verbal discussion creates a consequential project instruction?
A. Ignore it until construction is complete
B. Confirm and control it in writing through the authorised process
C. Ask every stakeholder to rewrite the contract
D. Issue the oldest drawing revision
Correct Answer: B. Confirm and control it in writing through the authorised process
Question 5
Which approach best reflects principled negotiation?
A. Defend positions without discussing reasons
B. Use interests and objective criteria to develop options
C. Accept the first proposal to avoid conflict
D. Trade away statutory compliance for speed
Correct Answer: B. Use interests and objective criteria to develop options
Question 6
What is the primary purpose of marking a document as superseded?
A. To increase its visual quality
B. To prevent an outdated version being mistaken for current information
C. To remove all historical records
D. To transfer approval authority to the author
Correct Answer: B. To prevent an outdated version being mistaken for current information
Question 7
Which item should a project report distinguish from actual status?
A. Forecast
B. Project title
C. Meeting venue
D. File colour
Correct Answer: A. Forecast
Question 8
A brand representative requests a change but lacks budget approval authority. What is the appropriate action?
A. Treat the request as an approved variation
B. Reject all brand input permanently
C. Develop and assess the change, then obtain approval from the authorised decision-maker
D. Ask the supplier to implement it without records
Correct Answer: C. Develop and assess the change, then obtain approval from the authorised decision-maker
Question 9
Why can a low-power user group still require active engagement?
A. It may provide essential usability or acceptance information
B. Low-power stakeholders always control the budget
C. It replaces the need for statutory approval
D. It automatically becomes accountable for the project
Correct Answer: A. It may provide essential usability or acceptance information
Question 10
Which practice is most important when using AI to draft project minutes?
A. Issue the draft without review to save time
B. Allow AI to make contractual decisions
C. Have a qualified person verify accuracy, context and actions before issue
D. Delete the audio and all supporting records immediately
Correct Answer: C. Have a qualified person verify accuracy, context and actions before issue
Interior Project & Cost Management
Chapter 12
of 15