How Vigilo learns a workflow: from repeated decisions to a validated rule
See how Vigilo connects decisions to their context, identifies recurring patterns and proposes business rules for the team to validate before activation.
Read the resourceResources
Understand what can be automated, and under what conditions.
Governed learning, adaptation to existing tools, order intake, invoicing and documents: each resource explains one Vigilo mechanism through a transport example, its controls and its limits.
Transport files & operations
From an incoming request to an actionable transport file, including the rules and exceptions that shape day-to-day operations.
The transport record in Vigilo: what is connected and what stays in your systems
Understand how Vigilo connects transport events, decisions and evidence without replacing the TMS, inboxes, portals or business master data.
Read the resourceHow do you automate transport order entry in a TMS?
A checklist and practical method for turning an emailed request into a verified transport order without inventing missing data.
Read the resourceMultichannel transport orders: connect emails, portals, EDI and calls
How to process a transport order when information arrives by email, portal, EDI, document or phone without losing the thread of the record.
Read the resourceWhat makes an operational handoff useful?
A useful handoff does more than report that an AI operator has stopped: it gives operations the case, sources, stop reason and next decision to make.
Read the resourceWhich event belongs to which transport record? Multichannel matching rules
References, chronology, sources and controls: a method for linking each email, status update or document to the correct transport record without hiding uncertainty.
Read the resourceHow much does rekeying transport orders into a TMS cost?
Measure the real cost of rekeying transport orders into your TMS with a time-study grid and a reproducible calculation.
Read the resourceTransport order template: a checklist for gathering information before entry
A practical transport order template that separates received data, known rules and details that still need clarification before TMS entry.
Read the resourceTransport operations inbox: organise requests so no order is left unanswered
A practical method for assigning, tracking and closing orders, documents, changes and follow-ups received in a shared transport operations inbox.
Read the resourceShipper portals: reduce duplicate order entry into the TMS
A practical method for moving orders, statuses and documents from shipper portals into a TMS without creating duplicates or losing the control trail.
Read the resourceAI operators & technology
Understand the technical building blocks, their limits and how to combine them in a real operational workflow.
Why the AI operator must adapt to the workflow, not the other way round
Tools, rules, screens and controls vary from one company to another. Adapting to them must be managed as a product capability, not an endless bespoke project.
Read the resourceThe lifecycle of a business rule: proposed, validated, active, suspended
How an observed practice becomes a governed rule: documented proposal, human validation, limited activation, monitoring, a new version or suspension.
Read the resourceAI agent, RPA, OCR or API: choosing the right building block for a transport workflow
A practical comparison of AI agents, RPA, OCR and APIs for automating a transport workflow without setting complementary technologies against one another.
Read the resourceAutomating a TMS without an API: user-interface interaction, controls and limits
How an AI operator can interact with a TMS without an API, within a validated scope, with verification, logging and recovery.
Read the resourceDeploying an AI operator progressively: observe before authorising action
A progressive deployment protocol for measuring an AI operator in transport before extending its access rights and scope.
Read the resourceNew order, change, or cancellation: how Vigilo identifies intent
How Vigilo distinguishes a new order from a change or cancellation by connecting each incoming event to the transport record it affects.
Read the resourceAfter the click: how Vigilo verifies that an action actually succeeded
A click or API request does not prove success. Learn how Vigilo compares the expected outcome with the state actually recorded in the TMS.
Read the resourceWhen the workflow changes: screen, document, rule or responsibility
A modified TMS screen, a new document, a revised rule or transferred responsibility: how to evolve an AI operator through controlled, versioned change.
Read the resourceHow to measure an AI operator pilot without confusing speed with reliability
A method for evaluating an AI operator pilot through decision quality, action outcomes, controls and escalations — without inventing performance claims.
Read the resourceCopilot, rules engine or AI operator: who actually owns the workflow?
A balanced comparison applied to the same transport file, showing which component advises, decides, acts and verifies.
Read the resourceWhat data and permissions does a first Vigilo workflow need?
A practical method for defining the sources, permissions, evidence, stops and responsibilities of a first Vigilo workflow.
Read the resourceAI in road transport: which administrative use cases should you assess first?
A practical map for comparing four road transport AI use cases through their data, controls and the decisions that must remain human.
Read the resourceTransport automation audit: which tasks should come first?
A field-based method for observing work, comparing volume, stability, risk and source quality, and framing a realistic first scope.
Read the resourceTransport automation ROI: build a model without overstating the benefits
A documented method for calculating transport automation ROI while separating released capacity, avoided costs, realised revenue and full project costs.
Read the resourceControl & continuity
Preserve the full history of a transport file to reconcile what was planned, performed and invoiced.
Transport record continuity: from order to invoicing
Why requests, amendments, actions, evidence and invoicing should be connected in one operational, auditable history that transport teams can use.
Read the resourceTransport invoice control: reconcile planned, performed and invoiced
A method for checking a transport invoice by connecting what was planned, what was performed and what was invoiced.
Read the resourceFrom invoice discrepancy to decision record
How to turn a transport invoice difference into an explainable, documented record that is ready for a human decision.
Read the resourceTransport pre-invoicing: how should carriers check customer statements?
A carrier-side method for reconciling a customer pre-invoice with completed shipments, agreed rates and evidence before approval or challenge.
Read the resourceTransport self-billing: which checks should the carrier retain?
A France-specific guide to separating self-bills, pre-invoices and supplier invoices, then checking operations, rates, extras, tax and corrections.
Read the resourceCompleted transport jobs not invoiced: how to find overlooked records
A method for reconciling completed transport jobs with invoice lines, classifying missing matches and organizing records that need completion or invoicing.
Read the resourceDock waiting charges: what evidence is needed to review invoicing?
A practical method for documenting dock detention, finding the applicable contractual rule and reviewing a potential charge without assuming it is payable.
Read the resourceMissing delivery note or CMR: organize evidence for transport invoicing
A practical method to identify, link, request and verify delivery notes, CMR consignment notes and other evidence before an invoicing decision.
Read the resourceDocuments & WMS
Turn delivery documents into verified information that logistics systems can use.
Next step
Still have a question?
Describe the workflow and the decision to be made. We will tell you what can be scoped, what needs validation and what remains out of scope.
Discuss your workflow