Guides
Transport visibility starts with a clear data question.
Visibility has different meanings: a sound approach names the source, recency, audience and intended operational purpose of the data.
- 01Intake
- 02Responsibility
- 03Status
- 04Proof
02 / Overview
What FalcGo connects
Distinguish status, milestones, events and location data and identify the prerequisites for each visibility level.
The guide deliberately separates general process practice from the capability scope represented in FalcGo.
03 / Capability scope
Capability scope
- 01Represented in the product
Public tracking
Purpose-specific tracking access shows current status, milestones and available events.
Do not promise predictions, refresh frequency or universal telematics availability. - 02Represented in the product
Shipment history
Status, actor, organisation and assignment changes remain traceable in shipment history.
- 03Where prerequisites apply
Location context
Available location data can appear in internal and public views.
The data source, frequency and universal availability are not verified.
04 / Workflow focus
Workflow focus
- 01Public tracking
- 02Shipment history
- 03Location context
06 / FalcGo
Show us your handoffs.
We will show you how customer intake, dispatch, drivers or partners, exceptions, proof and invoicing come together in FalcGo.