Level 3 HACCP

Module 8: Documentation, records and document control

Make HACCP documents practical, records honest and versions current, using reviews to check that the written system matches real food handling.

Video runtime: 11:09

What you will learn in this module
  • Documentation must guide achievable safe work and match the controlled process, not just fill a folder.
  • Corrective records connect a real failure with affected food, the decision and verified follow-up.
  • Investigate record weaknesses and reality mismatches without treating neat paperwork as proof of control.

Load this video from YouTube. Your browser will connect to YouTube; embedding follows your cookie preferences.

Watch on YouTube (opens a new tab)

External playback does not record on-page study progress.

Module 8: Documentation, records and document control

Module 8: Documentation, records and document control

Make HACCP documents practical, records honest and versions current, using reviews to check that the written system matches real food handling.

Records your study progress, not an assessment result or certificate.

Browse course modules

Key points

  • Documentation must guide achievable safe work and match the controlled process, not just fill a folder.
  • Plans and hazard tables need the real current flow and appropriately linked hazards and controls.
  • Monitoring forms should help genuine checks and decisions, with real food identity, results and responses.
  • Corrective records connect a real failure with affected food, the decision and verified follow-up.
  • Supporting records must be checked against practical competence, cleanliness and equipment performance.
  • Control active versions and turn updates into staff briefing and verified changes in practice.
  • Investigate record weaknesses and reality mismatches without treating neat paperwork as proof of control.

Lesson guide

8.1 Why documentation matters

Documentation tells people how the system is intended to control hazards: methods, responsibilities, monitoring and corrective action. It supports consistent work and training and should be understandable to the staff who use it, not written only for an inspection folder.

If a cooling procedure requires shallow trays but the workplace actually uses deep containers, the document does not establish effective control. Correct the resources and practice and ensure the system describes a suitable achievable method. Supervisors should use documents as working instructions, check their application and review them when conditions change. A large file is not necessarily a stronger system than a clear relevant one that staff can explain and follow.

8.2 Plans, flows and hazard tables

The plan brings together the process flow, hazard analysis, CCPs, limits, monitoring, corrective action, verification and records. Hazard tables consider microbiological, physical, chemical and allergenic hazards at the actual stages food passes through.

Examples include bacterial growth in chilled food and undeclared allergens in a label or ingredient change. These are different risks and need appropriate controls. A flow diagram gives context for those decisions, including preparation, packing, holding and transport where relevant. Keep the plan current when the process changes so checks and forms remain attached to the right hazards. A detailed table copied from an old operation can look complete while omitting what now happens on site.

8.3 Monitoring sheets

Monitoring sheets should make checks clear and usable during actual work. Include what was checked, when, by whom, the real result, the acceptable standard and action after a failure. A hot-holding sheet needs to identify relevant food and limits, not only list unconnected numbers.

Accessible, practical forms support good checks, but cannot replace them. Review entries for failed readings, repeated faults, missing cleaning or training needs. Do not tolerate copied or invented results because a sheet looks tidy. A manager needs to see actual conditions and corrective responses to judge whether controls work. If staff struggle with a form, improve instruction or design without removing the safety information needed.

8.4 Corrective action records

A corrective record should show the date and time, what failed, affected food or equipment, the actual result, immediate action, who decided and the food outcome and follow-up. It should explain what happened rather than simply contain the word “done”.

For a warm fridge, record the assessment and movement or disposal of food as appropriate, equipment action and a recheck. For wrong PPDS allergen information, stop and report the affected products and correct the information under the procedure, including escalation where required. Review repeated failures to find causes and improve controls. Clear evidence connects the initial risk with customer protection and longer-term correction; it does not erase a failure by entering a later normal result.

8.5 Supporting records

Training, cleaning, pest and maintenance records support the system’s foundations. Training evidence should connect to staff actually understanding and using the procedure; a signature alone does not establish competence. Cleaning records need to describe completed appropriate tasks rather than intentions.

