A municipal records modernization lists internal legal counsel and an external contracted UX firm as stakeholders. How should the associate BA distinguish those relationships?

Stakeholder analysis on a municipal records modernization must distinguish relationship type, not merely meeting attendance. Internal legal counsel is typically an employee stakeholder inside the city’s organizational boundary, with different escalation paths, confidentiality norms, and employment obligations than an external contracted UX firm. Classifying counsel as internal and the UX firm as external contracted stakeholder correctly reflects how engagement, contracts, access to sensitive records, and closeout differ even when both parties sit in the same workshop.

Treating both as identical internal stakeholders because they attend the same workshops fails conceptually because attendance does not change employment or contractual status; conflating them blurs access controls and engagement plans. Treating both as external vendors because legal advice is always outsourced fails when counsel is on staff; it misstates the internal relationship and may misroute escalation. Excluding the UX firm from stakeholder maps until a permanent hire replaces them fails because contracted specialists who influence design are stakeholders now; postponing recognition creates blind spots during elicitation and acceptance.

Exam caveat: CAPM stakeholder classification turns on influence and interest plus organizational relationship—not on whether people share a calendar invite. Operational check: update the records-modernization stakeholder register with internal versus external tags for legal counsel and the UX firm, align engagement and NDA or contract touchpoints accordingly, and verify both appear in communication plans before the next requirements workshop.