A PCB test point access review checks whether the planned production test can physically contact the required electrical nodes on the assembled board. Before PCB release, agree on the test method, contact locations, probe approach, mechanical support and assembly stage. A test point shown in CAD is not sufficient evidence that a fixture can reach it repeatedly.
This checklist is for engineers and buyers reviewing an assembly release with a test or fixture engineer. It produces an access drawing and an exception register. It does not specify universal pad diameters, probe pitches, force limits or fault coverage. Those decisions belong to the selected equipment, contact system and product requirements.
Start with the test operation, not the pad count
List what each station must do: check assembly defects, program a device, measure an output, verify a connection or exercise a product function. For each operation, identify the necessary electrical nodes and the board’s configuration at that station. Include the return connection, control signals and required power state. A pad count alone cannot show whether the intended operation is possible.
Keysight’s i3070 fixture application-note overview describes a bed-of-nails assembly that accesses board test points for structural testing. That is one equipment-specific arrangement, not a universal fixture specification. Ask the proposed test provider to review your access drawing against its actual station before committing the layout.
Separate engineering debug access from production access. A technician may reach an exposed node with a handheld probe on an open prototype; the production station may need simultaneous contacts with the board clamped and connectors attached. Record which requirement a contact serves so that removing a debug feature does not silently remove a manufacturing test connection.
Freeze a drawing that the fixture engineer can use
The following is a release worksheet. Assign an owner and a document revision to each row. Mark unresolved items as open rather than treating a missing response as approval. Include the drawing with the design for manufacturing review, while keeping test-access approval a distinct responsibility.
| Review item | Information to release | Question to close |
|---|---|---|
| Electrical identity | Test-point identifier, net name, operation and expected power state | Does each required operation have its necessary connections? |
| Coordinates | Units, origin, board side and orientation convention | Can the fixture supplier reproduce the positions without interpreting a screenshot? |
| Contact surface | Exposed target geometry, finish and solder-mask opening | Has the selected probe system been reviewed against the actual target? |
| Approach envelope | Component bodies, height limits, connectors, shields and nearby hardware | Is the entire contact approach unobstructed? |
| Support and location | Locating features, permitted support areas and clamp restrictions | Can the assembly be held consistently without loading vulnerable features? |
| Build configuration | Panel or individual board, fitted options and test stage | Does the drawing describe the assembly that actually enters the station? |
| Exceptions | Unavailable nodes, alternative checks, remaining gaps and approval owner | Has the team accepted the consequence of each missing connection? |
Keep the access drawing synchronized with fabrication and assembly data. Review a coordinate export after it is generated, especially when bottom-side views or panel transforms are involved. Record the convention explicitly instead of relying on a fixture designer to infer whether a view is mirrored. Approving the drawing should mean approving a named revision, not an untracked attachment.
Review the assembled board in three dimensions
A contact location may look clear in a copper-layer view but sit beneath a connector overhang after assembly. Include populated component outlines and relevant height information in the review. Check both the approach path and the space needed for locating, clamping and supporting the product. Consider cables or mating connectors installed during the test sequence.
Also specify when access is required. A node available before a shield, enclosure or protective material is installed may be unavailable during final test. Decide whether the earlier test provides the intended evidence or whether another interface is necessary later. The sequence must be written into the release package; a layout note alone does not define an assembly operation.
Match the contact system to the surface
INGUN’s test-probe application guidance distinguishes tip styles for different contact surfaces and emphasizes the combination of tip geometry and spring force. It also cautions about penetration with aggressive tips and higher forces. These are reasons to review the probe and target together, not to copy a generic test-pad rule into every design.
Ask the fixture engineer to identify the proposed contact parts, their operating conditions and the evidence needed to approve them. Include surface changes caused by the assembly process in that discussion. If a contact has to perform a demanding electrical measurement, have the test engineer review the complete connection and measurement arrangement as well as mechanical fit.
Example: a programming contact hidden by a connector
Consider a hypothetical controller with programming pads on the underside. A late connector change adds a plastic overhang above the fixture’s intended approach. The electrical nets have not changed, but the previous fixture-access approval is no longer enough. This is a design-review example, not a report of a customer build.
The team could evaluate relocating the pads, changing the contact approach or programming at a different assembly stage. Each option needs a named owner and a documented consequence. Programming earlier, for example, still requires a decision about later verification and access after rework. Record the selected option in the drawing and test sequence before releasing the board revision.
Close access exceptions without overstating coverage
Physical access and fault coverage are different records. A probe that reaches a node does not prove that a test detects every relevant defect. Conversely, an unavailable physical node may have an alternative test route, but that route needs its own technical review. Keep a matrix linking required checks to the approved test method and any uncovered conditions.
During the pilot build, check that the released fixture and populated assembly match the approved configuration. Record contact failures separately from confirmed product failures and investigate repeat attempts rather than deleting the original result. Use the first-build approval checklist to retain the configuration, observations, exceptions and release decision.
What to send for a test-access review
- Released PCB and assembly data, BOM variants and matching revision identifiers.
- A test-point list and access drawing with coordinates, units, orientation and board side.
- The intended test operations, assembly stage and required electrical connections.
- Mechanical models or drawings covering component heights, connectors and locating features.
- Any existing fixture constraints, unavailable nodes and proposed alternative checks.
- Build quantity, project stage and the people authorized to approve changes.
When planning an electronic manufacturing service project, agree who owns the test program, fixture design and access approval. Clear ownership makes the proposal easier to compare and keeps an open engineering question from becoming an assumed production capability.