Venturus
2026
[UI/UX] Tideline – Shipment Priority
Context
The context and prototypes were adapted due to disclosure matters (NDA).
Freight operators book more cargo onto a voyage than the vessel can carry. Deciding what actually loads — and in what order — is a judgment call made by one person, but it affects everyone downstream: the crew loading the ship, the shipping manager accountable for the manifest, and the customers whose containers get bumped if the call is wrong.
Problem
Whoever reprioritizes the load order needs to be able to act quickly, but that decision can't just take effect silently. There's also no single fixed approver — several people can hold that role — so a proposed change needs to actively reach whoever's on point, not just sit and hope someone notices. Without that, there's no record of who changed what, no clear point where someone with authority signs off, and no guarantee the right person even sees it in time.
Process
Benchmarked integrated platforms that featured complex change request and approval workflows.
Prototyped and aligned the solution internally with the development team.
Collected feedback and secured approval from stakeholders and end-users.
Solution
A staged-change model: a proposed reorder becomes a pending change rather than applying instantly, and it's explicitly routed for review rather than passively waiting. The Editor picks which Approver to send it to, and that specific person gets notified by email — it's a direct request, not a broadcast. As a backstop, the change is also surfaced the moment anyapprover opens the app, flagged as a pending count on the affected rows, so review doesn't hinge entirely on one email landing.
Rejection isn't a dead end either — it comes back to the Editor to acknowledge before they can try again.
Prototype
The prototype was built with Claude AI.
Editor (logistics coordinator) reviews the container list for a voyage and proposes a new load order via "Reorder Priority"
The Editor Requests Approver Review, choosing which Approver the request goes to — that person is notified by email.
Independently of the email, any Approver who opens the system will see the pending change already flagged — visible as flag counts on the affected rows and in the bulk bar — so it's not missed even if the notification is.
Approver reviews the pending change and either:
Approves
or Rejects it.
5. If rejected, the Editor Acknowledges it before proposing again;
If approved, the priorities reorder is applied to the table.
The voyage/ship selector scopes the table to one vessel at a time, and the table itself carries freight fields.
