Incident journal
Accident and incident register. A refrigerator breakdown at night, a power outage or a leak: every incident is recorded with the measures taken and the impact on products.
What this log is for
The accident log records all unplanned events, from power outages to cleaning product spills. A record cannot be closed without a corrective action.
How it looks in the system
What a completed log looks like
The same file the service provides to an inspector. The data is fictional: the organization “Ромашка” and five employees.
What gets recorded
- Incident date and time
- Situation description
- Action taken
- Consequences for products (write-off / return / release)
Regulatory basis
- Internal HACCP rules
- Major incidents create a linked CAPA ticket with corrective measures.
Questions and answers
What should I record in Incident journal?
Required fields: Incident date and time; Situation description; Action taken; Consequences for products. An empty field is equivalent to an incomplete log for an inspector, so use a dash deliberately and include an explanation.
How often should I complete Incident journal?
According to the HACCP plan: the frequency is set when describing the control point and justified in the plan itself.
Which document requires Incident journal?
Internal HACCP rules. Include the regulatory reference on the title page so the inspector can immediately see why the log is kept.
Can I keep Incident journal electronically?
Yes. SanPiN 2.3/2.4.4282-26 does not require paper: the important points are being able to see who made an entry and when, and preventing unnoticed retrospective changes. For an inspection, print the electronic log for the required period.
How long should I keep Incident journal?
Inspectors usually request records for the last 12 months, so one year is a practical minimum. Keep logs connected with a food poisoning investigation or a complaint until the proceedings are closed.