A project can clear every legal hurdle and still be stopped cold by a community that simply refuses to live with it. The licence on the wall says you're allowed to operate; it says nothing about whether the people next door will let you. That second permission, informal, unwritten, and easy to lose, is what external stakeholder and community relations is really about.

The quick version

  • External stakeholders are the groups outside your org who can affect, or are affected by, what you do, communities, regulators, media, advocacy groups, customers and the wider public (Freeman, 1984).
  • A "social licence to operate" is their ongoing, informal acceptance of your activity. It isn't granted once; it's earned continuously through trust, and it can be withdrawn.
  • Engage at the right depth. Telling people what you've decided is not the same as consulting them, and neither is the same as deciding together. Match the level of engagement to how much real influence you'll actually share (the IAP2 Spectrum).
  • Start before you need them. Relationships built only in a crisis read as damage control. The credibility you spend in a hard moment is the credibility you banked in the easy ones.

The idea in depth

Begin with who counts. In Strategic Management: A Stakeholder Approach (Pitman, 1984), R. Edward Freeman defined a stakeholder as "any group or individual who can affect or is affected by the achievement of the organization's objectives." Most leaders read that and picture investors, customers and staff. But the definition deliberately reaches further, to the people who never sign your contracts and never sit in your meetings, yet absorb the side-effects of your work: the neighbourhood beside the new depot, the regulator watching the sector, the advocacy group that speaks for a harm you'd rather not discuss. These are your external stakeholders, and the relationship is asymmetric: they often have little formal power over you, right up until the moment they have all of it.

That asymmetry is exactly what the idea of a social licence to operate captures. The phrase entered business use in 1997, when mining executive Jim Cooney used it at a World Bank conference to describe the community acceptance a project needs beyond its legal permits. Researchers Ian Thomson and Robert Boutilier later turned the metaphor into something measurable, defining the social licence as the ongoing approval and broad acceptance of a project by its local community and stakeholders, grounded, in their account, in perceptions of trust and fairness in how the project treats them. They studied it closely at the Minera San Cristóbal mine in Bolivia, tracing how a company earned its social licence, lost it, and had to win it back. The practical shift is this: stop treating community acceptance as a box ticked at approval, and start treating it as a relationship you maintain. Like trust between people, it decays when neglected and collapses when betrayed.

"A social licence is granted by the community, not the regulator, and it can be revoked the moment trust runs out."

Knowing acceptance matters is one thing; knowing how to engage is another, and this is where most community relations quietly go wrong. The International Association for Public Participation's Spectrum of Public Participation lays out five increasing levels of engagement: inform, consult, involve, collaborate, and empower. Each carries a different promise. To inform is to keep people balanced and updated; to consult is to gather their feedback; to involve is to make sure their concerns genuinely shape the work; to collaborate is to make decisions together; to empower is to hand them the final call. The discipline lives in one decision: before any community engagement, work out honestly which level you're actually at, and promise only that. The cardinal sin is dressing up an inform as a consult: holding a "listening session" about a decision that's already made. People can smell a sham consultation, and nothing burns a social licence faster than being asked for input that was never going to be used.

flowchart LR
    A(["Inform: we'll keep you updated"]) --> B(["Consult: we'll seek your feedback"])
    B --> C(["Involve: your concerns shape the work"])
    C --> D(["Collaborate: we decide together"])
    D --> E(["Empower: you decide"])
The IAP2 Spectrum, each step shares more real influence than the last. Promise only the level you'll honour. Leaders Loop

And the honest limitation: none of this is a settled science, and two cautions matter. First, "the community" is a convenient fiction, it is rarely one voice. A neighbourhood holds residents who want jobs, residents who want quiet, and organised groups who claim to speak for both; engaging "the community" can mean amplifying whoever is loudest or best-resourced while a quieter, equally legitimate group goes unheard. Mitchell, Agle and Wood's salience model (Academy of Management Review, 1997) is a useful corrective here: it asks you to weigh a stakeholder's power, the legitimacy of their claim, and its urgency separately, rather than reacting to volume. Second, the social-licence literature grew out of extractive industries, mining, energy, infrastructure, and travels imperfectly to other sectors; treat it as a frame for thinking, not a formula. The goal isn't to manufacture consent. It's to make decisions that can survive daylight, and to bring the affected along honestly.

