Compare
Built for the job that email and forms can't do
30 capabilities compared with the two set-ups most organisations start with, followed by the honest list of what ClearVoice does not do yet.
Capability matrix
Capability by capability
Grouped by what you need to do. The last two columns describe typical set-ups in general, not any particular product.
| Capability | ClearVoice | Email and spreadsheets | Basic hotline form |
|---|---|---|---|
| Reporting and anonymity | |||
| Anonymous reporting with no IP or device logging | Yes | No | Sometimes |
| Reporter follows up without revealing who they are | Yes | No | Sometimes |
| Forms tailored per category, with conditional questions | Yes | No | Sometimes |
| Attachments checked against content, scanned and encrypted | Yes | No | Sometimes |
| Lockout after repeated wrong access codes | Yes | No | Sometimes |
| Handling cases | |||
| Case opened and reporter acknowledged automatically | Yes | No | Sometimes |
| Enforced workflow with a complete timeline | Yes | No | Sometimes |
| Assignment history, with accept or reject and a reason | Yes | No | No |
| Investigator-only notes | Yes | No | No |
| Linking, merging and duplicate suggestions | Yes | No | No |
| Fairness and conflicts | |||
| Automatic conflict-of-interest routing | Yes | No | No |
| Restricted cases for senior subjects | Yes | No | No |
| Routing simulator and decision history | Yes | No | No |
| Workload-aware assignment | Yes | No | No |
| Cases released when an assignee leaves | Yes | No | No |
| Deadlines and investigation | |||
| Acknowledgement and feedback deadlines tracked | Yes | No | Sometimes |
| Clock pauses and justified extensions | Yes | No | No |
| Tasks, interviews, findings and recommendations | Yes | Sometimes | No |
| Closure approved by a second person | Yes | No | No |
| Corrective actions with effectiveness review | Yes | Sometimes | No |
| Protecting people | |||
| Reporter identity stored apart from the report | Yes | No | Sometimes |
| Four-eyes approval before an identity is revealed | Yes | No | No |
| Retaliation concerns from staff and reporters | Yes | No | No |
| Security and audit | |||
| Field-level encryption of sensitive content | Yes | No | Sometimes |
| Tamper-evident, hash-chained audit trail | Yes | No | Sometimes |
| Evidence hashing and chain of custody | Yes | No | No |
| Role-based access with separation of duties | Yes | Sometimes | Sometimes |
| Two-step sign-in for staff | Yes | Sometimes | Sometimes |
| Insight | |||
| Analytics that hide small groups | Yes | No | No |
| Board-ready CSV export | Yes | Sometimes | Sometimes |
Real situations
Where the cheap options break
These are the moments that turn a small concern into a crisis.
The report about the person who reads the inbox
Without a system: A shared mailbox delivers a complaint about the compliance head to the compliance head.
With ClearVoice: ClearVoice keeps the implicated person, their reporting line and their department away from the case, and routes it to someone else.
The deadline nobody noticed
Without a system: Three months pass on a spreadsheet row that was never revisited. A regulator asks for proof of timely feedback.
With ClearVoice: Deadlines start automatically, pause fairly, warn seven days ahead and alert on breach. The timeline shows what happened and when.
The forwarded email
Without a system: A report is forwarded to five people so someone can help. Now six people know who raised it.
With ClearVoice: Identity is stored in a separate vault. Revealing it needs a permission, a written reason and, if you choose, a second person's approval, all audited.
The edited spreadsheet
Without a system: A row is quietly changed after the fact and nobody can tell.
With ClearVoice: Every action goes to an append-only, hash-chained log. A one-click check proves nothing was altered, or shows the first entry that was.
Your options
Three ways to run a speak-up process
Each can work. They differ in what they cost you in risk and effort.
Building it yourself
Good
- Total control of design and hosting
- Fits your exact process
Watch out
- Needs security, cryptography and compliance expertise in-house
- Conflict handling, deadline logic and audit integrity are easy to get subtly wrong
- You maintain it, and you must prove its controls to auditors
- Reporters may not trust a channel run by their own IT team
A shared inbox and spreadsheet
Good
- Free and instant to start
- Everyone already knows the tools
Watch out
- No anonymity: addresses and metadata are visible
- No conflict control or audit trail
- Deadlines depend on memory
- Hard to show regulators a defensible process
ClearVoice
Good
- Purpose-built controls ready on day one
- Built and supported by SLEM Technologies, a product studio
- Configurable to your categories, rules and deadlines
- A change log and a help centre you can read before you buy
Watch out
- Some enterprise features are not built yet (see below)
- You still own the policies and the people
Ask any vendor
Nine questions to ask, with our answers
Use these with every supplier you evaluate, including us. We have answered them plainly.
| Question | ClearVoice answer |
|---|---|
| Do you log reporters' IP addresses or devices? | No. Reports are stored without IP addresses or device identifiers, and the reporting pages load no tracking scripts. |
| Can a reporter follow up without an account? | Yes, with a reference and a one-time access code, of which only a hash is stored. |
| Who can read our reports? | People in your organisation who hold the right permissions and are not in conflict with the case. Sensitive fields are encrypted individually and access is audited. |
| How do you stop conflicts of interest? | The server keeps the implicated person, their reporting line and the implicated department away from the case, in routing, lists and assignment. |
| Can you prove the audit log was not edited? | Entries are hash-chained and append-only. A built-in check finds the first broken entry. |
| What if we miss a deadline? | Deadlines are tracked with pauses and extensions, warnings arrive seven days before, and breaches alert the team and appear on the timeline. |
| Who can reveal a reporter's identity? | Only someone with a dedicated permission who is not in conflict, with a written reason and, if enabled, a second person's approval. |
| Which certifications do you hold? | None yet. The platform is designed around ISO 37002, the EU Whistleblower Directive, GDPR and the Nigeria Data Protection Act, and it does not make you compliant by itself. |
| Do you support single sign-on? | Not yet. It is on the roadmap. |
Honest limits
What ClearVoice does not do yet
Trust starts with an accurate picture. These are not available today.
Single sign-on (SSO)
Sign in with your identity provider.
Tenant-wide two-step sign-in
Require it for everyone, with an administrator reset for lost devices.
Retention policies and data-subject tooling
Automatic retention rules and export or erasure workflows.
Object storage for evidence
S3-compatible storage with versioning, plus a full antivirus engine, redaction and legal hold.
Language and location matching
Route by reporter language and the place an incident happened.
More channels
SMS and Microsoft Teams notifications, and per-person notification preferences.
Multilingual forms
Translated labels for categories and questions.
AI assistance
Optional, off by default, and only with a provider and data terms you approve.
ClearVoice is also not certified against ISO 27001 or SOC 2 at this time. It is designed to support your compliance programme and does not replace legal advice.
Judge it on a real report
Create your organisation, set up a category and a rule, then submit a test report and see how it is handled.