Admitting a contractor through a shipyard gate does not, by itself, establish permission to start the proposed work. The same person might attend a meeting in the morning and be asked to undertake maintenance aboard a vessel later. Their identity and host may be unchanged, but the location, task and technical conditions are different. A security specification should make that distinction visible.
From research to the service specification
Kim and colleagues' 2017 study compared safety-climate and occupational-stress assessments among directly employed and subcontracted workers at a Korean shipyard. It identified differences between groups; it did not test whether gate controls or permit-to-work arrangements prevented accidents. [1]
The ILO shipbuilding code addresses responsibilities and cooperation among the parties involved. HSE identifies separate technical hazards in shipbuilding and repair, including confined spaces. [2][3] The allocation below is our practical proposal for a service specification. International guidance does not replace applicable Turkish requirements.
Give three decisions separate owners
The first decision is site admission. The shipyard's designated authority confirms the purpose of the visit and the receiving department. Security carries out the identity and admission checks within its instructions. The gate record documents that process.
The second decision concerns starting technical work. A person authorised under the operator's relevant permit arrangements carries out the required technical assessment. A security officer checking a document reference is not certifying gas-free conditions, hot-work arrangements, equipment suitability or confined-space safety.
The third decision concerns changes. Moving work to another vessel, compartment or time should not automatically extend the original admission. The specification should identify which department assesses the change and how its decision reaches the access-control team.
These decisions may be supported by the same software, but they should not be reduced to one ambiguous approved status. Users need to understand which approval exists and which remains outstanding.
Make the information available at the gate clear
The authorised operational team should communicate the information security needs to perform its own role. Possible states include admission awaiting confirmation, host confirmed, response awaited from the technical department and visit completed.
Such labels do not replace the technical permit. In particular, admitted to site should not appear to mean cleared to start work. A form or screen that combines both decisions into a single tick box can conceal an unresolved responsibility.
The receiving officer also needs a recognisable instruction owner. A forwarded message without a clear origin should trigger the agreed confirmation process, rather than a personal judgement about whether the sender sounds sufficiently senior.
Treat changed work as a new decision
Consider a team admitted for a meeting that is subsequently asked to make a short repair aboard a vessel. Already being inside is not an adequate answer. The request goes to the technical owner, while security applies the current access boundaries communicated through the agreed process. Pressure to save time should not transfer an unresolved technical decision to an individual officer.
The site plan should address where visitors wait, who is notified and how the decision is recorded when the authorised person cannot be reached. Selecting a waiting area or route should not become an engineering judgement left to gate staff.
Add a short control form to the specification
- What is the reference for this visit or work request?
- Which department owns the admission decision?
- Who confirms the technical permit status?
- Who reassesses a change in location, task or timing?
- Are the owner and date of the latest security instruction clear?
- Are completion of the visit and closure of the technical work recorded separately?
Before mobilisation, the yard operator and security provider should test the form together using an ordinary visit and a changed-work scenario. The purpose is to establish what each approval means, without assigning technical authority to a security record that was never intended to carry it.