Employee Feedback¶

In one sentence: Staff raise personal concerns, wishes or problems at work in confidence, and the Feedback Officer follows them up. Menu: Reporting module → tab Employee Feedback · Status: Live (one change planned, see below)

What it is¶

Not every concern is an incident or an idea. Sometimes a person wants to say "my workload is too high" or "there is a conflict in our team". Employee Feedback is a confidential channel for exactly that.

Feedback is handled by the Feedback Officer. Besides the person who wrote it, only the officers and a few administrative roles can read it; Management and Professionals never see other people's feedback. The writer can limit a feedback to the officers only.

Older screens and documents may call this board "Another message" or "Employee Management".

This page adds the feedback details to the general Incident Reports page.

Key terms¶

Term	Meaning
Feedback	A personal concern, wish or problem raised by a staff member.
Implementation proposal	The writer's own suggestion for how to solve it.
Responsible for response	The person named to answer the feedback.
Feedback only visible to officer	Switch on the feedback. On: the officers and the RiQS Administrator (and the writer) only. Off: also the Power User and the administrators who may see the unit's feedback (see the table).

Who uses it¶

Role	What they typically do here
Professional, Management, Power User	Raise feedback.
Power User	Appoints the unit's Feedback Officer; reads and processes feedback at unit level.
Management	Downloads the overview when the unit uses Unit with insight.
Administrator, Group Administrator	Set up Employee Feedback; process feedback at organisation level.
Feedback Officer	Reviews, responds to and closes feedback.

How it works¶

Assignment → In Progress → Completed

Column	What it means	What moves it on
Assignment	New feedback, waiting to be assigned. The content can still be updated.	The officer assigns it and drags it to In Progress.
In Progress	Being handled. The responsible person can write response remarks.	Resolved: drag to Completed.
Completed	Closed.	Can be dragged back to In Progress.

The form asks for: - Send anonymously (optional). - Title and Short Description (both required). - An implementation proposal, keywords and attachments.

How to …¶

How to give feedback¶

Who can do this: Everyone except the RiQS Administrator. At Unit without insight level, Group Administrators and Administrators cannot. 1. Open Reporting module and click Employee Feedback. 2. Click the create button. 3. Fill in the title and Short Description. Add your proposal if you have one. 4. Switch on Send anonymously if you wish. 5. Click Report.

Result: The feedback appears in Assignment. Only you, the officers and the roles in the table can see it. You receive a confirmation email.

Who can do this: The person who writes the feedback, when creating it (every role that can create feedback). Whether the officer may change it later is open (see Open questions). 1. Open the feedback. 2. Switch Feedback only visible to officer off. Save.

Result: The Power User and the administrators who may see the unit's feedback can now read it. Switch it on again to restrict it.

How to handle feedback¶

Who can do this: See "Process" in the table below. 1. Open the feedback and drag it to In Progress. 2. Use Create To Do or Attach Guide if action is needed. 3. Drag it to Completed when it is resolved.

Result: The feedback is closed.

Rules to know¶

Feedback is never shown to all staff. Management and Professionals see only their own. The officers, the RiQS Administrator, the Power User (unit levels) and the Group Administrator and Administrator (organisation level and unit with insight) see the unit's feedback, unless it is officer-only.
The content of a feedback can only be updated while it is in Assignment.
A responsible person can edit response remarks only while it is In Progress.
Ideas requalified by the Ideas Officer arrive on this board and are officer-only. Their writer gets an email.
Only the RiQS Administrator can delete feedback.
Planned: the Feedback only visible to officer switch will move into the creation form, directly below Send anonymously, off by default. Then the writer decides who may read it (e.g. when reporting bullying). Today the switch is still on the feedback details.

Who can do what¶

Legend: ✅ allowed · ❌ not allowed · text = condition · Org = Organizational · Unit+ = Unit with insight · Unit− = Unit without insight.

Action	RiQS Administrator	Group Administrator	Administrator	Power User	Management	Professional	Feedback Officer
Switch Employee Feedback on and choose the level	✅	✅	✅	❌	❌	❌	❌
Appoint / change the Feedback Officer	✅	Org	Org	Unit+, Unit−	❌	❌	❌
Create feedback	❌	Org, Unit+	Org, Unit+	✅	✅	✅	✅
Send it anonymously	❌	✅	✅	✅	✅	✅	✅
Switch Feedback only visible to officer (when creating)	❌	✅	✅	✅	✅	✅	✅
See the own feedback	✅	✅	✅	✅	✅	✅	✅
See other people's feedback of the unit	✅	Org, Unit+, if not officer-only	Org, Unit+, if not officer-only	Unit+, Unit−, if not officer-only	❌	❌	✅
Process: edit, move, To-Do, guide	❌	Org	Org	Unit+, Unit−	❌	❌	✅
Deactivate / reactivate	❌	Org	Org	Unit+, Unit−	❌	❌	✅
See inactive feedback	✅	Org, Unit+	Org, Unit+	Unit+, Unit−	❌	❌	✅
Download the overview	✅	Org, Unit+	Org, Unit+	Unit+, Unit−	Unit+	❌	✅
Delete feedback	✅	❌	❌	❌	❌	❌	❌

Connected modules¶

Incident Reports: the common rules for all report types.
Ideas: ideas can be requalified as feedback.
Open Items and Process Guide: actions as To-Dos and guides.

Open questions¶

Rights sheet vs feature list. The Roles & Rights sheet (used on this page) and the feature list disagree on employee feedback. Please confirm the sheet is right:
Appointing the officer at Organizational level: the sheet says RiQS Administrator, Group Administrator and Administrator; the feature list says RiQS Administrator and Power User.
Processing at Unit with insight: the feature list also lets Management process; the sheet does not.
Feedback of the own unit at Organizational level: the feature list shows it to the Power User (and the overview download); the sheet does not.
Inactive feedback at Organizational level: the feature list shows it to the Power User; the sheet does not.
Planned switch in the creation form. When the switch moves to the creation form, should the officer still be able to change it later?

Last reviewed: 2026-10-27