InnerWeb
Skip to main content

Best practice: evidence of the BRC statement text version

A BRCGS auditor may ask not only whether a visitor signed the statement, but which wording they saw on a specific day. When the text was changed during the year, the date of the entry alone is not enough. We describe practices that let you reconstruct the wording for a given day and language.

SHA-256
hash of the text stored with the statement
2
language versions of the content: Polish and English

Why the date alone is not enough

A plant changes the statement text for various reasons: after auditor comments, after a change in the quality procedure, or after clarifying the questions. After a change the database keeps the entry "statement signed on day X", but if it is not known which wording applied at that time, the evidence is incomplete.

The system solves this by storing, with every statement, a SHA-256 hash of the text that was actually shown to the person. The hash proves the version of the wording even after the content is later changed, because the new text produces a different hash. The plant therefore does not need to archive screenshots from every change.

Practices concerning the content

The first practice is one person responsible for the wording, usually the quality manager. This person approves each text change and records the date in the procedure change log, because the system stores hashes but not the reason for the change.

The second practice concerns language versions. The statement content can be set separately in Polish and in English. When the English text is empty, the Polish version is used, and a person whose account is set to a language other than Polish sees the wording in their account language. For the audit this means the two versions can have different hashes, so both must be kept in the change log.

The third practice: do not leave the English version empty without a decision. An empty English text works as a fallback to the Polish version, which may be intended, but an auditor from a foreign headquarters may expect text in their own language.

Practices concerning recording and uniqueness

Every statement goes into one table regardless of channel, with uniqueness of one entry per person per day. The save is idempotent, so two parallel confirmations do not create a duplicate. For the audit this is a simplification: one day, one person, one hash.

The fourth practice: after each text change, make a test entry and compare the stored hash with the expected one. This detects a situation where the change did not reach a channel, for example the portal or the phone training.

The fifth practice: before an audit, prepare a summary of the text versions with their validity dates and hashes. The summary is a plant document, while the system provides the source data.

Practices concerning the audit

The sixth practice is a reconstruction test: choose a random day before a text change and show the auditor the statement entry with its hash and the matching version from the change log. It is worth running such a test yourself before the audit.

The system provides evidence for the audit but does not replace the auditor's assessment or the quality decision. Good practice is to describe in the procedure that the evidence of the version is the text hash and the change log, together.

Common mistakes when changing the text

The most common mistake is changing the text in one language without checking the other. The plant corrects the Polish version after quality comments, while the English version stays old or empty, and the system then shows the Polish one. The auditor from headquarters then sees a mismatch between what was approved and what the foreign visitor saw.

The second mistake is changing the text during the day without recording the time in the log. Because there is one entry per person per day, a guest who signed the statement in the morning does not sign again after the change, so two wordings can operate on the same day for different people. Good practice is to make changes at the start of the day or to record the time of the change in the log.

The third mistake is treating the hash as a substitute for approval. The hash proves which text was shown, but not that an authorised person approved it. The change log signed by the quality manager closes this gap.

Checklist

Video

Frequently asked questions

What proves which wording the visitor saw?

The SHA-256 hash of the text stored with the statement. A new text produces a different hash, so the version can be reconstructed even after the content has changed.

Do two parallel confirmations create a duplicate?

No. There is one entry per person per day, and the save is idempotent.

What does a visitor with an account in another language see?

The wording in their account language. When the English text is empty, the Polish version is used.

Let's talk about audit evidence

We will show how the system records the version of the statement text. Book a conversation with the InnerWeb team.

Let's talk