From preparation to serving Measuring where the work happens Deviations with follow-up

Custom HACCP app for CCP registration

Every business that handles food must control its hazards on the basis of the HACCP principles. In practice, it all comes down to the daily measurement: the cold store at seven in the morning, the core temperature when reheating, the oil in the fryer. If that happens on a sheet on the wall, it gets filled in from memory at the end of the shift, and it is not evidence.

What daily monitoring is all about

HACCP is not a document but a way of working. You map the hazards in your process, determine at which points they must be controlled, set limits there, and monitor them continuously. If a limit is exceeded, a correction follows and you record what you did. Many smaller businesses do this via 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 lower limit based on business size: paragraph 3 exempts only primary production, and paragraph 4 says you take the nature and size of your business into account. That determines how extensive your system needs to be, not whether you need one. The NVWA (Netherlands Food and Consumer Product Safety Authority) inspects this and looks not just at whether you have a plan, but at whether your records show that you follow it. The regulation itself is available on EUR-Lex.

That is where the problem lies. Paper sheets are rarely filled in at the moment of measurement. At the end of the shift, someone writes down eight measurements that all fall just within the limit, and an inspector can spot that from a mile away. Digital recording with a timestamp at the moment of measurement is not extra administration but less, and it is evidence rather than a sheet of paper.

This page is about measuring and recording itself. What needs to happen once a measurement falls outside the limit, meaning blocking, correcting and only then releasing, is described separately under 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 in there; we do not invent them and we do not assess them.

1
Turning your plan into tasks

We go through your HACCP plan or hygiene code and translate the control points into recurring tasks 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 checklist.

2
Mapping the measuring points

Cold stores, freezers, ovens, fryers, hot-holding equipment and the places where measurements are taken by hand. Each gets its own identity with a label, so a measurement is always linked to the right piece of equipment.

3
Daily measurements first

That is where the volume is, and therefore most of the time savings, so that is where the build starts. Your own people do a real round early on with an interim version, because a kitchen is not a test environment.

4
Deviations and handover

We set up the correction route and hand over to your quality manager, with a trial round in which we go through the file using the questions an inspector would ask.

What the app actually does

Loose sheets become watertight monitoring once these six things are in place. With ten measuring points, the first three are enough; with a hundred, you need all six.

Measuring at the equipment

A label on the cold store opens the right measurement and shows the previous values. The record gets a timestamp at that very moment, so a sheet with eight measurements filled in at half past ten in the evening no longer happens.

Limits per control point

Every measurement is checked against the limit in your plan. A value outside it is immediately visible to the person measuring, instead of only at the monthly check when the product has already been delivered.

Deviation with mandatory follow-up

An excursion triggers a fixed route: what was done with the product, which corrective action was carried out, and whether it was measured again. The record only closes once those steps are complete, because a deviation without follow-up is the first thing that stands out in an inspection.

Tasks by frequency

Daily, per shift, weekly or per production step, with a list that fills itself. A missed measurement doesn't disappear but stays open, so it's visible what hasn't been done.

Loggers where possible

For cold and freezer rooms, continuous logging is often better than manual measuring: less work and a complete picture between rounds. What can be pulled in via integrations depends on your equipment; we map that out before we promise anything.

File for the NVWA

Everything together per period and per measuring point, with the deviations and how they were handled, exportable whenever requested. Changes made afterwards are visible as changes.

Who we build for

Who takes the measurements determines what the design looks like. A dedicated quality employee 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're looking for one system for the whole company, software for the food industry is the broader answer; this page is solely about daily CCP monitoring.

Hospitality, catering and retail

Rotating staff, high workload and often multiple locations. Usability comes first here: a measurement must be recorded in seconds, otherwise it gets done at the end of the shift.

Healthcare 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 preparation. If you also cook for events or external locations, catering software covers the whole chain from request to serving; this page is only about the monitoring within it.

Storage and distribution

Monitoring the cold chain across multiple links, where continuous logging usually delivers more than manual measuring 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 entire production process. You build it separately when the monitoring has to run across multiple systems or locations.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

