Order of work
Structure before systems, systems before joinery, joinery before finish — and nothing closed up before what is behind it has been signed off.
On a foreshore yard, the expensive failures happen between trades, not inside them. The caulker waits on the shipwright; the shipwright waits on timber; the engineer arrives to find the bearers not yet rebuilt; the tide window passes. Yard project management is the discipline of making those handoffs happen on purpose.
Structure before systems, systems before joinery, joinery before finish — and nothing closed up before what is behind it has been signed off.
Timber, fastenings, coatings and equipment ordered against the schedule, with long-lead items identified at scope stage rather than discovered mid-programme.
Written description, photograph, price, approval — in that order, every time, including for small items batched weekly.
Dated photography, weekly notes and a final record listing what was replaced, repaired, and deliberately deferred.
Every programme on this coast is written against two clocks. The tide governs haul and relaunch. The season governs how long a hull can safely sit open, how quickly timber and coatings will dry, and whether labour is competing with other work on the beach. A programme that ignores either is a wish list. The desk's schedule therefore fixes the two irreversible events first — the haul window and the relaunch window — and fits the work between them, rather than scheduling the work and hoping the tide cooperates.
The shipwright, caulking and joinery gangs on this foreshore work to a craft tradition with its own rhythms and its own way of judging quality. Project management here is not about imposing an unfamiliar process on them; it is about translating between that tradition and an owner's need for dates, prices and evidence. In practice that means specifications written in terms the gang actually uses, inspections at the moments that matter, and payment structures that respect how the work is really staged.
Scope written only in English and never discussed in Indonesian on the beach produces confident agreement and divergent understanding. Every scope line that matters is confirmed verbally with the people doing the work.
Line-item scope, milestone schedule, long-lead list, and the two fixed tide events.
What moved, what did not, what is coming, and any risk to the completion window.
Dated images from consistent positions, especially of structure that will be permanently hidden.
Every approved variation with its reason, price and date — one running document, not scattered messages.
Final record of work done, materials used, items deferred with reasons, and recommendations for the next haul-out.
Project management stops where ownership decisions begin. The desk will present options, costs and consequences; it will not choose a layout, an engine or a finish standard on an owner's behalf. It also does not absorb functions that belong elsewhere: brokerage and charter marketing sit with PT Komodo Bahari Nusantara, ongoing technical and commercial vessel management with PT Komodo Vessel Management, and construction, repair, refit and sale contracts with PT Komodo Galangan Nusantara. Keeping those separate is deliberate — separate contracts, separate fees, separate ledgers.
Owners running work across more than one region can have the Bira stage sequenced against whatever is happening elsewhere, so the programme reflects where each stage is genuinely best done rather than where it is most convenient to book.
Send the scope you have, the dates you need, and the constraint you are most worried about. The first deliverable is a schedule with the tide windows fixed.