Hotel scope and technical scope, one redelivery date
Refit software for a vessel that has to sail with paying passengers the day after redelivery.
A cruise or ferry refit runs hotel scope, deck and cabin refurbishment, and technical scope, machinery and systems work, in parallel against a redelivery date that is already sold to passengers. Deskely tracks both scopes in one register so a delayed cabin refurbishment and an open engine room punch item are visible on the same board.
- Scope
- Hotel and technical
- Duration
- Days to a few weeks
- Constraint
- Fixed sailing date
- Gate
- Redelivery and passenger safety
Choose your project type
The problem
Cabin refurbishment and engine overhaul share a redelivery date and nothing else.
The hotel team is tracking cabins, galleys and public spaces against an interior designer's snag list. The technical team is tracking machinery overhauls, system upgrades and class items against a completely different document.
Neither team can see the other's risk to the sailing date until the two lists are manually compared, usually late and usually under pressure.
Deskely holds hotel and technical scope in the same register with the same redelivery gate, so a delay in either one is visible to the whole project the day it happens.
Setting up the register
Decks, cabins, public spaces and machinery are tagged assets with their own scope.
The vessel is modelled by deck and space for hotel scope, and by system and equipment for technical scope, within the same register.
General arrangements and the refit specification are parsed into the register, so every cabin, galley line and machinery item carries its scope of work from the outset.
That structure is what lets the yard report readiness by deck for the hotel team and by system for the technical team, from the same underlying data.
Execution
Snagging and technical punch are raised and closed the same way.
Interior contractors snag cabins and public spaces on tablet with photos, while technical teams record overhaul, hook-up and test results against machinery and systems, all in the same tool.
Every item is categorised by whether it blocks redelivery or passenger certification, so cosmetic snagging does not get treated with the same urgency as an open fire safety item.
Punch owners see their queue regardless of whether the item originated on a deck plan or a system diagram.
Redelivery
Redelivery is certified once, across both scopes, not twice.
The redelivery certificate lists both hotel and technical items that permitted it, with any carried snagging or punch shown against an owner and a date.
Passenger safety-related items, life-saving appliances, fire safety and stability follow their own certification path and cannot be waived the way cosmetic snagging can.
That distinction, enforced by the register rather than by memory, is what keeps a fast-turnaround refit defensible to the flag state and the cruise line's own technical team.
Stability and safety recertification under a hotel refit
New cabins and balconies add weight and the flag state will not certify a stability book nobody updated.
Adding balconies, extra decks, heavier furniture packages or new galley equipment during a hotel refit changes the vessel's lightship weight and centre of gravity, and life-saving appliances, evacuation routes and fire zones designed around the original passenger count and layout may no longer match what is actually on board.
Flag state and class require an updated stability booklet and evidence that life-saving appliance capacity, muster stations and fire safety systems still satisfy SOLAS for the revised layout, evidence that is difficult to assemble if hotel scope and technical scope have been tracked in two separate systems all refit.
Deskely ties added weight, revised general arrangement drawings and life-saving appliance and fire safety equipment changes to the same register the hotel and technical teams already use, so the stability and safety case going to the flag state reflects what was actually built rather than the original refit specification.
How it runs
From dry dock or pier-side start to a sailing date that holds.
A refit is won or lost on visibility across hotel and technical scope, because the sailing date does not care which team caused the delay.
- 01
Model decks and systems together
Hotel spaces and technical systems tagged in one register against the same redelivery gate.
- 02
Parse the refit specification
General arrangements and specification items drafted into the register per deck and per system.
- 03
Capture snagging and punch on tablet
Interior and technical teams raise items the same way, with photos, at the space or tag concerned.
- 04
Categorise by redelivery risk
Every item flagged as blocking or non-blocking for redelivery and passenger certification.
- 05
Track both scopes on one board
Hotel and technical readiness visible side by side, so risk to the sailing date is never one team's surprise.
- 06
Certify redelivery
Certificate issued from signed records across both scopes, with any carried items explicit and owned.
FAQ
Questions about Cruise and ferry refits scopes.
Keep reading
Marine and shipyard commissioning
The full sector view: hull and system registers, sea trial evidence, punch lists and redelivery certificates.
Read morePunch lists
Defects raised on board with photos, categorised by whether they block trials or redelivery.
Read moreWalkdowns
Pre-trial and pre-redelivery inspections run as structured walks that raise punch on the spot.
Read moreOther marine and shipyard project types: Newbuild vessel construction and trials, Vessel conversions and module integration, Drydock and repair periods, Naval and defence vessel completions, LNG/LPG carriers and gas systems, OSV, PSV, CSV and walk-to-work vessels, Dual-fuel, scrubber and emissions retrofits, Shipyard facility and drydock infrastructure, Commissioning through sea trials to delivery.
