Ship Repair Yard Software: Why Growth Work Agreed on the Dock Bottom Never Survives the Final Invoice

Why a ship repair yard bleeds margin between the docking and the final account

A handysize bulker sits on the blocks at 06:00. The agreed specification says renew 40 tonnes of steel in the number three topside tank. Blasting starts, the class surveyor taps the plating, and the wastage runs out into the adjacent frames and two longitudinals nobody opened up. It is now 68 tonnes. The owner's superintendent is standing on the dock bottom in a boiler suit, he nods, the production foreman writes S R extra frames 84 to 96 approx 28t agreed w supt on the back of a job card, and both men get on with the day. Four months later the owner's accounts department disputes the extra, because what the yard has is a foreman's handwriting and a superintendent who has since flown home and taken another vessel.

That is the whole business risk of ship repair in one paragraph. The quotation is a guess against a specification written before anyone opened the tank. The money is in what the survey finds. And the growth work, which is the part of the invoice that actually carries your margin, is the part with the weakest paperwork behind it. Every yard manager we have sat with can name a job where the final account was settled at a number the yard did not choose, because the evidence for the extras was a photo on someone's phone and a verbal agreement with a man who had left.

Problem 1: the repair specification arrives in the owner's format, not yours

An owner sends a specification numbered their way. One will use a class aligned structure with tank and compartment references. Another sends a spreadsheet from their technical superintendent with item numbers running to three decimal places. A third sends a scanned PDF from a fleet manager who inherited the template. Your estimator retypes all of it into the yard's own quotation sheet, and from that moment there are two numbering systems on the job: the owner's spec item and your work order.

Every downstream argument traces back to that split. The owner refers to item 4.12.3, your steel foreman refers to job 1188 line 40, your invoice refers to something else again, and reconciling the three at final account is a week of somebody's life per vessel. This is why yards that quote fast still invoice slowly.

A custom build fixes this at the root by treating the owner spec item as a first class identifier that never disappears. Import the spec once, map each owner item to one or more internal work orders, and carry both references on every quotation line, every timesheet posting, every variation, and every invoice line. Then the final account can be printed in the owner's numbering, which is the single change that ends most disputes before they start.

Problem 2: growth work is agreed on the dock bottom and argued in the office

Growth work is not a rare event in ship repair, it is the normal operating condition. You cannot know the wastage until the coating is off. You cannot know the tailshaft clearance until it is drawn. You cannot know the valve seat condition until it is opened. So the yard's real product is not the quoted specification, it is the ability to price and prove additional work while the vessel is still on the blocks and the superintendent is still standing next to it.

The proof is what breaks. A defensible variation needs the owner spec reference, a description written in the owner's language, the measured quantity, the rate applied, the photograph taken before the plate was cut, the date and time, and the superintendent's signature captured while he is still on site. Yards collect maybe two of those seven, on paper, then scan the paper.

What a custom build must include is a variation record raised from a phone or tablet on the dock, with photos attached at the moment of discovery, the rate pulled automatically from the contract rate card so nobody argues over price later, and a signature captured on the device from the attending superintendent. The variation then becomes a live commercial object: it appears on the yard's exposure report, it feeds the dock plan because 28 extra tonnes of steel is also extra days, and it appears on the owner portal so the superintendent's own office sees the number the same day rather than four months later. That last part changes the tone of the final account meeting more than any other feature you can build.

Problem 3: the dock slot is the only thing you actually sell

A graving dock or a floating dock is a fixed asset with a fixed number of vessel days per year. Every hour of overrun on the vessel in front pushes the vessel behind, and the vessel behind may have a delivery date tied to a charter. Yards manage this on a Gantt chart that is accurate at the moment it is printed and wrong by the afternoon, because the growth work that just got agreed on the dock bottom has not reached the planner.

Tidal gates, pump down and flooding windows, blasting and painting constraints where paint application has temperature and humidity limits set by the coating manufacturer, crane availability shared across berths, and the class survey attendance calendar all sit on top of that. A generic project scheduling tool models tasks and dependencies. It does not model the fact that you cannot paint tonight, the dock cannot be flooded until the sea valves are back, and the next owner's superintendent is already booked on a flight.

A custom build ties variations directly into the dock plan, so approved growth work automatically extends the vessel's estimated undocking and immediately shows the knock on to the next arrival. That single link converts a scheduling surprise into a commercial conversation you can have a week early, which is usually when you can still recover the day rate or renegotiate the slot.

