How to Compare LoRa Mesh Vendor Demos With One Buyer Scorecard
Prepared by the ChatField Editorial Team. Evidence reviewed August 18, 2026.
A polished demonstration can show that a product worked once under conditions selected by the seller. Procurement needs a repeatable scorecard that makes different suppliers answer the same questions and complete the same buyer-controlled workflow.
Short answer
Give every vendor the same route, phones, user roles, message tasks, evidence requests, failure drills and commercial questions. Score architecture clarity, end-to-end completion, route evidence, recovery, documentation, lifecycle support and total scope separately. Do not award a pass for an unexplained green indicator.
Gate 1: Is the architecture clear?
Require the seller to draw every link. For current J25 use, the smartphone is the interface, Bluetooth connects it to the carried terminal, and the configured terminal carries supported traffic through the local LoRa mesh to another equipped terminal and paired phone.
Ask whether the system uses a gateway, public network, subscription, cloud service or internet function. Do not treat LoRa, LoRaWAN and LoRa mesh as interchangeable labels.
The ChatField How It Works page provides an example of buyer-readable architecture.
Gate 2: Does the complete workflow finish?
Test the actual supported PTT, text, image and location tasks required by the buyer. Confirm the correct result on the recipient's paired phone, not only at the radio layer.
Record send time, receive time, acknowledgement, correct recipient and human understanding. A technically delivered PTT transmission can still be operationally unclear.
Gate 3: Is range evidence bounded?
Use the same safe route and checkpoints for every supplier. Record terrain, structures, vegetation, vehicles, device position and direction. Repeat marginal results.
Current J25 evidence includes 5 km in urban-obstructed testing and up to 10 km in ideal open terrain. Those conditions must remain visible. Do not compare one vendor's open-terrain number with another vendor's urban route as if they were equivalent.
For current J25 planning, evaluate no more than two participating relay nodes where the tested layout and configuration permit. Never multiply hop count by a headline distance.
Gate 4: Can users recover from failure?
Run controlled interruptions: Bluetooth disconnected, one terminal powered down, one participating relay removed, wrong group selected and phone restarted. Score how quickly the user recognizes the problem, follows the documented procedure and restores a confirmed message.
Do not create a hazardous condition or interrupt a live operational system for a product demonstration.
Gate 5: Does the evidence identify the product?
Ask for the exact model, hardware revision, firmware, application build, regional configuration, labels, manuals and compliance records. Current public J25 evidence includes FCC ID 2BVP9-J25.
An FCC grant identifies authorized equipment and applicable conditions; it does not certify range, mesh capacity, application quality, emergency suitability or every destination market. The FCC OET Knowledge Database provides equipment-authorization procedures and measurement guidance.
Use the J25 specifications page to start the controlled-document review.
Gate 6: Is lifecycle support defined?
NIST's IoT guidance emphasizes product capabilities, documentation, maintenance, support and end-of-life communication. Ask who provides application and firmware updates, how issues are reported, which versions are supported and what happens when support ends.
Score a vague “lifetime support” promise below a bounded written support scope with owners, channels, response expectations and exclusions.
Gate 7: Is the commercial scope complete?
Compare terminals, phones, accessories, spares, packaging, documents, customization, training, testing, freight, import, warranty, repair and support. State Incoterm, currency, quote validity, payment milestones and acceptance gates.
ChatField's current B2B discussion begins at a minimum order quantity of 100 units. Final commercial terms remain quotation-specific.
Suggested 100-point scorecard
| Category | Points | Minimum evidence |
|---|---|---|
| Architecture clarity | 15 | Complete link and dependency diagram |
| Buyer workflow completion | 20 | Repeated recipient-confirmed tasks |
| Route and range evidence | 20 | Buyer-controlled checkpoints and conditions |
| Failure recovery | 10 | Documented controlled drills |
| Product and compliance identity | 10 | Exact model and controlled records |
| Lifecycle and support | 10 | Written update, support and end-of-life scope |
| Commercial completeness | 15 | Comparable total scope and exclusions |
Set mandatory gates in addition to the score. A product should not win on price if it fails a required workflow, destination-market evidence or safety boundary.
Demo-day checklist
- Same route, phones and users
- Same message tasks and time window
- Exact model and software versions
- Direct and relay results separated
- Failure and recovery drill
- Recipient acknowledgement and understanding
- Documents and FCC identity reviewed
- Support and end-of-life answers
- Complete bill of scope
- Signed exceptions and follow-up items
Contact ChatField procurement support with the buyer scorecard, destination market and representative route to arrange a comparable J25 evaluation.
Sources reviewed
FCC and NIST do not endorse ChatField or J25. Their materials provide authorization and lifecycle context, not approval of this scorecard or a vendor ranking.