Appearance
Inspections Setup
Inspections setup defines the checklists and criteria that users apply during inspection work.
Workspace Reference
| Workspace | How Users Reach It | Main Actions |
|---|---|---|
| Inspection Templates | Inspections -> Setup -> Inspection Templates | Use New Template, view template detail, edit templates, review linked items, and confirm active or approval status. |
| Inspection Template Items | Inspections -> Setup -> Template Items | Use New Item, edit checklist lines, configure pass rules, set severity, and confirm required evidence behavior. |
| Quality Standards | Shared quality-specification setup where enabled | Use New AQL Level, New Defect Category, or New Measurement Spec for reusable standards consumed by inspection templates. |
Inspection Templates
An inspection template is the reusable structure for a type of inspection. It defines what should be checked and how results should be captured.
Important attributes include:
- Template name and purpose.
- Business or service scope.
- Inspection category.
- Pass, fail, scoring, or grading behavior.
- Whether evidence, comments, measurements, or attachments are expected.
- Whether review or approval is required before the inspection becomes final.
The template list shows template code, name, domain, inspection type, item count, inspection count, active status, and approval status.
Use New Template when the organization needs a reusable quality contract for a domain such as general operations, production, agriculture, manufacturing, inventory intake, assets, loans, or services.
Important template fields include:
| Field | Meaning | User Impact |
|---|---|---|
| Template Code | Short reference for the inspection template. | Helps users and reports identify the checklist consistently. |
| Template Name | Human-readable template title. | Operators should recognize which inspection standard they are selecting. |
| Domain | Service or operational area the template supports. | Allows production, agriculture, inventory, assets, or general checks to reuse the same inspection framework without mixing contexts. |
| Inspection Type | The purpose of the inspection, such as intake, final QC, safety, verification, or compliance. | Filters templates to the relevant workflow and controls reporting categories. |
| Active Status | Whether the template can be selected for new records. | Inactive templates remain for history but should not drive new inspections. |
| Approval Status | Whether the template has passed review. | Operators should use approved templates for controlled inspection work. |
Template Items
Template items are the individual checks inside a template. They represent questions, measurements, quality attributes, compliance points, or observations.
Good template items should be specific and measurable. Avoid vague checks such as "quality is good" unless the expected standard is clearly explained.
Common item types include:
- Yes or no checks.
- Numeric measurements.
- Text observations.
- Grade or rating selections.
- Evidence or attachment requirements.
Template item setup includes:
- Inspection Template: the template that owns the checklist line.
- Item Label: the question or check shown to the operator.
- Item Type: BOOLEAN, NUMBER, TEXT, SELECT, MULTI_SELECT, PHOTO, FILE, or RATING.
- Category: groups the item for review.
- Sort Order: controls checklist order.
- Severity On Fail: INFO, MINOR, MAJOR, or CRITICAL.
- Unit: used for numeric measurements where relevant.
- Required: forces the operator to complete the item.
- Active: controls whether the item remains available.
Template Item Implications
| Item Setting | What It Controls | Mistake To Avoid |
|---|---|---|
| Item Type | The kind of answer users provide: yes/no, number, text, selection, photo, file, or rating. | Choosing free text for a standard that should be measurable. |
| Required | Whether the inspector must complete the item before finalizing. | Marking every item required when some are conditionally applicable. |
| Severity On Fail | How serious a failed item is. | Treating critical safety or quality failures as minor observations. |
| Unit | Measurement unit for numeric checks. | Leaving unit blank for measurements that need consistent interpretation. |
| Sort Order | Checklist order shown to inspectors. | Allowing important checks to appear late or inconsistently. |
| Pass Rule | Automatic logic used to classify the result. | Using automatic pass/fail rules where professional judgment is required. |
Options And Pass Rules
Template items can define allowed values and pass/fail logic.
Examples include:
- pass when a yes/no check is answered Yes;
- pass when a yes/no check is answered No;
- pass when a number is at most a threshold;
- pass when a number is at least a threshold;
- pass when a value equals the expected value;
- no automatic pass rule, where the inspector chooses the outcome manually.
Use automatic rules where the standard is objective. Use manual outcomes where the inspector needs professional judgment.
Agriculture produce grading should reuse these shared standards and templates. The service may originate the produce-delivery workflow, but the grading checklist, AQL logic, defect categories, and measurement rules should remain reusable here instead of living in an agriculture-only quality ledger.
Setup Checklist
Before using an inspection template operationally:
- Confirm the checklist matches the real inspection process.
- Confirm required items are actually mandatory.
- Confirm pass, fail, grading, and scoring behavior is understandable.
- Confirm operators know what evidence to attach.
- Confirm the severity level for failed items.
- Confirm allowed values and numeric thresholds are correct.
- Confirm templates are approved and active before operators need them.
- Test a complete inspection record before releasing the template.
