Asking employees about their licences
Ask a seat holder one question that can be answered with one click, tell them what your records show, and promise that nothing changes until they have answered. Offer two clear answers, keep and release, and a third for people who use the tool rarely. Send one reminder after a few days, then pass the question to the manager if that was announced, and never remove a seat because of silence. Keep a do-not-contact list and check it when a message is sent, and involve the works council before the first question goes out.
The way to ask an employee about a licence is one question, one click, and a promise: nothing changes until you have answered. The question is needed because activity data has gaps, as described in how to find unused software licences, and because only the holder knows whether a tool they open twice a year is one they cannot do without.
When to ask and when not to
| Situation | Ask? |
|---|---|
| Seat without activity for longer than the threshold | Yes |
| Seat on a higher tier, usage below the threshold or not measured | Yes, about the tier |
| Vendor reports no activity data at all | Yes, it is the only way to know |
| Contract renews soon and you want to hear from users | Yes, as a survey that changes no individual seat |
| Holder has left the organisation | No. See licences at offboarding |
The wording
A message that works looks like this. The parts in brackets come from your records, per recipient.
Subject: Quick question about your [application] seat
Hi [first name],
we are reviewing our software licences, and our records show
you last used [application] on [date].
Do you still need your seat? One click is enough. If you use
another tool instead, or only need it now and then, a sentence
about that helps a lot.
Nothing changes until you have answered.
Thanks,
[sender]The rules behind it:
- One question. A message that asks about three tools gets no answer about any.
- Say what you know. "Our records show you last used it on 3 September" is a fact the holder can correct. "You do not seem to use it" is an accusation.
- A colleague writes to a colleague. No urgency, no deadline threat, no mention of cost per head. Nobody should feel their job or their tools are under review.
- Every figure and date comes from the record. Do not let the person or the model drafting the text write a date or a number freehand.
- Invite a sentence. "I use the other tool instead" or "only at quarter end" tells you more than the click.
Different openings for different holders
| What the records show | How the message opens |
|---|---|
| Never used | It may have been set up for you and never needed |
| Used before, not recently | Our records show you last used it on a given date |
| Used lightly | Our records show a small number of actions in the last 30 days; do you need your own seat for that? |
| In active use, the question is about the tier | Do you use what the higher licence adds? |
| No usage data | The application does not tell us how much it is used, so we are asking |
The answers
Two answers settle the question: "Yes, I need it" and "No, remove it". A third, "I rarely use it", is worth offering, because it finds the people for whom occasional access or a lighter licence would do, the subject of right-sizing SaaS plans.
| Answer | What follows |
|---|---|
| Yes, I need it | The seat stays. Record the answer and do not ask about this seat again for several months |
| I rarely use it | The seat stays for now. Check whether a lighter tier or a shared arrangement fits |
| No, remove it | The seat goes on the list for removal, with the name and date of the answer |
Tell the holder what was recorded. A reply in free text can be sorted into one of the three by a person or a model; a clicked button always outranks an interpretation.
One reminder, then the manager
- Day 0: the question goes out.
- After a few days, for example three: one reminder, the same question. If the next step is the manager, the reminder says so, with the manager's name and the date.
- A few days later, for example four: the manager gets the question about the person, with the same answers: they need it, they rarely use it, remove it. The answer is recorded for the holder's seat together with who gave it.
- At the end: the campaign closes. Whoever stayed silent is noted as silent, and a person decides.
Whether to involve managers is a choice to make before sending, not after. Someone who was never told the question would go to their manager will rightly feel reported. And silence is never a release: the promise in the message was that nothing changes without an answer.
Who is not asked
Keep one do-not-contact list for the organisation: typically the executive team, and anyone excluded by policy or by agreement with the works council. Three points make the list reliable:
- It is checked at sending, at every reminder and before a manager is written to, not only when the draft is written.
- A manager on the list is treated as no manager. The question about their report is not passed on to them.
- The draft shows who was left out, so the person approving it sees the gap.
Add a cooling-off period: nobody gets a second question within, say, two weeks of the first.
Works council and data protection
In Germany, evaluating when named employees last used an application can touch the co-determination right of the works council for technical systems that monitor behaviour or performance, section 87(1) no. 6 of the Works Constitution Act. The last sign-in of a named person is also personal data within the meaning of Article 4(1) of the GDPR. In practice: show the works council and the data protection officer the message, the data it uses, who sees the answers and what happens after silence, before the first campaign. Put on record that the check serves the licence inventory and no assessment of performance. This is general information and no legal advice.
What goes wrong
- Asking too often. The third message in a month is ignored, and so is the fourth, which mattered.
- Removing after silence. The first person who loses a tool they needed ends the programme.
- A survey nobody acts on. If released seats are still assigned two months later, people learn that answering is pointless.
- No record. Without name, date and answer per seat, the same question is asked again next year.
How Cureman does it
Cureman drafts the question for each situation in the table above, by email or Slack. The wording is drafted by a model or taken from a fixed template; what is specific to a recipient (name, last activity, usage, tier) is filled in from the records, and a draft that states a figure of its own or contains a link is replaced by the template. Every message carries the sentence that nothing changes until the holder has answered. A person approves the campaign together with its reminder and, where chosen, the message to the manager, which is why those may go out by themselves later. Holders answer with one click on a page of their own; free-text replies are interpreted and filed, and a clicked answer outranks the interpretation. The do-not-contact list is checked at drafting, at sending and before every reminder and message to a manager, and people another campaign wrote to recently are skipped. Nothing is removed because somebody did not answer. See the page about licence optimisation.
Questions and answers
How do you ask employees whether they still need a software licence?
- With a short message that names the application, says what the records show about their last use, asks one question and can be answered with one click. It states that nothing changes until they have answered. A sentence of free text is invited, because the reason behind an answer is often worth more than the answer.
What if an employee does not answer?
- Send one reminder after a few days. If the plan says so and the reminder announced it, the question then goes to the person's manager, who gets the same answers worded about the employee. If nobody answers, the silence is recorded on the seat and a person decides. A seat is not removed because somebody did not reply.
Who should not be asked about their licences?
- Whoever the organisation has decided not to contact, typically the executive team, and anyone covered by an agreement with the works council. These addresses belong on one do-not-contact list that is checked when a message is sent, when a reminder goes out and before a manager is written to. Their seats are still reviewed, by a person, directly.
Does the works council have to be involved in a licence usage check in Germany?
- It can be necessary. Evaluating when individual employees last used a tool can fall under the co-determination right for technical systems that monitor behaviour or performance in section 87(1) no. 6 of the Works Constitution Act. Involve the works council and the data protection officer before the first campaign. This is general information and no legal advice.
How often can the same person be asked?
- As rarely as possible. Bundle questions, leave at least two weeks between two messages to the same person, and do not ask again for several months about a seat its holder said they need. People who are asked every few weeks stop answering.