Consent management and documentation is about more than getting your contacts' ”yes”. It is about keeping the overview over time, when different contacts have consented to different wordings, in different contexts.
10. august 2026
When the overview of consents is missing, it is hard to know whether the consent that was given actually covers what you are using it for today. Whether it still applies – and if not, whether you can easily find what needs updating.
A consent can be given in many ways and many places, for example:
On signing up to a newsletter.
In connection with a competition.
When a new member registers.
When an adviser sends their first email.
Via an app, a form on the website or a call to customer service.
In other words, consent is typically spread across systems, points in time and wordings.
It also means that for many organisations, when we ask which specific version of a consent text a specific contact said yes to in which specific context, the answer starts with ”… We think so”.
In the most common email systems it is simply not possible to see anywhere what text an individual contact consented to. And if the text is changed, there is no record of who saw which version.
Nor is the context in which the consent was given recorded anywhere. That can cause problems when a company runs a competition, for instance, and collects consents through it. Because in the context of a competition there is a legal requirement that the primary text states what marketing you are agreeing to by taking part.
One of the challenges we see again and again is what happens when a consent text changes. Perhaps the wording has been sharpened legally. Perhaps a new purpose has been added. Perhaps a channel has been added. When that happens, a series of questions arises:
Does the consent already given also cover the new wording?
Does the change require everyone to actively accept again?
Or is passive acceptance sufficient?
And who has consented to which version?
Without a system that handles versioning and source documentation, these questions are hard to answer precisely. And when the GDPR audit or an internal compliance review comes knocking, „We think so“ is not enough.
For organisations operating across borders, further challenges can arise. Here you have to keep your wits about you when not only Danish but all international requirements have to be met as well.
The larger the organisation, the greater the risk of losing the overview, and the more important the right consent management and documentation becomes.
Consent management is about more than complying with the GDPR and marketing law. A consent is also a promise.
When a union member signs up to a newsletter about inspiration for working life, they trust that is what they will get – and not something else. When a bank customer accepts emails from an adviser, there is likewise an expectation that contact happens on the terms they said yes to. That they will not suddenly get emails from other senders.
If it then turns out the organisation cannot document precisely which text was accepted, when and through which channel, it is hard to ensure the promise is actually kept. That much is clear. And it is not only a question of law, but of trust.
Unions and banks, which work with many different contact points and different types of communication, feel this particularly. The relationships are typically long-lasting. Contact can be frequent. And the people you communicate with have chosen to be there. They deserve an organisation that at minimum knows what was agreed, and shows that it respects it.
It is worth saying that the problem is not always solved by going big. We have seen organisations invest considerable resources – both time and money – in dedicated, complex consent management systems. And the thinking behind it is entirely right.
But once such a system is in place, it often turns out to be rigid: hard to adapt, hard to integrate with the rest of the communication, and hard to change when needs shift. So instead of solving the challenge, the solution has simply become a new form of complexity. Where the system takes centre stage rather than the consent.
There is a difference between a system that documents consents and a system that makes it possible to handle them in practice – in the daily communication, in the employee's workflow, in what the customer or member actually meets.
A structured approach to consent management does not have to be overwhelming. What in our experience typically makes a difference is a single overview of consent wordings, where changes are locked as soon as the first person accepts them, so the history is preserved:
A precise log recording the time, source and channel of every individual consent.
Clear documentation of what the specific person actually said yes to – not just what the system currently says.
Transparency both for employees and for the customer or member themselves.
That last point is important. When a person can go in and see exactly what they have consented to, when and through which channel – and adjust it themselves – it becomes more than a compliance element. It becomes a way of showing respect.
At Yulsn we build consent handling in as an integrated part of our marketing platform. That means consent management is not a separate system living alongside the communication – it is part of it.
We typically work with organisations that already have part of the puzzle in place: some things are recorded in internal systems, some happen at sign-up, some are handled manually. Our job is then to map what is missing and build the structure that ties it all together – in a way that serves both the compliance requirements and the communication our customers actually want to run.
Concretely, we make it possible for companies to document which different consent texts a specific contact has seen, and which specific version of the text, in which specific context, a specific contact said yes to and when.
Our aim is that the customers we work with can answer unambiguously:
Can your current approach genuinely stand up to the legal requirements? And – not least – to the expectations that sit in the relationship between you and the people you communicate with?