drydock work scope

What is drydock work scope

A drydock work scope is the structured set of tasks and deliverables that specifies what work will be performed on a vessel during a drydock period, including maintenance and repairs, inspections, class-related requirements, coating and surface preparation activities, equipment work, and any project work that must be completed to a defined standard and schedule. In a maritime ERP and ship-management context, it is the operational bridge between planning inputs (maintenance history, defect lists, class conditions, spares availability, and budget assumptions) and execution outputs (yard quotations, work orders, technical reports, and acceptance evidence).

For technical and fleet leadership, the scope is not only a document for the yard. It is the controlling definition of the work that will drive off-hire planning, downtime windows, procurement of spares and services, maintenance execution records, QHSE controls, and financial tracking. When the scope is incomplete or ambiguous, the yard and ship operator often resolve gaps through change orders, additional inspections, and revised estimates, which can create schedule slippage and budget variance.

Synonyms

Drydock scope of work: The same concept expressed as a formal scope document.
Drydocking work package: A scope bundled with supporting documents and acceptance criteria.
Drydock specification: A scope expressed with technical requirements and deliverable definitions.
Yard work scope: Scope as quoted and executed by the yard.
Planned drydock maintenance scope: Scope focused on planned maintenance and condition-based tasks.
Drydock project scope: Scope that includes project-type modifications beyond routine maintenance.

drydock work scope Examples

A scope that lists hull and machinery tasks by system and location, each with a reference to the underlying defect or PMS history item, plus acceptance criteria and required documentation.
A scope that includes class survey tasks, coating system requirements, and surface preparation steps, with dependencies such as grit blasting completion before coating application.
A scope that bundles equipment overhauls (for example, pumps, valves, or steering components) with spares lists, lead-time assumptions, and test or commissioning steps after installation.
A scope that captures inspection-only items (for example, thickness measurements, NDT, or underwater survey findings) and defines what triggers repair work if results fall outside tolerances.
A scope that includes QHSE requirements for hot work, confined space entry, waste handling, and environmental controls, tied to the yard’s execution plan.
A scope that aligns planned work with off-hire windows and identifies critical path activities, such as steel renewal, coating cure cycles, and sea trial preparation.

Key features and considerations

Task granularity: Work items should be specified at a level that supports work order creation, procurement planning, and acceptance verification.
Traceability: Each task should link back to its origin, such as PMS history, defect reports, class conditions, or engineering recommendations.
Acceptance evidence: The scope should define deliverables, test steps, inspection records, and documentation required for sign-off.
Dependencies and sequencing: Coating, steel renewal, NDT, and equipment installation often depend on prior steps; sequencing reduces rework.
Budget and quotation alignment: Scope wording should match what the yard can quote and execute, reducing the need for change orders.
Operational constraints: Off-hire windows, access limitations, and vessel readiness requirements should be reflected in the schedule assumptions.

What a drydock work scope typically contains

A robust drydock work scope usually combines technical content with operational and governance structure. In practice, it is most useful when it is organized so that maintenance, procurement, and reporting teams can act on it without reinterpreting the intent.

Maintenance and repair tasks

Maintenance tasks in a drydock scope cover planned and condition-based work that requires vessel access not available while afloat. Typical categories include hull structural repairs, machinery maintenance, corrosion control, insulation renewals, and renewal of worn components. Each task should specify:

The system or area (for example, hull, piping, machinery, tanks, or deck equipment).
The work type (inspection, repair, renewal, adjustment, replacement, or testing).
The technical basis (defect reference, PMS work history, or engineering recommendation).
The expected outcome (restored function, corrosion removal, thickness restoration, or compliance with tolerances).
The documentation required (inspection reports, test results, and material certificates where applicable).

Inspection and survey tasks

Inspection tasks are often the largest source of scope expansion if not defined clearly. A drydock scope should define what will be inspected, the method, the acceptance criteria, and what happens if findings require additional work. Common inspection elements include:

Visual inspections with defined focus areas.
NDT or thickness measurement plans with tolerance thresholds.
Survey preparation steps required for class or internal verification.
Reporting format and sign-off responsibilities.

A practical boundary is to separate “inspection-only” items from “repair-triggered” items. If repair is conditional on inspection results, the scope should state the decision logic, the approval process, and how the yard will price the additional work.

Class-related tasks are often time-bound and documentation-heavy. Even when class requirements are handled through separate workflows, the drydock work scope should translate them into actionable yard tasks. This includes:

Survey preparation and access requirements.
Specific inspection and testing steps required by the class plan.
Documentation deliverables needed for class submission.
Any constraints on materials, welding procedures, or coating systems.

The key is operational translation: the scope should be written so yard execution can produce the evidence needed for class acceptance without rework.

Coating and surface preparation scope

