FSSC DEVELOPMENT · SOUTH AFRICA
FSSC Development documents and records: what is the difference?
Build useful FSSC Development documentation by separating instructions from evidence, matching records to your process and keeping versions under control.
Part of our FSSC Development guide for South African food businesses.
Instructions explain the work; records show what happened
A procedure tells someone how an activity should be carried out. A record captures what actually happened. A cleaning instruction might describe an approved method and responsibilities; its associated record might show when the task was completed and checked. A blank form is a tool for collecting evidence, not evidence that the activity took place.
This distinction matters when preparing for FSSC Development. A folder full of templates can look substantial while providing little information about how a business operates. Begin with the requirements and the real process, then decide what instructions and records support it.
Map documents to your operation
Use the official requirements for your sector to identify the documented information needed. Do not treat the following examples as an exhaustive list or a prescribed number of documents.
- Product descriptions and process flows explain what is made and how it moves through the operation.
- Hazard analysis and control plans explain food safety decisions and how controls will be managed.
- Work instructions explain relevant activities such as cleaning, receiving, storage or monitoring.
- Completed records capture checks, results, deviations and actions.
- Review and verification evidence shows how the business checks that arrangements remain effective.
One well-designed document may serve several related purposes. Several disconnected templates may repeat the same information and become inconsistent. Choose a structure people can maintain.
Design records around decisions
Start with the task and the decision it supports. What is checked? By whom? When? What result is acceptable? What happens if the result is unacceptable? Which details must be retained to understand the event later?
For a monitoring activity, a tick box may not capture enough detail to demonstrate the result or explain a deviation. Where a measurement is required, make room for the actual result and the response. The appropriate limits, frequencies and methods must come from your own controls and applicable requirements; do not copy numbers from an unrelated business.
Test the form with the person who will use it. If the layout encourages omissions or ambiguous entries, fix it before rolling it out.
Keep current instructions where the work happens
Give controlled documents a clear identity and revision status. Decide who can approve changes, where the current version is held and how superseded copies are removed from use. When a process changes, check the connected documents rather than updating only the first one you find.
Paper and digital systems both need ownership. A shared drive with unclear filenames can be as confusing as an overfilled binder. Staff need a dependable way to find the current instruction during a shift.
Handle missing records honestly
Do not recreate historical records as though they were completed at the time. Identify what is missing, assess its implications and document the action taken. Where other reliable evidence exists, keep its source and limitations clear.
Before an assessment, choose a recent product or batch and trace the connected information through the system. Can you follow the relevant activities, results and decisions? That exercise often reveals more than counting documents. Our programme guide explains how documentation fits into the broader preparation route.
Sources and scope
Sources checked on 5 October 2026. This article offers practical preparation guidance; the current official programme documents and your buyer's written conditions determine the requirements that apply.