Checks that stop a document, not a note in a folder.
Inspections with reading-level acceptance criteria that can refuse a receipt or a delivery, non-conformance raised against the procedure it breached, and corrective actions with owners and dates. The management system and the operational records are the same records.
6 feature areas·14 record types·Blocks the document, not a report
What is inside the Quality module.
Six areas, from the check on the receiving dock to the management review that reads the year. What makes this different from a document library is that the criteria act on live transactions.
Inspection
The check itself, at the three points it happens.
Inspection templates
A named set of parameters per item or item group, so the same product is checked the same way by whoever is on shift.
Parameters and readings
Acceptance defined per parameter as a value, a range, or a formula, with the reading recorded — so 'passed' means a number somebody can go back and check.
Three inspection points
Inbound on purchase receipt, in-process at the job card, and outbound before delivery, each with its own template.
Blocking behaviour
Set per company: an unsubmitted or failed inspection stops the document from submitting, or warns. Stop means the receipt does not post.
Mandatory per item
Flagged on the item or the BOM, so the requirement follows the product rather than depending on memory.
Sample size and batch
The inspected quantity recorded against the batch or serial it represents, which is what makes a recall traceable.
Rejection routing
Failed quantity sent to its own rejected warehouse rather than mixed into good stock.
The management system
Goals, procedures, and processes as records rather than a shared drive.
Quality goals
A named goal with its objectives, each with a target, a measurement unit, and a period, owned by a named person.
Quality procedures
A procedure tree with parent and child procedures, each holding its own ordered process steps.
Processes within a procedure
The individual steps, so a procedure is executable rather than descriptive.
Linked to what happens
Non-conformance and actions reference the procedure and process they concern, so the system is connected to the work.
Ownership
Every goal, procedure, and action has a named owner, which is the difference between a system and a folder.
Revision history
Every version of every procedure with who changed it and when, kept by the platform rather than by a naming convention.
Non-conformance and action
What happens when something fails, and who is doing something about it.
Non-conformance
Raised against the procedure and process it breached, with a status, a severity, and a named owner.
Corrective and preventive action
A quality action typed corrective or preventive, with its own resolution table of steps, owners, and completion dates.
Resolutions
Each step of an action recorded separately with who did it and when, so closure is evidenced rather than asserted.
Root cause on the record
Held against the non-conformance rather than in an attached document nobody opens again.
Link to the transaction
The failed inspection, job card, receipt, or ticket that caused it, so the investigation starts from the actual event.
Cost of poor quality
Rejected and scrap quantities and rework job cards roll up, so the cost is a figure rather than an argument.
Review
The cycle that proves the system is running.
Quality reviews
A dated review against a goal, with each objective's target set beside what was achieved.
Review objectives
The individual measures inside a review, so the outcome is per objective rather than one overall verdict.
Quality meetings
Agenda and minutes as records against the meeting, with actions raised from it linked back.
Actions from review
Anything arising becomes a quality action with an owner and a date, rather than a line in minutes.
Audit evidence
Because inspections, non-conformance, actions, and reviews are all documents with trails, the evidence pack is a report rather than a project.
Feedback
What customers say, structured enough to count.
Quality feedback
Structured feedback against a customer or supplier using a template, scored per parameter rather than captured as free text.
Feedback templates
Named parameter sets, so responses across a year are comparable.
Link to the party
Held against the customer or supplier record, alongside the transactions it refers to.
Into supplier scorecards
Supplier quality feeds the scorecard variables that decide standing, which can then warn on or block new orders.
Where the agents sit
The quality work that is monitoring, gathering, and chasing.
Failure pattern detection
Rejections grouped by item, supplier, batch, workstation, and shift, with the pattern named rather than left in a table.
Overdue action chasing
Corrective actions past their date escalated to their owners, and to the owner above them on time.
Review preparation
Objectives, measurements, open non-conformances, and closed actions assembled before the review meeting.
Audit pack assembly
Evidence for a named standard or customer audit gathered from the live records, with the gaps listed.
Limits and approval
An agent may gather and prompt. Closing a non-conformance and signing off an action are always a named person's decision.
One pass through quality, end to end.
- 01
Define
Templates set what is checked and what counts as acceptable, per item or item group. Goals, procedures, and their processes are recorded with named owners.
- 02
Check
Inbound, in-process, and outbound inspections record readings against criteria. A failure routes stock to rejected and stops the document where you set it to.
- 03
Act
Non-conformance is raised against the procedure it breached, with a root cause and a corrective action whose steps have owners and dates.
- 04
Review
Objectives are measured against target in a dated review, meetings raise further actions, and the evidence pack for an audit is a report off live records.
The switches that decide how it behaves here
- Inspection not submitted
- Stop the document, or warn
- Inspection required
- Flagged per item or per BOM, not per occasion
- Rejected warehouse
- Named, so failed stock is never mixed in
- Acceptance basis
- Value, range, or formula, per parameter
- Action escalation
- To the owner, then above them, on a set delay
- Procedure revisions
- Versioned by the platform, with who and when
- Feedback templates
- Named parameter sets, so a year is comparable
- Supplier standing
- Warns on or blocks new orders, by your rule
Every document this module keeps.
Quality Inspection
Readings against parameters, able to block a document.
Quality Inspection Template
A named parameter set per item or item group.
Quality Inspection Parameter
One criterion, with its acceptance value, range, or formula.
Quality Goal
A goal with objectives, targets, units, and a period.
Quality Procedure
A procedure in a tree, holding its ordered process steps.
Non Conformance
A breach against a procedure, with severity and an owner.
Quality Action
Corrective or preventive, with resolutions and dates.
Quality Action Resolution
One step of an action, with who did it and when.
Quality Review
A dated review of a goal, objective by objective.
Quality Meeting
Agenda and minutes, with the actions raised from it.
Quality Feedback
Structured, scored feedback against a party.
Quality Feedback Template
The parameter set that makes responses comparable.
Job Card
Where in-process inspection and rework are recorded.
Purchase Receipt / Delivery Note
The documents inbound and outbound checks can stop.
Reports that ship with it, not ones you commission.
- Quality Inspection Summary
- Passed, failed, and pending by item, supplier, and period.
- Non Conformance Summary
- Open and closed by procedure, severity, and owner.
- Quality Action Status
- Corrective and preventive actions against their due dates.
- Batch-Wise Balance History
- Where an affected batch went, for recall.
- Serial No Ledger
- Every document a given unit appeared on.
- Supplier Scorecard Variables
- Quality inputs behind each supplier's standing.
- Job Card Summary
- Rejected and scrap quantity by operation and workstation.
- Purchase Receipt Trends
- Received against rejected volume by supplier and period.
- Issue Analytics
- Customer-reported failures by type and product.
Next step