Yacht refit management: from first issue to final handover
Across 120 open items and four teams working at once, the coordination problem becomes the project. Here is how to keep every item, person, part, and decision connected from day one.
Six weeks into a large refit, the chief engineer raises an issue with the watermaker. The shipyard logs it separately from the project manager's list. The owner's rep hears about it on a call and follows up by email. A replacement membrane is ordered, but the order lives in the procurement manager's inbox. By the time the job is complete, four people have partial knowledge of what happened, and none has the full picture. The watermaker works. The record does not exist.
Multiply that across 80 or 120 open items, spread across interior, engineering, deck, and galley teams, with in-house crew, shipyard workers, and third-party specialists all working at once, and the coordination problem becomes the project. Yacht refit software does not solve this by digitising a spreadsheet. It solves it by keeping every item, every person, every part, and every decision connected in a single workspace from the first day to the last.
Why refits break down structurally, not just logistically
The standard explanation for overruns is logistical — late parts, scope creep, communication gaps. Those are symptoms of a deeper structural problem. A large refit involves at least three categories of work running in parallel: internal work carried out by crew or in-house teams; external work sent to specialist vendors or repair facilities; and procurement, sourcing the components both of the above require. In most environments, each category is managed in a different place — internal tasks in a spreadsheet, external work by email, procurement across supplier relationships with no central record.
The specific failure this creates is dependency blindness. A job cannot start until a part arrives. A part cannot be ordered until the job is scoped. A job cannot be scoped until someone has inspected the space. When these dependencies exist across disconnected systems, they are invisible until they become delays. Good yacht refit software does not just organise the three categories — it connects them so the dependencies are visible and trackable in real time.
How Map My Maintenance structures a refit
Map My Maintenance is built around three connected modules that map onto the three categories. The Work List handles internal tasks, each item capturing title, overview, priority, status, proposed dates, assigned team and persons, and the exact location on the vessel's GA plan, with images, annotated instructions, and sub-sections attached directly. The Project List handles external work, with a status workflow that reflects its real lifecycle — Initiated, Progressing, Paused, Pending Review, Sent to Vendor, Sent to Repair Facility, Sent to Agent, Cancelled — and the same documentation capability. Special Purchases handles procurement, each order capturing components, quoting companies, uploaded quotes, delivery dates, and address, with components assigned their own location so the delivery destination is recorded at the component level.
The connection between the three is direct and explicit: each Project List or Work List item can be linked to one or more Special Purchase records, which appear on the item detail screen. The dependency between a job and its required parts is visible in both directions — from the work item you see what has been ordered; from the procurement record you see which job it supports.
Locating every job on the vessel
During setup, the vessel's GA plan is uploaded as a background canvas, and the Area Setup drawing tool maps the vessel's structure: each deck named, spaces drawn directly onto the plan, precise location markers placed within each space — Bridge Deck, Main Deck, Lower Deck, Engine Room, Crew Quarters, Tender Garage, each broken into compartments and machinery spaces. Every item is then assignable to an exact Area, Space, and Location, and the Site Plan filter filters any list to a selected zone.
A spatial view, no extra data entry
A chief engineer reviewing outstanding engine room jobs does not filter by keyword. They open the Site Plan filter, select the engine room, and see every open item in that space across all three modules — internal tasks, external jobs, and outstanding deliveries.
Keeping the team coordinated across a long project
A large refit runs for months, with people moving on and off the project. The Activity Log on every item records each status change, priority change, date change, image upload, and comment automatically, with a timestamp and the name of the person who made it — permanent and uneditable. When a contractor leaves, their work record does not leave with them; when a new crew member joins, every prior decision is readable in the log. Comments stay attached to the item, and @everyone notifies all assigned users. Email digest notifications can be configured per site at 12-hourly, daily, or weekly intervals, so an owner's rep who is off-site receives structured summaries without chasing updates.
The timeline view across the full refit
The Timeline and Follow-Up module plots every item as a horizontal bar across a Gantt chart spanning its proposed dates, organised by module and grouped by Group Tag, each bar colour-coded by status. Group Tags collect related items across modules into a single collapsible group — "Engine Room Phase 1," "Interior Soft Furnishings" — and bars with a linked Special Purchase show a chain-link icon. The Has Special Purchase filter shows only items waiting on parts, when those parts are due, and whether the delivery dates align with the work start dates. Export to Excel shares the full schedule with the shipyard or owner's rep.
From first issue to final report
At the end of a refit, the reporting function generates structured documents from live data: Work List and Project List reports with the item header, priority, status, dates, sections, personnel, area and location, and linked Special Purchase references; Special Purchase reports formatted as procurement documents with component details, quoting companies, and uploaded quotes. Reports can be individual PDFs, a combined full report, or summary lists, and exported as Excel, CSV, or Word, sent to any email directly from the list view. The handover report is not compiled at the end — it is a formatted output of records built throughout the refit. For a chief engineer who has run the project in Map My Maintenance from the first issue, the handover is not a task. It is a consequence of how the work was recorded.