How Protected Incidents Work in FN CrashGuard+

Understand the purpose of a Protected Incident, what information belongs in it and why keeping evidence connected is more useful than storing disconnected files.

FN CrashGuard+ is designed to help keep an incident record structured, but the quality of the record still depends on safe use, accurate information and careful review. The practical steps below are intended to make that process clearer.

One incident, one organised record

A Protected Incident acts as the container for the event. It gives recordings, photos, statements, vehicle information and later notes a common place to live.

Protection creates a point of reference

When you protect an incident, you create a clear boundary between ordinary driving context and the event you may need to review later.

Add evidence as it becomes available

You do not need to complete every field at the roadside. Once safe, you can add photographs, other-vehicle details, voice or written statements and follow-up information.

Keep the timeline factual

Use the incident timeline to show when key actions happened. A timeline is most useful when it describes events rather than interpreting them.

Review before export

A protected record can become the basis for a report or export, but it should be reviewed first for missing information and obvious errors.

Private Profile dependency

CrashGuard+ uses your Private Profile information in reports and exports. Complete the profile before you rely on those outputs.

Protection is organisation, not judgement

Protecting an incident does not mean the app has determined fault or wrongdoing. It means the evidence has been preserved and organised for later review.