Custom app for deviations at a critical control point
Almost everyone records measurements. What happens once a critical limit is exceeded is a different story: someone has to decide what happens to the product, the batch has to be held back, and that decision has to be defensible later. That moment falls in the middle of a production run that keeps going, and it is where records are weakest.
Why the deviation is the hardest step
A critical control point involves more than a measurement. There is a critical limit, a monitoring procedure, and a corrective action for when that limit is exceeded. Verification and record-keeping belong to it as well, because without those two the control cannot be demonstrated.
The measurement is the easy part. It is a number, it repeats, and there is a system for it. The deviation is not like that. Within minutes you have to determine which product is affected, hold it back before it leaves the building, and have someone with the right authority decide whether it can still be released.
In practice this happens verbally. An operator calls a team leader, something is decided, and the record follows later or not at all. In an audit or a complaint, that is exactly where the file stops: the measurement is there, the decision is not, and the question of who released it cannot be answered.
This page is about what happens once a measurement falls outside the limit. Where that limit comes from, which step is a control point and why, is covered one level up at software for the HACCP plan and control points.
How we build this
Here the deviation is the unit, not the measurement. If that creates a record with a block and a decision, accountability becomes a report rather than a reconstruction.
Which critical limit belongs to which point, and which corrective action is in your plan. That is substantive work for your quality manager; we implement it.
When a limit is exceeded, the first question is which batch or time period is involved. That follows from the previous good measurement, and we build that link in.
The block comes first and the assessment after. The other way round, the batch is already on its way before anyone makes a decision.
Who may release, on what grounds, and with what justification. That is the signature an audit looks for.
What the app actually does
The app starts where the measurement ends. Which components you need depends on your process and on how quickly products leave your site.
A deviation immediately becomes a record
As soon as a value falls outside the critical limit, a record is created with the time, the point, the value and the operator who identified it. Not a notification but a case with an owner.
Determining which product is affected
The period between the last good measurement and the deviation determines which batches are involved. Calculating that by hand costs minutes you don't have.
Blocking in a single action
The affected batch is held back before anything is decided. That is the order that gets reversed in practice, resulting in a recall.
Corrective action from your own plan
The app shows what your HACCP plan says must happen at this point, instead of an operator doing it from memory at a moment when he is in a hurry.
Release by someone authorised to do so
The decision to release after all, with its justification and the person who made it. In a complaint or an audit, this is the question that gets asked, and it has usually been answered verbally until now.
Works without a connection
In a cold store or behind steel, the network drops out. Blocking and recording carry on and sync later, with the actual time.
Who we build for
How quickly products leave your site determines how much this delivers. Four situations.
Short lead-time production
With fresh products, the lorry is already waiting. Then the difference between blocking within two minutes and within twenty is the difference between an internal deviation and a recall.
Batch production
The batch boundary is clear, and the question is which time window within the batch was affected. That makes a difference to how much you have to block, and therefore to cost.
Cooling and storage
A temperature excursion affects everything that was in that cell, and that is rarely a single batch. Determining the scope is the real work here.
Private label with customer notification obligations
Your customer wants to hear within an agreed time that something has happened. That is only possible if the file already exists at the moment you call. The certification file around it is covered on IFS software.
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
The app carries out your HACCP plan and does not replace it. Critical limits, points and corrective actions are settings that your quality officer manages.
Why Appfront
Blocking comes before deciding
We build that order in. In practice, people discuss first and block afterwards, and in the meantime the shipment drives away.
Determining the scope is a calculation, not a matter of memory
We derive the affected time window from the last good measurement. By hand, that takes minutes and leads to debate.
Release is a signature, not a conversation
We record who decided and on what grounds. That is the question in an audit and in a complaint, and it cannot be reconstructed afterwards.
The measurement comes from elsewhere
Monitoring and recording of CCP values run through HACCP monitoring; we connect to that via integrations.
Security and privacy
A deviation file is commercially sensitive in a way that goes beyond ordinary production data: it contains the cases where things went wrong and the decisions to release products anyway. We therefore set access per role, separate detecting from releasing, and log every view. An operator sees their own reports, a quality officer sees everything.
The evidential side is stricter here than for any other record. A release decision that can be amended afterwards is not a decision; and an auditor or regulator who discovers that changes were made retroactively has found a bigger problem than the excursion itself. We therefore record detection, blocking and release immutably, with time and person, and turn a correction into a visible correction alongside the original. How we handle security ourselves is set out in our information security policy; external reports go through our CVD policy.
Frequently asked questions about CCP deviations
Monitoring is about measuring and recording values at fixed moments; see HACCP monitoring and CCP recording. This app starts where that ends: at the deviation. Blocking, determining the scope, correcting and releasing are different actions with different authorities.
Technically it can, and where lead times are short it is the core of the gain. Whether it is wise depends on your process and on which system controls dispatch. What you settle in advance is who may lift the block; that is an organisational decision, not a setting.
From the period between the last good measurement and the deviation, linked to what was produced or stored in that period. How precisely that can be done depends on how fine-grained your production records are; the coarser they are, the more you have to block.
You determine that in your HACCP plan, and the app enforces it. What we build in is that release can only be done by someone with that authority, with a justification attached. Without those two, the action has happened but cannot be demonstrated.
Yes, and in a cold store or a production hall that is essential. Blocking and recording carry on and synchronise later with the actual time. We do agree in advance what happens if two people assess the same batch offline.
No. The plan, with its hazard analysis, critical control points and limits, remains the work of your quality manager. The app carries out what it says and holds those limits as a setting, so a revision does not require a code change.
Mainly with the question auditors most like to ask: show me a deviation from last quarter. If the finding, block, correction and release are in a single file with timestamps and names, that conversation is short. Otherwise a search begins, which is a warning sign in itself.
That depends on the number of control points, whether the block has to reach your production system, and how fine-grained the batch records are. The deviation file with release is usually usable quickly; the block and the integrations take more. We give a well-founded estimate after the discovery phase.
Do you know who released the last batch?
Look up the last deviation and check whether it says who decided the product could leave the building anyway. If it does not, that is the work to be done. We build this as a standalone app and as part of a broader project: custom app or custom software.