Bring work in
Create the transport internally or invite a customer into a purpose-specific self-booking flow.
The Logistics Operating System
Bring transport planning, dispatch, live tracking, and exception management into one platform. Connected workflows and traceable status data help teams coordinate operations.
- Order
- From intake
- Status
- During execution
- Invoice
- After proof
From order to invoice
One operation. One shared workflow.
Keep scrolling to see how FalcGo connects intake, dispatch, execution, and close-out in a single transport context.
- Dispatch
- Live status
- Exceptions
- POD & invoice
01Order or self-booking
02Own driver or partner
03Status, exception and history
04POD and invoice
FROM ORDER TO INVOICE
One operation that becomes more complete with every step.
These are real views from the Owner and dispatch workspace: an order becomes dispatched shipments, traceable execution and finally a deliberately created individual or collective invoice. Every step adds to the same transport context.
Actual Owner & dispatch workspace01 / 04
The order directory connects references, lanes, status and shipment counts. Search and status filters narrow the list; an order can then be edited or opened with all of its shipments.
- Search & status filters
- Order status
- Related shipments
01 // HANDOFFS
The work is distributed. The context should not be.
Customers provide transport data. Operations structure and assign the work. Drivers report progress. Partners take over shipments. Proof comes back. When every handoff lives in a separate channel, the shared operational history disappears.
One shipment. Multiple roles. One shared history.Illustrative example
FG-2408-017 / 01Customer intakeSTATUS // SYNCHRONISIERT
FG-2408-017 / 02DispatchSTATUS // SYNCHRONISIERT
FG-2408-017 / 03Partner handoffSTATUS // SYNCHRONISIERT
FG-2408-017 / 04Execution statusSTATUS // ABWEICHUNG
FG-2408-017 / 05PODSTATUS // SYNCHRONISIERT
FG-2408-017 / 06InvoiceSTATUS // SYNCHRONISIERT
02 // ONE OPERATION
From self-booking to invoice, without losing the operational thread.
Each step adds context, responsibility and proof to the same operation.
Request received
Structure it
Capture addresses, time windows, contacts, references, packages and weights.
Assign it
Choose your own driver, hand it to an accepted partner or leave assignment open.
Execute it
Keep statuses, actual events and assignments in one operational history.
Resolve change
Record delays or problems with a reason, action and follow-up state.
Prove delivery
Capture POD documents, photos and signatures where the workflow enables them.
Close and invoice
Create individual or collective invoices from eligible shipments and maintain payment status.
03 // ACTUAL PRODUCT VIEWS
See the connected workflow inside FalcGo.
Every view comes from the current platform and uses controlled demo data—not recreated UI mockups or customer evidence.
Actual product view · synthetic demo data- Search & status filters
- Order status
- Related shipments
04 // ROLES
One operation. Different responsibilities. Relevant access.
Not every role needs the same interface. They do need the right shipment context.
ROLE VIEW // Owners & dispatch
Owners & dispatch
Keep orders, teams, partners, exceptions and invoicing in operational context.
- Review the order
- Choose driver or partner
- Oversee status and close-out
ROLE VIEW // Operations
Operations
Create and manage transport work, coordinate execution and resolve change.
- Structure the shipment
- Coordinate assignment
- Resolve an exception
ROLE VIEW // Drivers
Drivers
Work on assigned shipments and report progress through the intended status flow.
- Accept assigned work
- Update status
- Capture proof
ROLE VIEW // Partner companies
Partner companies
Review forwarded work, accept or reject it and assign their own drivers.
- Accept or reject
- Assign own driver
- Report execution
ROLE VIEW // Customer & public access
Customer & public access
Submit requested data or open purpose-specific tracking, POD and invoice links.
- Complete self-booking
- Follow status
- Open a document
Partners take over the shipment, not the context.
Dispatch selects an already accepted partner company and forwards the shipment with its lane, time windows and optional agreed price and note. The partner makes its own decision, assigns an own driver after acceptance and updates execution. Status, assignment and history remain visible on the same operation.
Only accepted partners are selectable. Every handoff and acceptance is deliberate.A closed partner network — not an open spot market or automated matching.
This step explains
Dispatch selects the partner and can add an optional price and note.
Waiting for acceptanceComplete partner workflow
- The same shipmentAccepted partner relationshipPartnership accepted
Both companies confirm the relationship before any shipment can be forwarded.
- Your dispatch teamForward deliberatelyWaiting for acceptance
Dispatch selects the partner and can add an optional price and note.
- Partner company 02Review and decidePartner accepted
The partner reviews the context and deliberately accepts or rejects the shipment.
- Partner company 02Assign an own driverDriver assigned
Only after acceptance does the partner assign one of its own active drivers.
- Partner company 02Update executionIn delivery
Pickup and further allowed status updates are added to the operation.
- The same shipmentKeep the record connectedDelivered · history retained
Status, assignment and proof stay connected to the same shipment.
05 // DRIVER APP
The same operation, in the driver's hand.
The FalcGo driver app on iPhone and iPad walks through the shift, pickup, delivery and proof. Every confirmation writes into the same shipment history that dispatch and the customer see later.
Actual app views · synthetic demo data- SHIFTAssigned shipments in one place.Active shipments and archive, filterable by pickup, picked up and delivery — with addresses and the current state per shipment.
- ROUTE CONTEXTMap, addresses and packages in view.Pickup and delivery address, reference number, package count and total weight sit on the shipment the driver has open.
- PROOFPhoto, signature and note on site.Delivery confirmation collects proof photos, the recipient signature and an optional note before the state changes.
On the way, and at the drop.
Two more views of the same app on iPhone — the part of the day the driver holds in one hand.
ROUTE CONTEXTMap and shipment on one screen.The route sits above the open shipment: reference number, pickup and current state stay visible while the driver is on the way to the address. 
PROOFProof captured at the drop.Proof photos from camera or gallery, the recipient signature and a note — collected in one sheet over the map before the state changes.
From sign-in to proof.
Five views of the driver app on iPad — in the order a driver moves through them across a working day.
SIGN INSign in as a driverThe driver signs in with their own account. Assignment and history hang off that identity. 
SHIFTOpen the shipments for the shiftThe list shows active shipments with from and to addresses and whether a pickup or a delivery is due. 
PICKUPConfirm the pickupMap and address lead to the pickup point. Confirmation is a swipe; rejection, delay and failure are separate actions. 
DELIVERYRun the deliveryThe open shipment keeps pickup and delivery address, reference number, packages and total weight next to the exception actions. 
PROOFCapture the proofProof photos from camera or gallery, a drawn signature and an optional note close out the delivery.
Scroll or swipe horizontally to see all five views.
06 // EXCEPTIONS
When the plan changes, the next step stays visible.
Delays and problems become part of shipment history with a reason, action and follow-up state. Position data appears only when it is available for that shipment.
Illustrative example // EVENT HISTORY // FG-2408-017
01
In delivery14:20 · Partner company 02
02
Delay reported14:34 · Reason recorded
03
Action assigned14:41 · Recipient informed
04
Resolved · history retained15:08 · Follow-up state set
07 // FOCUSED ACCESS
Customers get exactly the access the next step requires.
Request structured transport data.
Invite a customer to submit shipment drafts with addresses, time windows, packages and required acceptance. You review, approve or return a correction reason.
See the self-booking flowShare status and documents without a platform account.
Purpose-specific links open public status views and released POD or invoice documents. Content and availability depend on the operation.
Open tracking08 // PROOF TO PAYMENT
Delivery becomes proof. Proof becomes invoicing context.
POD photos, documents and signatures stay connected to the shipment. Eligible shipments can then feed individual or collective invoices with editable line items, document preview, sending and payment status.
See the workflowIllustrative example
01DeliveryFG-2408-017
02POD photoFG-2408-017
03SignatureFG-2408-017
04DocumentFG-2408-017
05Invoice previewFG-2408-017
06Payment status · openFG-2408-017
09 // PROCESS CHECK
Where handoffs create work today.
This calculator shows an estimate based only on your inputs. It is not a customer result or a guaranteed FalcGo saving.
Estimated current coordination workload0hours / month
Show formula
(Shipments per month × (Handoffs per shipment + Manual status requests per shipment) × Minutes per request or handoff) ÷ 6010 // GO DEEPER
The most important workflows in detail.
11 // CLARITY
Common questions, clear boundaries.
01What is FalcGo?
FalcGo is a role-aware transport-execution workspace. It connects order and shipment, internal or partner execution, exceptions, POD and invoicing in one operational history.
02Who is FalcGo for?
Freight forwarders and transport operators working with their own operations teams, drivers and/or accepted partner companies.
03How does partner handoff work?
A shipment is deliberately forwarded to an accepted partner company. The partner can accept or reject it, assign its own driver and update status through the intended flow.
04Can customers provide transport data?
Yes, through a purpose-specific self-booking invitation. Submitted information is reviewed before operational acceptance and can be returned for correction.
05Do customers need a platform account?
Tracking and released POD/invoice documents use purpose-specific links. A self-booking invitation may require registration.
06What happens during an exception?
A delay or problem is recorded with its reason, action and follow-up state. The original event remains visible in shipment history.
07Does FalcGo automatically optimise routes?
No. The current product provides map and route context, not universal automated tour or HGV route optimisation.
08Does FalcGo replace full accounting software?
No. FalcGo connects transport data to individual and collective invoices, documents and payment status; it is not positioned as complete financial accounting.
12 // CONTACT
Show us your handoffs. We’ll show you how they come together in FalcGo.
Briefly describe how transport work moves through your operation today. We confirm receipt without inventing a response time or outcome promise.