# Review and accept a declared evidence file

Check exact source, coverage, duplicates and conflicts before admission.

Source: https://help.smartfact.ai/manuals/lottrail/review-and-accept-files

Review edition: 25 October 2026

Roles: supervisor

Use the supported strict JSON source envelope for the selected declared dataset. Obtain stable source event identities, exact references and explicit coverage from the responsible source owner. The website does not accept arbitrary raw CSV or guess a vendor mapping.

## Stage the authorised file

Open the ordinary evidence intake page, choose the Declared dataset and supported file, and complete recent Accounts authentication when requested. File safety and strict structure checks must pass. An unavailable scanner refuses intake; it does not provide an unscanned fallback.

A private unfinished review can be resumed by its uploader while it remains available. Do not share a review link as a substitute for the other person's source rights or authentication.

## Inspect the whole declaration

Under Review before acceptance, check source instance, generation, scope and Declared coverage. Read sequence and time boundaries, declared completeness and warnings. Inspect counts of new, duplicate and conflicting events and the bounded event examples.

The preview displays only bounded examples, not every event. Check the original approved file through your organisation's process when full source review is needed. A declared complete snapshot can still have a missing sequence or uncaptured relationship.

A reused event identity with different content is a conflict. Acceptance holds the candidate for review without admitting its events. Do not change identifiers or delete inconvenient rows merely to avoid the conflict. A backwards or narrower source checkpoint can also refuse new admission.

## Refresh and accept current bytes

Use Refresh this review before acceptance where offered. Acceptance needs a fresh preparation bound to exact bytes, actor, session, dataset state and recovery authority. A changed dataset requires a refreshed review and another explicit confirmation.

Choose Accept this reviewed file only after checking the warnings. Exact replay of an admitted file reconciles without creating new facts. A lost answer must be settled through the original command rather than uploading under invented event identities.

The private review lasts thirty minutes, while final preparation is shorter. An expired review needs a fresh upload. Read the current displayed expiry rather than assuming an old tab remains valid.

## Hand over the outcome

Check the retained intake record and dataset state. New evidence affects later investigations, not the bytes of earlier saved reports. Use [corrections and late evidence](/manuals/lottrail/corrections-and-late-evidence) for restrictive notices and [run an investigation](/manuals/lottrail/run-an-investigation) for the next authorised question.

## Confirm again after refreshing

Choose the Evidence file (.json) control for ordinary intake. After reviewing the current file identity, dataset and declared coverage, select the declaration beginning I have reviewed this dataset, file identity and declared coverage. Then choose Accept this reviewed file.

Refreshing the review clears that declaration. Read the refreshed information and confirm it again, rather than assuming an earlier checkbox applies to changed dataset state. An unavailable or expired private review needs the offered current preparation path; it is not permission to bypass acceptance.