Skip to content

Incident management

Reported early.
Handled on the clock.

Incident management for regulated firms: anyone can report an incident in a minute, and owners triage it, track every regulatory notification clock, find the root cause and close it with four-eyes sign-off and a full audit trail.

Incident management, in the platform

Incidents

48
Dashboard Incidents Incident Settings
ReferenceTitleTypeOwner(s)StatusSeverityNext deadlineReported
INC-014Client file sent to the wrong personData breachOpenHighICO · 41 h left14/10/2026
INC-013Fund platform down for three hoursSystem outageOpenCriticalCBI · 2 h 15 m left15/10/2026
INC-012Wire paid on a spoofed instructionFraud or theftOpenHighBoard, firm target · 6 h overdue13/10/2026
INC-011Screening ran on a stale listAML or sanctionsReportedHighFCA · 4 d left15/10/2026
INC-010NAV published with a pricing errorProcessing errorClosure pendingMedium-02/10/2026
INC-009Custodian missed a reconciliationSupplier failureOpenMediumCommittee, firm target · 3 d left08/10/2026
INC-008Complaint acknowledged lateComplaint failureClosedLow-22/09/2026
INC-007Hospitality above the gifts limitConflict, gift or dealingDismissedLow-17/09/2026
Items per page 25  1 of 1 Showing 1 to 8 of 8
What it does

Incident management, in the function you actually run.

Most incidents are seen first by people outside compliance: the operations analyst who spots the misdirected email, the administrator who notices the payment that should not have gone. Vantage Point makes reporting something anyone can do in a minute, in plain language, from their own menu, and shows them what happened to their report afterwards. A firm that hears about incidents early can deal with them while they are still small.

From there the incident belongs to its owners. They triage it, set the severity, assign the work and decide which notification regimes apply. Each regime starts its own clock from the right moment, and the incidents list shows the next deadline for every open incident, so nothing depends on someone remembering a 72-hour window. Drafts, submissions and correspondence with the regulator are kept on the incident itself.

The investigation records what went wrong and what it cost: losses by currency, the root cause and the remediation that stops it happening again. Owners can link the incident to the control that failed, the obligation that was breached and the risk it changes, which is how a run of small incidents becomes visible in the risk register before it becomes a large one.

Closure is four-eyes. A second person approves it, sees every change made since the request and acknowledges it before signing off. The incident keeps a complete trail of who did what and when, and the dashboard shows how the firm is speaking up: reports by entity, time to triage and how many reports were closed with no further action.

  • Anyone can report in plain language. Owners triage, set severity and take it from there.
  • Every notification clock on one list, amber as it nears and red once overdue.
  • Root cause, remediation and closure, signed off by a second person and kept on the record.
Questions

Questions about incident management.

Who can report an incident?
Everyone in the organisation, against any entity, from their own menu. The report form asks plain questions in plain language, so a member of the operations team never needs to know a control name or a rule reference. Reporters see the progress of what they raised in their own list, and nothing more.
How are notification deadlines tracked?
When an owner triages an incident, the platform suggests the notification regimes that may apply and starts each clock from the right moment, such as awareness or classification. Every incident shows its next deadline, which turns amber as it nears and red once it is overdue. Drafts, submissions and correspondence sit on the incident, so the evidence of what was sent and when is on the record.
Which notification regimes are built in?
Regimes for the UK and the EU are built in, including the FCA's SUP 15 notifications and operational incident reporting, personal data breaches under the UK GDPR and the EU GDPR, and major ICT-related incidents under DORA. For anything else, your firm sets its own targets, such as notifying the board within a day, and those run on the same clocks.
What happens if we decide an incident is not notifiable?
That decision goes through four-eyes approval with a recorded rationale, so a second person confirms it before the clock is stopped. Dismissals are measured too: the dashboard shows how many reports were closed with no further action, and why.
How do incidents connect to risks and controls?
Owners can answer three optional questions when they investigate: which control failed, which requirement was breached and what it means for the risk posture. The answers link the incident to the control, obligation and risk records, so a pattern of incidents shows up where the board reads about risk. Incidents can also link to entries in your breach and error registers.
How is an incident closed?
The owner records the losses, the root cause and the remediation, then requests closure. A second person approves it, and if anything changes after the request, the approver sees every change and acknowledges it before approving. Closed incidents can be reopened, and every edit at every stage is in the audit trail.
Can we restrict who sees a sensitive incident?
Yes. An incident can be restricted to named people, and removing someone from the list removes their access straight away. Retention rules, legal holds and approved redaction keep sensitive records for as long as the law requires and no longer.
Next step30 min · Tailored · No deck

See incident management running on your firm's structure.

A 30-minute walkthrough using your entities, your licences and a real workflow you bring to the call. No slide deck.