Replacing a reporting system is not something you improvise
Your case handlers know their current tool, your cases are open, your obligations keep running. We build the switch around those constraints, for a transparent switch.
A configuration that starts from your organization, not from our screens
No two reporting programs look alike: the legal perimeter, the role of works councils, where HR sits and how investigators are spread all change the design. So we start from how your organization actually runs to define intake channels, handling paths and permissions — with the aim that your own leads run the platform unaided within weeks.
Four workstreams, run in parallel
Mapping your program
Who receives, who qualifies, who investigates, who decides. We write these rules down before touching any configuration.
Configuration
Channels, forms, handling paths, statutory deadlines and permissions translated into the platform.
Internal awareness
The material that explains the new channel to employees and removes any doubt about confidentiality.
Joint steering
Regular checkpoints, a shared timeline and decisions settled as they come up.
That raising a concern becomes a safe reflex inside your organization: one clear channel, deadlines that hold, decisions that can be traced — and teams who know a case never gets lost.
A switch affects people as much as settings
These topics come up in almost every scoping conversation we have. We would rather put them on the table in the first meeting than discover them mid-project.
Cases already handled
Years of qualifications, evidence and decisions that must remain accessible and defensible. A switch does not reset the counter.
Whether the channel gets used
A program nobody uses is not a program. The reporting path has to stay readable for a shop-floor employee and for a manager abroad alike.
Deadlines that will not move
Open investigations, 7-day acknowledgements, 3-month feedback, annual reporting: the migration fits that calendar, never the other way round.
Internal sign-offs
Legal on compliance, IT on hosting, HR on handling paths, leadership on budget: each body has its own decision cycle.
Four stages, on a timeline you know upfront
At any point you know what is under way, what is expected from you and what comes next. Our security and data protection commitments frame each of these stages.
Scoping
Understand your program before configuring it
We review your current channels, handling paths and regulatory constraints, then agree the perimeter, the milestones and who is involved on each side.
A written timeline and assigned roles before any configuration.
Configuration
Translate your internal rules into the platform
Forms, intake channels, routing rules, notifications, deadlines and permissions are set up from the mapping signed off at scoping, then reviewed with you.
A setup that mirrors your rules, not a standard template.
Testing and training
Stress-test the program before opening it
We replay real cases end to end, fix what needs fixing, then train your compliance leads, HR contacts and administrators in separate sessions.
Nobody discovers the tool on the day it opens.
Opening and follow-up
Support the first months of real use
We support the launch communication, review the first reports with you and adjust the configuration in light of how the channel is actually used.
A program that settles in instead of fading out.
What happens to your existing case history?
We inventory what sits in your current tool, decide together what is carried over, archived or left behind, then check the integrity of the imported data before opening. You sign off the perimeter in writing before anything moves.
Discuss your case history →“An internal investigation tolerates neither a gap in the audit trail nor a contact who keeps changing. We hold migrations to the same discipline: a written perimeter, verified data, and the same team from scoping through the first months of use.”
Julien Mascaro
CEO, Evidencia
We run the project, you stay the decision-maker
A successful migration rests on one clear boundary: we own the platform and the method, you own your organization and its internal trade-offs. Here is what that means in practice.
What you own
You settle the choices that commit your organization and make sure the program is understood internally.
- Settle handling rules and permission levels
- Engage internal bodies (legal, IT, HR, works council)
- Update your procedures and reporting policy
- Carry the communication to employees
What we take on
We take the technical and methodological load, and leave you self-sufficient on the platform.
- Configure the platform from the signed-off mapping
- Train your case handlers and administrators
- Run the inventory and carry-over of your case history
- Provide your communication and procedure templates
The same people from scoping to the first months of use
No hand-off between sales, delivery and support. Every role is named at kick-off, on our side and on yours, and stays identifiable for the whole project.
Project lead
Holds the timeline, runs your checkpoints and remains your contact after opening to keep the program evolving.
Technical expert
Configures the platform, handles integrations and runs the carry-over of your data with the associated checks.
Program owner
Settles internal rules, engages the relevant bodies and drives communication towards employees.
IT / security lead
Validates hosting, the data transfer arrangements and alignment with your in-house security requirements.
What is already settled the day the channel opens
Opening is not the risky part: everything below has been signed off with you beforehand.
A stress-tested configuration
Real cases replayed end to end and corrected before opening.
Communication ready to send
Posters, internal notes and explainer pages adapted to your organization.
Case history carried over and checked
Perimeter signed off in writing and data integrity verified after import.
Self-sufficient case handlers
Your administrators can handle a case and train their peers internally.
Follow-up over the first months
Regular checkpoints with your project lead and accessible technical support.
Frequently Asked Questions
Everything you need to know
Let’s talk about your switch
One conversation is enough to frame the perimeter, the timeline and the carry-over of your cases.