Prepare for the API SIEE credential by studying the decision layer of source inspection of electrical equipment: how purchase specifications and inspection and test plans define what you verify, how hold, witness, and review points differ, how to judge acceptance test records and nameplate data, and how to document nonconformances and deviations. The API Individual Certification Programs page is the reference for application steps, exam windows, and administrative details; this guide concentrates on the reasoning skills the subject itself demands.
What source inspection of electrical equipment actually verifies
Source inspection means verifying, at the manufacturer's facility, that electrical equipment conforms to the purchase specification and applicable standards before shipment. Your role is evidence-based acceptance, not redesign or advisory engineering.
In a source inspection context, you act on behalf of the purchaser at the vendor's plant. The equipment may be switchgear, motors, transformers, panels, or similar electrical assemblies, and the pattern of your work is the same regardless of product: confirm that materials, workmanship, and tests match what the purchaser ordered and what the referenced standards require. You verify against documents, observe or witness activities, and record results.
The distinction that shapes everything else is the boundary of your authority. A source inspector accepts, rejects, or holds material based on the contract documents; you do not waive requirements, reinterpret specifications to suit production schedules, or approve substitutions on your own initiative. When you study, frame each topic as a question of evidence: what document authorizes this check, what record proves it was done, and what happens when the two disagree.
Hold points, witness points, and review points: telling them apart under time pressure
A hold point stops work until the inspector is present and releases it; a witness point is an observation opportunity that the vendor may proceed past if the inspector does not attend; a review point is evaluation of records after the activity.
These three terms describe very different obligations, and confusing them produces wrong answers in both exams and real jobs. At a hold point, the manufacturer must not proceed without you; missing one means the activity may have to be repeated or formally dispositioned. At a witness point, you are invited to observe, but if you are absent the vendor can continue, which is why attendance records matter. A review point asks you to evaluate documentation, such as test reports, against requirements after the fact.
Practice attaching consequences to each type. If you miss a hold point on a pressure or dielectric test, the practical question becomes whether retest is required and who authorizes it, not simply whether you can review the paperwork later. If a vendor proceeds past a witness point, your later review is limited to whatever records they produced. Building this habit of asking 'what happens next given the point type?' is more valuable than memorizing the definitions in isolation, because reasoning about consequences forces you to apply the concepts instead of merely recalling their labels.
| Point type | Inspector's obligation | If the inspector is absent | Typical evidence produced |
|---|---|---|---|
| Hold point | Vendor must wait for inspector attendance and release before continuing | Activity may require re-performance or formal disposition | Attendance sign-off and the activity record |
| Witness point | Inspector observes a notified activity; observation is an opportunity, not a gate | Vendor may generally proceed with the activity | Notification record, observation notes, test report |
| Review point | Inspector evaluates completed records against requirements | Review occurs on the records that exist, no re-observation | Reviewed and accepted (or rejected) documents |
| Surveillance | Unannounced general oversight of ongoing work | Coverage is partial; findings depend on what was observed | Surveillance notes and any resulting findings |
Reading the purchase order and ITP as your inspection contract
The purchase specification, purchase order, and inspection and test plan (ITP) together define your scope: what to inspect, which standards apply, which points you attend, and what records must exist before shipment.
Treat the purchase documents as the controlling hierarchy. The purchase order and specification state what was bought: ratings, enclosure and environmental requirements, applicable codes, and required tests. The ITP translates that into a sequence of inspection and test activities, each assigned a verification level. When you study a topic such as factory acceptance testing or nameplate verification, always start by asking which document line item it serves, because acceptance in source inspection is always acceptance against the contract, not against general best practice.
A disciplined reading order helps: identify the equipment scope, then the referenced standards, then the required tests with their acceptance criteria, then the ITP's assigned verification points. Note anything the ITP does not cover that the specification requires, because gaps between the two are where inspection decisions become genuinely difficult. In your study notes, take one purchase-style requirement and trace it forward: which ITP line covers it, what test proves it, what record demonstrates it. That tracing exercise builds the habit of connecting each requirement to its evidence, which is the same reasoning you practice with paper scenarios.
Worked scenario: a factory acceptance test record below the specified level
When a witnessed test record shows a value or duration below the specification's acceptance criterion, the record documents a nonconformance; acceptance requires retest or a formally authorized concession, never a verbal assurance.
Scenario: you witness a dielectric (high-potential) test on a medium-voltage assembly. The specification requires a stated test voltage applied for a stated duration. Afterward, the vendor's test record shows a lower voltage than specified, with a handwritten annotation that the 'equivalent' level was used and a technician's initials. The vendor's lead tells you the equipment passed and asks you to sign so the shipment can meet its load-out date.
The tempting mistake is signing on the basis of the verbal explanation, because the annotation looks like a rational adjustment. The better decision is to treat the record as evidence that the specified test was not performed as required: report it as a nonconformance, request retest at the specified parameters, and, if the vendor believes a lower level is justified, route that through a documented deviation or concession approved by the purchaser's authorized representative. Why it matters: your signature is your professional attestation that requirements were met. Accepting a substitute test level without documented authorization means the equipment ships with no valid evidence of conformance, and the paper trail no longer supports the acceptance you recorded.
Worked scenario: nameplate and rating discrepancies at final inspection
A nameplate that does not match the purchase order's ratings, enclosure type, or identification requirements is a discrepancy to be dispositioned in writing; comparing nameplate data line by line against the purchase documents is the verification habit that catches it.
Scenario: during final inspection of a motor before shipment, you compare the nameplate against the purchase order. The nameplate shows a different insulation class than specified and a serial number that does not match the number on the certificate of conformance. The vendor explains that the correct nameplate is 'on order' and offers to email a corrected certificate after shipment so the crane and transport scheduled for that week are not delayed.
The mistake is allowing the substitution of future paperwork for present evidence: if the shipped unit and its records disagree, every downstream recipient inherits the discrepancy. The better decision is to hold acceptance, raise a nonconformance report identifying both the insulation class difference and the serial number mismatch, and require either a corrected nameplate applied and re-verified before shipment, or a written purchaser disposition that explicitly accepts the unit as delivered. Why it matters: nameplate data is the permanent identity of the equipment; a mismatch can invalidate the asset's traceability, its installation design checks, and its maintenance records for its entire service life.
Nonconformance reports, deviations, and the documentation you must be able to produce
A nonconformance report records a condition that does not meet requirements; a deviation or concession is documented, authorized acceptance of a specific departure. Inspectors must know which document they are writing and who has authority to approve it.
These two instruments are frequently conflated, and the difference is central to professional source inspection. An NCR is the objective record that something fails to conform: identify the item, the requirement violated, the evidence, and the proposed disposition (rework, repair, retest, use-as-is, or reject). A deviation or concession is not the inspector's tool; it is the purchaser's documented decision to accept a defined departure, granted before or through formal disposition. The inspector's contribution is accurate reporting, not approval of departures on their own authority.
Beyond the NCR, plan to produce and recognize the standard documentation set: attendance records for hold and witness points, completed checklists, test reports reviewed against acceptance criteria, the certificate of conformance, and a punch list of outstanding items cleared before shipment. A practical exercise you can run at home: take any equipment datasheet you can access, draft a one-page mock ITP with at least one of each point type from the table above, then write the evidence list you would need to close each line. Expected observations: you will find at least one line whose acceptance criterion you cannot state, which is exactly the gap to study next. Self-check rubric: for each line you can name (1) the governing requirement, (2) the verification method, (3) the record produced, and (4) the consequence of a failed result. Four of four means the line is solid; two or fewer means rework that topic.
A preparation sequence and readiness checks for SIEE study
Build study in layers: purchase documents and ITP interpretation first, verification point decisions second, test and nameplate verification third, and nonconformance documentation fourth, checking readiness after each layer with scenario work.
An adaptable sequence over several weeks: begin by reading a purchase specification and datasheet and tracing requirements into a mock ITP, as described above. Next, drill the point-type table until you can state the consequence of absence at each point type without hesitation. Then work acceptance-test reasoning with paper scenarios: write the decision you would make for a below-spec test record, a lapsed witness notification, and a missing review record, and check your decisions against the logic in the scenarios in this guide. Finish each cycle by drafting an NCR and the covering note you would send to the purchaser.
Use readiness checks that test reasoning rather than recall. You are ready to move on when you can, without notes: distinguish a hold point from a witness point by their consequences; state which document controls when a vendor's practice conflicts with the specification; identify whether a situation calls for an NCR or a purchaser concession; and list the evidence set required to close out a shipment. You are exam-ready in this subject area when a fresh scenario produces a correct decision plus the correct document and the correct authority in under a minute of thought. Self-check scores from the rubric earlier are learning milestones for pacing your study, not predictions of any exam result.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.