Reconstructing a food batch: a practical traceability exercise with verified records

Source → Verification → Decision → Evidence

A batch number appears in a supplier document, a production sheet, a warehouse entry and a delivery record. Those entries can disagree without anyone noticing during ordinary work. The difficulty emerges when the quality team needs to reconstruct a batch quickly. A search finds many files, but some describe planned production, others actual production and others a corrected quantity. The team needs confirmed relationships, not a plausible narrative assembled from similar numbers.

Start with an exercise for a historical batch whose outcome your team already understands. The deliverable is a reconstruction packet: sources, relationships, quantities where available, unresolved differences and a responsible reviewer. AI can help locate records and draft the packet. Your organisation decides the safety response and any withdrawal, recall or notification. This guide describes Brillnet's recommended exercise design and separates it from the legal requirements cited below.

Set the exercise boundary with the food business operator

Define the establishment, product, period and systems included. A batch can cross several production stages and external parties. State which part of that journey you are testing. A successful reconstruction inside one bakery does not establish that every supplier and customer has equivalent records. Make the boundary visible on the packet cover.

Choose an actual historical record without unnecessary personal information. Confirm who may access commercial and supplier documents. Ask the operator's responsible person to approve the test objective and identify the reference answer. A test based solely on what the assistant finds cannot reveal a document the assistant failed to retrieve.

Article 18 of Regulation 178/2002 addresses traceability within its scope, including systems and procedures for identifying relevant suppliers and business recipients. Article 19 addresses responsibilities concerning unsafe food, including withdrawal and related actions in the circumstances specified there. Check the applicable duties for the actual activity. The exercise structure proposed here is not a universal legal template. [1]

Establish identifiers before searching for connections

Record the finished product batch identifier exactly as the approved system stores it. Keep formatting differences visible: a leading zero, separator or supplier prefix can distinguish two identifiers. If you normalise values for search, preserve the original value alongside the normalised one. A convenient match should remain reversible to its source.

List the identifiers used at each stage: incoming material lot, internal production order, intermediate batch, finished batch and shipment. One identifier can connect to several later records, while a later batch can use materials from several earlier lots. The packet should show those relationships explicitly rather than forcing everything into one flat row.

Do not accept proximity in time as proof of a relationship. Two deliveries received on the same day may contain different lots. If the production sheet lacks a link to the incoming material record, the assistant should mark a missing relationship. The responsible reviewer can investigate; the draft should not fill the gap with the most likely supplier entry.

Separate planned quantities from actual records

A production plan describes intended activity. An actual production record describes what staff recorded as happening. A warehouse adjustment changes stock, and a shipment record describes movement to a recipient. Label each source type so a reviewer does not accidentally reconcile a plan against a later delivery as if both were confirmed physical events.

Record the unit with every quantity. Kilograms, packs and individual items do not become comparable merely because a spreadsheet stores them in one numeric column. When a conversion is necessary, link to the approved conversion rule and its version. Keep the calculation in the packet so another reviewer can reproduce it.

The exercise should expose unexplained differences, including waste, retained samples, rework and adjustments where relevant. Do not describe a quantity difference as a safety incident solely because it exists. Classify it as an unresolved record difference until the responsible person determines its meaning. That avoids turning an accounting inconsistency into an unsupported operational conclusion.

Build a relationship table that points to originals

The reviewer should be able to open the evidence for every connection. Store a document identifier, version or timestamp, the relevant location within the source and the person who checked it. If a file changes during review, the packet needs a stable reference to the version actually used.

This table is a recommended design, not a claim that every operator must use those exact documents. Some establishments use a single integrated record, others several controlled systems. Adapt the design to the actual process while retaining a way to verify the relationships.

Test a fictional discrepancy without treating it as a result

Consider an illustrative bakery exercise. One receipt records 240 kilograms of a material. Production entries link 210 kilograms to two finished batches. A stock record shows 20 kilograms remaining. Ten kilograms are unexplained in the first draft. These invented numbers demonstrate how to present uncertainty; they are not business data or a benchmark.

The assistant should show the 10-kilogram difference and the sources used in the calculation. It should not invent a waste event to make the totals balance. The reviewer might find a documented sample, a correction or an incorrect unit. If the evidence remains missing, the packet keeps the issue open with a named owner and next investigation step.

The quality team separately considers whether the missing record affects a safety decision. A reconciliation table can support that assessment, but it cannot determine food safety merely by balancing quantities. A mathematically complete packet may still omit a critical product or process condition.

Keep HACCP documentation within its proper purpose

Regulation 852/2004 addresses food hygiene, and Article 5 concerns procedures based on HACCP principles within its scope. Assess the activity and applicable treatment of primary production. The Commission's guidance and Codex materials provide context for food safety management and hygiene practices. They should not be replaced by an assistant's generic checklist. [2][3][4]

If the reconstruction requires a monitoring record or corrective action from your food safety system, link to the controlled original. Record which question that evidence answers. A traceability relationship, a hygiene check and a batch-release decision serve different purposes. Keep those distinctions when presenting the packet to management.

An AI summary of a deviation may omit its exact time, product condition or operator observation. Verify those details against the original before relying on the summary. For the first exercise, have the responsible person review every safety-relevant statement. Define the point at which the assistant must stop and ask for a missing source.

Design access around the selected batch

The task can usually start with read access to the selected records and a draft-output area. Supplier contracts, staff files and unrelated customer information need their own access justification. Do not give a model a broad database credential simply because one search is difficult to configure.

