Record the checks your people already do, with a reading, a reason and a photograph.
Quality control records the checks your people already do: material at the gate, one in-process check at the stage that matters, and a final look before despatch. Each is a parameter with a reading, a pass or a fail, a reason and a photograph. Rejections then count against the job, the operator and the supplier who sent the material.
Checking happens. Writing it down is what does not, and the notebook that does hold it sits under the weighing scale. When a consignment is returned, the argument is about memory: the fitter says he checked, the supervisor says he saw him, and neither has a paper with a reading on it.
A check becomes a short screen at the station, on the tablet that lives there. It takes a pass or fail, the measurement and a photograph if it helps. Failures ask for a reason from your own list, so after a month of failures the same three reasons are impossible to miss.
What your team uses today.
The module takes over these, one at a time, so nothing has to stop while it is set up.
- A paper check sheet filed at the station
- Photos kept on personal phones
- A verbal word from the checker to purchase
The problems this is meant to ease.
What quality control does.
What this looks like in a working week.
Illustrative scenarios, written to show the shape of the work. They are not accounts of client systems.
The people who open this every day.
From first conversation to daily use.
Walk the shop floor
Show us where checks happen now. A note names the checkpoints and the parameters to record.
Set parameters and limits
Provide limits and your list of rejection reasons. A test lot can then be checked on the trial screen.
Trial at a chosen station
Checkers use it at a station for a trial run. Their remarks return as changes.
Train checkers and supervisors
Checkers, production and purchase each practise their part. Each group gets a printed card.
Extend to every station
Other stations join as the trial station settles. The team reviews rejection reasons together.
How you would know it is working.
Record where you stand before it goes live, so the change is measured against your own figures.
- Lots rejected, by supplier
- Rejections by reason, by stage
- Rework, scrap and return, by job
- Deviations accepted, with the person who accepted
- Checks completed against checks due
It is one part of a system, not an island.
A module earns its place by what it passes to the next one. These are the connections we set up most often.
- Work orders
- Goods receipt
- Purchase returns
- Batch and serial tracking
- Sales returns
Products that include it.
How we would put it in.
Questions owners ask about quality control.
Will this make us ISO or food-safety compliant?
No. The software keeps the record and produces it on demand. Whether your process meets a standard is for your auditor and your consultant to decide, and nobody here certifies anything.
Is it a problem that our checker writes in a notebook?
Not while he is there. It becomes one when he is on leave, when a customer wants last April’s reading, or when the same defect returns and nothing counts how often. Send us even a notebook page of last year’s rejections and the first job is to count it; that tally makes the case on its own.
Will it run on a tablet at the station?
Yes. The check screen is built short enough to fill with oily hands, usually four or five fields. A tablet fixed at the station works better than a phone in a pocket. Short is the rule.
Does it connect to what we already run?
It hangs off the work order or the goods receipt, whichever you keep. Where stock sits in your accounting software, the scrap and return entries go across so the two agree at month end.
Which choices raise the cost of quality control?
Checkpoints, parameters per item and links to goods receipt and work orders. More parameters mean more screens. Each link is priced alone, and you can start without goods receipt or work orders.
What decides how long quality checks take to start?
How clearly your limits and parameters are stated. Incoming, in-process and final checks, with reasons and photographs, come first. Batch links follow. A date goes against each stage in the proposal.
Businesses that ask for this.
Modules that work with it.
Tell us how you handle quality control today.
A spreadsheet, a register or another system: say which, and we will tell you plainly what is worth changing.
What happens after you share your requirements
- A senior engineer reads your answers. Nobody phones first.
- Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
- If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
- No call is booked and nothing is paid until you have read the note. Your details stay with us.
Start with your requirements
Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.
Share your requirements