Pest records can include inspections, sightings, contractor work and proofing actions. Maintenance can record repairs, probe checks or calibration, slicer defects, surface damage, leaks and temperature-control faults. Review the records against reality: did the repair work, is the equipment clean and can the person explain the failed-check action? Use the evidence to find gaps and arrange practical improvement, not merely show that a contractor or trainer visited.

8.6 Version control and review

Version control helps staff use the current procedure rather than outdated instructions. Use suitable version identifiers, issue and review information, responsible authors and approvals and remove obsolete copies from active use. The aim is consistent instructions, not preserving conflicting forms in circulation.

Review after supplier, ingredient, menu, equipment, layout, cooking, packing, label or staff-role changes, as well as incidents, complaints, faults and inspection findings. Update affected allergen information and procedures, brief staff and check the revised practice. Changing a document alone is not enough if staff continue the old method. Correct unsafe real work as well as documentation so the current version reflects the controlled operation.

8.7 Common record failures

False or copied figures, missed actions, incomplete entries, unreadable writing, unclear signatures or times and old forms weaken records. They can prevent a supervisor from establishing what happened, which food was affected and whether a decision was safe.

Perfect-looking temperature sheets alongside staff who cannot explain the method are a warning that the system needs checking, not by themselves proof of deliberate misconduct. Review the evidence, observe practice and train staff in why genuine entries matter. Records are useful when they reveal failures and action truthfully. Concealed gaps or an outdated form can hide a risk while making the file appear complete.

In practice

Two conflicting active procedures

Source teaching example rewritten as a formative scenario; not a real reported incident

A worker uses an old allergen sheet while the office holds a revised version.

Has issuing the new file completed the change?

Control obsolete active copies, brief staff and verify current information is used in practice.

Version control must change daily behaviour, not only the office file.

A correction recorded as done

Source teaching example rewritten as a formative scenario; not a real reported incident

The warm-fridge entry says done without identifying affected food or rechecks.

Is that enough for review?

Record the actual failure, food decision, action and follow-up so the response can be understood and verified.

A vague entry does not connect the risk with effective correction.

Reflect on your learning

What should a monitoring form identify?

Select one answer.

Does a training signature establish competence?

Select one answer.

What must happen after a procedure changes?

Select one answer.

What do neat records with unexplained checks indicate?

Select one answer.

For your own learning — not the certification assessment.

FAQs

Are records and procedures the same thing?

Procedures describe how control should work. Records show actual checks and actions. They must agree with one another and the real operation.

When should documents be reviewed?

Review changes to products, ingredients, processes, equipment, roles or labels and relevant incidents, complaints, faults or inspection findings. Use suitable routine review arrangements too.

Can a corrective entry just say fixed?

It should give enough information to understand the failure, affected food, decision, action and follow-up. Vague words cannot show that the food risk was controlled.

Further reading

  • CookSafe: keeping food safety records (opens a new tab)

    Supplementary guidance on monitoring, corrective action, verification and review records.

    Food Standards Scotland. Applicable jurisdiction: Scotland; catering businesses. Supplementary reading; checked 2026-10-07.

  • Safer food, better business (SFBB) (opens a new tab)

    A practical small-business pack and diary, not a substitute for procedures that fit the actual operation.

    Food Standards Agency. Applicable jurisdiction: England and Wales; the page directs Northern Ireland users to Safe Catering. Supplementary reading; checked 2026-10-07.

  • Food safety management systems for businesses (opens a new tab)

    Supplementary overview of HACCP-based procedures, checks and records.

    UK Government / Food Standards Agency. Applicable jurisdiction: UK overview; check the relevant national regulator and business-specific rules. Supplementary reading; checked 2026-10-07.

Jump to a key moment
Transcript

