In AEC projects, the person who signs the contract is rarely the only person who decides who gets it. Hidden stakeholders — budget controllers, community groups, board members with informal veto power — shape outcomes that firms never see coming. Here's a systematic approach to identifying them all.
Ask an architecture firm who their client is on a given project, and the answer is usually a name: the development director, the facilities VP, the project manager who issued the RFP. That person is the point of contact. They're the one who scheduled the meeting, distributed the brief, and will send the selection notification.
They're also, in many cases, not the person who actually decides the outcome.
The gap between "who you're talking to" and "who influences the decision" is where a significant number of AEC proposals go to die. Firms write proposals tailored to their primary contact's stated priorities, present to the visible committee, and then lose to a firm that — they later learn — addressed concerns held by people they didn't know were in the room.
Stakeholder identification is the practice of closing this gap. It's the process of systematically discovering every person and group whose preferences, authority, or influence can affect a project selection decision — not just the ones who appear in the RFP.
Why Hidden Stakeholders Exist in AEC
The multi-stakeholder nature of architecture and construction projects isn't a bug in the process. It's a structural feature of projects that are physically permanent, publicly visible, expensive, and politically sensitive.
A corporate office renovation might involve only a facilities team and a CFO. A university science building involves the facilities department, the provost's office, the dean of the relevant college, a faculty advisory committee, the board of trustees, campus planning, the sustainability office, potentially a state regulatory body, and the student population who will use the building.
A mixed-use development in an urban context might add a planning commission, a zoning board, a neighborhood association, an affordable housing advocacy group, a historic preservation committee, local elected officials, the developer's investors, and the future tenants — all of whom have some degree of influence over whether the project gets approved and who designs it.
The RFP for each of these projects identifies a selection committee. It does not identify the network of influence that surrounds that committee and shapes its decisions. Finding that network is the firm's job.
The Five Stakeholder Categories in AEC Projects
Not all stakeholders play the same role. Classifying stakeholders by their function in the decision helps firms allocate attention and tailor their proposal content proportionally.
Decision-Makers
These are the stakeholders with formal authority to select the design firm. They vote, approve, or sign. On smaller projects, this might be a single person. On institutional or public projects, it's typically a committee with a defined evaluation process.
Identifying formal decision-makers is usually straightforward — the RFP names them. The work is in understanding each decision-maker's individual priorities, which are rarely uniform across a committee. One member might prioritize design vision. Another might focus on team qualifications. A third might weigh fee above all else. A proposal that treats the committee as a monolithic audience misses the opportunity to speak to each member's actual concern.
Influencers
Influencers don't have a formal vote but shape the opinions of those who do. In AEC projects, influencers are everywhere — and they're the stakeholders firms most commonly miss.
A department head whose recommendation carries weight with the VP on the selection committee. A trusted consultant who's been advising the client on project parameters. A board member who doesn't sit on the selection committee but whose preferences are well known to those who do. A facilities team member who worked with a competitor on a past project and has strong opinions about that experience.
Influencers are identified through organizational mapping, informal conversations, and research into the client's past project decisions. The question to ask: who has this committee listened to before?
Gatekeepers
Gatekeepers control what information reaches decision-makers. In AEC contexts, the most common gatekeeper is the project manager or procurement officer who manages the RFP process. They determine which questions get answered, which addenda get issued, and how proposals are packaged before reaching the committee.
Understanding the gatekeeper's priorities is important because they filter the committee's experience of your submission. If the gatekeeper has a strong preference for compliance — exact formatting, page limits, specific section order — then deviating from those requirements, even to create a more compelling proposal, can backfire before the committee ever sees your work.
Champions
Champions are internal advocates — stakeholders who actively prefer your firm and are willing to advocate for you inside the organization. Identifying and supporting champions is one of the highest-return activities in any pursuit.
Champions need two things from you: confidence in your capability and language to advocate on your behalf. The first comes from the quality of your proposal and interactions. The second is often overlooked — giving your champion specific talking points, data, or materials they can use when your firm comes up in internal discussions. A champion who says "I think they're good" is helpful. A champion who says "their phasing approach specifically addresses the schedule constraint the board raised last month" is powerful.
Blockers
Blockers can slow, redirect, or stop a decision. Community groups with opposition standing, regulatory bodies with approval authority, budget committees that can defer funding, and internal stakeholders with a preference for a different direction are all potential blockers.
The goal with blockers isn't conversion — it's risk mitigation. Your proposal should avoid giving blockers ammunition. If a neighborhood group has historically opposed tall buildings, and your proposal leads with an image of a tower, you've handed them a talking point regardless of how the committee felt about your design.
How to Find Them: Sources and Methods
Identifying stakeholders beyond the named committee requires active research. The good news is that most of the information exists in publicly accessible or professionally obtainable sources. The challenge is investing the time to look.
Public Records and Meeting Minutes
For public and institutional projects, board meeting minutes, planning commission records, and community hearing transcripts are gold mines. They reveal who participated in past decisions, what concerns were raised, which stakeholders showed up consistently, and how influence flowed between them. If the same board member has questioned project budgets in three consecutive meetings, that person's financial conservatism will shape how the committee evaluates your fee.
Organizational Charts and Websites
Most client organizations publish enough information on their websites to build a preliminary stakeholder map. Leadership pages, committee structures, governance documents, and annual reports reveal the formal hierarchy. The question to ask while reviewing: who in this structure would need to approve a project of this scope?
Past Project Announcements
How the client organization has announced past projects — who was quoted, who was credited, which stakeholders were mentioned — reveals who carries influence. If the university president was personally quoted in the press release for the last major building project, that person is engaged at a level that the organizational chart alone wouldn't indicate.
Professional Network Intelligence
Subconsultants, engineers, contractors, and other professionals who've worked with the client organization before often have detailed knowledge of the internal dynamics. A structural engineer who worked on the client's last project knows whether the facilities team runs the process or the provost's office does. A contractor who's bid on the client's work knows whether the procurement department's evaluation criteria are actually what drives the selection or just a formality.
These conversations are standard professional practice, not espionage. The information is freely shared because it's mutually beneficial — professionals helping each other navigate complex client structures.
The Client Themselves
The most direct source of stakeholder information is often the client contact themselves. Most project managers, when asked "who else in your organization will be involved in reviewing proposals?" will provide a straight answer. The question is rarely asked because firms assume the RFP tells them everything they need to know.
Follow-up questions that reveal more: "Are there any stakeholders outside the formal committee whose input the committee values?" "Has the board or leadership expressed any specific priorities for this project?" "Are there community groups or regulatory bodies whose concerns will factor into the decision?"
These aren't aggressive questions. They're the kind of thoughtful engagement that signals you take the selection process seriously — which is itself a positive signal to the client.
From Stakeholder List to Stakeholder Map
Identifying stakeholders is the first step. Mapping the relationships between them is where the practice becomes strategically powerful.
A stakeholder list tells you who matters. A stakeholder map tells you how they interact — who influences whom, where alliances exist, where tensions create risk, and where your proposal needs to navigate competing priorities.
The map should capture formal relationships (reporting lines, committee membership, governance authority) and informal ones (trusted advisors, historical allies, known tensions between departments). The informal relationships are often more predictive of decision outcomes than the formal ones.
This mapping doesn't need to be perfect. A partially complete map that reveals three stakeholders and two relationships you didn't know about is infinitely more useful than no map at all. And the map improves with every interaction — each conversation with the client, each public document reviewed, each professional contact consulted adds clarity.
Maintaining Stakeholder Intelligence Over Time
The most strategic firms don't build stakeholder maps project by project. They maintain them as evolving documents tied to each client organization.
The stakeholder landscape at a university or hospital or municipal government doesn't change completely between projects. The CFO who controlled the budget on the last project likely controls it on the next one. The community group that raised concerns about the parking structure will have opinions about the new building too. The board member who championed the arts center may not champion the laboratory — or may bring different priorities to a different project type.
Maintaining this intelligence across engagements creates an information advantage that competitors starting from scratch cannot match. It's the kind of compounding asset that gets more valuable with every project, every interaction, and every year.
Frequently Asked Questions
Who are the typical stakeholders in an architecture project? The full stakeholder landscape in AEC projects typically includes formal decision-makers (selection committee), budget controllers (CFO, finance committee), end users (department heads, occupants), regulatory authorities (planning commissions, zoning boards), community groups (neighborhood associations, advocacy organizations), internal champions (project advocates within the client organization), and gatekeepers (project managers, procurement officers who control information flow). The RFP typically identifies only the selection committee. The rest require active research.
How do you find hidden stakeholders before writing a proposal? Five primary sources: public records and meeting minutes (especially for institutional and public projects), organizational charts and leadership pages on the client's website, past project announcements (who was quoted, credited, or mentioned), professional network intelligence (subconsultants and contractors who've worked with the client), and the client contact themselves. Most project managers, when asked "who else in your organization will be involved in reviewing proposals?", will give a straight answer.
What's the difference between a stakeholder and a decision-maker? A decision-maker has formal authority to select the firm (they vote or sign). A stakeholder is anyone who can influence, approve, block, fund, or be affected by the project. In complex AEC projects, the stakeholders who shape the outcome often outnumber the decision-makers significantly. A community group with no formal vote can still kill a project. A board member who doesn't sit on the selection committee can still override it.
When should stakeholder research happen in the proposal process? Before any proposal writing begins. Stakeholder intelligence directly shapes what content to include, how to allocate emphasis across sections, and which concerns to address proactively. Firms that research stakeholders after writing the proposal are reverse-engineering a document that should have been informed by the intelligence from the start. The best firms maintain stakeholder intelligence continuously across client relationships, not per-pursuit. For guidance on how to structure and visualize this intelligence, see What Is Stakeholder Mapping and Why Architecture Firms Need It.
Related Reading:
About the Author
Kitae Kim
Experiential architect and co-founder of Foveate, passionate about spatial storytelling and empowering creative professionals through technology.
