01
Position and movement
Vehicle and load position, unplanned stops, remaining driving time, read from telematics.
Platform · Signal
Sees the operation.
Signal reads position, dwell, documents and milestones from the systems you already run. It compares them against your contracts and delivery windows, and raises the difference before a client calls.
Signal · Exceptions
5 open · 2 awaiting approval All Detention Demurrage Documents ETA
-
Detention PL 4821/26
Dwell 4h 10m at Kaufland DC Rawa
Free time 2h 00m · 2h 10m chargeable
-
Demurrage MSKU 7741903
Free time ends in 26h at DCT Gdańsk
5 days used of 7 · no pickup booked
-
ETA risk PL 2207/26
92 min late against the 14:00 window
Gniezno · driving time 1h 40m remaining
-
Document Order 118-2244
CMR not filed, 6 days after delivery
Carrier chased twice · no response
-
Unbilled Contract SUUS-14
3 pallet-handling services not on the invoice
Rate card §4.2 · 58 EUR
Updated 2 min ago View all 5 →
Interface shown with illustrative data.
01What it watches
Six streams, one picture per load.
02
Dwell and idle time
Arrival and departure at each facility, measured against the contractual free time on the order.
03
ETA against the window
Projected arrival against the delivery window, with the gap stated in minutes rather than a colour.
04
Container milestones
Gate-in, loaded, discharged and gate-out, collected across carrier portals and terminal systems.
05
Free time and demurrage
Days used against days allowed, per container, with the exposure stated in currency.
06
Document completeness
Which documents an order should carry, which it does, and which are overdue against the contract.
02How detection works
Rules come from your contracts, not from defaults.
Configured per customer
Free time, rates, delivery windows and escalation thresholds are read from your contracts and rate cards. Nothing is assumed.
Raised once, then tracked
A detection is opened once and followed until it closes. The same dwell does not reappear as a new alert every hour.
Evidence attached at detection
Timestamps, the contract clause and the applicable rate are captured when the exception is raised, not reconstructed later.
Detection changes nothing
Signal writes nothing back to your systems and sends nothing to your clients. Only Desk acts, and only after approval.
03What it connects to
It reads from what you already run.
Signal never asks for a system you do not have. It takes whichever path your estate supports, and states what it needs before you commit.
| Path | When it applies | What it needs from you |
|---|---|---|
| API | The TMS, WMS or telematics exposes one | Credentials and scope |
| Scheduled export | Any system that can email or drop a report | A daily report to a dedicated mailbox |
| File exchange | CSV or XML import and export | A folder or SFTP |
| Mail intake | Orders and documents arriving by email | A shared mailbox |
| Government interfaces | Invoices via KSeF, later eFTI | A token for your tax ID |
| Messaging | Drivers and subcontractors | WhatsApp Business, SMS |
| Interface automation | Systems with no API, as a last resort | Your own environment and credentials, authorised in writing |
04How it is measured
Four numbers, reported monthly.
- Dwell hours
- Detected, and the share that turned into a charge.
- Exceptions raised before client contact
- Against the total raised.
- ETA accuracy
- Projected against actual arrival, in minutes.
- False positives
- Detections withdrawn after operator review.
Next
Detection changes nothing on its own.
Desk is the line that acts, and it acts after approval.
05Start a conversation
Talk to our team
about your operation.
A demo built around your vocabulary and your exceptions. Or an operational audit of what is unbilled or uncollected, using your data.
An operational conversation
Your systems. Your constraints.
A clear starting point.