Food safetyHACCP records
Correcting digital food safety records without losing the original
A correction should preserve the original entry and identify the corrected information, reason, author and time. A record that simply changes in place can become difficult to explain when an investigator compares exports taken on different dates.
At a glance
A correction should preserve the original entry and identify the corrected information, reason, author and time. A record that simply changes in place can become difficult to explain when an investigator compares exports taken on different dates.
Define the decision behind the record
Decide which roles may correct records and which changes require review. A typo in a comment and a changed measurement can have different implications. Separate corrections from new follow-up observations so each event keeps its meaning.
Preserve the original entry and the reason for its change
Define who can correct a record and which changes require review. Distinguish an incorrectly typed value from a later observation or a changed interpretation. A correction process should retain the original context and should not allow any authorised edit to appear as though it was the first entry.
Capture the amended value, reason, correction author and time while preserving the original observation and event time. Keep supporting evidence where relevant and identify whether the correction changes a previously recorded decision. A later measurement belongs in a linked observation rather than in the original value field.
Test history and export using an entry corrected after a supervisor review. Another reader should see what was initially recorded, what changed and which decisions followed each state. Check ordinary user permissions as well as administrator access; an audit history that only one specialist can retrieve may not support routine review or handover.
Worked example
An operator notices the wrong equipment was selected. They submit a correction with its reason. The history preserves the original selection, the new reference and the person making the change; subsequent readings remain separate observations.
Build a usable record
Use the fields below to capture the facts needed for this particular decision. Keep the actual observation separate from any later correction or approval.
- Original record identifier
- Original and corrected information
- Reason and author
- Correction timestamp
- Review status where required
Example record and review decision
Fictional record example: ENTRY-01: original value and event time; CORRECTION-01: revised value, reason, author and correction time; REVIEW-01: decision.
Retrieve both versions and verify that corrections remain distinguishable from the original observation.
Replacing the initial value without history prevents a reviewer from understanding what was known when the decision was made.
Test the review, not just the form
Change a practice record and compare the history and exported version. The reviewer should understand what changed without relying on a separate chat message. Check whether attachments and downstream references still point to the intended record.
A few useful answers
Is deleting and recreating a record a good correction method?
It can obscure the history. Use a process that retains the original and makes the change understandable.
Is a later measurement a correction to the first value?
No. It is a new event unless the change specifically corrects an error in the first entry. Keep new observations and amendments distinguishable, each with its own time, author and meaning.
Sources and further reading
MarkdownExplore starter templates
Start with a useful checklist
English
