Pre-deployment IoT checklist

This is the list to sign off before ordering the first mass batch of SIMs and devices. Every item is a failure mode we've watched stall deployments mid-campaign. Print it, walk through it with your hardware, software, and operations leads, and file it with the project contract. Anything missing when the batch arrives costs between 5x and 20x more to fix in the field than to fix beforehand.

1. 1

   Validate per-country and per-postal-code coverage

   Knowing a country has coverage isn't enough: you need to validate operator, bands, and technology at the exact locations where deployment will happen. Get trial SIMs from your provider and measure in the field with the real device.

   Tip: If the customer deploys in an underground warehouse or parking, validate there, not on the street.

2. 2

   Confirm bands supported by the module

   Each module (Quectel, u-blox, Telit, Sequans, Sierra…) supports a subset of bands. Cross-check that the bands used by your operator in each country are on the module's datasheet. Critical for 5G NR (n78, n28) and LPWA.

3. 3

   Verify module firmware and stack

   Some modules need specific firmware for permanent roaming, NB-IoT in unusual bands, or features like SMS over IP. Ask the manufacturer for the recommended version for your case and verify your batch carries it.

4. 4

   Configure the correct APN on the device

   APN depends on operator and plan (public vs private). Document the exact APN and, if private, the auth params (user/password). For mixed fleets, APN can be injected via the SIM toolkit.

5. 5

   Implement watchdog and scheduled reset

   Any unattended IoT device needs a hardware watchdog (not software) that reboots after N minutes without heartbeat. Additionally, schedule daily or weekly resets to free memory, reload APN, and force a network re-attach.

   Tip: Software watchdogs alone don't work — if the firmware hangs, the watchdog hangs with it.

6. 6

   Define consumption thresholds and alerts

   Every SIM needs portal-side consumption alarms: notify at X% of monthly plan, block at Y%. Without this, a SIM with a software bug can rack up thousands of euros of roaming before you notice.

7. 7

   Document operator and iot.cards SLAs

   What uptime is guaranteed? What's the penalty if breached? How fast is service restored? Is there 24/7 incident escalation? For critical use cases (alarms, healthcare), demand an SLA with financial commitment.

8. 8

   Test the data plan in a real pilot

   Deploy 10-50 units for 30 days, measure actual consumption (portal CDRs), and project to the fleet. Initial estimates are always +/- 50% — the pilot is the only source of truth. Adjust the plan BEFORE ordering the mass batch.

9. 9

   Define the bulk activation process

   Activating 10,000 SIMs by hand isn't an option. Define the process: REST API script? CSV import in the portal? On-demand activation at first attach? Document it, test with 100 SIMs, and time it.

10. 10

    Set up observability and dashboards

    Minimum dashboard: active SIMs, SIMs silent in last 24 h, aggregated consumption by country, top-10 SIMs by consumption, active alerts. If your provider doesn't offer this, request API access and build it in Grafana or Looker.

11. 11

    Document the rollback plan

    If in month 3 you discover operator A doesn't work in some region, how do you migrate to operator B without touching 10,000 devices in the field? The answer is eUICC with OTA profile. If you don't use eUICC, document the manual SIM-swap logistics plan.

12. 12

    Sign the contract with exit clauses

    No mandatory term, guaranteed data migration, clear ownership of CDRs and the installed base. A sticky contract is the last thing you want when something goes wrong in month 6.