A supplier describes a cellular module as "FCC and PTCRB certified." Your team still needs a plan for the sensor, gateway or other device that will contain it. Start by connecting the module documents to the exact product configuration: the selected variant, firmware, antennas, other radios and intended use. That gives engineering, purchasing and the test lab a shared basis for deciding which existing work can be reused and what the device needs next.
This checklist uses a US cellular IoT device as its market example, with T-Mobile as the operator example. It separates the regulatory, industry-program and operator records you will collect. For the earlier hardware shortlist, use the cellular module selection guide; the regional variant checklist covers market and ordering details.
Separate the three approval records
Ask what the word "certified" refers to on each document. A module grant, an industry-program listing and an operator acceptance record answer different questions. Give each its own line in the project record.
Three records to distinguish in a US cellular IoT project.
Scroll horizontally to read all columns.
| Record | What to identify | Next discussion |
|---|---|---|
| FCC equipment authorization | The module FCC ID, grant conditions and integration instructions | Module grantee and the team handling the host equipment authorization |
| PTCRB / IoT Network Certified | The certified component and the certification route for the assembled device | A test lab authorized for the applicable program |
| Operator acceptance | The intended network and its device intake requirements | The operator device certification team |
The PTCRB certification page directs IoT devices to IoT Network Certified, a program that uses PTCRB certification of embedded modules. Its device certification process also calls for government compliance and a check for additional operator testing. Keep those tasks visible in the schedule alongside the component purchase.
Match the documents to the part you will buy
Request the manufacturer name, full regional variant, hardware revision and proposed firmware build. Record the complete ordering code when the quoted configuration is settled. A family brochure is useful for finding candidates; use the documents for the selected part when reviewing its integration conditions.
For the FCC record, obtain the grant reference and the manufacturer's integration instructions. Check that the named model and FCC ID match the supplied part, then read the grant comments and any host restrictions together with the instructions. Ask the module manufacturer to explain a limited approval or a condition that your design does not clearly meet.
For the industry record, ask for the module certification reference, the applicable software identity and the route for supplying supporting reports to the test lab. The October 2026 IoT Network Certified guide describes the module manufacturer providing its certification reports and PICS documentation to that lab. PICS is the protocol implementation conformance statement that identifies supported capabilities. Ask who will provide these files and record the document revisions.
Review the host configuration with the module manufacturer
The FCC's Module Integration Guide v02 assigns the host manufacturer responsibility for following integration conditions and addressing requirements outside the module grant, including applicable digital-circuit requirements. Review the actual assembled product, with its enclosure, power supply, cables and radio operating modes.
Host details to send with the module integration questions.
Scroll horizontally to read all columns.
| Design item | Information to provide | Question for the review |
|---|---|---|
| Antenna system | Antenna type, gain, cable loss, connector and installation drawing | Does this arrangement meet the grant and integration instructions? |
| RF exposure use case | How the product is installed and the distance between antennas and people during use | Does the proposed use fit the authorized conditions, or need further evaluation? |
| Other transmitters | Wi-Fi, Bluetooth and other radios, with the modes that can transmit together | Which simultaneous-transmission conditions and assessments apply? |
| Host electronics | Enclosure, supply, interfaces, cable set and representative operating modes | Which host emissions and equipment-authorization work should enter the test plan? |
| Labels and user instructions | Proposed product label and relevant installation/manual pages | Which module identification, statements and installation instructions belong on this host? |
Use the specified antenna and exposure conditions for the selected authorization. For antenna drawings and cable details, the LTE and 5G antenna guide helps assemble the engineering information. Give the manufacturer any proposed departure from its instructions before freezing the design.
Agree the device test and operator route
First classify the product you are submitting. The IoT Network Certified guide distinguishes a finished IoT device from a module or embedded modem, with conditions for final use and host interfaces. Send a block diagram and a description of the finished assembly to the authorized lab. Ask it to identify the applicable route and the certified component work it can use.
The program guide describes additional device testing as typically covering network performance, the SIM interface and radiated spurious emissions. The lab determines the scope for the device. Ask for a written test plan tied to the submitted configuration, with separate entries for regulatory work and the industry program.
Questions for the authorized test lab
- How do you classify this assembled product, and which program and test-plan revisions apply?
- Which module reports and PICS files do you need, and should the manufacturer send them directly?
- Which antenna, RF exposure, host-emissions and network-performance checks remain for this configuration?
- Which samples, test modes, fixtures and documents should we prepare, and who will review design changes?
T-Mobile publishes a separate device certification process and OEM prerequisites. Its checklist names PTCRB certification, OEM functional results, RF over-the-air performance and device compliance documents. Because the PTCRB site directs IoT products to IoT Network Certified, ask T-Mobile which program record and reports it expects for your device category. Confirm that answer with the lab before booking tests.
Questions for the operator team
- Which certification record and reports do you accept for this device and the selected module?
- Which firmware, network features, functional results and RF performance criteria should the submission cover?
- Which device identity/TAC, IP-version and SIM/service details must we supply?
- What is the review path for later hardware, firmware or application changes?
Keep the operator response with the project configuration. A module entry in a device catalog helps identify that component; use the device intake response to plan the assembled product's submission.
Keep one reusable integration record
Use a shared sheet to connect documents, configuration and unresolved actions. Each evidence link should identify the part or device it covers. Assign an owner to every open item so purchasing knows which configuration can be carried into the order.
A reusable record for module-to-device approval preparation.
Scroll horizontally to read all columns.
| Record group | Information to retain |
|---|---|
| Device and market | Device model, hardware revision, intended use, US deployment and target operator |
| Module identity | Manufacturer, complete variant/ordering code, hardware and firmware identity |
| Regulatory references | FCC ID and grant reference, grant conditions and integration-manual revision |
| Antenna and host design | Antenna/cable drawings, other radios, simultaneous modes and installation details |
| Industry-program evidence | Module certification reference, PICS/report contact and device classification |
| Lab plan | Agreed scope, sample configuration, report references and open test actions |
| Operator review | Expected program record, device/software identity and operator response |
| Release and changes | Approved document/configuration revisions, review owner and outstanding actions |
Before a component substitution or software update, give the proposed change to the people who reviewed that record. T-Mobile's process page calls for hardware and firmware/application updates to be communicated and approved. Ask the module manufacturer, lab and operator which records or tests the specific change affects, then attach their answers to the revised configuration.
Send the document request with your BOM
A useful enquiry states the intended device, US operator, use case, module candidate, antennas, other radios and firmware needs. Request the matching grant and integration instructions, the industry certification reference and the manufacturer contact who can support the lab. Include quantities and the required sales form so the quoted item can be linked to that technical record.
Use the Quectel module catalog to identify candidate hardware and the Datasheet Center for technical references. Send the part list and document request through the BOM service. Keep the manufacturer, lab and operator responses with the configuration that engineering and purchasing agree to use.
Sources
- FCC KDB 996369, publication entry dated November 15, 2024; linked D04 Module Integration Guide v02 is dated October 13, 2020, sections 1 and 2.
- PTCRB: Get Certified, including its IoT-device program direction.
- IoT Network Certified: Get Certified, process and device-testing explanation.
- How to Get IoT Network Certified, Version 2.3, October 2026, sections 1.2 and 1.3.
- T-Mobile device certification process and OEM prerequisites.
Source review: October 19, 2026.