If political advocacy is to be traceable, it must be treated as structured data, not as meeting notes in inboxes and spreadsheets. In practice you need five building blocks in the same model: stakeholder (who you want to reach), issue (what you want to achieve), position (where the stakeholder stands on the issue), meeting (what actually happened) and commitment (what you promised, and what you were promised). A spreadsheet handles one of these dimensions at a time, and a membership system is built around membership and dues, not around issues and positions. A CRM platform such as Dynamics 365 can model all five, but not in the standard sales setup: the objection that Dynamics is the wrong tool for stakeholder management applies to the standard setup, not the platform. Our recommendation is therefore to start with the data model, not the tool: define the five building blocks, clarify the privacy basis for position data, and then decide whether to build on the platform you have or buy a ready-made domain solution. The rest of this article walks through both choices.
Advocacy tracking is a data model, not a note archive
For interest organisations and NGOs, political advocacy is a core activity: consultations, committee hearings, meetings with politicians and officials, alliances with other organisations. The work is long term and relational, and it produces information that quickly becomes unmanageable in email and meeting notes: who said what, in which meeting, about which issue, and what did we promise to follow up? That holds whether you call the work stakeholder mapping, stakeholder management or advocacy.
The reason the overview breaks down is rarely lack of discipline. It is that the information is inherently relational: a meeting concerns both a person and an issue, a position belongs to the combination of a stakeholder and an issue, and a commitment binds your organisation to a follow-up with a deadline. Five building blocks recur in every advocacy operation we have seen, whatever the tool.
| Building block | What it is | The question it answers |
|---|---|---|
| Stakeholder | A person or organisation you want to influence or cooperate with: politician, adviser, ministry, allied organisation | Who are we in contact with, and who knows whom? |
| Issue | A political question you are working on, with phases and deadlines: consultation, committee stage, decision | Which issues are we working on, and where do they stand? |
| Position | The link between a stakeholder and an issue, with direction, source and date | Where does each stakeholder stand on each issue, and has it changed? |
| Meeting | Completed and planned contact points, linked to both stakeholder and issue | Who has talked to whom, about what, and when? |
| Commitment | What you promised and what you were promised, with an owner and a deadline | What do we owe, what are we waiting for, and who follows up? |
Does your organisation lose track after each round of consultations? We run a half-day working session where we map your issues, stakeholders and follow-up routines against the five building blocks, and give you a concrete recommendation: extend what you have, or establish a dedicated structure.
Why the spreadsheet and the membership system fall short
The spreadsheet is where most organisations start, and it works as long as one person owns the whole picture. It stops working the day the questions become relational. A sheet of contacts cannot answer which stakeholders you have met about a given issue in the last six months, because the meeting, the issue and the person live in different columns, different tabs or different files. Every new dimension multiplies the maintenance, and version conflicts arrive as soon as two people edit at once.
The membership system is the other natural candidate, and it is a fair thought: it already holds people, organisations and communication. But a membership system is designed around a different core: membership, dues, enrolment and member communication. Advocacy tracking concerns external stakeholders who are not members, issues with political phases, and positions that change over time. Some membership systems can be extended part of the way, but without dedicated structures for issue, position and commitment, the advocacy work ends up as free text in note fields, and free text does not lend itself to reporting across issues. We cover the underlying architecture question, one platform or several specialised systems, in the article on membership system or CRM platform.
The consequence of both workarounds is the same: the organisation's political memory lives in individuals. When a subject lead changes jobs, the contacts, the half-promises and the context disappear with them.
"What the organisation remembers is not the same as what the organisation knows. After an election or an annual meeting, the relationship history leaves with the people who carried it, if it only lives in inboxes."
Cartagena, based on CRM and Dynamics 365 deliveries to membership and interest organisations in Norway
Is Dynamics the wrong tool for stakeholder management?
If you search internationally for stakeholder management software, you will meet the argument that a CRM like Dynamics 365 is the wrong tool. In a comparison published in June 2026, the Canadian vendor Jambo argues that the standard Dynamics data model of leads, opportunities, accounts and deals works against stakeholder teams, because stakeholder relationships never close the way a sale does. The piece is vendor content written to sell a competing product, and should be read as that. But the core observation is fair, and it matches what we see: the standard sales setup assumes a linear pipeline towards a transaction, and political relationships are not transactions.
What the objection misses is the layer beneath the app. Dynamics 365 runs on Dataverse, and Microsoft's own documentation describes how Dataverse lets you define your own tables, relationships and business rules with little or no code. The five building blocks are five tables and the relationships between them. The question is not whether the platform can model advocacy work. It can. The question is who should define and maintain that model, and that is a real choice with real costs on both sides.
| Dimension | Ready-made domain solution (SRM tool) | Platform build on Dataverse |
|---|---|---|
| Time to start | Short: the model exists on day one | Longer: the model must be defined first. A reference model shortens this considerably |
| Data model | Predefined by the vendor, limited adaptation to Norwegian political processes | You control the definition and can adapt it to consultations, committees and Norwegian practice |
| Connection to member and donor data | Separate system: integration must be built and maintained | Same foundation: a politician who is also a member or donor is one record, not three |
| Ongoing ownership | The vendor maintains the solution and the roadmap | You carry the stewardship responsibility, alone or with a partner. This is a real, recurring cost |
| Reporting | Ready-made engagement reports out of the box | Built in Power BI against your own data, alongside member and finance reporting |
Both columns are legitimate. A ready-made domain solution is the right answer for an organisation where advocacy is an isolated function with no need to share data with membership, donations or casework. The platform build is the right answer where the same people appear in several roles and the organisation already runs, or is moving towards, Dataverse as its foundation. The same trade-off applies across the whole membership domain, and we go deeper into it in the article on ready-made solution or your own platform.
Positions are special category personal data
One thing must be in place before any tool discussion: registering a person's political opinion is processing of special category personal data under GDPR Article 9, and the Norwegian Data Protection Authority is clear that such processing requires a separate legal basis in addition to the ordinary one.
In practice, the important distinction runs between what is public and what is inferred. A position a politician has manifestly made public, in a hearing, a vote or a signed opinion piece, falls under the exception in Article 9 for data manifestly made public by the data subject. An internal note guessing what someone privately thinks does not. The exception also only lifts the Article 9 prohibition; an ordinary legal basis must still be in place. Our advice is simple: record positions with a source, prefer the public record, be restrained with inferred assessments, and document the assessment you have made. This is exactly where a structured model helps, because a position field with a source reference is far easier to audit than free text spread across documents and email.
How to structure the follow-up after a conference
The value of advocacy tracking is most visible right after an intensive week. Arendalsuka is the Norwegian extreme: the organisers describe around 1 900 events and 200 stands over five days. An organisation that participates actively comes home with dozens of conversations spread across several people, and the routine below is what decides whether those conversations become organisational knowledge or private memories. It is the same routine after a consultation deadline, a national congress or a sector conference.
- Gather the notes the same week. Set a fixed internal deadline while memory is fresh. The format does not matter yet; completeness does.
- Create or update the stakeholders you actually met. Not the business cards: the people and organisations the conversation actually involved, with role and affiliation.
- Link every meeting to an issue. A conversation without an issue is a social event. If it mattered, it concerned something you are working on.
- Register commitments with an owner and a deadline. Both directions: what you promised to send, and what you were promised. This list is the follow-up plan for the autumn.
- Update positions where the conversation gave new information. With a source: what was said, by whom, in which setting.
- Report to management from the data, not from memory. Meetings per issue, new commitments, changed positions. When the report comes out of the structure, the structure gets maintained.
Pattern: A recurring situation in the organisations we work with: three subject leads attend the same conference week, each meets politicians about the organisation's main issue, and each writes notes in their own OneNote. In October, management asks what the parliamentary group actually signalled. The answer exists, but in three versions, none of them linked to the issue. The real cost shows up later, in the follow-up meetings that were never booked because nobody owned the commitments.
From reference model to daily use on Dynamics 365
Cartagena has built the five building blocks as a reference model on Dataverse: Political Compass, part of our accelerator for member and interest organisations. A reference model is not a finished product you install; it is a proven starting point that is adapted to your issues, your political arenas and your privacy assessments in each implementation. The point of the accelerator is to skip the blank-sheet phase, not to skip the adaptation.
The architectural argument for placing advocacy tracking on the same foundation as member data is covered in our article on a data platform for membership organisations, and the broader service context on our page about Dynamics 365 for membership organisations. For nonprofits currently running Microsoft's own nonprofit module, the timing question is real: the retirement of Fundraising & Engagement means many organisations are already reviewing their Dataverse foundation, and the advocacy model belongs in that review.
Whichever direction you choose, the sequence matters more than the tool: data model first, privacy basis second, then the platform decision, and only then screens and reports. Organisations that start with the tool tend to get a system shaped like a demo. Organisations that start with the model get a system shaped like their work.
Frequently asked questions about advocacy tracking
What is advocacy tracking?
Advocacy tracking is the systematic recording of your organisation's political work as structured data: which stakeholders you are in contact with, which issues you are working on, where each stakeholder stands on each issue, which meetings have taken place, and which commitments have been given and received. The point is that the overview should survive staff turnover, and that management can answer who has talked to whom about what, without searching inboxes and old notes.
Can we use our membership system to track advocacy work?
Rarely in full. A membership system is built around membership, dues and communication with your own members, while advocacy work concerns external stakeholders, issues and positions that change over time. Some systems can be extended part of the way, but without dedicated structures for issue, position and commitment, the work ends up as free text in note fields. Consider whether the data should live on the same foundation as your member data, rather than in yet another standalone tool.
Is Dynamics 365 the wrong tool for stakeholder management?
The standard sales setup is, and there the criticism from vendors of ready-made stakeholder tools has a fair point: sales pipeline, leads and opportunities fit poorly for relationships that never close. But the platform underneath, Dataverse, lets you define your own tables for stakeholder, issue, position, meeting and commitment. The choice is between a ready-made domain solution that starts fast, and a flexible foundation that shares data with the rest of the organisation. Both alternatives have real advantages and real costs.
Is it lawful to register politicians' positions?
Political opinion is a special category of personal data under GDPR Article 9, and processing requires a separate basis in addition to the ordinary legal basis. Positions a politician has manifestly made public, for example in a hearing or a signed opinion piece, stand differently from internal assumptions about what someone privately thinks. Record the public, be careful with the inferred, and document your assessment. If in doubt, involve a privacy adviser in the assessment.
How do we get started after a conference?
Set aside time the same week, while memory is fresh. Gather the notes from everyone who attended, create or update the stakeholders you actually met, link every meeting to the issue it concerned, and register commitments with an owner and a deadline. Update positions where the conversation gave new information. Finally, produce a short summary for management from the data, not from memory. The routine is the same after a hearing, a national congress or a conference like Arendalsuka.
Sources
- Jambo (vendor content, published June 2026, updated July 2026): Dynamics CRM vs a stakeholder CRM
- Microsoft Learn: What is Microsoft Dataverse?
- Lovdata: GDPR Article 9, processing of special categories of personal data
- The Norwegian Data Protection Authority: On special categories of personal data
- Arendalsuka (official site): This is Arendalsuka
Sources checked 24 August 2026.
Is the decision heading to your board or management team? We prepare a written decision basis that weighs the three directions against each other: extending the membership platform you have, building on Dataverse with our Political Compass reference model as the starting point, or choosing a ready-made domain solution. The privacy assessment for position data is part of the deliverable.