# What staff ask stays theirs.

For the works council. You have the right of consent. Below is what goes to the organisation and what never does, each rule with the clause that binds it.

> Does anyone read what colleagues ask?

- [Works Councils Act (WOR), art. 27(1)(k) and (l), the right of consent](https://wetten.overheid.nl/jci1.3:c:BWBR0002747&artikel=27)
- [AI Act, art. 5(1)(f), no emotion recognition at work](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32024R1689)

## Whoever isn’t watched dares to ask more.

A question never becomes a judgement. So your organisation sees where knowledge is missing.

Stops at the line

- Rule 1

  Care worker conversations

  No one in the organisation opens the care worker’s conversations, management included.

  Information letter and model consent request art. 4, condition 1

  > Information letter and model consent request art. 4, condition 1 [Read it](https://axiomatic.digital/policies/works-council-consent-request.en.pdf)
  >
  > “No one in the organisation reads a member of staff’s conversation with Inora, *management included*.”

  stops

- Rule 2

  How often, how fast and when staff work

  No figure about one member of staff, for anyone in the organisation.

  Information letter and model consent request art. 4, condition 2

  > Information letter and model consent request art. 4, condition 2 [Read it](https://axiomatic.digital/policies/works-council-consent-request.en.pdf)
  >
  > “No one in the organisation gets *a figure about one member of staff*: not how often, how fast or when they work.”

  stops

- Rule 3

  A judgement of the care worker’s work

  Inora assesses no one and gives no one a score.

  Privacy statement Staff conversations

  > Privacy statement Staff conversations [Read it](https://axiomatic.digital/en/trust/privacy#staff-conversations)
  >
  > “Inora assesses no one and gives no one a score.”

  stops

- Rule 4

  Mood

  Inora infers no emotions, from voice or face. The AI Act prohibits it.

  Inora and the EU AI Act What Inora never does

  > Inora and the EU AI Act What Inora never does [Read it](https://axiomatic.digital/en/trust/quality-and-clinical#what-inora-never-does)
  >
  > “It infers no emotions or mood of staff, *from voice or face*. Article 5(1)(f) prohibits that.”

  stops

- Rule 5

  What Axiomatic reads on request

  Only on a written request, for an incident or a complaint, logged, and the care worker is told; never in an outage. They are told of a legal demand too, unless the law forbids it. The requester gets a finding about Inora, never what they asked.

  Information letter and model consent request art. 4, condition 5

  > Information letter and model consent request art. 4, condition 5 [Read it](https://axiomatic.digital/policies/works-council-consent-request.en.pdf)
  >
  > “In an outage or security incident Axiomatic examines the system logs and the answer record, *never a conversation*.”

  > Information letter and model consent request art. 4, condition 5 [Read it](https://axiomatic.digital/policies/works-council-consent-request.en.pdf)
  >
  > “If the law demands a conversation, Axiomatic gives only what the demand asks, logs it, and *the member of staff is told*, unless the law forbids it.”

  > Privacy statement Staff conversations [Read it](https://axiomatic.digital/en/trust/privacy#staff-conversations)
  >
  > “Whoever made the request gets a finding about Inora, *never what the member of staff asked or read*.”

  stops

Crosses, and how

- Rule 6

  What the care worker’s team asks about

  per team of five or more

  The monthly report: subjects and counts, without a single name. The topic is set together with the answer, without names; no person reads along. Per team to the team lead and the works council; the board and quality receive the sum across all teams.

  Information letter and model consent request art. 4, condition 6

  > Information letter and model consent request art. 4, condition 6 [Read it](https://axiomatic.digital/policies/works-council-consent-request.en.pdf)
  >
  > “Reports cover teams of at least five people: per team to the team lead and the works council; *the board and quality receive the sum across all teams*.”

- Rule 7

  A question with no answer

  as a topic, without a name

  Goes as a topic, without the care worker’s name and without their words, to the owner, pooled per protocol, so the source gets completed.

  Information letter and model consent request art. 4, condition 7

  > Information letter and model consent request art. 4, condition 7 [Read it](https://axiomatic.digital/policies/works-council-consent-request.en.pdf)
  >
  > “A question with no answer goes as a topic, *without a name and without the asker’s words*, to the subject’s owner.”

- Rule 8

  A wrong answer

  as a finding about Inora

  A finding about the system and the source, never about whoever came across it.

  Information letter and model consent request art. 4, condition 8

  > Information letter and model consent request art. 4, condition 8 [Read it](https://axiomatic.digital/policies/works-council-consent-request.en.pdf)
  >
  > “A wrong answer is a finding about Inora and the source, *never about the member of staff* who came across it.”

- Rule 9

  A reserved or high-risk procedure

  by name, in the competence record

  The competence record: the procedure, the protocol with its version, the date and on whose instruction. The care worker sees it themselves in Inora.

  Information letter and model consent request art. 4, condition 9

  > Information letter and model consent request art. 4, condition 9 [Read it](https://axiomatic.digital/policies/works-council-consent-request.en.pdf)
  >
  > “The care worker’s questions to Inora *never count*, not even as evidence of competence.”

  > Information letter and model consent request art. 4, condition 9 [Read it](https://axiomatic.digital/policies/works-council-consent-request.en.pdf)
  >
  > “It records the procedure, the protocol with its version, the date, on whose instruction and who signed off the practical assessment, *never the content of a conversation, a score or a usage figure*.”

The line Built into Inora. Not a setting anyone can change.

- Processing P8 Test set only once you consent

  Questions from the organisation and flagged answers with their question; the language model takes the names out, no person reads along. Only to test every new version of Inora, and for nothing else.

  Information letter and model consent request art. 4, condition 11

  > Information letter and model consent request art. 4, condition 11 [Read it](https://axiomatic.digital/policies/works-council-consent-request.en.pdf)
  >
  > “We switch on the test set only if you *consent to it separately* below.”

  > Information letter and model consent request art. 4, condition 11 [Read it](https://axiomatic.digital/policies/works-council-consent-request.en.pdf)
  >
  > “*No person reads* a question or answer in the test set; testing a new version is automated.”

## This is all the team lead sees.

The monthly report as the team lead and the works council receive it.

Team report · monthly October 2026

Heuvelland-Oost district team

Zorggroep Voorbeeld · 11 members of staff

To: team lead, Heuvelland-Oost district team · the works council

What the team asked about 143 questions

- Wound care 41
- Medication 33
- Reporting 28
- Catheter care 17
- Other subjects 24

No answer yet 4

Per protocol to whoever owns the subject.

- Insulin pen: shelf life outside the fridge · 2× → medication policy
- Replacing a urinary catheter: competence · 2× → reserved procedures

Gaps closed 2 Work agreements completed after a question with no answer.

Time given back 14 hours For the whole team, on searching and reporting.

Heuvelland night shift 4 members of staff Fewer than five: no report of its own.

The board and quality receive only the sum across all teams.

What you will not find in it

1. 1

   No names The report knows the team and its size. Who works in it is not there.
2. 2

   No figure per person The counts are the team’s together. Who asks a lot or a little cannot be seen.
3. 3

   No question as typed A question with no answer appears as a topic, without identifying detail, with a count; the care worker’s words and name do not go with it. A topic asked once goes in only when it comes a second time; after three months it goes only into the sum across all teams.
4. 4

   No one is measured The time that comes back belongs to the team. The report credits it to no one by name.
5. 5

   No small groups A team smaller than rule 6 allows gets no report, so no one in it can be recognised.

## Only what the inspectorate expects carries the care worker’s name.

Whoever performs a reserved or high-risk procedure is demonstrably competent. You own the record.

Competence record · Inora Matrix The organisation’s, kept in Inora

- Care worker

  Sanne de Wit, senior care assistant

- Procedure

  Subcutaneous insulin injection, a reserved procedure

- Protocol

  Insulin administration, version 6

- Date

  14 October 2026

- On whose instruction

  The client’s attending physician

- Practical assessment

  Signed off by the assessor, 2 September 2026

- Current

  From their own report, last on 14 October 2026

* How it works

  Per role the register lists the procedures your training policy asks for. The theory comes from your own protocol, in the work itself. The assessor signs off the practical assessment in the same report flow. From then on the register stays current with the procedures the care worker reports doing themselves, with the protocol and the version that applied; if they have not performed a procedure for a long time, they see that a new assessment is due. Whether they are competent, they judge again themselves each time.

* In the pilot

  During the pilot the record is a preview for the participating team, and staff take part voluntarily. It becomes your official register only after the works council consents. If you already keep a register in the client record system or a learning platform, Inora connects to it.

* Kept

  In Inora for as long as the care worker works for you, plus 30 days; in those 30 days you export it to your own personnel file, where your own term applies.

[Wet BIG](https://wetten.overheid.nl/jci1.3:c:BWBR0006251&hoofdstuk=IV&artikel=38), art. 35 and 38: whoever performs a reserved procedure on the instruction of an independently authorised professional, such as a doctor, must be competent to do so and follows their directions

Never goes to the organisation

- What the care worker asked or read; their questions never count, not even as evidence of competence
- How often the care worker uses Inora
- How long the care worker took
- A score or a judgement

Who sees it

- The care worker

  Their own competence record, always, in Inora, and on request a copy to take with them: their right of access (art. 15 GDPR), which the organisation answers and Axiomatic helps with.

- Team lead and training

  The competence record, to know who is competent for what. They had to know that already.

Why it serves care workers: No longer written up after the fact: it is recorded at the moment itself, with the protocol and the version in force, and the care worker sees what it says about them. Proof of their craft, not a yardstick.

## The letter for your agenda, already written.

Your consent is needed before the rollout to more teams.

Read the whole letter

Model · consent request

\[Name of the organisation], the board

To the works council of \[name of the organisation]

\[Place], \[date]

Subject: request for consent to the introduction of Inora (WOR article 27(1)(k) and (l))

Dear members of the works council,

Under article 27 of the Works Councils Act we ask for your consent to the proposed decision below.

Article 1. The proposed decision. We introduce Inora, starting with an eight-week pilot in \[name of the team], from \[start date] to \[end date]. Taking part in the pilot is voluntary; during the pilot Inora Matrix is a preview for the pilot team. Until you have consented, no other team works with Inora and Inora Matrix does not become the official competence register. After the pilot we decide which teams follow. This decision contains the scheme for the processing and protection of staff personal data in Inora, with the conditions in article 4.

Article 2. The reasons. Care workers look up how it is done here, log what they did and write it up, often after their shift. Inora takes those three steps over, with answers from our own protocols and the source attached. Inora readies the report; the care worker reads and signs, and only on that approval does Inora file it in the client record; Inora acts on that person’s behalf, never with more rights than they have. We want to bring administration time down, make the current work agreement reachable at any moment, at night too, and give the time back to the client.

Article 3. The consequences for staff. Staff in the teams that work with Inora sign in with their own account. They ask questions in plain language and check the answer against its source; they decide. No one is required to ask Inora instead of a colleague. Staff receive training at the start. The pilot measures the effect per team, never per person.

Article 4. The conditions. We introduce Inora only on these conditions:

1. 1\. No one in the organisation reads a member of staff’s conversation with Inora, management included.
2. 2\. No one in the organisation gets a figure about one member of staff: not how often, how fast or when they work.
3. 3\. Inora assesses no one and gives no one a score.
4. 4\. Inora infers no emotions or mood.
5. 5\. Axiomatic reads a conversation only on a written request from \[function, for example the data protection officer], for an incident or a complaint; every access is logged and the member of staff is told. In an outage or security incident Axiomatic examines the system logs and the answer record, never a conversation. Whoever made the request gets a finding about Inora, never what the member of staff asked or read. If the law demands a conversation, Axiomatic gives only what the demand asks, logs it, and the member of staff is told, unless the law forbids it.
6. 6\. Reports cover teams of at least five people: per team to the team lead and the works council; the board and quality receive the sum across all teams. A smaller team gets no report of its own. The topic is set together with the answer, without names; no person reads along.
7. 7\. A question with no answer goes as a topic, without a name and without the asker’s words, to the subject’s owner. A topic asked once goes in only when it comes a second time; after three months it goes only into the sum across all teams.
8. 8\. A wrong answer is a finding about Inora and the source, never about the member of staff who came across it.
9. 9\. What a care worker asks Inora never reaches the organisation. Only what the care worker sends reaches it, such as a report or an incident report, and the competence record the inspectorate expects (Wkkgz, Wet BIG). That record is our competence register for reserved and high-risk procedures under our training policy: the assessor signs off the practical assessment, and from then on it stays current with the procedures the member of staff reports doing themselves, with the protocol and the version that applied. The care worker’s questions to Inora never count, not even as evidence of competence. It records the procedure, the protocol with its version, the date, on whose instruction and who signed off the practical assessment, never the content of a conversation, a score or a usage figure. In the pilot the record is a preview for the participating team and staff take part voluntarily; it becomes our official register only after your consent. It stays in Inora for as long as the member of staff works for us, plus 30 days; in those 30 days we export it to our own personnel file. Only our team lead and training department see the competence record, and the member of staff themselves. The member of staff sees their own competence record in Inora and receives a copy on request. The record log shows, once Inora reads the record, through a connection or the user’s own login, per step what Inora did and on whose behalf. The function the organisation appoints sees it only on written request, per client or in an investigation, to check record access; it is no figure about a member of staff and never holds what anyone asks.
10. 10\. The time Inora gives back goes to care. A decision on staffing is a decision of its own, which we put to you separately.
11. 11\. We switch on the test set only if you consent to it separately below. No person reads a question or answer in the test set; testing a new version is automated. If you withdraw the consent for the test set, Axiomatic deletes the test set within 30 days.

Conditions 1 to 9 and 11 also stand in the data processing agreement with Axiomatic, Axiomatic’s privacy statement (Staff conversations) and the page Inora and the EU AI Act (What Inora never does). Condition 10 is an agreement within our organisation and stands in this decision only. Axiomatic weakens no condition without our written consent.

Article 5. Evaluation. We evaluate the introduction with you after the eight-week pilot and every year after. For that you receive the monthly report per team and an overview of every access by Axiomatic (article 4, condition 5), without its content.

Article 6. Change. If we want to change these conditions, or deploy Inora for another purpose, we put that to you as a new request for consent. If we use Inora other than on these conditions, that is a decision without your consent. You can then invoke its nullity in writing, within one month of our telling you of that use or of it becoming apparent to you (WOR article 27(5)), and we stop that use.

Article 7. Our request. We ask you to consent to this decision, on the conditions in article 4. We would welcome discussing it with you at the consultation meeting of \[date of the meeting], before the rollout to more teams after the pilot. After your decision we let you know in writing which decision we take and the date it takes effect.

Kind regards,

\[Name], for the board of \[name of the organisation]

Signature:

Decision of the works council

To be filled in by the works council.

- Discussed at the consultation meeting of

- Decision on the request

  Consent / no consent

- Test set (condition 11)

  Consent / no consent

- Reasons

- Date and signature of the chair

Agenda item

Consent request, Inora

1. 1 The board puts the request to you in writing, with the reasons and the consequences for staff: in a pharmacy the pharmacist-owner, in a municipality the management.
2. 2 You discuss it at least once in a consultation meeting, before the rollout to more teams.
3. 3 You decide and say so in writing, with your reasons.
4. 4 The board reports its decision and the date it takes effect.

[WOR](https://wetten.overheid.nl/jci1.3:c:BWBR0002747&hoofdstuk=IVA&artikel=27), art. 27(1)(k) and (l), and 27(2)

Enclosures

- The information letter to the works council
- Privacy statement, updated on 7 November 2026
- An example of the monthly report per team

Organisation First team Consultation meeting

[Download the letter](https://axiomatic.digital/policies/works-council-consent-request.en.pdf) PDF · information letter and model request, to fill in

## Everything for your meeting, in writing.

What the works council receives from Inora, with the information letter and the consent request.

- [Works council pack](https://axiomatic.digital/policies/works-council-pack.en.pdf): What reaches the organisation and what never does, the team report, each rule’s clause.
- [Privacy statement](https://axiomatic.digital/policies/privacy.en.pdf): What we process, why, where and for how long.
- [Information letter and model consent request](https://axiomatic.digital/policies/works-council-consent-request.en.pdf): What Inora processes and keeps, who sees what, and that no report names an employee.
- Monthly report per team: Per team to the team lead and the works council, teams of five or more, never per person.

## Your colleagues ask this. Here is the answer.

### Can my manager see what I ask?

No. No one in the organisation reads a conversation, management included (rule 1). Reports cover a team only (rule 6), no one gets a score (rule 3), and only the competence record carries a name (rule 9). The record log is seen only by the function you appoint, on written request, per client or in an investigation.

### Does this replace talking to colleagues?

No. Inora takes away the searching, not the talking. Whoever wants to call a colleague calls; at night the protocol is there even when there is no one to call.

### Does the time that comes back cost staff?

The time goes back to care, to clients and to the work that now waits until after the shift. Your organisation decides on staffing, not Axiomatic, and Axiomatic never sells Inora as a cut in staff. A funding application counts in fte saved, as the scheme asks; what the organisation does with that time, it puts to you separately (condition 10).

### What happens to the logs?

The record log shows, once Inora reads the record, through a connection or the user’s own login, per step what Inora did and on whose behalf. The function the organisation appoints sees it only on written request, per client or in an investigation, to check record access; it is no figure about a member of staff and never holds what anyone asks. Sign-ins and admin actions are kept 12 months, to keep the service secure. On request the organisation receives the logging only totalled per team of at least five people and per day; one member of staff’s sign-in times and IP addresses never. Question counts and response times per user are kept 30 days, only to run the environment, then only totalled per team of at least five people; never per member of staff to the organisation. Conversations are kept 90 days by default; the organisation sets that period.