Coating work is frequently a critical path item because it depends on surface preparation quality, weather and curing conditions, and sequencing with steel works. A drydock work scope for coatings should include:

Coating system identification and intended thickness or performance requirements.
Surface preparation method and standard (for example, blast profile and cleanliness requirements).
Repair and pre-treatment steps for existing coatings and corrosion areas.
Application conditions and cure or recoat windows.
Inspection points (surface profile checks, holiday detection, thickness measurements).
Documentation such as coating inspection reports and material data.

Ambiguity in coating specifications is a common driver of budget variance. The scope should avoid mixing “general coating refresh” language with detailed coating system requirements unless both are aligned with the vessel’s coating management plan.

Equipment and systems work

Equipment tasks in a drydock scope include overhauls, replacements, and commissioning activities that require dry access. The scope should specify:

Equipment identification and location.
Work steps (dismantle, inspect, repair, replace, reinstall).
Test and commissioning steps after installation.
Spares and consumables requirements.
Interface responsibilities between ship staff and yard personnel.

For ERP-driven planning, equipment tasks should be linked to spares lists and procurement categories so that lead times and availability constraints are visible before the drydock window begins.

Project work and modifications

Some drydock periods include modifications beyond routine maintenance. Project scope elements should include:

Engineering drawings or technical references.
Work breakdown structure that supports procurement and change control.
Interfaces with existing systems and any operational constraints.
Testing and commissioning deliverables.
Acceptance criteria and handover requirements.

Project work often introduces additional stakeholders and documentation. The drydock work scope should define who provides engineering inputs and who signs off on completion.

drydock work scope Examples (operationally structured formats)

System-based scope: Group tasks by vessel system (hull, propulsion, auxiliary, piping, electrical, tanks) with sub-items for location and work type.
Defect-based scope: Group tasks by originating defect or PMS history item, with each defect driving one or more yard tasks.
Class-plan-based scope: Group tasks by class survey requirement, with documentation deliverables and sign-off points.
Critical-path scope: Highlight tasks that control the schedule, such as steel renewal and coating cure cycles, and list prerequisites.
Procurement-ready scope: Include spares and services requirements per task so procurement can proceed without reinterpretation.
Acceptance-evidence scope: For each task, define what evidence will be produced (reports, measurements, test results, photos, certificates).

Benefits of drydock work scope

Reduced change orders through clearer definition

A well-defined scope reduces the likelihood that the yard must interpret missing intent. When tasks are traceable to defects, PMS history, class requirements, and engineering recommendations, the execution team has fewer reasons to propose additional work outside the agreed basis. This supports implementation confidence by aligning planning assumptions with yard quotation structures.

Better off-hire and downtime control

Drydocking affects off-hire planning because schedule slippage can extend downtime and delay return to service. A scope that includes sequencing, dependencies, and critical path tasks allows fleet and technical leadership to plan off-hire windows with fewer unknowns. It also supports internal readiness planning, such as crew availability, commissioning resources, and test scheduling.

More accurate budgeting and cost tracking

Budget variance often arises when scope boundaries are unclear. When the scope is aligned with yard quotations and internal cost categories, finance teams can track planned versus actual costs with better granularity. This improves reporting quality and reduces post-drydock reconciliation effort.

Stronger maintenance record quality for future cycles

A drydock is a major data capture event. When the scope defines acceptance evidence and reporting formats, the resulting maintenance records become cleaner and more complete. This improves the quality of future PMS history and condition-based planning, supporting legacy system replacement and data migration by establishing consistent operational data structures.

Improved procurement planning for spares and services

Scope tasks that specify spares, consumables, and service requirements enable procurement planning before drydock execution begins. This reduces the risk of work stoppages due to missing parts and supports a single operational data layer approach where maintenance planning, procurement, and execution records share consistent identifiers.

Better QHSE integration during high-risk activities

Drydock work includes hot work, confined spaces, abrasive blasting, waste handling, and environmental controls. When the scope includes QHSE requirements tied to tasks, it supports operational governance and reduces the likelihood of safety or environmental nonconformities that can halt work.

Implementation, data, workflow, reporting, and governance

Scope creation workflow in a maritime ERP context

In an integrated ship-management environment, the drydock work scope typically emerges from multiple inputs:

PMS history and planned maintenance tasks.
Condition findings and defect reports.
Class condition trackers and survey requirements.
Coating management plan requirements and prior coating performance.
Spares and materials availability checks.
Yard quotation inputs and commercial assumptions.
Internal engineering recommendations and risk assessments.

The scope should then be translated into execution-ready work orders and procurement requests, with controlled change management for any deviations.

Data model considerations for AI-ready operational data

A drydock scope becomes more valuable over time when it is stored as structured operational data rather than only as a document. For AI-ready maritime ERP foundations, the scope should support:

