Ship Husbandry & Agency Software: Vessel Services in One System

A vessel calling at port needs two different kinds of help. It needs someone to clear it with the authorities and handle the paperwork, and it needs someone to keep the ship and its crew supplied while it is alongside. The first is agency work. The second is husbandry. Many teams do both, and the software they use should reflect that reality instead of splitting the work across spreadsheets, inboxes, and chat threads. This is what ship agency software and husbandry agency software are meant to solve, and it is why the two belong in the same system rather than two disconnected tools.

What is ship husbandry and how does it differ from port agency work?

Ship husbandry refers to the services delivered to the vessel itself and to the people aboard. It covers provisions and stores, fresh water supply, crew boat transfers to and from the anchorage, crew changes, and the coordination of bunker deliveries. Husbandry is about keeping the ship running: fed, watered, fueled, and crewed. When shipowners speak of a husbandry agency, they mean the party that takes care of these practical, on-the-ground needs during the call.

Port agency work is a different discipline. The agent represents the vessel to port authorities, customs, immigration, and security. Agency work is the clearance, the documentation, the statutory filings, and the billing of the call. It is the administrative and regulatory side of getting a ship in and out of port. Some ports and some owners keep these roles separate, using a protective agent for the interests of the vessel and a husbandry agent for the practical services. In many markets a single agency handles both.

The distinction matters when choosing software. A tool built only for clearance and documents will treat provisions or a fresh water order as an afterthought, if it handles them at all. A tool built only for supply logistics will not understand a port call as a regulated event with a timeline and statutory obligations. The teams that do both need a single system that treats agency and husbandry as two views of the same call, not as separate businesses that happen to involve the same ship.

What should a ship agency or husbandry agency look for in software?

Generic project tools and accounting packages do not understand a port call. When evaluating vessel agency software or a marine agency system, a few capabilities separate a real fit from a tool that will create more work than it removes:

• One shared record for the call. Agency and husbandry services should attach to the same port call, so the operator, the captain, and the finance team all read from one source instead of re-typing the same details into separate places.
• Native vessel services. Provisions, fresh water, crew boat, crew change, and bunkering coordination are not add-ons. Software for ship agents should model them directly, including line items and quantities, not bury them in a free-text note.
• A path from request to quote to invoice. A service requested during the call should flow into a quotation and then an invoice without anyone copying figures by hand. Every hand copy is a place where two records can start to disagree.
• A way for the captain to reach you directly. Much of the daily friction in husbandry is the back and forth over what was requested. A self-service channel for the master removes the phone tag and puts the request into the system in the captain's own words.
• An audit trail and role-based access. In a regulated industry you need to know who changed what and when, and different team members need different views. This should be enforced at the data level, not just hidden in the interface.

The core problem is not that the work is hard. It is that the work is scattered across email, spreadsheets, and WhatsApp, and every handoff between those surfaces is a chance to lose a detail or re-key a number. UNCTAD's Review of Maritime Transport 2025 names the same pattern across the sector: fragmented systems, manual processes and repetitive reporting (p.126). The point of a marine agency system is to collapse those surfaces into one.

How does PortFlow handle husbandry and vessel services?

PortFlow treats the port call, the physical visit of the vessel, as the anchor. Services for that call attach to the same record. Husbandry services have their own dedicated handling rather than being squeezed into a generic line: bunkering, water supply (fresh water), provisions (stores and victuals itemized line by line with quantity and unit), crew boat transfers, and crew changes. Each one is a first-class service on the call, not a note in a comment field.

Alongside these vessel services, PortFlow carries a catalog of port call service codes covering the agency side of the visit: berthing, pilotage, towage, customs clearance, ISPS security, sanitary inspection, and agency coordination, together with the five husbandry services above. Because agency and husbandry services share the same call, an operator sees the whole visit in one place instead of switching between a clearance tool and a separate supply log.

The captain does not need an account to take part. PortFlow's Captain Portal works through a secure link of the vessel's own, with no login. The master opens the link and can request provisions, fresh water, and a crew boat directly, and report the ETA, and each request lands in the agency's workspace attached to the right call. There is no app to install and no password to manage, which matters when the person submitting the request is on the bridge and short on time. We cover how that self-service flow works in more detail in our guide to the captain portal, and how a request travels from the bridge to the invoice in our guide to streamlining port operations.

How husbandry requests connect to quotation and invoicing.

A husbandry request only creates value once it is priced and billed correctly, and that is where scattered tools tend to break down. In PortFlow, the services on a call feed a multi-service quotation. Provisions, fresh water, crew boat, bunkering coordination, and the agency services sit together on the same quote, so the estimate the client sees reflects the real scope of the visit. For a call billed as a disbursement account, the quotation is grouped into the standard PDA sections that follow BIMCO and FONASBA convention: agency fees, port dues, operational, and third-party pass-through. The same records carry through to the final disbursement account (FDA) once the call is closed.

From there the same figures move into invoicing, which is backed by a ledger, without anyone re-typing amounts from one screen into another. Because the request, the quote, and the invoice all draw on one shared record, what the captain asked for, what the agency quoted, and what the client is billed stay aligned. This is the practical meaning of what we call one single reality: a single record read by the captain, the operator, and the finance team, rather than four copies of the truth drifting apart in four inboxes.

It is also why we draw a line between automation and digitalization. Scanning a document or emailing a PDF is digitalization: the information is now electronic, but it still has to be re-entered somewhere else to be useful. Automation is the request becoming a quote becoming an invoice on the same record with no re-keying in between. A husbandry agency does not need a faster way to shuffle files. It needs the file to stop being shuffled at all.

PortFlow runs on infrastructure from providers that hold SOC 2 Type II attestations, Vercel and Neon. PortFlow itself does not hold a SOC 2 certification, and we would rather say so than let the hosting imply one. The agency-side platform is available in English and Spanish, including PDF exports. If you want to see how the pieces fit for your own workflow, the frequently asked questions answer the practical points, and the PortFlow home page walks through the full port call lifecycle. There is a 14-day free trial, and registration asks for no credit card.