The weekly return gives the aft deck one percentage, and it is rising. It rose last week as well. What it cannot show is that the joiner has run ahead of his programme while the systems first fix behind that lining has not moved in a fortnight. The deck was never divided in a way that would let it.
Percentage complete is usually an opinion. Somebody walks a compartment, forms a judgement and writes a figure. It becomes a measurement only where the contract defines what earns the credit. Hours booked and material issued against a cost code measure something else, what has been consumed, off a timesheet and a store docket that exist whether anybody is reporting or not.
The structure those codes sit in is agreed at contract signature, usually quickly and without argument. It sets a hard ceiling on what any later report can tell an owner, however good the report looks. Reporting resolution is a procurement decision taken before work starts, not something a report can recover afterwards.
Percentage complete is usually an opinion with a number on it
A foreman who has fitted out more cabins than he can name reads a compartment faster than any reporting system, and his figure arrives already averaged. Put coating, joinery and systems for one deck under a single code and the three trades are summed before anyone sees them. One trade running ahead subsidises another standing still, the return climbs smoothly, and the deck loses its sequence.
The averaging has a timing consequence. A trade behind on a shared code gives no signal until it blocks something. The first visible sign is a hold point missed near the end, when there is no float left to absorb it, which is one of the ordinary mechanisms behind why a refit programme slips. Nothing was concealed. Nothing was measurable either.
Yacht refit cost codes set a ceiling at signature
A report cannot be finer than the data behind it. If the books carry one line for a deck, no weekly return or site meeting can separate what happened inside it. Resolution can be lowered afterwards by summarising. It can never be raised: the hours were never written that way.
The work breakdown belongs in the tender, beside the scope, not in a reporting annex drafted after award. A specification three yards can price is the structure three yards can be made to book against, if the contract says they must. Retrofitting that structure mid-programme is always partial: hours already booked stay where they were booked.
None of it is visible by default. A yard's timesheets are its own commercial record, and a fixed price does not open them. What makes booked hours readable to an owner is a term that says so: a reporting clause naming the codes, or a cost-reimbursable basis that carries the right with it. On a lump sum the structure still earns its keep, because every variation is priced and argued against it.
Ask for the breakdown at the grain decisions are made
The test is not how many codes there are. It is whether each code matches a decision the owner will actually take: whether to defer the guest bathrooms, whether to pay to recover the engine room. Each needs its own line or it will be argued from opinion.
- By compartment, taken off the general arrangement rather than invented for the contract, so every code names a space somebody can point to and open.
- By trade within each compartment, because joinery, coatings, electrical and systems finish at different times and block each other in a sequence the compartment sets.
- By variation, each one coded on the day it is instructed and never folded into the base scope it touches.
Crossed that way a code names a space and a trade, and the return reads to someone outside the hall. It matters most when the owner's team is not resident, the normal case when managing a refit from abroad. At Reviva the trades are in-house, within a short walk of the berth, so the bench that did the work is a short walk from the office asking about it.
Every variation carries its own code when instructed
Coding discipline is won or lost on variations, and the deciding moment is earlier than owners expect. Not when the variation is priced, and not when it is agreed. The day the instruction goes out. If hours can be booked to a change before that change has a code, they land on the nearest base-scope line, and the change is now inside the cost of the base work.
The change then stops being separable at redelivery, so nobody can say what it cost against what was quoted, and the base scope appears to have overrun. End-of-refit arguments are rarely about whether work was done, but about which pot it belongs in.
A variation code should carry who instructed it, on what date, against which drawing revision, the same provenance anything in the pack that leaves with her needs before it is worth keeping.
A three-way check a weekly return cannot fake
Once the grain is right, the weekly read compares three independent things, not one figure. Hours booked to the code. Hours allowed for that code in the estimate, read against where the programme says the work should have reached. The physical state of that compartment, which a captain can see with a torch.
A single percentage collapses all three into one judgement and cannot disagree with itself. Three readings can, and the disagreement is the information. Hours ahead of the allowance with the compartment looking right means the allowance was optimistic or the sequence changed. Hours on allowance with the compartment visibly behind means rework nobody has reported, or hours booked to the wrong code. Hours behind it with the compartment apparently ahead means those hours are landing on another code, or the allowance over-allocated them.
None of those readings is an accusation. Each is a question whose answer takes a phone call, not a flight, and the check adds little: timesheets, estimate and programme exist already.
The two cost codes owners leave undivided and regret
The first is yard services. Cranage, staging, power, waste, hall time, protection, cleaning. Under one code it grows steadily, and at redelivery it is one of the few figures nothing physical can test. Split by the activity that consumed it, each line becomes arguable while the job is still running, and it stops being the quiet line that makes two refit quotes impossible to compare.
The second is labour standing time. Hours booked to the job and waiting: on a part, on a decision, on another trade's clearance, on an owner's answer. With no code of its own it is booked as production, so the compartment looks expensive and the waiting looks free. Give it a code and the return shows what the programme is losing, and to whom. The owners who ask for that line answer their own emails faster.
None of this needs a new system, only the code list argued over before the contract is signed. It is a conversation worth having before signature, with a scope in hand.
Written at the yard in Tuzla, where joinery, metalwork, coatings, electrical and systems sit within a short walk of the berth. Cost codes, programmes and timesheets are the yard's own records. What an owner can set is the grain the work is reported at, and that is set in the contract rather than asked for later.
Send the scope before the code list is fixed
Send the specification, or the problem, with the general arrangement. We come back with a scope, a schedule and a berth. Ask any yard how the work is to be broken down before you compare prices, and read the structure as carefully as the figure. Write to info@revivarefit.com.
START A REFIT