Problem 4: three pricing models on one job number

Ship repair pricing is a hybrid and no packaged system likes hybrids. Hull cleaning and anode renewal go lump sum. Steel renewal goes by weight, with different rates for flat plate, shaped plate, and work in confined or overhead positions. Machinery work goes day rate per trade per man. Subcontracted work, tank coating or ultrasonic thickness measurement, goes at cost plus a handling percentage. Dock occupancy goes per day. Cranes and staging go per lift or per square metre per week.

A custom build posts every cost to the job at the level it was incurred: trade hours from the timesheet, plate and consumables from stores issue against the job, subcontractor invoices matched to the work order that raised them, and dock days accrued automatically. Then the margin report runs per owner spec item, per pricing model, per trade, and per vessel. Yards discover which owners are structurally unprofitable and which repair types they should stop quoting cheap to win.

Where the incumbent systems actually stop

SpecTec AMOS, SERTICA and ShipNet are serious, mature maritime systems and we would not dismiss them. The point to understand is which side of the transaction they were built for. They are fleet systems, designed for the shipowner and the technical manager: planned maintenance schedules, component hierarchies, requisition and procurement, certificate and survey tracking across a fleet, crew and stores. When an owner sends you a specification, there is a good chance it came out of one of those systems.

What none of them was designed to do is protect a yard's commercial position. They do not price growth work against a negotiated rate card, they do not capture a superintendent's signature on the dock bottom, they do not plan a graving dock against tidal and coating constraints, and they do not produce a final account defensible in a dispute. Some yards buy a general contracting or ERP (Enterprise Resource Planning) package instead and find the same gap in a different shape: the work breakdown structure assumes the scope was known when the contract was signed, which in ship repair is never true. That assumption is the entire problem.

What this costs and how long it takes

Across the 2,000 plus projects Digital Heroes has delivered, the honest shape for a ship repair yard is this. A first release covering specification import and mapping, quotation against a rate card, job numbering, dock and berth planning, and mobile variation capture with photos and signature runs $70,000 to $150,000 and ships in 12 to 18 weeks. That is a system your estimators and dock foremen use on the next vessel, not a pilot.

A full yard platform adding timesheet and stores posting to job numbers, subcontractor commitment control, permit to work and gate access, class attendance scheduling, progressive and final invoicing, and an owner portal runs $180,000 to $450,000 phased over 6 to 14 months.

What drives cost up in this category specifically: multiple docks and berths with genuinely different constraints, integration to an existing accounting or ERP system where the job costing structure was designed for something else, offline capability because dock bottoms and tank interiors have no signal and your variation capture has to work anyway, and multi currency and multi language if you serve international owners and a mixed workforce. What keeps cost down: starting with one dock, your top three repair types by revenue, and variation capture, because variation capture alone usually pays for the release.

Build versus buy, and when buying is the right call

Do not build if you are an afloat repair outfit doing voyage repairs, small steel jobs and superintendent assisted machinery work with no dock of your own. Your scarce resource is people, not slots, and a good spreadsheet with a disciplined variation form will hold. Do not build if your yard runs on long term fixed contracts with one naval or government customer under their own reporting system, because you will be forced into their formats anyway.

Build when two or more of these are true. You own a dock or a syncrolift and slot utilisation drives your P and L. Growth work is a material share of your typical final account. You have lost a dispute in the last two years for lack of evidence. You quote in more than one pricing model on the same job. You serve owners who each send specifications in a different format and your estimating team retypes them.

How to choose a developer for ship repair yard software

Ask them to model the variation before they quote. A developer who has done yard work will draw owner spec item, work order, variation with rate reference and evidence attachments, and approval with captured signature, and they will ask you which of those the owner is contractually allowed to reject. A developer who draws project, task and change request has built a construction tool and is about to learn ship repair on your money.

Ask specifically how the variation capture behaves with no connectivity inside a double bottom tank. If the answer does not include local storage and a sync queue, the feature will not be used, and an unused variation feature is worse than paper because it creates a false record.

Ask what they have integrated. Posting labour hours from a clocking system, issuing stores against a job, and pushing a final account into an accounting ledger are three different integration problems with three different failure modes. Ask for the specific system and the specific document, not a claim about integrations in general.

Ask who owns the code and get it in writing before kickoff. You should own the repository, the cloud accounts, and the right to hire anyone else to continue the work. At Digital Heroes the code is yours from the first commit, and we would tell you to walk away from anyone who hedges on that.