Manual Inspection
The Blind Spot in Your Test Automation Data

If you're reading this, you already know the stakes. Production flaws don't stay on the factory floor but end up in returns, recall notices, legal battles, and headlines. What's less obvious is how often the early warning signs were there all along, buried in a spreadsheet no one looked at twice.

Manual inspection is where many of those signs live. And for most manufacturers, it's also where data goes to die.

Why non-digitized manual inspection creates blind spots

When manual inspection results aren't captured in a structured, digital format, the consequences are predictable: blind spots open up in your production analytics, root cause analysis becomes guesswork rather than evidence, and full traceability across a unit's lifecycle is simply out of reach. Quality issues rarely announce themselves; they accumulate quietly until they're expensive.

This article walks through what solving that actually looks like and how to digitize your inspection process, and what you gain when all your test data lives in one place.

The problem with pen, paper, and Excel

Most production lines in electronics include anywhere from a few to many manual checkpoints, from visual inspections, physical measurements, assembly verification, or functional checks that can't (yet) be automated.

Operators perform these checks carefully. They record the results. And then, in most cases, that data is never seen again. The data sits in a static spreadsheet. Or a paper log. Or a shared folder no one remembers to check.

The result is a blind spot at the center of your production data. Your automated tests produce rich, structured data that feeds into dashboards and analytics. Your manual inspections produce... a column in a file from three months ago.

This matters because patterns and root causes don't respect data silos. A 3% defect rate showing up in manual LED inspection might point directly to a PCB board issue - however only if you can correlate that manual data with the rest of your data. If the data lives in isolation, the pattern stays invisible until it's expensive.

What digitized manual inspection actually looks like

Manual inspections cover the checkpoints where automated test equipment isn't available, isn't practical, or simply isn't efficient. Basically the steps that still require human judgment.

Replacing paper with a structured digital system doesn't have to mean rebuilding your inspection process from scratch.

In WATS, this happens through the Operator Interface: a dedicated application where technicians scan or enter a unit's serial number and are guided step by step through the relevant inspection sequence. The interface is designed to be simple enough for any operator, with an instruction PDF pane on the right that scrolls automatically to match the current step - so your documentation and your inspection stay in sync.

The inspection steps themselves can include:

• Numeric limit steps: the operator enters a measured value, and the system automatically applies pass/fail limits
• Pass/fail steps: a simple go/no-go decision, with optional image attachment for visual defects
• Message and instruction steps: guidance text or images shown to the operator at key points
• Wait steps: for timed procedures
• Sub-sequences: nested sequences for complex, branching flows

When the operator submits the completed inspection, it generates a Units Under Test (UUT) report - the same structured format as your automated test results. That means all your inspection data lands in the same system, ready to be analysed alongside everything else

Designing inspection sequences: more control than you might expect

Inspection sequences are built and managed in the WATS Control Panel, using a graphical sequence designer. You don't need to write code — you assemble steps visually, set limits and options for each one, and upload instruction PDFs that operators will see during the inspection.

A few features worth knowing about:

Instruction PDFs. You can attach any number of PDFs to a sequence and link each step to a specific page or search term. This keeps your technical documentation directly connected to the inspection steps, rather than living in a separate folder no one opens.

Relations. Each sequence can be linked to specific part numbers, batch numbers, serial number ranges, or station names. This means when an operator scans a unit in the Operator Interface, they only see the inspections that are actually relevant to what they're working on, not a list of every inspection in the system.

Global sequences. If you have a set of steps that recur across multiple inspections, for example a standard safety check, you can define it once as a global sequence and reuse it as a sub-sequence anywhere you need it.

Version control. Sequences follow a Draft → Pending → Released workflow. You can develop and test a new version of an inspection without it going live, and release it to all users in a single click when it's ready. If you need to revise a released sequence, you copy it (the new copy automatically gets the next version number), make your edits, and release the new version. This automatically revokes the previous one.

When a unit fails: closing the full loop

This is where things get interesting and where paper-based inspection falls completely apart.

When a unit fails a manual inspection, the story isn't over. It typically goes to a repair cell, gets reworked, and then needs to be retested.

In a paper-based system, failure, repair, and retest are often recorded in different places, by different people, in different formats. Connecting them later is either difficult or impossible.

In WATS, you can configure exactly how this flow works for each inspection:

Inspection only. The operator submits the failed result, the unit moves to a repair cell, and a separate repair report is logged and linked to the original failure. The full story, failure, repair, retest, is captured and connected.

Inspection with inline repair. When the inspection fails, the repair interface appears immediately in the same session. The operator logs the failure cause and the corrective action before submitting. One session, two linked reports.

Inspection, repair, and automatic retest. After logging the repair, the inspection restarts automatically. The operator completes the full cycle, inspect, repair, retest with minimum clicks and a complete audit trail as the output.

There's also a specific case worth mentioning: units that fail automated testing not because of a unit defect, but because of a fixture issue, a software problem, or faulty test equipment. In these cases, you can run a manual verification and document the root cause alongside the override, keeping the record honest rather than simply deleting the failed report.

What you get when on the other side

Once manual inspection data is flowing into the same system as your automated test results, a few things change:

Patterns become visible. Correlate manual inspection failures with upstream automated test results. Find out which stations, part numbers, or batches are generating the most manual failures, and whether those failures cluster around specific automated test outcomes.

Costs come down. The further down the line a failure is caught, the more expensive it is to fix. Digitized inspection data lets you identify upstream causes earlier, before rework costs compound.

Operators are consistent. Guided sequences with defined step types and embedded instructions remove ambiguity from the inspection process. Every operator follows the same steps in the same order.

Traceability is complete. Scan any unit's barcode and see its full history: every automated test result, every manual inspection, every repair, in sequence. Nothing is lost, and nothing has to be reconstructed from memory. See how you can configure barcode scanners in WATS

See Manual Inspection in action

Reading about it is one thing. Seeing an actual inspection sequence being built, released, and executed, including the repair integration, is another.

Our Integration Architect Ola Reppe recorded a full walk-through of WATS Manual Inspection, covering the sequence designer, the operator interface, repair flows, tips and tricks and best practice.

Watch the recording

Or if you'd like to see how it fits into your specific production setup, book a 30-minute demo with one of our specialists.