Custom voyage report app for inland shipping
Appfront builds voyage report apps for inland shipping: the skipper records what happens on each voyage on board, from departure and loading to waiting, lock passages, bunkering and unloading, with time, position and supporting documents, and the report is ready ashore for the charterer, the shipper and invoicing. So waiting hours and demurrage days are no longer reconstructed from the logbook.
What is a voyage report app for inland shipping?
A voyage report is the account of a voyage: when the vessel departed, where it loaded and how much, how long it waited and why, which locks it passed, where it bunkered, when it unloaded and with which documents. This data determines the settlement with the shipper, the waiting hours that are invoiced and the demurrage days the charterer has to substantiate. The app records it on board, at the moment it happens, with the time and position of the device, and turns it into a report at the end.
Without an app, the skipper writes in the logbook, phones the charterer when there is a delay and hands in the report after the voyage. Waiting hours then become a dispute: the shipper says the vessel arrived too early, the skipper says the quay was occupied, and nobody has a timestamp with a position. For a shipping company with dozens of voyages a week, that means administration that lags behind and settlements that slip.
We build custom because the report has to fit your contracts and your chartering: what counts as waiting time, from which moment, which documents the shipper wants to see, and how the voyage appears in your chartering system. A generic logbook app knows the vessel, but not the agreements with the shipper and not the settlement that has to follow from them.
Recording on board
One tap per event: departure, arrival at the loading place, start and end of loading, waiting with a reason, lock passage, bunkering, unloading. With the device's time and position, even without coverage.
Documents and quantities
Loading and unloading documents photographed or received, quantities entered or read out, and the quay's signature where customary.
Report ashore
At the end of the voyage, the report per voyage, with the timeline, the waiting hours and demurrage days according to the contract, and the documents, goes to the charterer and invoicing.
How we build your voyage report app for inland shipping
We start with the settlement of your most recent voyages: which waiting hours were disputed, which documents were missing and how the skipper currently reports.
Which events per voyage count, what the contract says about waiting time and demurrage days, which documents the shipper wants and how the voyage appears in chartering. We look at the disputed settlements.
Today's voyage on the phone or tablet, events with one tap, time and position automatic, photos and documents attached. Works without coverage.
Per voyage the timeline, the waiting hours and demurrage days according to the contract rules, the quantities and documents, as a report for the charterer and shipper.
The voyage goes out and the report comes back to the chartering system, the export to invoicing, and then maintenance and new contract types.
What a voyage report app for inland shipping actually does
The components below appear at almost every shipping company. Which ones you need depends on your contracts and your chartering system.
Voyage timeline
Every event of the voyage in order, with time and position: departure, waiting, loading, passages, bunkering, unloading, arrival.
Waiting time with reason
Waiting starts and ends with a tap and a reason from a list: quay occupied, lock, weather, documents. The reason determines whether it counts.
Loading and unloading registration
Quantities, documents photographed or received, and the quay's signature. The basis for the settlement with the shipper.
Bunkering and consumption
Bunkerings with quantity and receipt, and consumption per voyage if the engine provides it, for the cost price per voyage.
Voyage report
A report per voyage with timeline, waiting hours and demurrage days according to the contract, quantities and documents, as a PDF and as data.
Chartering and invoicing integration
The voyage from the chartering system, the report back, and the invoice lines for waiting hours and demurrage days to invoicing.
Who we build an inland shipping voyage report app for
The app is for anyone who has to account, per voyage, for what happened on board and what the settlement depends on.
Shipping companies with their own skippers
Dozens of voyages a week with an office team ashore. The voyage timeline and the report to chartering are the core.
Independent skippers on regular routes
One vessel, regular clients, waiting hours that get disputed. The waiting time with time and position matters most.
Charterers
Voyages across multiple vessels with settlement to the shipper. What you need is the report per voyage in a single format.
Tanker and dry bulk shipping
Loading and unloading documents that the shipper and the terminal require. Document registration and the quayside signature are the core.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
This page is about recording the voyage on board. For planning the voyage in advance, see our page on voyage and lock planning, and for road transport with the same questions our page on trip registration software. You can read about our approach at building software.
If you also want locks, bridges and the expected arrival time on board, read more about our on-board voyage planning app.
For the office, with the reports of all vessels, demurrage and invoicing, there is our inland shipping voyage report software.
Why Appfront for your inland shipping voyage report app?
A voyage report is evidence in a settlement. It has to be created on board, with time and position, and it has to know the rules of the contract. That is what we build on.
Time and position from the device
Not from the skipper's memory after the voyage, but at the moment itself. That is what a shipper accepts in a discussion about waiting hours.
The contract does the counting
What counts as waiting time and from when is set per contract in the app. The report calculates according to those rules, and the charterer no longer has to do the sums.
One tap per event
A skipper has no time for forms. Departure, waiting, loading: one tap, and the rest comes from the device.
Security and privacy in an inland shipping voyage report app
The app processes vessel positions, cargo data and customer data from shippers, and sometimes signatures from quayside staff. Access is set up per role: the skipper sees their own voyages, the charterer their voyages, the shipper only the report for their cargo. Data is kept for as long as the settlement and the retention obligation require.
The app runs in a European data centre, with encrypted storage and daily backups. Integrations with chartering systems and invoicing work with their own keys, which can be revoked per integration.
Frequently asked questions about an inland shipping voyage report app
Questions that shipping companies and skippers ask before they get started.
On board, the skipper records every event of the voyage with one tap: departure, waiting with a reason, loading and unloading with documents, lock passages, bunkering and arrival, with the time and position of the device. At the end, the app produces the voyage report with waiting hours and demurrage days according to the contract, for the charterer, the shipper and invoicing.
Yes. Events are stored with the time and position of that moment and sent as soon as there is a connection. On the river, in a lock or at a remote quay, the skipper simply carries on registering; the office sees it as soon as the vessel has coverage again.
According to the rules of the contract with the shipper: from which moment waiting time counts, which reasons count and which do not, and how demurrage days are rounded. Those rules are stored per contract in the app, and the report calculates with them. The skipper only records; the calculation is done ashore.
Yes. Loading and unloading documents are photographed or received digitally, quantities are entered or read automatically, and where the quay signs, the signature appears in the report. Photos of damage or an occupied quay are attached to the event, with time and position.
Yes. The voyage comes from your chartering system to the skipper's phone, and the report goes back to the voyage, with the invoice lines for waiting hours and demurrage days going to invoicing. We connect to the package you use; the app does not become a second chartering system.
No. The voyage report covers the commercial accountability of the voyage to the charterer and shipper. The statutory log and the sailing-time registration have their own rules and their own tools; the app can supply data, but does not replace them.
Check that first. Some logbook apps record events, and for a skipper without settlement disputes that is enough. Custom development makes sense when waiting hours have to be calculated according to contract rules, when the report has to land in the chartering system, or when shippers demand their own formats and documents.
Every voyage accounted for on board, settled without dispute?
Tell us how many vessels you operate, which chartering system you use and how many waiting hours were disputed over the past months. We will show you what the skipper app, the calculation and the report look like.