Incident Timeline

What it does

Incident Timeline keeps a register of incident records for your account. Running an incident in order and leaving a record of how it went. Each incident has a title and the fields below, and its state moves only along the steps listed. The database refuses any other step and any value outside the field rules, and a record in a final state cannot be changed.

The fields

The states

A new incident starts as detected.

Using it

Signed-in accounts open the Incident Timeline, add records, and move them between states. The change is recorded in the account's audit chain; a state change names the revision it was made against and is refused if the record has moved on. The same operations are available as JSON on the same address.

Data handling

Records belong to the account that created them and are visible to that account only. They are stored in the platform's PostgreSQL database. Do not store special-category personal data in a register unless you have a lawful basis; the privacy notice states what the platform collects and keeps.

Limits

• It is a register for one account; sharing a register between accounts and attaching files are not built.
• The account cannot delete or edit a record, and a record in a final state is kept as it was. The automated erasure step does not remove register records: an erasure request that covers them is completed by the operator.
• There are no reminders or recurring records: dates are stored and shown, nothing is sent when one passes.
• It does not give legal, clinical or regulatory advice; the account holder remains responsible for what the records mean.

Availability

Incident Timeline is running on RJV's own platform. RJV does not sell a licence for it as a separate product today: the commercial terms state what is on sale. It can be part of the result of an engineering engagement, where the written proposal names it, its licence terms and what you would hold at the end. To discuss it, use Work with Us.

Evidence

The field rules, the permitted steps and the refusal of every other step are enforced by the database and exercised by the platform's own tests. The evidence register lists the graded claims.