COMPLIANCE INVESTIGATIONS
Investigations where you can show who saw what.
Restricted to the team, time-boxed emergency access, and a record that proves itself.
A worked example: compliance investigations on Alaflow.
Every screen and step below is illustrative. They show how the platform handles this kind of work, set up the way your own rules require.
Compliance and regulatory bodies investigate reports of wrongdoing: a complaint, a tip, a referral or a failed inspection. Investigations are sensitive by nature. Evidence has to be kept intact, the number of people who know about a case has to stay small, and, if the work is ever challenged, the organisation has to be able to show who saw what and when. A weakness in any of these can cost the case, or harm the people involved.
The service on this page is an investigations service. Each investigation is one record that holds its evidence, interviews, tasks and deadlines, with access restricted to the team assigned to it. Every view and change is written to a record that proves itself, and retention and legal hold decide what may be disposed of. The sections below show how that service is made up.
The security controls underneath are available today.
What this service is made of.
The people who use it
Staff work on their own screens. People outside your organisation use a separate portal.
- The investigating team
Your services
Set up for each kind of work, in days, and changed as your rules change.
- Compliance investigations
This layer and the two below it are set up in days and changed as your rules change.
What you keep track of
recordsThe record types your services need.
- A report or allegation
- The assigned investigator
- Evidence
- Interviews and calls
- Steps against deadlines
What each record can do
capabilitiesBuilding blocks you switch on for each record type.
- Versioned documents for evidence
- Interactions for interviews and calls
- Tasks and checklists against deadlines
What is built in
controlsBuilt in from the first day, tuned to your rules when your services are built, and not switched off by accident.
- Access control
- Classification
- Protected identifiers
- Retention and legal hold
- Audit trail
- Emergency access
Built in from day one. Cannot be switched off by accident.
A worked storyline.
- A report is received and triaged.
- An investigator is assigned.
- Evidence is filed as versioned documents.
- Interviews and calls are logged.
- Tasks and checklists track steps against deadlines.
- Access is restricted to the investigating team, with explicit deny rules and classification.
- Emergency access is time-boxed and justified.
- Every view is in the audit trail.
- Retention and legal hold govern what can be disposed of.
Controls in use.
Each of these is available today, and described in full on the security page.