These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Pharmaceuticals QMS
- Features
- Out Of Specification
Out Of Specification
Trace a batch test exception through laboratory and manufacturing review against its linked inspection.
OverviewCheck evidence×
Pharmaceuticals QMS · Out Of Specification
New
Check evidence
Inspection checks
| Requirement | Observation | Result | Evidence | Inspection | |
|---|---|---|---|---|---|
| RQR-363 | OBS-116 | Pending | EVD-858 | INS-68210 | |
| RQR-980 | OBS-754 | Fail | EVD-975 | INS-93820 | |
| RQR-430 | OBS-468 | Pending | EVD-402 | INS-24001 | |
| RQR-676 | OBS-384 | Fail | EVD-696 | INS-54793 | |
| RQR-333 | OBS-186 | Pending | EVD-717 | INS-64330 |
6 of 6 records
RQR-363Inspection checks · IC-45089
PendingObservationOBS-116
EvidenceEVD-858
InspectionINS-68210
What you can do
Keep the test case beside the quality record
An Out Of Specification Case records a batch number, test name, observed value, specification, opened date and status. It points to an Inspection as its operational record. This link gives the case a quality context: the reviewer can move from a batch test exception to the inspection and its checks. The numeric observed value and the specification text should be read together. The record is a case for review, with a visible progression through open, laboratory review, manufacturing review and closed states.
The capture flow starts when an authorized Inspector submits a case against a selected inspection. It resolves the linked operational record and the responsible person through People. It validates case data and source evidence before saving the attributed case. The permitted path then gives Laboratory Reviewer and Manufacturing Reviewer clear handoffs. For a batch with a test outside its stated specification, those people can inspect the same case instead of passing a loose result by email.
How the work is organized
- Case capture. Associate the batch and test result with the correct operational inspection.
- Laboratory review. Examine the submitted value, stated specification and source context.
- Manufacturing review. Continue the same case after laboratory work before the final close decision.
What to agree during setup
Agree the batch number format, the exact source of the test name and how the specification should be written. Decide how an Inspector finds the operational inspection before submitting. A linked inspection is required for the case to make sense across teams. Name the Laboratory Reviewer and Manufacturing Reviewer for each product area, and settle what evidence each handoff needs. If the laboratory result originates elsewhere, establish how its source evidence is brought into the case without changing the observed result.
A case’s status shows where it is in the review path. The team should also agree when an out of specification case requires a linked nonconformance. That decision belongs in the operating procedure and must refer to the source inspection; the case alone does not replace the nonconformance and corrective action records.
Check the handoff on an actual case
Choose a real inspection reference and a sample batch. Have the Inspector submit a case with test name, observed value and specification. Try the wrong inspection link and incomplete source evidence so the capture step can reject them. Then use a valid case and follow it from open through laboratory and manufacturing review. At each step, ask the next reviewer to identify the batch, original observed value and operational inspection without asking the prior reviewer for missing context. Keep the case open until the responsible review is finished.
What your team sees
- Out of specification review — Open cases and those moving between laboratory and manufacturing review.
- Inspection queue — The source quality work associated with each operational record.
Follow the work through
See out of specification review and the linked inspection execution.
What it keeps track of
Data model- Out of specification cases
- Out Of Specification Cases records for Quality & Compliance (Source).
- Inspections
- Inspections records for Quality & Compliance (Source).
- People
- People records for Quality & Compliance (Source).
- Inspection checks
- Inspection Checks records for Quality & Compliance (Source).
Who uses it
Permissions- Inspector
- Captures the case.
- Laboratory Reviewer
- Examines the test context.
- Manufacturing Reviewer
- Follows the downstream review.
- Quality Reviewer
- Coordinates related inspection and nonconformance work.
Set up Pharmaceuticals QMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.