Enforce the scope in the integration layer. A supplier attachment can contain misleading instructions, and OCR can create accidental command-like text. Neither should change permissions or cause an external message. Test that a document cannot instruct the assistant to send the packet to a new recipient.

Where names, contact information or other personal data enter the process, assess the GDPR requirements for purpose, legal basis, access, processor arrangements and security. Supplier and customer records can combine commercial information with personal data. Limit what the draft packet copies into a new location. [5]

Define the response to an uncertain or urgent result

The exercise owner needs a clear route for a missing relationship, conflicting record or possible safety concern. Provide a responsible contact and the information required for escalation. The assistant should show a status such as “relationship not verified” rather than a generic success label that hides the problem.

A historical test must not accidentally trigger a live recall message, warehouse block or notification. Keep operational actions outside the initial integration's permissions. When the organisation conducts a live response, the designated people apply its procedures and the relevant legal obligations. Article 19 must be read in its actual circumstances; this exercise does not supply a universal notification decision. [1]

Record the test's start and end, the people involved and the unresolved issues. If the operator already runs traceability exercises, connect the new method to those records. A separate AI dashboard should not become an unowned second account of the same event.

Evaluate completeness and reviewer effort together

Measure whether the packet reconstructs the reference relationships, uses the correct source versions and exposes known missing evidence. Track wrong links separately from missing links. A wrong link can appear complete and lead the reviewer toward the wrong batch; it deserves more attention than a visibly unresolved question.

Include the time spent finding, checking and correcting records. A draft produced in seconds is not a useful saving if the quality team spends longer verifying it than preparing the existing packet. Compare exercises of similar difficulty and report the sample size. Do not generalise from one clean case to the operator's whole portfolio.

Try a missing receiving record, a reused supplier number, a unit mismatch and an unavailable source system. The manual route should still work. Staff should know which controlled records to consult and who resolves a disagreement when the integration cannot produce a packet.

Connect evidence and learning after the exercise

Pulsar GRC is being developed in early access to organise requirements, controls, risks, corrective actions and evidence from customer documents. Its proposed fit here is organising the exercise record and follow-up actions after the available scope is confirmed. It is not offered as a HACCP guarantee or an independent decision about food safety.

CrewShift, known as Zmianowo in Polish, is being developed for document-based training and tests with human approval. A verified procedural change can become learning material after review. Course completion does not establish practical competence or authorisation to perform a task independently. The responsible organisation defines and records any required practical assessment.

Bring an anonymised batch packet, the source-system map and one difficult discrepancy to an implementation discussion. That allows the first deliverable to be defined precisely: a reconstruction that a reviewer can reproduce, with uncertainty visible and the operational response owned by the food business.

Review a reconstruction with one unresolved relationship

Consider a fictional reconstruction in which the finished batch and shipment are known, but the material-use record does not identify the supplier lot. A receipt from the same day looks plausible. The assistant links it and produces a complete-looking diagram. The quality reviewer should reject that connection unless the actual record or an authorised investigation supports it. A visually complete relationship map is not a substitute for evidence.

Keep the plausible candidate available as an investigation lead and label it as unverified. Show why it was selected, such as the product identifier or date, and what evidence is still needed. The reviewer can then distinguish an unsupported match from a confirmed relationship. Removing the uncertainty marker merely to simplify the packet would make the result less reliable.

The next action should identify the person who investigates the missing link and the source that person will check. They might consult a receiving record, an approved production entry or a documented correction according to the establishment's process. The assistant should not generate a replacement material-use entry that appears to have existed at the time of production. A later investigation needs its own date and explanation.

When the responsible person confirms or rejects the candidate, retain the decision and its supporting evidence. Recalculate any affected quantity reconciliation using the verified relationship and the stated units. Keep the earlier draft available to authorised reviewers if it is needed to explain the correction. A later clean total should not erase the history of an unsupported assumption.

The food business separately assesses whether the missing relationship affects a safety response. This example does not determine that every record gap requires a recall or that a balanced reconstruction proves safety. It shows where the document workflow should stop and hand an unresolved question to the designated people. They apply the establishment's procedures and the relevant legal obligations.

For pilot evaluation, compare the draft with a reference packet containing the known missing link. Check whether the system exposes the gap, whether the reviewer finds it and how much effort the investigation requires. Include the cost of correcting the source system if necessary. Brillnet recommends that full-work measure because a quick reconstruction that leaves extra manual reconciliation can increase the team's workload. The fictional case and evaluation design are author recommendations, not a prescribed traceability template.

Sources

The sources support the identified legal facts, guidance and public product scope. Workflows, fictional examples and evaluation measures are Brillnet's operating recommendations. Source review: 2026-10-04.

1. European Parliament and Council — Regulation 178/2002, particularly Articles 18 and 19: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02002R0178-20240701
2. European Parliament and Council — Regulation 852/2004, particularly Article 5: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02004R0852-20210324
3. European Commission — food hygiene and HACCP guidance: https://food.ec.europa.eu/food-safety/biological-safety/food-hygiene/guidance-platform_en
4. Codex Alimentarius — official codes of practice, including General Principles of Food Hygiene: https://www.fao.org/fao-who-codexalimentarius/codex-texts/codes-of-practice/en/
5. European Parliament and Council — GDPR: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02016R0679-20160504
6. Pulsar GRC — public product scope and early-access status: https://pulsar-grc.com/en/
7. CrewShift / Zmianowo — training, tests and the meaning of a completion record: https://crewshift-app.com/en