# Inspection input reference: readings, files and reasons

Use the accepted decimal grammar, attachment bounds and correction-reason limits for an inspection.

Source: https://help.smartfact.ai/manuals/checkstation/input-reference

Review edition: 25 October 2026

Roles: supervisor, operator

Use the approved check's instructions, displayed unit and repetition number while entering an inspection. The fields described here are manual entries. Follow [Record exact manual readings](/manuals/checkstation/manual-readings) for the measurement procedure.

## Reading and answer fields

| Field or control | What to enter | Checks and limits | If it is refused |
| --- | --- | --- | --- |
| Reading n of the required repetitions, followed by the unit | The exact numerical reading in the displayed unit. | Plain decimal digits with a full stop and no more than the displayed allowed decimal places. Use 0.25, not .25; do not use grouping, a leading plus sign, an exponent, surrounding spaces or unnecessary leading zeros. A minus sign is allowed only by the approved check; negative zero is refused. No rounding or unit conversion is performed. | Check transcription, unit, permitted sign and input precision against the actual reading. If the real reading cannot be represented by the approved check, stop and ask the Supervisor to review the method. |
| Record the observation | Select Pass, Fail, an approved choice, or Instruction performed and acknowledged, as the current check offers. | The selected answer must belong to this approved check. An instruction acknowledgement records that the instruction was performed. | Select the observed answer. A failed answer remains a valid recorded observation, rather than a malformed entry to replace. |
| Reviewed instrument | Select the actual reviewed instrument used, where required. | The reference must remain qualified and match the approved method revision, unit and scale. The entered reading must lie within its reviewed range. Being listed is not a guarantee that it is suitable for this check. | Check the instrument details and ask the Supervisor for a suitable reviewed reference. Do not substitute another instrument record for the one actually used. |

The allowed number of decimal places applies to what you type, including trailing zeroes. With two permitted decimal places, 12.30 has two places and 12.300 has three. The latter is refused even though the numerical amounts are equal. Keep the actual measurement and approved reporting precision consistent; do not round a value to obtain acceptance.

An approved engineering input range is separate from the pass limits. A value outside the input range is refused without a physical observation being recorded. A representable value inside that range but outside an acceptance limit is recorded as nonconforming and places a hold. Use [failures and release](/manuals/checkstation/failures-and-release) for the resulting decision.

## Evidence file bounds

Evidence file offers only the file types admitted by the selected check, and the screen states its file count and per-file MiB allowance. Choose a non-empty file within that allowance, then Inspect and prepare file. The actual content type, malware scan and structure are checked; renaming an extension does not establish a permitted format.

A PDF must not exceed 50 pages. An image must not exceed 24,000,000 pixels in total. The attempt can attach at most ten files and 30 MiB (31,457,280 bytes) in total, with no more than three files against one evidence check. The same file hash cannot be attached twice to that check. A smaller per-file limit in the approved check still applies.

Inspect the prepared file details, then attach it to the intended check. A prepared file alone is not an attachment. Preparation is tied to the attempt revision, check and preparing person, and expires after 15 minutes. If it expires or the attempt changes before attachment, refresh, inspect the current check and prepare the file again. At capacity, ask the Supervisor to review the evidence requirements rather than adding duplicate copies. See [inspection evidence](/manuals/checkstation/inspection-evidence).

## Correction and review reasons

Corrected entry uses the same reading or answer validation as the original check. What was transcribed incorrectly? requires at least three characters in the form and a non-blank explanation. The server limits correction and review reasons to 1,000 Unicode characters, including where a review textarea permits more. Keep the account concise and specific to the exact entry or file.

A fresh measurement after further physical work belongs in a [full retest](/manuals/checkstation/full-retests). Use a [transcription correction](/manuals/checkstation/transcription-corrections) for an inaccurately entered original observation. If the original has already been corrected, inspect its retained successor rather than proposing another replacement of the old entry.