Consistent task identifiers and standardized categories (system, location, work type).
Traceability fields that link tasks to their originating maintenance or survey drivers.
Acceptance evidence types and measurement records.
Dependency relationships (prerequisite tasks and gating activities).
Versioning and change control history.

When these elements are structured, later analytics can use them for predictive maintenance planning, schedule risk analysis, and budget forecasting without relying on unstructured text extraction.

Data migration and legacy system replacement risks

When migrating from legacy systems or document repositories into a unified ERP, drydock scope data often causes issues if it is not normalized. Common risks include:

Loss of traceability between defects, PMS history, and executed tasks.
Inconsistent naming conventions for vessel areas and equipment.
Missing acceptance evidence definitions, leading to incomplete historical records.
Quotation mismatch where scope wording does not align with how costs were categorized.
Version confusion when multiple scope revisions exist without clear lineage.

Mitigation approaches include defining a scope taxonomy, mapping legacy categories to the new structure, and ensuring that acceptance evidence and work order statuses are migrated with consistent semantics.

Governance and change control

Drydock scopes evolve. Governance should define:

How scope revisions are requested and approved.
How changes are priced and whether they are treated as variations or included in the base quotation.
How schedule impacts are assessed and communicated.
How acceptance criteria are updated when work changes.

A key governance principle is to keep the scope as the authoritative basis for work orders and cost tracking. If execution diverges, the system should record the divergence as a controlled change rather than overwriting the original intent.

Reporting implications for technical, fleet, and finance stakeholders

A drydock work scope should support reporting at multiple levels:

Technical reporting: work completion status, inspection results, and evidence attachments.
Fleet reporting: schedule adherence, critical path progress, and readiness milestones.
Finance reporting: planned versus actual costs by scope category and work order.
QHSE reporting: incident logs, permits, waste handling records, and environmental monitoring outcomes.

When scope definitions are consistent, reporting becomes more comparable across drydock cycles, improving trend analysis.

Challenges With drydock work scope

Scope incompleteness and ambiguity

Incomplete scope is often caused by missing defect drivers, missing acceptance criteria, or overly broad task descriptions. Ambiguity can lead to yard interpretations that do not match operator intent, which then triggers change orders.

Misalignment between scope and yard quotation structure

Even when the scope is technically correct, it may not align with how the yard prices work. If the quotation uses different categories or includes assumptions that are not reflected in the scope, cost tracking and variance analysis become difficult.

Sequencing gaps for coating and steel work

Coating and steel renewal are tightly coupled. If the scope does not define prerequisites and gating activities, coating work can be delayed by incomplete steel repairs, or steel repairs can be delayed by coating hold points. These sequencing gaps can extend downtime.

Spares and lead-time mismatches

A scope that lists equipment work without confirming spares availability can lead to work stoppages. In an integrated ERP, spares requirements should be visible early so procurement can manage lead times and substitutions with controlled approvals.

Acceptance evidence not defined early enough

If the scope does not specify what evidence will be delivered for each task, sign-off can become subjective. This can delay closure, complicate class submission, and reduce the quality of maintenance records for the next cycle.

Version control and revision confusion

Drydock scopes often exist as multiple revisions. Without clear versioning, teams may execute against an older scope while reporting against a newer one, creating reconciliation problems after drydock.

Drydock work scope vs drydock plan

A drydock plan describes the overall schedule, milestones, and operational readiness steps. The drydock work scope defines the technical and deliverable content of what will be executed. The plan may reference the scope, but it should not replace it. For operational control, both should be consistent.

Drydock work scope vs work order

A work order is the executable unit created from the scope within the ERP or maintenance system. The scope is the authoritative definition of tasks and acceptance criteria, while work orders operationalize those tasks for execution, tracking, and evidence capture.

Drydock work scope vs quotation

A quotation is the commercial offer from the yard. The scope should be the technical basis for quotation and execution. However, quotations may include assumptions or exclusions. A controlled alignment process is needed so that the scope and quotation do not diverge.

Drydock work scope vs class condition tracking

Class condition tracking identifies requirements and status for class-related items. The drydock work scope translates those requirements into yard-executable tasks and defines acceptance evidence. Keeping these aligned reduces the risk of missing survey steps or documentation.

Drydock work scope vs coating management planning

Coating management planning defines the long-term strategy and coating system selection. The drydock scope applies that strategy to the specific drydock window by defining the exact coating work, surface preparation, and inspection steps for the vessel’s current condition.

Practical boundary: scope should not be only narrative text

Narrative documents can be useful for context, but operational execution benefits from structured task definitions. When scope content is stored as structured operational data, it supports work order creation, procurement planning, and reporting without manual interpretation.