A lot of engagement programmes run on an email marketing tool and a form builder. It's a reasonable place to start. Mailchimp, Constant Contact and Campaign Monitor are good at what they were built for, which is sending well-designed email to a list of people and telling you who opened it.
The trouble starts when that list quietly becomes the stakeholder record. Nobody decides to do this. It happens because the list is where the names are, and the names are what you need.
Can you use an email marketing tool as a stakeholder database?
You can hold names and addresses in one, and for a small, short project that may be enough. But an email marketing tool records what you sent and who opened it, not who you met, what they think, what you promised them or how their position has changed. If you need to evidence engagement rather than measure a campaign, the gap shows up fast.
Here are seven signs you've crossed that line.
Mailing list or stakeholder database, side by side
| What you need to answer | Email marketing tool | Stakeholder database (SRM) |
|---|---|---|
| Who did we email, and did they open it? | Yes | Yes |
| Who did we meet, call or run an event with? | No | Yes, logged as activities against the record |
| What is this stakeholder's influence, interest and sentiment? | No | Yes, scored and tracked across project phases |
| What did they raise, and what did we promise in response? | No | Yes, as tracked issues and commitments |
| Which organisations and groups are they affiliated with? | Tags only | Yes, modelled relationships across organisations and projects |
| Where are they, geographically? | Basic fields | Yes, mapped, with boundary and radius targeting |
| Can we produce the full engagement history for one person on request? | Send history only | Yes, the complete record |
| Does it hold up as consultation evidence? | No | Yes, date-stamped and exportable |
Tractivity, the UK stakeholder relationship management platform, sits in the right-hand column: stakeholder records, mapping, activities, issue and commitment tracking, surveys, events and mailshots in one system, with 150+ pre-built reports over the top. It costs £9,495 a year for the base licence plus £500 per additional user, with no caps on records, mailshots or survey responses. The Engage-360 public portal is a separately priced module.
1. You know who you emailed, but not who you met
This is the clearest sign. Open your list and pick a stakeholder. You can see the six newsletters they received and that they opened four. You cannot see the site visit, the objection they raised at the parish council, the phone call from their agent, or the meeting where your project director agreed to move a compound.
Email is one channel. It is rarely the channel where anything important happens. A record built around sends captures the least consequential part of the relationship in perfect detail and the rest not at all.
2. Everything you know about a stakeholder fits in a spreadsheet column
Email tools give you tags and a few custom fields. That works for 'newsletter' and 'events'. It falls apart the moment you need to know that this person is a statutory consultee, moderately supportive, high influence, low interest, affiliated with two community groups, and has shifted from negative to neutral since the design change.
Influence and interest aren't tags. They're scores that move, and the movement is the insight. Being able to say 'this group's sentiment improved after the February exhibition' is a different capability from being able to say 'this group is tagged February exhibition'.
3. Unsubscribes are the only sentiment you track
In an email tool, the sentiment signals available to you are opens, clicks and unsubscribes. All three measure interest in your email, not in your project.
Someone who reads every update and objects strenuously at every opportunity looks identical, in that data, to someone who reads every update and quietly supports you. Meanwhile a genuine sentiment record captures what people actually said, tagged by issue and scored positive, negative or neutral, so 40 comments about construction traffic become one visible, reportable issue rather than 40 unread replies.
4. Replies land in a person's inbox, not on the record
When you send from a marketing tool, replies come back to whoever's address is on the send, or to a no-reply address that swallows them.
That's the point where the record breaks. The stakeholder replied, the reply is real engagement, and it now lives in one person's Outlook. When that person changes role, it's gone. On a project of any length, this is how institutional memory is lost, one inbox at a time.
The fix is unglamorous: every inbound and outbound message logged automatically against the stakeholder it came from, in a shared record the team can see. Tractivity does this two ways, capturing anything sent from the platform against the record, and connecting an existing shared mailbox so a generic project inbox is administered inside the system rather than beside it. Sender addresses are configurable, and mail sent through the platform uses SPF and DKIM authentication so it reaches inboxes rather than spam folders. Before a mailshot goes out, the system validates every stakeholder email address and checks that the stakeholder has opted in.
5. The list is organised by campaign, not by relationship
Email tools are built around audiences and segments. Over time you accumulate 'CWWTPR residents', 'Phase 2 landowners', 'Parish councils', 'Newsletter 2025' and a dozen more, and the same person is on five of them under three slightly different email addresses.
That's fine for sending. It's useless for answering 'what is our relationship with this person', because there is no single 'this person' to ask about. A stakeholder record models the person once and links them to every project, organisation, affiliation and activity they touch. It's the difference between a set of lists and a picture of a network.
6. You can't answer 'what did we promise them?'
This is the question that ends careers on major projects, and no email marketing tool can answer it.
Commitments are made constantly during engagement: we'll keep you informed before works start, we'll look at the access issue, we'll fund the survey. Some end up in formal agreements. Most are made verbally and remembered vividly by the person they were made to.
Unless a commitment becomes a tracked record with an owner and a status, it exists only in the memory of whoever made it. EDF's teams on Hinkley Point C and Sizewell C log and tag every issue and comment in Tractivity, close to 30,000 of them, and maintain a 100% response rate on stakeholder issues. That number isn't a vanity statistic, it's what a complete commitment record looks like when the alternative is a regulator asking you to prove it.
7. When someone leaves, the relationship leaves with them
Ask yourself what happens if your most experienced engagement officer resigns tomorrow. In a mailing-list set-up, what survives is the list. What doesn't survive is everything that made them good at the job: who to call first, who's still annoyed about the 2023 route change, which councillor prefers a phone call to an email.
Anglian Water coordinates engagement with more than 13,000 stakeholders across day-to-day operations and three major capital programmes, and National Grid has more than 400 users working in one shared record. At that scale, individual memory isn't a viable system. The record has to be the team's memory, not a supplement to it.
What email tools are genuinely good for
None of this is an argument against Mailchimp, Constant Contact or Campaign Monitor. They're well-built products for marketing to an audience, and if what you're doing is broadcasting a newsletter to subscribers who asked for it, they'll do that better than most.
The mismatch is one of purpose. Marketing tools optimise for reach and response rate. Engagement work is judged on whether you can demonstrate who you consulted, how, what they said and what you did about it, sometimes years later, sometimes to a regulator or a court. The data-protection bar is its own question again, which we've set out in GDPR-ready stakeholder databases. Those are different jobs, and the second one needs a record rather than a list.
It's the same reasoning that applies to generic CRMs, which we've written about in more detail in the difference between CRM and SRM, and to spreadsheets, where a University of Hawaii study found 94% contain errors, roughly one in every 20 cells. If a spreadsheet is the other half of your set-up, the spreadsheet alternatives are worth reading alongside this.
If several of these sound familiar
Start by writing down the three questions you most often get asked that your current set-up can't answer. For most teams it's some version of: what have we said to this person, what did we promise, and can you prove it.
Then look at what it would take to answer them. Usually the answer isn't a better email tool. It's moving the record to the place where the engagement actually happens, and letting the email go out from there.
If you'd like to see what that looks like with your own stakeholder data, book a demonstration.
FAQ
You can store names, email addresses and a few custom fields in Mailchimp, and for a small, short-lived project that may be enough. What it can't do is record meetings, calls, issues raised, commitments made, influence and interest scores, or sentiment over time. If you need to evidence engagement rather than measure a campaign, you'll outgrow it quickly.
A mailing list records who you sent something to and whether they opened it. A stakeholder database records the relationship: who the person is, which organisations and projects they're connected to, every interaction across every channel, what they raised, what you promised, and how their position has changed. One measures distribution, the other evidences engagement.
An email tool will usually track marketing consent and unsubscribes well. That's a narrower thing than UK GDPR compliance for an engagement programme, which also means being able to produce everything you hold about an individual on request. If the meetings, calls and feedback live outside the tool, a subject access request can't be answered from it.
One record per stakeholder that spans projects and teams, activity logging across every channel, influence, interest and sentiment tracking, issue and commitment management, GDPR-safe communications with an audit trail, geographic targeting, and reporting you can hand to a board or a regulator without rebuilding it by hand.
Export the list, then decide what else needs to come with it: meeting notes, complaint logs, consultation feedback and any commitments recorded elsewhere. Most of the work is consolidation rather than migration. Tractivity imports stakeholder data as part of onboarding, which typically runs four to six weeks depending on how quickly the data is available.
