The plan drifts away from the process Every change is a trigger The reasoning, not just the outcome

Custom software for your HACCP plan and control points

At most companies, the HACCP plan is a Word file that was drawn up properly once. After that, a new product was added, a process step moved and a supplier changed. The plan did not move with them. What gets measured every day then comes from an analysis of a different process than the one you actually run.

Where the plan drifts away from the process

HACCP rests on seven principles from the Codex Alimentarius: analyse hazards, determine control points, set critical limits, organise monitoring, record corrective actions, verify, and document what you do. The first three are design work and happen once. The last four are daily work. Software almost always focuses on those last four.

That is understandable, but it leaves the biggest risk unmanaged. If a control point sits at the wrong process step, or if a limit value is not substantiated, you are faithfully measuring the wrong thing every day. In an audit, that is a more serious finding than a missed measurement, because it goes to the foundation of your system rather than its execution.

The triggers for a review are also more concrete than people think. Every change to a product, process, supplier or packaging is a reason to revisit the hazard analysis. In practice, those changes happen weekly while the plan is reviewed annually. That difference in pace is exactly where the gap opens up.

How we build this

The process flow diagram is the foundation. Hazards, control points and limits attach to a step, not to a chapter in a document.

1
Record the process as data

Every step with its inputs and outputs. As long as the process flow diagram is a drawing in an appendix, nothing can be attached to it and everything drifts apart.

2
Attach hazards to a step

Biological, chemical and physical, per step, with an assessment of likelihood and severity. That makes it visible which steps have been left empty.

3
Record the decision tree with its answers

Not just the outcome but the path that led to it. In an audit, the question is about the reasoning, and that lives in the answers, not in the conclusion.

4
Let changes reach the plan

A new product, a different supplier or a moved step puts the relevant analysis up for review. Without that link, the plan goes out of date unnoticed.

What the software actually does

The process flow diagram with the hazard analysis carries everything. What else you need depends on how many products and lines you have and how often something changes.

Hazard analysis per process step

Hazards per step with likelihood, severity and the control measure. A step without an assessment stands out, and that is the finding you want to discover yourself.

Decision tree with its answers preserved

The path to the conclusion, not just the conclusion. Why something is or is not a control point is the first question that comes up in an audit.

Limits with their justification

Every critical limit with the source it relies on: a legal standard, literature or your own validation. A limit without justification is an assumption.

From plan to daily measurement

What needs to be measured, how often and by whom follows from the plan and is passed on from there to recording on the shop floor.

Review on change and at set intervals

A new product or a different supplier reopens the relevant analysis, and the periodic review runs alongside it. Two triggers, one flow.

Versions you can lay side by side

When a complaint comes in about a batch from last year, the question is which plan applied at the time. That is a different question from what applies now, and most systems can only answer the second.

Who we build for

How often the plan falls behind depends on how often your process changes. Four situations.

Production with changing recipes

Every new product affects the analysis. This is where the gain is greatest, because the trigger for a review occurs most often here.

Storage, repacking and distribution

Fewer process steps but more third-party products. The hazard analysis then relies more heavily on what your supplier controls, and that changes with every supplier switch. For tracing this there is BRCGS software.

Primary production and fresh produce

Short chains with seasonal influences. Control more often lies in prerequisite conditions than in measurements during the process, and that calls for a different set-up.

Companies with multiple lines or sites

The same product on two lines can have different control points. A single plan for everything is then inaccurate, and a separate document per site is unmanageable.

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

Standards and insights change, and so does your process. Everything to do with hazards, decision rules and limit values should be configurable and stored with version history.

Node.js / Python / .NET PostgreSQL Process flow as data Hazards per step with assessment Decision tree with stored answers Limits with source references Validation and verification recorded Review on change Versions that can be compared side by side Handover to monitoring Multiple lines and sites Export for the auditor Audit logging Hosting in the EU

Why Appfront

The plan is the source of all measurements

We build the analysis as data, so that what is measured daily genuinely follows from the analysis and not from habit.

The justification is the audit

We store the answers in the decision tree and not just the outcome. Auditors rarely ask about the conclusion, but always about the route to it.

A change must affect the plan

We link product changes and supplier switches to the analyses involved. Otherwise the plan ends up a year behind the process.

The question is about then, not now

We build versions that can be compared side by side, because with a complaint about an old batch, the plan that applied at the time is what counts.

Security and privacy

A hazard analysis records your recipe and your process steps, along with the places where things can go wrong. That is commercially sensitive information, and also information you do not want to show a customer unfiltered. We set access per role and per product, and log every view.

For this subject, the version history is itself a requirement. You must be able to show which plan applied at the moment a batch was produced, and that only works if earlier versions have not been overwritten. We keep every change to a hazard, a limit or a control point with timestamp and person, and show an amendment alongside the old value rather than over it. How we handle security ourselves is set out in our information security policy; external reports go through our coordinated vulnerability disclosure (CVD) policy.

Frequently asked questions about the HACCP plan

A registration app records the daily measurements. This software is about the plan those measurements come from: which hazards exist, which steps are control points and why, and which limits apply. If that is wrong, you faithfully measure the wrong thing.

The CCP app is about what happens as soon as a measurement falls outside the limit: blocking, correcting and releasing. That is the execution of principle five. This page is about principles one to three, where that limit and that corrective action are determined.

No. Determining control points is the work of your HACCP team, which knows your product and process. We build the place where that reasoning is recorded, with the answers from the decision tree and the justification for each limit, and where it comes up for review again as soon as something changes.

Besides a periodic review, any change to a product, process, supplier or packaging is a reason to revisit the hazard analysis. In practice that happens more often than the annual round many companies stick to. That difference in pace is where the plan drifts away from the process.

Validation answers the question of whether the chosen measure actually controls the hazard; you do that before you put the plan into use, using literature, a standard or your own research. Verification answers the question of whether it also happens in practice, through internal audits and checks after the fact. Both need to be documented.

Yes, and usually you have to. The same product on two lines can have different control points, for example because one line has a metal detector and the other does not. A single plan for everything is then incorrect; separate documents per site are unmanageable. We build variants on top of a single analysis.

Yes. The food safety plan is a fundamental part of both standards, and the evidence you record here ends up in your certification file. We link the two rather than mixing them; see also IFS and BRCGS software.

That depends on the number of products and process steps, whether there are multiple lines and how much has already been documented. The process flow diagram with the hazard analysis can usually be put to use quickly and immediately shows where the gaps are; review workflows and variants grow from there. We give a well-founded estimate after the discovery phase.

Want to know whether your plan still reflects your process?

Take the latest product you have added and look up where it appears in the hazard analysis. If it isn't there, you have been measuring ever since on the basis of an analysis that doesn't know about it. We build this as a standalone application and as part of a broader custom software project.

Edit content