4 questions that show if your supplier really uses APQP

Table of Contents
    Add a header to begin generating the table of contents
    19/06/2026 12:57 pm
    APQP
    The prototype worked. What could still go wrong later?

    Four decisions made during design can prevent late validation problems, production changes and field failures.

    The prototype works. The first tests are positive. The electronics fit the product, and the project appears ready to move forward.

    Then a problem appears later.

    A requirement is understood differently during validation. A component changes, but it is not clear which tests must be repeated. A function that worked in the laboratory is difficult to check on the production line. Or one fault affects more of the product than expected.

    This does not always mean that the original design was poor. In many cases, one important decision was still open while the project continued to move.

    The good news is that these decisions are not random. The same four areas appear again and again in electronics projects.

    Download the one-page PDF (no form) →

    The four decisions a board needs before it is built

    APQP · Design FMEA

    01 Can one fault stop the whole product?

    Some products depend too much on one board, one signal or one control function. This may not be visible during normal operation. The problem appears when one fault affects the full machine instead of one limited function.

    Decided early

    The team identifies which failures can stop the product and decides where protection, monitoring, backup or a safe state is needed. The board architecture can then include the right response from the beginning.

    Left for later

    The risk may only become clear during validation or in the field, when the architecture is already fixed. A small fault can then require a board change, a new validation cycle or a different control strategy.

    APQP · Design verification

    02 Is every important requirement measurable?

    Words such as “quiet”, “fast”, “stable” or “efficient” sound clear during a meeting. But different people may understand them in different ways.

    Decided early

    Important words become values, limits and test conditions. “Low noise” becomes a sound level. “Fast response” becomes a maximum response time. “Stable temperature” becomes an agreed variation around the set point.

    Left for later

    Without a number, different teams may work toward different targets. The product can pass one test and fail another because both sides were using a different definition of success.

    APQP · Change control

    03 What happens when a component or process changes?

    Changes are normal in electronics. Components become obsolete, materials change, processes improve and firmware is updated. The problem is not that change happens. The problem is when its effect is not clear.

    Decided early

    The team defines how changes are recorded, reviewed, approved and tested. Everyone knows which changes need information, which need technical review and which need new validation.

    Left for later

    A new component or process may enter production before its full effect is understood. The difference may only appear during validation, production or field use, when the approved product no longer behaves in exactly the same way.

    APQP · Control plan

    04 Can every critical function be tested in production?

    A function can work well in the laboratory and still be difficult to check on the production line. This often becomes visible only when the product reaches series production.

    Decided early

    The board layout, test points and control logic allow the line to check every critical function on each unit. The production team knows what to measure, which limits apply and what happens when a unit fails.

    Left for later

    Some functions may be difficult to confirm without changing the board, adding manual work or reducing test coverage. The result can be longer cycle times, incomplete checks or problems that only appear after shipment.

    What these four decisions have in common

    One decision is about risk. One is about requirements. One is about change. One is about production control. But they all have the same purpose: to make quality part of the design before there is anything to inspect.

    Advanced Product Quality Planning (APQP) is the practical idea behind these four decisions. It helps the customer and supplier agree requirements, risks, tests and controls before production starts. APQP does not guarantee that no problem will ever appear. It makes important decisions visible while the design is still open and changes are still easier to make.

    Use these four questions before your next board is built

    Before the next design review, ask:

    1. 1Can one fault stop the complete product?
    2. 2Are the important requirements measurable?
    3. 3Is there a clear process for changes?
    4. 4Can every critical function be tested in production?

    If one answer is unclear, the project may still continue. But the open decision should be visible, assigned and closed before it becomes a late surprise.

    A prepared electronics supplier should be able to explain how these decisions are reviewed and controlled. This is not about adding more paperwork. It is about making important decisions while they are still easy to change.

    An electronics design and manufacturing partner for manufacturers

    KELD is an electronics design and manufacturing partner for manufacturers in HVAC, ventilation, motors, pumps and refrigeration. We apply APQP from the first idea, so these decisions are settled with you — before the board is built. See how we work with your team.

    Review these four decisions with KELD

    Before your next electronics project moves from prototype to production.

    Request a Technical Discovery Call →

    latest insights