The starting point: who needs delivery information?
The same delivery creates different tasks in a transport company. A dispatcher plans the job, a driver completes the route, and a manager needs an overview of the team's work. When each person relies on a separate message or spreadsheet, identifying the current information becomes difficult.
FreightETA is a CodaLumo project for transport and logistics. This article examines scope and interface decisions that are also useful when commissioning software for another industry. The feature description reflects the publicly presented product as checked on 26 October 2026.
Product scope: arrival estimates, transport orders and user roles
FreightETA combines an estimated-arrival calculator with transport orders. Administrators and dispatchers use the web dashboard and mobile app, while drivers work in the mobile app. The roles reflect different responsibilities for the same delivery.
This illustrates how to define a product through a workflow. Before counting screens, describe who creates information, who updates it and who uses it to make a decision.
Why do the web dashboard and mobile app have different jobs?
Office work benefits from comfortable data entry and an overview of several jobs. On the road, the user needs a clear phone screen and information about the task at hand. The same layout is not necessarily the best choice for both situations.
When planning a similar system, identify the primary action on each device. A dashboard might support comparing jobs, while a mobile view guides one action at a time. This helps determine whether a responsive web app is sufficient or whether a dedicated mobile app is also useful.
Define a user journey before listing features
An illustrative journey to discuss with a supplier could be: an employee creates a job, assigns responsibility, and the team sees its current status. Each step needs inputs, permissions and an expected outcome. This is a more useful basis for a quote than the broad instruction “build a transport system”.
In another industry, the equivalent might be a booking, a service request or a B2B order. The principle is similar: the first version should let users complete one important task from beginning to end.
- who starts the process and which information they provide
- who can read or change a record
- how a user recognises a status change
- what happens when an error occurs or required data is missing
How to choose a realistic first-version scope
Ideas often grow faster than the budget. For a new project, separate the features required to complete the main task from those that merely make it more convenient. Advanced reports or further integrations can become a separate phase if the core workflow works without them.
FreightETA demonstrates a possible direction for a dedicated product, but its current scope is not a universal MVP package. Companies differ in their data, dependencies and requirements. The quote for a similar application should follow an agreed scope rather than the industry label alone.
What should be checked before launching a similar system?
Application acceptance should cover complete user tasks rather than the appearance of individual screens alone. Prepare sample data and walk through creating, changing and completing a job together. Separately check that each user can access only the information intended for their role.
Features that depend on external data also need clear behaviour when a service is unavailable, information is outdated or a connection drops. The project scope should explain how users are informed and who handles these situations after launch.
- completion of the main task on desktop and mobile
- data visibility for each role
- clear confirmations and error messages
- maintenance, backup and further-development arrangements
The result and lessons for commissioning your own app
The project resulted in a working product available at freighteta.pl. For a business commissioning software, the key lesson is consistency: people, data and interfaces should support the same business workflow.
Measure the impact of a comparable implementation after launch using indicators such as time spent handling a job, data corrections or tasks completed without an extra call. Record a baseline before implementation and compare equivalent types of work.
If you are planning your own system, describe one task, its users and the tools currently used. That provides a starting point for discussing the first version, necessary integrations and the order of future development.