Less technical interpretation
The user supplies the facts. Apricus is intended to apply the applicable path rather than exposing every module name.
How It Works
A controlled sequence, not a longer form.
Apricus 2.0 is being designed around a simple sequence: collect the facts that matter, apply the relevant controls, present a clear outcome, and retain an explainable record.
Core principle
Fewer decisions for the user. The required controls still run.
Users are asked for the information needed for the task in front of them, not a complete technical questionnaire. Company facts are intended to be entered once and reused.
Apricus should appear simple without reducing the number of controls it performs. Users should not need to understand internal module names to complete common work.
Four stages
How the work moves through Apricus
-
1
Provide the facts
Users are asked for the information needed for the task in front of them, not a complete technical questionnaire. Company facts are intended to be entered once and reused.
-
2
Apply the relevant controls
The platform is intended to determine which checks, evidence requirements and workflow steps apply, so the user does not have to select a technical route.
-
3
Review the outcome
Results should show what was determined and what to do next. The interface should remain clear even when the underlying controls are substantial.
-
4
Retain an auditable record
Completed work is intended to remain explainable: the facts used, the evidence considered, the outcome produced and the actions taken.
What this means
What this means for the user
Clearer next steps
Results are presented so the next action is clear, without hiding the basis of the outcome.
Auditable work history
Work is intended to remain explainable: what was submitted, what was applied, and what was produced.