Guides
Treat POD as a process, not a detached file.
Proof becomes operationally useful when the delivery event, documents, photos or signature and subsequent work stay connected.
Workflow focus
- 01Intake
- 02Responsibility
- 03Status
- 04Proof
02 / Overview
What FalcGo connects
Plan how delivery proof is captured, reviewed, provided and used in downstream transport work.
The guide deliberately separates general process practice from the capability scope represented in FalcGo.
03 / Capability scope
Capability scope
- 01Where prerequisites apply
Proof of delivery
Documents, photos and a signature can be connected to the shipment in supported delivery states.
Availability depends on shipment state and the proof that exists. - 02Represented in the product
Shipment history
Status, actor, organisation and assignment changes remain traceable in shipment history.
04 / Workflow focus
Workflow focus
- 01Proof of delivery
- 02Shipment history
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.