# Export evidence for LotTrail

Download this site's kits, jobs and checked component serials and lots as files LotTrail admits, and admit them in order.

Source: https://help.smartfact.ai/manuals/kitproof/export-evidence-for-lottrail

Review edition: 13 November 2026

Roles: owner, supervisor

Use this when your organisation traces lots and serials in LotTrail and wants KitProof's records there: which kits were made for which job, and which component serials and component lots were checked against each kit's requirement when it was verified. KitProof writes them as files LotTrail admits as they stand. It sends nothing and connects to nothing: you download the files here and a LotTrail Supervisor admits them there, one at a time. You need the Owner or Supervisor role, at the real site, and your authenticator confirmed in the last five minutes; Accounts asks for it on the way. The export works whatever your plan, including after it has ended. The sample workspace has none.

## Register this site in LotTrail once

Open Overview and find Evidence for LotTrail. Under To register this source in LotTrail it shows four values, named as LotTrail's Create a declared dataset form names them:

- Source instance ID, such as `kitproof:01JC3Z5K8Q4N7R2T6V9X0B1D3F`. It is this site's, and it never changes.
- Source generation, which is the history: 1 to begin with.
- Declared scope code: `kitproof.lottrail-evidence/v1`.
- Relationships this source can record. Tick exactly verified component and context reference, and nothing else.

Copy each value with its Copy button and give them to the person who creates the dataset in LotTrail, with the data owner and permitted readers your organisation chooses. A dataset in LotTrail keeps these values for good. LotTrail's own steps are in [admit a SmartFACT product's export](/manuals/lottrail/admit-a-smartfact-export).

## Export new records

Select Export new records. KitProof prepares the export within about a minute; select Check again to see it. The first export holds every kit of this site with a verification, the jobs they were made for, and the serials and lots checked for them; each later export holds what is new since the one before, and corrections for anything withdrawn. Records are numbered from 1, with no gaps, and every file says which numbers it holds. If the export did not finish, the panel says why. No record was given a number, so the next export starts where that one did.

A busy site's first export is several parts, each a file. Select Download on each part. Each file's name starts `kitproof-lottrail-`, sorts in the order the parts are admitted, and is kept here for a day. After that, Write again writes the same file, byte for byte, with the same checksum.

## Admit the parts in order, one at a time

The panel lists the exports newest first, and each export's parts in order. Start with the oldest export and with part 1 of each. Every part says which part to admit before it. In LotTrail, stage one part, compare its File checksum with the Checksum the panel shows for that part, accept it, and only then stage the next.

LotTrail does not stop a part being admitted out of turn. If you stage a part that skips records, LotTrail warns that records are missing and asks for a second tick before it will accept the file. Do not tick it for a KitProof part: admit the earlier part first.

A part marked Corrections withdraws records already exported. Admit it in its place in the order, like any other part.

## When a part was skipped or lost

If a later part was accepted in LotTrail before an earlier one, LotTrail refuses the earlier part as it was written. Open If a part was skipped or lost, choose the skipped part and the latest part LotTrail has accepted, and select Write this part. The file holds exactly the skipped part's records, stated as the later part stated its coverage, so LotTrail accepts it and the gap closes. It is listed under the parts written that way.

If a part's file is no longer kept here, select Write again on that part.

## When the history starts again

After this installation is restored from a backup, the record numbers given since that backup cannot be trusted, so the panel asks you to start the next history before anything more is exported. Select Start history 2 (or the next number). Everything is then exported again from record 1 under the new source generation, and LotTrail needs a new dataset with that generation: register it as before. The same happens if KitProof's mapping ever changes its scope code.

You can also start a new history yourself, with a reason, under Start a new history, for example when a dataset in LotTrail cannot be put right. Do this only when the LotTrail data owner has agreed, because it means a new dataset and admitting every part again.

## What the export says, and what it does not

A kit is stated under its printed reference, `KP1:` and its code, so scanning a kit's label in LotTrail finds it. A job is the job reference under the order source that holds it. A serial or a lot is stated under the component it belongs to, so the same lot code under two components is two lots. Each kit is linked from its job, and from every serial and lot that was checked against its requirement when it was verified. A kit completed with exceptions is exported the same way, with what was checked; the result itself, Verified or Completed with exceptions, is not in the file.

When a verified kit is reopened for rework, or its job changes after it was verified, KitProof stops treating that verification as standing, and the next export withdraws its links. The kit, its job and the serials and lots stay stated: they were true when recorded. When the rework is verified, its links follow as new records. A verification reworked before it was ever exported is never exported.

The export never says that a component was fitted: a check against a requirement is not proof of assembly. It holds no component without a serial or a lot, no rejected or reversed scan, no kit in progress or cancelled, no approval, waiver or manual count, no bin scan, and no people. In LotTrail, start from a job to see its kits, from a serial or a lot to see the kits it was checked for, or from a kit to see its job and the serials and lots checked for it. LotTrail's view of physical inputs and outputs has no answer from KitProof, because KitProof does not record them.

A record whose values a LotTrail file cannot hold, such as a serial longer than 120 characters (KitProof accepts up to 128), is left out and listed on the panel with the reason, and so is a kit's verification that names it. Every file from then on says the history is incomplete. Each record is tried again at every export.

## How much LotTrail can investigate

LotTrail refuses an investigation over 50,000 events across the datasets chosen. A kit is two events (the kit and its job link), and each serial checked for it adds two (the serial and its link) and each lot one more link; a job or a lot shared by many kits is stated once. A kit like the reference control box, with one serialised controller and two fuses of one lot, is about six events, so 50,000 events is about 8,000 such kits. A kit with four serialised components is about ten events, so about 5,000 kits. It is fewer when KitProof's dataset is investigated together with another. The panel shows how many events this history has exported, so you can compare.
