Transportation Management Systems (TMS)
A TMS can influence carrier selection, dispatch, shipment changes, and payment. The provider should make critical identity and transaction decisions traceable while giving customers control over their own operational decisions.
These criteria guide evidence review for this role alongside the common Dalilah Standard requirements. Submission does not grant recognition.
Requirements for recognition review
Entity and user identity
Document how the platform identifies customer organizations and authorized users. Support verification of counterparties, authority, and relevant insurance where those checks are offered; disclose what the system has and has not verified.
Permissions and separation of duties
Give customers role-based permissions for carrier setup, tendering, dispatch changes, documents, and payment instructions. Support approval or escalation for sensitive changes and promptly revoke former users.
Integrations and source transparency
Identify the source, timestamp, update schedule, and known limits of external identity, authority, insurance, and safety data. Monitor failed or stale integrations and visibly distinguish missing data from a favorable result.
Transaction controls
Preserve a reviewable history of carrier selection, tender acceptance, substitutions, pickup or delivery changes, document changes, and payment destination changes. Make material warning signs and overrides visible to the responsible customer.
Security and incident response
Protect account and shipment data in storage and transit, control API credentials and partner access, monitor suspicious access, and maintain tested response and customer-notification procedures for material incidents.
Accuracy, disputes, and corrections
Provide a way to report incorrect records or suspected identity misuse. Investigate, correct, and document material errors, including downstream data affected by the correction.
Records and continuity
State retention and export practices for audit trails and customer evidence. Maintain backup and recovery procedures and a plan for service interruptions that affect live shipments.
Governance and claims
Review these controls periodically, track corrective actions, and disclose relevant conflicts. Do not imply that a software status or program recognition replaces the customer’s own carrier selection or safety decision.
Evidence to prepare
Prepare a product and integration map, permissions matrix, sample transaction/change log, source-freshness disclosure, incident and correction procedures, retention/export policy, and a recent control review.
Do not upload sensitive customer, driver, government ID, or shipment records in the initial application. The review team will request evidence through a controlled process.