01
Peer recognition
Anyone can recognise anyone, with a message and points credited to the person receiving it.
Culture & communication · the half that keeps people
Attendance and payroll tell you who is here. Recognition, pulse surveys and a knowledge base people actually read are what make them stay — and on a factory floor they have to work without an inbox.
Hana recognised Karim — covered a double on the press line
+40Mostafa recognised Line 3 — zero defects for a full week
+25Salma recognised Youssef — trained two new starters
+30Anonymous and still useful
Anonymity usually costs you the ability to act: if you never record who answered, you cannot stop double-voting and you cannot tell which team is unhappy. Flip the read layer below and watch the names go while the department signal stays.
Survey read layer
Identity is recorded either way. Anonymity is applied when results are read, not by failing to store who answered.
Redaction happens in one place, at the read layer, so an anonymous survey and an attributed one share the same storage and the same guarantees.
What ships
01
Anyone can recognise anyone, with a message and points credited to the person receiving it.
02
An HR-managed catalog with point costs, and redemption that snapshots the price at the time it was claimed.
03
Short recurring questions with a week label, targeted company-wide or at one department.
04
A dedicated survey type with its own prompt, tracked separately from the weekly pulse.
05
Anonymity enforced by redacting identity at the read layer, so segmentation still works without exposing anyone.
06
Results broken down by department, which is where a morale problem is actually visible.
07
Company or department-scoped posts, pinned when needed, with per-employee read receipts.
08
Evergreen categorised articles — policies, benefits, how-tos — searchable rather than emailed.
09
Mobile push and in-app notifications, with realtime updates in the web console.
10
The whole employee surface in Arabic or English, on the phone people already carry.
How it actually works
It sounds trivial and it is the whole economy. Crediting the giver rewards the act of posting; crediting the recipient rewards the work. Every serious rewards platform runs it the second way, and getting it backwards quietly turns recognition into a popularity feed.
Identity is stored and then redacted when results are read, rather than never captured. That is what makes one-response-per-person enforceable and department-level segmentation possible at all — a table with no identity in it can do neither. The tradeoff is deliberate, and the redaction happens in one place.
Announcements carry per-employee read records, so "we told everyone" is a number rather than an assumption. For safety notices and policy changes on a plant floor, that distinction is the one that matters if something later goes wrong.
Book a demo
The fastest way to judge Flume is to run it against a period you already argued about. Send a month of punches and the payroll you produced from it, and we will show you the same month reconciled — including what the anomaly detectors flag.