Wearable device engineering services at NexPCB are done when the deliverables named for that agreement are in hand, at the approved revision, complete against that list, and accepted on the condition the agreement names. The list can include the schematic, the board layout, design for manufacture and test, the housing, the engineering-validation prototypes, and the bring-up test firmware the requirement names. The smart-ring list later in the file is the hardware file set that was shown for that package. Leaving firmware off that list describes the files that were listed. It does not by itself put firmware outside the contract. The schematic and the layout say what has to be frozen before those files mean the package is done.
What has to be written before the wearable schematic
The schematic starts after the interfaces, the power, and the function this version has to perform are written as requirements. A circuit drawn before those three are written has no requirement to be reviewed against. The review of the schematic is a review against that requirement.
Interfaces, power, and the function are the requirement a later layout is checked against. A layout that moves a function comes back to this requirement.

What the smart-ring package contained
The wrist-worn tracker in the photograph beside this case is a generic concept. It is not the smart ring, and it is not a photograph of that package.
| Deliverable | What it records | On the smart-ring hardware file set that was shown |
|---|---|---|
| Gerber | Board fabrication data | Listed in that set |
| Bill of materials | Parts the build buys | Filed with the Gerber |
| Pick-and-place | Where each part sits | Held with the fabrication data |
| Design source | The editable design | Kept with those fabrication files |
| Schematic PDF | The circuit as reviewed | Issued as that PDF |
| Layer stackup | The board stack | Paired with the schematic |
| Firmware | Drivers, host software, integration, or the product application | Not in the hardware file set that was shown. That omission does not put firmware outside the contract |
The smart-ring hardware file set that was shown was the Gerber, the bill of materials, the pick-and-place file, the design source, the schematic as a PDF, and the layer stackup. Firmware was not in that list. Whether firmware sat in the contract is a separate question from the list. The fabrication files are what a DFM review checks before tooling.
The layout is what those fabrication files are deciding, on a schematic that is already frozen. A package is done when the approved revision is complete against the named list and meets the acceptance condition in the agreement.
What the device layout is deciding
Layout places the parts, and the routing it chooses changes electrical behavior, radio performance, and heat. Connector direction and the power path sit on a schematic that is already frozen. It leaves the circuit function on the schematic. A layout change that moves a function back into the schematic is a schematic change. The layout still waits until that requirement is written again.
One product requirement limited the engineering work to the hardware platform: schematic, board layout, design for manufacture and test, the housing, engineering-validation prototypes, and bring-up test firmware for the sections that requirement named.

What firmware the package includes
On a multi-channel project the team can own the schematic, the layout, and a basic test setup. Drivers depended on the chip vendor's software kit. Driver development, host software, system integration, and product application firmware are in the package when the agreement names them. Where the software scope is still open, that open scope stays open. It is not work already finished, and it is not a decision that the work sits outside the agreement. Production delivery starts from the package that is in hand. The contract page is the place that names the boundary (the contract).
Frequently asked questions
Which files close a wearable engineering package?
The files named in the agreement, at the approved revision, complete against that list, and accepted on the condition the agreement names.
When is firmware inside the package?
When the agreement names it. A hardware file set that does not list firmware describes that list. It does not by itself put firmware outside the agreement. On the multi-channel project, an open software scope stays open until it is named.
What to bring to the first conversation
Bring the deliverable list you expect at the end, and mark which firmware, if any, you want inside it. If a product requirement already limits the work to the hardware platform, send that. The schematic comes across after a non-disclosure agreement. Start at our project inquiry form.