Inspections

A quality manager creates an inspection number, identifies the subject, selects incoming, in-process, final or service work, and sets a scheduled date. The assigned inspector sees the work on My Inspections and can open the inspection before the planned date. This keeps the inspected subject and the person doing the work in the same record. The team can use the subject reference to match the inspected item with its operational context during review.

• Plan the assignment. The quality manager selects an inspection type and assignee, then reviews the Inspection Queue for planned work.
• Capture each requirement. The inspector opens Inspection Checks and Details, records an observation and result for each linked requirement, and attaches evidence where the check needs it.
• Submit for decision. The inspector moves a complete inspection into review. The reviewer reads the check outcomes and accepts or rejects the inspected scope.

The conduct workflow checks the current inspection state and linked check evidence before review. If a required check lacks an observation or result, the submission is rejected. Inspectors should resolve that gap on the check record, then submit again. A check marked not applicable still needs an explicit result so the reviewer can distinguish it from unfinished work.

Agree how teams identify the subject in the reference text, who can assign inspections, and which inspection types apply to each operating area. Decide what evidence an inspector should attach for a failed result and how reviewers will identify the affected scope. Those choices make the review decision repeatable across shifts.

Set a practical rule for when an inspection can be scheduled and who takes over an assignment if the original inspector is unavailable. Confirm that the inspector and reviewer are separate people where your operating policy requires independent review. The role design should make the decision clear to everyone who uses the review inbox.

Take a final inspection for a finished lot. The quality manager records the lot identifier as the subject reference and assigns the inspector. The inspector starts the planned inspection, works through the linked checks and records one failing result with its observation. The submit action should place the inspection in review only when every required check is complete. The reviewer opens the inspection and the related check detail, rejects the failed scope and creates a linked nonconformance for containment.

Run the same rehearsal with passing checks. The reviewer should be able to accept the scope, with the original observations still attached to the inspection. Compare the two paths in Inspection Status Board. This lets a manager see which work remains planned, which is under review and which has received a decision.

• Inspection Queue — Scheduled and active work with its assignee, type and current state.
• Inspection Review Inbox — Completed check work awaiting the reviewer’s decision.
• Inspection Status Board — Inspection records grouped by their current decision state.

Follow inspection review for the conduct and decision path. For a rejected scope, continue to nonconformance and correction.