MacroPoint tracking needs a driver notice-and-consent record

Separate the freight purpose from the person impact

The direct operating answer is to define why freight is being tracked before enrolling a driver, device, phone number, vehicle, or carrier connection. Record the customer entity, shipment or load population, freight owner or manager, named MacroPoint product, contracted purpose, permitted use, operating region, carrier relationship, data sources, expected tracking window, accountable business owner, privacy owner, and legal-review basis. The product schedule supports a narrow distinction: Visibility concerns real-time tracking of freight, while Capacity concerns sourcing carrier capacity. Neither label by itself establishes every downstream use of information about a person.

Create a separate person-impact assessment for each activation path. Identify whether the connection can expose a driver's phone number, vehicle identifier, inferred location, message history, device information, or another personal attribute; who receives it; why each recipient needs it; where it is stored; how long it remains available; and whether it will be reused for safety, performance, payroll, discipline, marketing, insurance, or another purpose. A shipment may remain operationally visible while a proposed secondary use of person-linked data is unresolved. Do not convert access to a freight signal into permission for an unrelated people decision.

Make notice and consent reproducible

Descartes' schedule says the location of individuals transporting freight may be inferred from tracking data and places responsibility on the customer to notify drivers and obtain consents that applicable law may require. Turn that responsibility into an evidence record rather than a checkbox. Retain the driver identifier used by the customer, carrier or employer, relevant role, jurisdiction, language, notice version, delivery channel, delivery time, acknowledgement where used, consent question, response, legal or policy basis, scope, effective period, collector, source system, and any later correction. Preserve unknown, not delivered, declined, withdrawn, expired, superseded, and not required as distinct reviewed states.

Consent should not be claimed where another basis or a contractual notice is actually being used, and the existence of a notice should not be reported as agreement. The governing team should determine which requirements apply to its facts and jurisdictions. If consent is relied on, record whether it was specific to location inference, text messages, device access, a named load, a recurring relationship, or another bounded activity. Provide a route to ask questions, correct identity, challenge an enrollment, and withdraw where applicable. Keep the exact notice and decision that governed the tracking period even after templates or policies change.

Gate activation by product, module, and user scope

The product schedule also says use is tied to the agreement, permitted users, permitted use, and individually named products, and that a module is not authorized unless it is specifically listed in the order form or a later ordering document. Build the activation gate from those records. Confirm the contracting entity, effective agreement and schedule version, order form, named product and module, permitted user group, freight population, customer ownership or management relationship, connection method, service term, configuration owner, and any geographic or carrier limits. A family name, available menu, valid credential, or successful integration call is not evidence that a module or use has been ordered and approved.

Join that entitlement record to the driver notice-and-consent record without collapsing them. Contract scope can support access to a service but does not decide whether a particular person received the right notice or whether a jurisdiction-specific consent is necessary and valid. Conversely, a driver's response to a notice cannot expand the customer's purchased product, permitted use, or internal authority. Activation should require both applicable tracks to resolve, with a named reviewer for exceptions and a preserved reason when tracking proceeds without a consent because the accountable team documented a different basis.

Test one enrollment through withdrawal and closeout

A useful demonstration follows one representative driver and load from carrier assignment through tracking closeout. Test a subcontracted carrier, a shared phone, an incorrect driver match, a reassigned load, a cross-border route, a delayed notice, a declined or withdrawn consent where applicable, an applicable opt-out from text messages, an expired tracking window, and a removed permitted user. Inspect whether the system prevents premature activation, records the applicable evidence, stops the affected channel, preserves a lawful operational exception without relabeling it as consent, restricts secondary access, and retains the historical decision without continuing unnecessary collection.

Reconcile the result across the order form, customer policy, carrier and driver records, messaging workflow, connected application, access log, retention process, and deletion or restriction outcome. Supply Chain Signal reviewed Descartes' registered MacroPoint schedule on September 12, 2026 but did not inspect an executed customer agreement, determine any legal requirement, enroll a driver, receive a text message, operate a customer environment, or test a carrier connection. Descartes' official sitemap records the exact URL at January 27, 2026, 19:18:56Z, before the cutoff. The later HTTP Last-Modified value is transport metadata rather than attributable evidence of a material semantic change; version PMPDSG26.0 is current on the page, whose publication and semantic revision times remain unknown.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Supply Chain Signal will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.