[0:00] Welcome to lesson 8.1. Why hack
[0:02] documentation matters. Hack
[0:05] documentation matters because it
[0:06] explains how the business controls food
[0:08] safety. At level three, managers and
[0:11] supervisors need to understand that
[0:13] documentation is not just paperwork for
[0:15] inspections.
[0:17] It is the written evidence of the food
[0:18] safety system, including what hazards
[0:20] have been identified, what controls are
[0:22] in place, who is responsible, how checks
[0:25] are completed, and what action must be
[0:27] taken when something goes wrong.
[0:30] Good hack documentation helps staff work
[0:32] consistently.
[0:33] It gives clear instructions instead of
[0:35] relying on memory habits or verbal
[0:38] explanations.
[0:39] For example, if a business cooks
[0:41] chicken, the hack documentation should
[0:43] explain the hazard, the cooking control,
[0:45] the critical limit, how cooking is
[0:47] monitored, what records are completed,
[0:49] and what corrective action is needed if
[0:51] the limit is not met. Documentation also
[0:54] helps with training. New staff and
[0:57] supervisors can understand the food
[0:59] safety system more easily when
[1:00] procedures are written clearly and kept
[1:02] up to date. However, documentation only
[1:06] helps if it reflects real practice. A
[1:09] hacked plan that says food is cooled in
[1:10] shallow trays is weak if staff actually
[1:12] cool food in large deep containers
[1:14] because the correct equipment is not
[1:16] available. At level three, managers
[1:19] should regularly check that hack
[1:20] documents match the way food is actually
[1:22] handled. The key messages, hack
[1:25] documentation explains the system. It
[1:28] should be accurate, practical, current,
[1:30] and used by staff, not just stored in a
[1:33] folder. Welcome to lesson 8.2, hack
[1:36] plans, flow diagrams, and hazard
[1:39] analysis tables. A hack plan brings
[1:42] together the key information about how
[1:43] food safety hazards are controlled. At
[1:46] level three, you should be familiar with
[1:48] important hack documents such as process
[1:50] flow diagrams, hazard analysis tables,
[1:53] critical control point records, and
[1:55] monitoring procedures. A process flow
[1:58] diagram shows the steps food goes
[2:00] through, such as delivery, storage,
[2:02] preparation, cooking, cooling,
[2:05] reheating, packing, display, service, or
[2:08] delivery. The flow diagram helps the
[2:10] hack team understand where hazards may
[2:12] enter, grow, survive, or spread. A
[2:15] hazard analysis table looks at each
[2:17] process step and identifies possible
[2:19] microbiological, physical, chemical, and
[2:22] allergenic hazards. It also identifies
[2:25] controls and may help decide whether a
[2:27] step is a critical control point. For
[2:30] example, during chilled storage, the
[2:32] hazard may be bacterial growth if high-
[2:34] risk food is stored too warm. The
[2:37] control may be fridge temperature
[2:39] control and monitoring. During labelling,
[2:42] the hazard may be undeclared allergens
[2:44] if the wrong label is used. The hacked
[2:46] plan should also show critical limits,
[2:48] monitoring methods, corrective actions,
[2:51] verification checks, and records
[2:53] required. At level three, managers and
[2:56] supervisors should make sure these
[2:58] documents are understandable and match
[2:59] real workplace practice. If the process
[3:03] changes, the documents may need
[3:04] updating.
[3:06] The key messages, hack plans, flow
[3:08] diagrams, and hazard analysis tables
[3:10] help the business understand the food
[3:12] journey, identify risks, and control
[3:14] hazards before customers are harmed.
[3:17] Welcome to lesson 8.3, monitoring
[3:19] records and check sheets. Monitoring
[3:22] records and check sheets show whether
[3:24] food safety controls are being checked
[3:26] in daily practice.
[3:28] These records may include fridge and
[3:30] freezer checks, cooking temperatures,
[3:32] reheating checks, cooling records, hot
[3:35] holding checks, cold display checks,
[3:37] delivery checks, date checks, cleaning
[3:40] records, allergen checks, and pest
[3:42] checks. At level three, managers and
[3:45] supervisors must make sure check sheets
[3:47] are clear, useful, and completed
[3:49] correctly. A form that staff do not
[3:52] understand, cannot access, or cannot
[3:54] complete during busy service will not
[3:56] protect food safety. A good monitoring
[3:59] record should show what was checked,
[4:00] when it was checked, who checked it, the
[4:02] result, whether the result was
[4:04] acceptable, and what action was taken if
[4:06] something was wrong. For example, a hot
[4:09] holding record should not only show a
[4:11] temperature. It should also make clear
[4:13] what food was checked, what the required
[4:15] limit is, and what staff must do if the
[4:17] food falls below that limit.
[4:20] Managers should review records
[4:21] regularly, not only file them away.
[4:24] Records can show patterns such as
[4:26] repeated fridge failures, missed
[4:28] cleaning tasks, cooling problems, or
[4:31] staff who need more support. Monitoring
[4:34] records must also be honest. False
[4:37] records are dangerous because they hide
[4:38] food safety failures. The key messages,
[4:42] monitoring records, and check sheets
[4:44] turn hacked controls into daily
[4:45] evidence. They should be simple,
[4:48] accurate, reviewed, and linked to
[4:50] corrective action. Welcome to lesson
[4:52] 8.4, the corrective action records.
[4:56] Corrective action records show what
[4:57] happened when a food safety control
[4:59] failed and what the business did to
[5:01] protect customers. At level three,
[5:04] corrective action records are important
[5:05] because they prove that staff did not
[5:07] simply notice a problem and ignore it. A
[5:10] good corrective action record should
[5:12] include the date and time, the issue
[5:13] found, the food or equipment affected,
[5:16] the failed result, the immediate action
[5:18] taken, who was informed, what happened
[5:20] to the affected food, and what follow-up
[5:22] action was needed. For example, if a
[5:25] fridge is found above the safe limit,
[5:26] the corrective action record should show
[5:28] the real temperature, which foods were
[5:30] affected, whether food was moved,
[5:32] checked, or disposed of, whether repair
[5:34] was arranged, and whether the fridge was
[5:36] checked again afterwards.
[5:38] Corrective action records are also
[5:40] important for allergen issues. If a PPDS
[5:43] label is wrong or the wrong allergen
[5:45] order is prepared, the record should
[5:47] show that the food was stopped, the
[5:49] issue was reported, and the system was
[5:50] corrected. Managers should use
[5:53] corrective action records to identify
[5:55] repeated problems. If the same issue
[5:58] happens again and again, the business
[6:00] may need to review training, equipment,
[6:02] procedures, or supervision. The key
[6:05] message is corrective action records
[6:07] show that food safety problems were
[6:09] controlled properly. They protect
[6:11] customers and help the business learn
[6:13] from failures.
[6:15] Welcome to lesson 8.5. Training,
[6:18] cleaning, pest and maintenance records.
[6:21] Training, cleaning, pest, and
[6:23] maintenance records are important
[6:24] supporting evidence in a hackbased food
[6:26] safety system. Training records show
[6:29] that staff have received suitable
[6:31] instruction for their role.
[6:33] This may include food hygiene, hack,
[6:35] allergen awareness, cleaning,
[6:37] temperature checks, personal hygiene,
[6:40] delivery checks, or specific workplace
[6:42] procedures.
[6:43] At level three, managers should remember
[6:45] that a training record alone does not
[6:47] prove competence.
[6:49] Staff should also be observed and
[6:51] supported to make sure they can apply
[6:52] the training correctly. Cleaning records
[6:55] show that food areas, equipment, and
[6:57] food contact surfaces are being cleaned
[6:59] and disinfected according to the
[7:01] business procedure.
[7:02] These records help support contamination
[7:05] control. Pest records may include pest
[7:08] contractor visits, baitpoint checks,
[7:10] pest sightings, proofing work, and
[7:12] corrective actions. Pest control is
[7:15] important because pests can contaminate
[7:17] food, packaging, surfaces, and
[7:19] equipment. Maintenance records show that
[7:22] equipment and premises are kept in safe
[7:24] condition.
[7:25] This may include fridge repairs, probe
[7:28] calibration, slicer maintenance, damaged
[7:30] surfaces, broken tiles, leaking pipes,
[7:33] or faulty hot holding equipment. For
[7:36] example, repeated fridge temperature
[7:38] failures may be linked to poor
[7:39] maintenance. If the repair record is
[7:42] missing, the business may struggle to
[7:44] show that the issue was properly
[7:45] controlled. The key message is hack is
[7:48] supported by strong training, cleaning,
[7:51] pest, and maintenance records.
[7:53] These records help prove that the
[7:55] foundations of food safety are being
[7:57] managed. Welcome to lesson 8.6, version
[8:01] control and document review. Version
[8:03] control means making sure staff are
[8:05] using the latest correct version of
[8:07] hacked documents and records. At level
[8:10] three, this is important because
[8:12] outdated documents can lead to unsafe
[8:14] practice. Hack documents may change when
[8:17] the business changes suppliers,
[8:19] ingredients, menus, equipment, layout,
[8:21] cooking methods, packaging, labels, or
[8:24] staff responsibilities.
[8:26] For example, if a business changes from
[8:29] one source supplier to another, the
[8:30] allergen information may change. The
[8:33] recipe card, allergen matrix, menu
[8:36] information, and hack documents may all
[8:38] need updating. If old versions remain in
[8:41] use, staff may give customers incorrect
[8:44] information. Version control should make
[8:46] it clear which document is current. This
[8:49] may include a version number, issue
[8:51] date, review date, author, approval
[8:54] record, and a system for removing old
[8:56] copies. Document review means checking
[8:59] whether hacked documents are still
[9:00] accurate and effective. Review should
[9:03] happen regularly and whenever there is a
[9:05] significant change, incident, complaint,
[9:07] equipment failure or inspection finding.
[9:10] Managers should also check that
[9:12] documents match real practice. If staff
[9:15] have developed shortcuts or the process
[9:17] has changed, the documents may need
[9:19] updating or the practice may need
[9:20] correcting. The key message is hack
[9:23] documents must stay current. Version
[9:26] control and regular review prevent staff
[9:28] from using outdated procedures, old
[9:30] forms, or incorrect food safety
[9:32] information.
[9:34] Welcome to lesson 8.7. Common
[9:36] recordkeeping failures.
[9:38] Recordkeeping failures can weaken the
[9:40] whole hacked system. One common failure
[9:43] is completing records without doing the
[9:45] actual check. For example, writing a
[9:48] fridge temperature without checking the
[9:50] fridge or ticking a cleaning task that
[9:52] has not been completed. Another failure
[9:55] is copying previous records.
[9:58] This may make paperwork look tidy, but
[10:00] it hides the real condition of food,
[10:02] equipment, and hygiene controls.
[10:05] Missing corrective actions are also a
[10:07] problem. If a check fails, but the
[10:09] record does not show what was done, the
[10:11] business [clears throat] cannot prove
[10:12] that the risk was controlled. Other
[10:15] failures include missing signatures,
[10:17] unclear handwriting, blank sections,
[10:19] wrong dates, old forms, records
[10:22] completed at the wrong time, staff using
[10:24] outdated check sheets, and records that
[10:26] do not match the actual process.
[10:28] For example, if cooking records show
[10:30] perfect results every day, but staff
[10:32] cannot explain how they check cooking
[10:34] safely, the records may not be reliable.
[10:38] At level three, managers should review
[10:40] records regularly and challenge anything
[10:42] that looks unrealistic, incomplete, or
[10:44] repeated without explanation.
[10:46] Managers should also train staff to
[10:48] understand why records matter. Records
[10:51] are not about looking perfect. They are
[10:54] about proving real control. The key
[10:57] message is poor records can hide food
[10:59] safety risks.
[11:01] Level three staff must make sure records
[11:03] are honest, complete, timely, reviewed,
[11:06] and linked to corrective action.