TL;DR (Short answer): Crew management software is a tool. Managed crewing is an outcome. The software runs payroll, plans rotations, tracks certificates, and logs MLC 2006 hours of rest, and it does all of that well. What it does not do is find the seafarer, judge whether they are actually competent for your tanker, or stand in front of the flag state when something goes wrong. A managed crewing service owns that accountability end to end. Most serious owners end up with both: a manager who runs the crewing and a platform underneath for visibility. If you buy the licence expecting a manned, compliant ship, you have bought the wrong thing.
Search “crew management software” and the results are a wall of SaaS vendors and “top 10” listicles. That is fine if you already have a crewing department and want to run it better. It is misleading if you are an owner trying to get out of the crewing business, because software does not crew a ship. It gives your crewing team a better desk. This guide separates the tool from the outcome and explains why a tanker owner still needs a managed service on top of it. It is written for shipowners, operators, and DPAs who keep hitting the same confusion: am I buying a system, or am I buying a result?
What crew management software actually does
Crew management software is a database and workflow engine for a crewing operation. It holds every seafarer record, automates the repetitive administration, and raises an alert before a certificate lapses or a rest-hours rule is breached. Used properly, it removes the spreadsheet chaos that sinks an in-house crewing desk.
The core modules are consistent across the market: payroll and allotments from embarkation to sign-off, crew planning and rotation, certificate and document tracking for seaman’s books, endorsements, passports, visas, and medicals with expiry alerts, hours-of-rest logging against the legal limits, and a crew matrix that scores the manning against company or OCIMF criteria. That is a genuinely useful stack, and if you run your own crewing department you should have it. For a plain-language grounding in the function these tools support, our sibling explainer What Is Crew Management in Shipping? sets the baseline.
The point to hold onto is that every one of those modules is a record of work someone else did. The software tracks the certificate; a person still had to recruit the officer who holds it. The software logs the rest hours; a person still has to plan a rotation that makes those hours achievable. The tool is the ledger, not the labour.
Where the software stops
Software stops at three hard limits, and the vendors are honest about it if you read the fine print. It does not source or hire the crew. It does not judge competence. And it does not carry accountability. Those three gaps are the entire reason a managed service exists.
Take hiring first. A crew management platform will store and rank candidates beautifully, but it will not go to Batam, interview a second engineer, check his references against a former master, and decide he is right for a product tanker on a demanding trade. That is human work, and on tankers it is specialist human work. The tanker version of it sits in Seafarer Recruitment and Manning for Tanker Fleets.
Then competence. This is the gap owners underestimate most. Certificate tracking confirms that an officer holds a valid STCW advanced oil tanker endorsement. Under the International Maritime Organization’s STCW Convention, that endorsement is mandatory for the master, chief engineer, chief mate, second engineer, and anyone with immediate responsibility for cargo on an oil tanker. The software will flag the day it expires. What it cannot tell you is whether the officer who holds it has real recent tanker time or is endorsed on paper and thin in practice. The certificate side is covered in STCW Requirements: What Tanker Crew Must Hold, but the judgment behind it is not a field in a database.
Finally accountability. Read almost any crew software vendor’s own description and you will find the same line: the operator retains responsibility for regulatory compliance. The tool does not assume it. So when a chief officer fails a medical in a load port at three in the morning, or a rest-hours breach turns up in a Port State Control inspection, the licence does not answer the phone. Someone has to, and with software alone that someone is you.
What managed crewing is
Managed crewing is a contract under which a specialist takes responsibility for putting qualified, compliant seafarers on your ship and keeping them there. Sourcing, vetting, certification, deployment, payroll, welfare, and repatriation are the manager’s job, and so is the risk that comes with each. The owner keeps commercial control of the vessel. The manager carries the manning obligation. This is the outcome the software cannot deliver, and it is the whole subject of the hub pillar, Maritime Crew Management Services for Tankers.
The difference is not a feature list. It is who is answerable. A platform gives you a better view of your crewing. A managed service gives you a crewed ship and a named party who is on the hook for it. Those are different purchases at different prices for different buyers, and confusing them is how an owner ends up with a subscription and no crew.
Managed crewing vs crew management software, side by side
The cleanest way to see the split is by asking, for each task, who does it and who is accountable when it fails. That second column is the one that matters.
Task | Crew management software (the tool) | Managed crewing (the outcome) |
|---|---|---|
Source and vet seafarers | You do; the tool stores the records | The manager, from its own pool |
Judge tanker competence | Not covered; it tracks certificates, not ability | The manager screens for it |
Run payroll and allotments | You run it, inside the software | The manager runs it |
Track STCW endorsements and certificates | Yes, with expiry alerts | The manager tracks and acts on them |
Log MLC 2006 hours of rest | Yes, with breach alerts | The manager plans rotations so the hours are achievable |
Plan and execute crew change | You plan it, using the tool | The manager owns the logistics |
Answer a SIRE 2.0 crew finding | You do | The manager does |
Carry MLC and flag-state accountability | No; the operator retains it | The manager holds it |
What you still need in-house | A full crewing department | Commercial oversight only |
Best fit | Operators digitising their own crewing | Owners who want the outcome outsourced |
The table makes the reframe concrete. Software is columns of capability with the accountability line always landing back on you. Managed crewing moves that line onto the manager. The KPI you should track to judge either arrangement is retention by rank, which we argue in KPIs Every Ship Owner Should Track is the single number that predicts your real cost and safety outcome.
The four things a platform cannot own
Strip the marketing away and a managed service buys you four things no licence provides: accountability, competency, welfare, and compliance.
Accountability is binary. Either a named party is responsible for your manning or you are, and a dashboard does not sign a seafarer employment agreement or answer a detention. Competency is where the tool confirms the paperwork but the manager confirms the person. On a tanker that gap is expensive, because the failures that cost you a charter are rarely a missing certificate caught at screening. They are competence gaps that only surface under a SIRE 2.0 inspection or during an actual cargo operation, the point we make in SIRE 2.0 Compliance: Beyond Checklists. Welfare is a legal duty rather than a soft extra: retention, medical support, grievance handling, and on-time wages are what keep a crew stable, and a stable crew is the one that runs your safety management system as intended.
Compliance is the fourth, and it is where the hours-of-rest example bites. A platform logs rest hours against MLC 2006 Standard A2.3, which sets a minimum of 10 hours of rest in any 24-hour period and 77 hours in any seven-day period, with rest split into no more than two periods, one of at least six hours, and no more than 14 hours between them, as the International Labour Organization sets out. The software will show you a clean log and flag a breach. What it will not do is build a rotation that makes those numbers real on a tanker with tight port calls, or answer for the breach when the log turns out to be optimistic. That is the manager’s job, and it connects straight to the wider duty set in MLC 2006 Explained: Maritime Labour Convention Compliance.
First-hand: where software alone fails
From the operator’s chair, the failure mode is almost never a missing feature in the software. It is a clean screen sitting on top of a tired ship.
Here is the scenario we see. An owner runs crewing in-house with a good platform. The certificate matrix is green, the payroll runs on time, the rest-hours module shows full compliance. Then a vetting inspector talks to the crew, or a cargo operation goes long, and the truth emerges: the reliefs kept slipping a port at a time, the same officers kept covering the gap, and the rest-hours log was being completed to satisfy the software rather than to reflect the deck. Every field was filled in correctly. The ship was still fatigued.
The tool did exactly what it was built to do. It recorded and alerted. It could not plan a rotation a full cycle ahead, and it could not decide that this trade needed a fresh chief officer rather than a fifth extension. Those are judgment calls, and judgment is what you outsource when you buy a managed service. This is also why visibility tools matter on top of the service, not instead of it. Data that surfaces a slipping rotation early is genuinely useful, which is the case we make in How Real-Time Fleet Monitoring Reduces Downtime. The data helps a human decide. It does not decide.
Our opinion: buy the outcome, run the platform underneath
Our stated position, as operators: the right answer for most tanker and bunker owners is not software or a managed service. It is a managed service with a strong platform underneath it, and the owner should insist on both.
Buy the outcome, because accountability, competence, welfare, and compliance are not things a subscription can hold. Then insist the manager runs a real crew platform beneath the service, so you get the visibility a good tool provides without having to staff and operate it yourself. The mistake we watch owners make is treating this as an either/or: they buy a licence and quietly rebuild a crewing department around it, or they accept a managed service with no digital transparency and wait for the monthly report. The better arrangement is a manager who is accountable for the crew and gives you live access to the same data the software holds.
How Emaris runs both
Emaris Shipping runs managed crewing for tankers and bunker vessels across Singapore, Southeast Asia, and the Middle East, with a crewing base including Batam, Indonesia. Underneath that managed service we run the NOZZLE crew and fleet platform, so the certificate tracking, hours-of-rest logging, payroll, and OCIMF crew matrix are all live and visible to the owner, while the accountability for sourcing, competence, welfare, and compliance stays with us. You get the tool and the outcome in one contract, rather than a licence you have to operate and a compliance risk you have to carry. That is the distinction this whole page turns on: the platform is how the work is recorded, and the managed service is who is answerable for it.
FAQ
Is crew management software the same as a crew management service?
No. Crew management software is a tool you operate with your own crewing department. A crew management service is a managed outcome, where a specialist sources, vets, deploys, and takes accountability for the crew. Software gives you a better system; a service gives you a manned, compliant ship.
What does crew management software do?
It runs the administrative core of a crewing operation: payroll and allotments, crew planning and rotation, certificate and document tracking with expiry alerts, MLC 2006 hours-of-rest logging with breach alerts, medical records, and an OCIMF-style crew matrix. It records and alerts. It does not recruit, judge competence, or carry compliance accountability.
Can software make my crew MLC 2006 compliant?
Not on its own. Software logs hours of rest against the MLC 2006 limits and flags a breach, which is useful. But compliance is achieved by planning rotations that make those rest hours achievable and by a party taking legal responsibility for them. The log is evidence; the manager is the compliance.
Do I still need a crewing team if I buy the software?
Yes. A crew management platform assumes you have a crewing department to operate it. If you do not want to run one, you need a managed crewing service, not a licence. The software is for operators digitising crewing they already do in-house.
Who is accountable if a certificate lapses or a rest-hours breach is found?
With software alone, you are. Vendors are explicit that the operator retains regulatory responsibility. With a managed crewing service, the manager holds that accountability, including the STCW endorsement tracking, MLC 2006 duties, and the answer to a Port State Control or SIRE 2.0 finding.
Why does the search for crew management software return only SaaS vendors?
Because the term is a software-buyer’s query, so the SERP is filled with platforms and “top 10” listicles. That does not mean software is the answer to your problem. If you are an owner looking to outsource the crewing outcome rather than digitise your own, you are searching in the wrong category, and a managed service is what you actually need.
Does a good manager use software too?
Yes, and you should require it. The best arrangement is a managed crewing service running a real crew platform underneath, so you get accountability and live visibility together. A manager with no digital transparency is as much of a red flag as software with no one accountable behind it.
Quick Q&A for decision-makers
Should I buy crew management software or a managed crewing service? Buy the service if you want the crewing outcome outsourced and someone accountable for it. Buy the software only if you already run a crewing department and want to run it better. Do not buy the licence expecting a crewed ship.
If I already own crew software, do I still need a manager? Only if you also want to be out of the crewing business. The software supports a department; it does not replace one. If you do not want the department, you want the service, with the software running underneath it.
What is the one question that cuts through the confusion? Ask, for each crewing task, who is accountable when it fails. If the answer is “you,” you have bought a tool. If the answer is “the manager,” you have bought an outcome.
Next step
If you run tankers or bunker vessels and you are weighing a crew management platform against a managed service, decide first which one you are actually trying to buy: a better system for a team you keep, or a crewed and compliant ship you do not have to staff. Bring your fleet’s trade pattern, flag, and vetting requirements to the conversation, and judge any arrangement on who is accountable, not on the length of the feature list.