A worked example

Consider a logistics firm, figures here are illustrative, opening a 24-hour distribution centre on the edge of a residential suburb. Legally, it's clear: the site is zoned for it and the permits are in hand. The project lead, Marcus, treats community relations as a formality and sends a glossy flyer announcing the opening date. That's pure inform, and it lands badly. Residents who first hear of overnight truck movements from a leaflet conclude, reasonably, that their concerns were never wanted. A local group forms, a councillor takes up the cause, and the launch is now a fight.

Rewind, and play it at the right depth. Months earlier, Marcus maps his external stakeholders, nearby residents, the local council, the school on the truck route, a resident's association, and decides this calls for involve, not inform. He holds a genuine session before the route is fixed, promising that concerns will shape the plan, and means it. Residents raise the school run; the firm reroutes night deliveries and commits to a noise cap, publishing both. That's the social licence being built deliberately: not by spin, but by visibly trading a little operational convenience for a lot of trust. When a delivery driver later breaches the curfew, the relationship holds, because the firm has credibility in the bank and a known channel to raise it. The first version had a permit and no permission. The second had both. The difference cost Marcus a few early conversations and bought him a centre that could actually run.

flowchart TD
    A(["Map external stakeholders: who is affected, who can affect us"]) --> B(["Choose the honest engagement level per group"])
    B --> C(["Engage early, before the decision hardens"])
    C --> D(["Trade something real: a change they can see"])
    D --> E(["Keep the channel open; the licence is ongoing"])
Community relations as a continuous loop, not a launch-day announcement. Leaders Loop

Frequently asked questions

What's the difference between a social licence and a legal licence?

A legal licence is the formal permission granted by an authority, a permit, a zoning approval, a regulatory sign-off. A social licence is the informal, ongoing acceptance of a community and other stakeholders. You can hold the first and lack the second, which is how fully-permitted projects still get stalled by protest or political pressure. The legal one is granted once; the social one has to be re-earned continuously.

How do I engage a "community" that doesn't speak with one voice?

Accept that it won't, and resist treating the loudest group as the whole. Map the distinct interests, residents who want jobs, those who want amenity, organised advocates, and engage them as the different stakeholders they are. Mitchell, Agle and Wood's (1997) lens helps: weigh each group's power, the legitimacy of their claim, and its urgency, rather than reacting only to who shouts. Your job is to surface the quieter legitimate voices, not just manage the organised ones.

When should I start? We're not in a crisis.

That's precisely when to start. Relationships built only when you need something read as transactional, and credibility is hardest to manufacture under pressure. Engaging early, before a decision has hardened, is also the only way involve or collaborate is even possible, once the plan is fixed, all you can honestly offer is inform. The trust you'll draw on in a hard moment is the trust you deposited in the calm ones.

Isn't this just PR with a nicer name?

It becomes PR the moment the engagement is decorative, a consultation whose result was predetermined. Genuine community relations changes the decision sometimes; that's the test. The Thomson–Boutilier framing rests on perceived trust and fairness, and people are good at detecting their absence. If nothing a community says can alter what you do, you're informing, not engaging, and you should at least be honest about which one it is.

What's the single most common mistake?

Over-promising on the engagement level. Calling a session a "consultation" or "collaboration" when the real intent is to inform a settled decision. It feels generous in the moment and corrosive afterwards, because the gap between the promise and the reality is exactly where trust dies.

Related in the Toolkit

Before you engage, you need to know who is actually out there and how much each can move, that's stakeholder mapping & analysis. And much of community relations is the patient work of building coalitions among groups who each hold a piece of your social licence.

Where to go next