Custom HACCP app for CCP registration
Every business handling food must control its hazards on the basis of the HACCP principles. In practice, this comes down to daily measurement: the fridge temperature at seven o'clock, the core temperature during regeneration, the oil in the fryer. If this is done on a list on the wall, it is filled in from memory at the end of the shift and is not evidence.
What daily monitoring is all about
HACCP is not a document but a method. You map the hazards in your process, determine which points need to be controlled, set limits for them, and monitor them continuously. When a limit is exceeded, you take corrective action and record what you did. Many smaller businesses do this through an approved hygiene code for their sector, which has already carried out the analysis for them.
The obligation is set out in Article 5 of Regulation (EC) No 852/2004 and applies to every business that prepares, processes, stores, transports or serves food. There is no minimum size threshold: paragraph 3 only excludes primary production, and paragraph 4 says you take account of the nature and size of your business. The latter determines the scale of what is required, not whether you must comply. The NVWA inspects this and looks not only at whether you have a plan, but whether your records show you are working to it. The regulation itself is available on EUR-Lex.
This is where the problem lies. Paper checklists are rarely filled in at the moment of measurement. At the end of a shift, someone writes down eight readings that all just fall within the limit, and an inspector can spot that from miles away. Digital recording with a timestamp at the moment of measurement is not extra paperwork but less of it, and it provides evidence rather than a list.
This page is about taking and recording measurements itself. What must happen as soon as a reading falls outside the limit, meaning blocking, correcting and only then releasing, is described separately in the app for deviations at a critical control point.
How we build your HACCP app
Your plan or hygiene code is the starting point. The control points and limits are already set out there; we do not invent them and we do not assess them.
We review your HACCP plan or hygiene code and translate the control points into recurring tasks, each with a frequency, a responsible person and a limit. What is a paragraph in the plan becomes a measurement in the app that appears on a list.
Fridges, freezers, ovens, fryers, hot-holding equipment and the places where readings are taken by hand. Each receives its own identity with a label, so a measurement is always linked to the correct appliance.
That is where the volume lies and therefore where most of the time savings are, so that is where the build begins. Your own staff run a genuine round on an early interim version, because a kitchen is not a test environment.
We set up the corrective route and hand over to your quality manager, with a trial round in which we review the file against the questions an inspector would ask.
What the app does in practice
Loose lists become a watertight monitoring system once these six things are in place. With ten measuring points the first three are sufficient; with a hundred you need all six.
Measuring at the appliance
A label on the fridge opens the correct measurement and shows the previous readings. The record is timestamped at the moment itself, so a list of eight readings entered at half past ten at night is no longer possible.
Limits per control point
Every measurement is checked against the limit set out in your plan. A value outside it is immediately visible to the person taking the reading, rather than only at the monthly review when the product has already been delivered.
Deviation with mandatory follow-up
When a limit is exceeded, a fixed route begins: what was done with the product, which correction was carried out, and whether a new measurement was taken. The record is not closed until these steps are complete, because a deviation without follow-up is the first thing an inspection will notice.
Tasks by frequency
Daily, per shift, weekly or per production step, with a list that populates itself. A missed measurement does not disappear but remains open, so it is visible what has not been done.
Data loggers where possible
For cold rooms and freezers, continuous logging is often better than manual readings: less work and a complete picture between rounds. What can be pulled in through integrations depends on your equipment, which we'll map out before committing to anything.
File for the NVWA
Everything together by period and by measuring point, with deviations and how they were handled, exportable on request. Changes made afterwards show up as changes.
Who we build for
Who takes the readings shapes the design. A dedicated quality officer needs something different from rotating kitchen staff. Four situations.
Production and processing
Many measuring points and a process with critical steps. If you work under IFS or BRCGS, this monitoring belongs in the same system as your audit file. If you are looking for one system for the whole business, food industry software is the broader answer; this page covers only daily CCP monitoring.
Hospitality, catering and retail
Changing staff, high pressure and often several sites. Usability matters most here: a reading has to be recorded in seconds, or it gets done at the end of the shift.
Care and institutional kitchens
Vulnerable users and therefore a stricter standard, often with a central kitchen and serving points on wards. The reheating temperature on the ward is then just as critical as the cooking. If you also cook for events or external locations, catering software covers the whole chain from order to service; this page covers only the monitoring within it.
Storage and distribution
Monitoring the cold chain across several links, where continuous logging usually delivers more than manual readings, and where a deviation only counts once someone follows it up. If you process meat or fish, that monitoring is usually already part of meat processing software or fish processing software, which cover the whole production process. You build it separately when the monitoring has to span several systems or locations.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore OneDayBuild →Technology and integrations
In a cold store or kitchen, coverage is patchy and people work in gloves or with wet hands. Offline operation and many touchpoints are therefore design requirements here, not details to sort out later.
If you hold an FSSC 22000 certificate, look at our software for the FSSC 22000 audit file.
If you are a service company and also want to record the release of a machine after repair, look at our software for food machine service.
For the periodic recall test, with traceability from batch to customer and a mass balance per batch, there is our recall simulation software for food.
Why Appfront
Recording has to be faster than writing it down
As long as a paper list takes less time, it wins. Our benchmark is that a reading is captured in fewer steps than with a pen; if the design doesn't achieve that, it isn't finished.
A deviation has to set something in motion
Recording that the cooler was at nine degrees changes nothing. We build the corrective route as a mandatory follow-up step, because that is what an inspector assesses.
Built on your own plan
The control points and limits are set out in your HACCP plan or hygiene code. We adopt those rather than imposing a standard list that doesn't fit your process.
Honest about our role
We are not a HACCP consultant and we don't draw up the hazard analysis. We build the system that carries out your plan and collects the evidence; the substantive assessment remains with you and your adviser.
Security and privacy
A HACCP record contains little personal data, but it does show who took which measurement and who dealt with a deviation. That is more sensitive than it seems: an exceedance feels like a mistake by the person who reported it, when it is usually a process problem. We therefore focus reporting on the measuring point rather than the employee, because otherwise there is an incentive not to report.
During an incident or inspection, this record becomes evidence, and then reliability matters. A completed record cannot be changed silently: a correction is visible as a correction and does not overwrite the original. Photos taken of a deviation are timestamped. A list that can be edited after the fact has no value with the NVWA and can work against you. For how we handle security ourselves, see our information security policy; reports from outside come through our vulnerability disclosure policy.
Frequently asked questions about HACCP records
Almost every business that prepares, processes, stores, transports or serves food. The requirement stems from the European hygiene regulation and has no minimum business size. What does differ is the level of rigour: many smaller businesses may work with an approved hygiene code for their sector, in which the hazard analysis has already been carried out.
No. Your plan or hygiene code remains the document that sets out the hazards, control points and critical limits; that substantive work is yours or your adviser's. The app carries out that plan: it turns the control points into measurements at set frequencies, monitors the limits and collects the evidence. If your process changes, you revise the plan and we then adapt the app.
Often yes for cold rooms and freezers, and usually it's better than manual readings: less work and a continuous picture instead of two checks a day. What can be connected depends on your loggers and equipment, which we'll map out in advance. Core temperatures and visual checks remain hands-on work, but with a scan so each reading is tied to the right point.
A fixed procedure starts, and the record does not close by itself. What was done with the product, which corrective action was taken, and whether it was re-measured with an acceptable result. That follow-up is what the NVWA assesses: not whether deviations occurred, but what you did about them. A system that merely records a deviation misses exactly that.
Yes, and that's a requirement here. Cold cells, freezer rooms and kitchens often have poor coverage. The app stores data locally and syncs once there's a connection, with a clear view of which readings are still pending. We also design for use with wet hands or gloves.
Yes, and that's usually the reason to have it built. Each site gets its own measuring points and tasks, with an overview on top showing where readings are outstanding or deviations haven't been resolved. Off-the-shelf packages are often built for a single location and struggle beyond it.
These are schemes that sit on top of the statutory HACCP obligation, with their own requirements and an annual audit. The records overlap considerably. We therefore link a reading to every requirement it meets rather than duplicating it; see IFS and BRCGS audit file. If you're organic, the Skal administration runs alongside.
That depends on the number of sites and measuring points, and whether logger integrations are needed. Recording on the shop floor is usually quick to make useful and delivers the most value; the logger integration takes more effort because each manufacturer offers something different. We'll give you a reasoned estimate after the discovery phase.
Ready to build a HACCP app?
Send us a photo of the inspection list currently hanging on the wall. It shows how many measurement points you have, and usually whether readings are recorded on the spot. We build this as a standalone app and as part of a broader custom software project.