In a cold store or a kitchen, coverage is patchy and people work with gloves or wet hands. Offline working and large touch targets are therefore design requirements, not details to add afterwards.

If you want to record temperatures and batch numbers at the batch itself, on the production floor, read more about our fresh production app for specialist shops.

If you also want to be able to practise and substantiate a recall, read more about our software for recall simulation and notification files.

If you hold an FSSC 22000 certificate, take a look at our software for the FSSC 22000 audit file.

If, as a service company, you also want to record the release of a machine after repair, take a look at our software for the breakdown service of food machinery.

For the periodic recall test, with tracing from batch to customer and a mass balance per batch, there is our recall simulation software for food.

Native iOS and Android Offline-first storage QR and NFC labels at measuring points Integration with temperature loggers Bluetooth thermometers Node.js / Python / .NET PostgreSQL Limit values per control point Time series per measuring point Photo for a deviation Alerts and escalation Export for inspection Audit logging of changes Hosting in the EU

Why Appfront

Recording must be faster than writing it down

As long as a paper list takes less time, paper wins. Our benchmark is that a measurement is recorded in fewer steps than with a pen; if the design doesn't achieve that, it isn't finished.

A deviation must set something in motion

Recording that the fridge was at nine degrees changes nothing. We build the corrective-action 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 HACCP consultants and we don't draw up hazard analyses. We build the system that carries out your plan and gathers the evidence; the substantive assessment stays 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, whereas it is usually a process problem. We therefore focus reports on the measurement point rather than the employee, because otherwise people have an incentive not to report.

In the event of an incident or an inspection, this file becomes evidence, and what counts then is whether it is reliable. A completed record cannot be changed silently: a correction is visible as a correction and does not overwrite the original. Photos attached to a deviation are timestamped. A log that can be edited afterwards carries no weight with the NVWA and can work against you. How we handle security ourselves is set out in our information security policy; reports from outside go through our CVD policy.

Frequently asked questions about HACCP records

Almost every business that prepares, processes, stores, transports or serves food. The requirement comes from the European hygiene regulation and has no lower limit based on company size. What does differ is how demanding it is: many smaller businesses may work with an approved hygiene code for their sector, in which the hazard analysis has already been done.

No. Your plan or hygiene code remains the document that sets out the hazards, control points and limits; that is substantive work for you or your adviser. The app carries out that plan: it turns the control points into measurements with a set frequency, monitors the limits and gathers the evidence. If your process changes, you revise the plan and we then adapt the app.

For cold rooms and freezers, often yes, and that is usually better than measuring by hand: less work and a continuous picture instead of two readings a day. What can be integrated depends on your loggers and equipment; we map that out beforehand. Core temperatures and visual checks remain manual, but with a scan so that the measurement is tied to the right point.

A fixed route starts and the record does not close by itself. What was done with the product, which correction was carried out, and was it measured again with a good result. That follow-up is what the NVWA assesses: not whether there are deviations, but what you did about them. A system that only notes a deviation misses exactly that.

Yes, and here that is a requirement. Cold rooms, freezers and kitchens often have poor coverage. The app stores data locally and syncs as soon as there is a connection, showing clearly which measurements are still pending. We also design for use with wet hands or gloves.

Yes, and that is usually the reason to build it. Each site gets its own measurement points and tasks, with an overview on top showing where measurements are outstanding or deviations have not been resolved. Off-the-shelf packages are often built for a single location and get stuck there.

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 measurement to every requirement it satisfies instead of duplicating it; see IFS and BRCGS audit file. If you are organic, the Skal records run alongside this.

That depends on the number of sites and measurement points, and on whether integrations with loggers are involved. Recording on the shop floor is usually quick to get working and delivers the most; the logger integration costs more because every manufacturer offers something different. We give a substantiated estimate after the discovery phase.

Building a HACCP app?

Send us a photo of the recording sheet that currently hangs on the wall. From that we can tell how many measurement points you have, and usually also whether measurements are entered at the moment they are taken. We build this as a standalone app and as part of a broader custom software project.

Edit content