Loading...
compliance

Declaration of Security Completion Form

A Declaration of Security Completion Form for recording ship-port security measures, responsible parties, and the effective period of the agreement. Use it to document the ship-port interface clearly and keep a traceable record of what was agreed.

Fill it now — Free Get Started
Customize with AI →

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Maritime Shipping · Port Operations · Logistics And Freight · Terminal Security

Overview

This Declaration of Security Completion Form records the agreed security measures between a vessel and a port facility for a specific ship-port interface. It captures the submitter, vessel and port details, security levels on both sides, the effective period, the measures agreed for access control, cargo handling, and communications, plus the responsible parties who confirm the record.

Use this template when a security agreement needs to be documented clearly and kept available for later review, especially when the ship and port are operating under defined security levels or temporary measures. It is useful for planned arrivals, cargo operations, and any situation where both sides need a shared record of what was agreed and when it took effect. The form also helps create an audit trail by tying the submission to named roles and a submission acknowledgment.

Do not use it as a broad incident report or a general port operations log. If the situation does not require a formal ship-port security agreement, this template may be more detailed than necessary. Keep the fields focused on the minimum necessary information, and avoid adding unrelated PII or narrative notes that do not support the security record. The best version of this form is one that is easy to complete, easy to review, and specific enough to show exactly what was in force during the effective period.

Standards & compliance context

  • The form supports an audit trail by documenting who submitted the record, who accepted responsibility, and when the agreement became effective.
  • Use data minimization principles by collecting only the vessel, port, security, and sign-off details needed for the ship-port security record.
  • If the template is adapted for public-facing or shared access, make labels and validation accessible in line with WCAG 2.1 AA.
  • Where role-based sign-off is required, keep the responsible party fields explicit so accountability is clear during review.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Submission Notice

This section captures who is submitting the record and whether they consent to recording the information.

  • Submitter Name (required)

    Name of the person completing this form.

  • Submitter Role (required)
  • I confirm the information provided is accurate and may be retained for compliance and audit trail purposes. (required)

Vessel and Port Details

This section identifies the exact ship-port interface so the security agreement can be matched to the right call.

  • Vessel Name (required)
  • IMO Number

    Enter only if needed for your compliance record.

  • Port Facility Name (required)
  • Port Location (required)
  • Declaration of Security Reference Number

    Use if your organization assigns a DoS reference number.

Security Level and Effective Period

This section defines the security context and the time window during which the agreement applies.

  • Ship Security Level (required)
  • Port Facility Security Level (required)
  • Effective Date (required)
  • Effective Time (required)
  • Expected End Date

Agreed Security Measures

This section records the specific controls both sides agreed to implement for access, cargo, and communications.

  • Access Control Measures (required)
  • Cargo and Ship's Stores Controls (required)
  • Communication Procedures (required)
  • Additional Security Measures

    Describe any additional measures not covered above.

Responsibility and Sign-off

This section confirms who is accountable for the agreement and creates the final submission acknowledgment.

  • Primary Responsible Party (required)
  • Ship Security Officer Name
  • Port Facility Security Officer Name
  • Signature Confirmation (required)

    Provide an electronic signature or equivalent authorization.

  • I confirm this Declaration of Security has been completed and the agreed measures are in effect. (required)

How to use this template

  1. 1. Set up the form with required fields for the submitter, vessel, port facility, security levels, effective period, agreed measures, and sign-off so the record is complete without extra back-and-forth.
  2. 2. Assign the form to the person coordinating the ship-port security record and make the ship security officer and port security officer the named reviewers or signers.
  3. 3. Enter the vessel and port details exactly as they appear in operational records, using structured fields such as date picker, time field, and reference number input where appropriate.
  4. 4. Capture the agreed security measures with conditional logic or progressive disclosure so users only see the controls that apply to the current interface.
  5. 5. Review the submission acknowledgment and signature confirmation before submission, then store the completed record in a location that supports retrieval and audit trail review.

Best practices

  • Mark required fields clearly and keep optional fields limited to details that support the security record.
  • Use structured field types for dates, times, and reference numbers instead of free text.
  • Keep the agreed measures section specific by naming the control, the owner, and the operational context.
  • Use conditional logic to hide measures that do not apply to the current vessel, port, or security level.
  • Record the effective end date so the form does not imply that temporary measures remain active indefinitely.
  • Include a clear submission acknowledgment that tells the user what happens after they submit.
  • Avoid collecting unnecessary PII or unrelated operational notes that do not help verify the agreement.

What this template typically catches

Issues teams running this template most often surface in practice:

Security levels are entered inconsistently between the ship and port fields, making the agreement hard to interpret.
The effective date or time is missing, which leaves the record without a clear start point.
Agreed measures are written too broadly, so it is unclear which controls actually apply.
The responsible party is named, but the ship security officer and port security officer fields are left blank.
The form collects extra narrative details that do not support the security record and create unnecessary PII exposure.
Submission acknowledgment is missing, so the user cannot tell whether the record was successfully captured.

Common use cases

Port Security Coordinator
A port security coordinator uses the form to document the agreed controls before a vessel is granted access to restricted areas. The completed record gives operations and security teams a shared reference for the active measures.
Ship Security Officer
A ship security officer completes the form during arrival planning to confirm the vessel's security level and the measures that will apply at berth. This helps prevent confusion when multiple teams are coordinating the interface.
Terminal Operations Manager
A terminal operations manager uses the template to align cargo handling controls with the current security arrangement. The form keeps the operational steps tied to the approved security agreement.
Compliance and Audit Review
A compliance reviewer checks the completed form to verify that the ship-port agreement was documented, signed, and stored with a clear audit trail. The structured fields make it easier to compare records across calls.

Frequently asked questions

When should this Declaration of Security Completion Form be used?

Use it when a ship and a port facility need to document agreed security measures for a specific interface, security level, or operating period. It is especially useful when responsibilities must be clear before access, cargo handling, or communications begin. If no formal ship-port security agreement is needed, a lighter operational checklist may be enough.

Who should complete and sign this form?

The form is typically completed by the person coordinating the submission and signed off by the ship security officer and port security officer, or the designated responsible parties. The submitter can be an admin, operations lead, or security coordinator, but the sign-off should come from the people accountable for the measures. Keep the responsible party field explicit so the audit trail is clear.

How often should a Declaration of Security be completed?

It is usually completed for a specific ship-port interface and effective period, not as a one-time blanket record. Reuse only when the security level, vessel, port facility, and agreed measures still match the current situation. If any of those change, create a new submission rather than editing the old record without a trace.

What information should be included, and what should be left out?

Include only the fields needed to identify the vessel, port facility, security levels, effective period, and agreed measures. Follow GDPR data minimization and avoid collecting unnecessary PII or unrelated operational details. If a field does not support the security record or later verification, leave it out or make it optional.

How does this template support compliance and audit trail needs?

The template creates a structured record of who agreed to what, when it became effective, and which security measures were in place. That makes it easier to review decisions later and show an audit trail during internal checks or external inspections. The submission acknowledgment and signature confirmation fields help prove the record was completed intentionally.

What are the most common mistakes when using this form?

Common mistakes include leaving security levels blank, using free text where a date picker or structured field would be clearer, and omitting the effective end date. Another frequent issue is listing too many measures without distinguishing required actions from optional ones. The form works best when each field is specific and the agreed measures are written in plain operational language.

Can this template be customized for different ports or vessel types?

Yes. You can add conditional logic for vessel class, port facility rules, or local security procedures so users only see the fields that apply. You can also rename the measures section to match your internal terminology while keeping the core ship-port details intact.

Can this be integrated with other systems or workflows?

Yes. It can be connected to document storage, incident management, or compliance workflows so the completed record is routed to the right team. Many teams also link it to approval steps or notifications so the ship and port security officers are alerted when submission is ready for review.

How is this better than handling security completion by email or chat?

Email and chat make it harder to confirm what was agreed, who approved it, and which version is current. This template standardizes the fields, supports a cleaner audit trail, and reduces the risk of missing a required security measure. It also makes review faster because the information is captured in the same order every time.

Related templates

Forms

Declaration of Security Completion Form

Declaration of Security Completion Form for recording ship-port interface security measures, resp...
Forms

Cruise Ship MARPOL Garbage Exception Record Form

Record a MARPOL Annex V garbage exception with the vessel, voyage, waste category, quantity, loca...
Forms

ISM Non-Conformity and Corrective Action Tracking Log

Track ISM non-conformities, corrective actions, evidence, and closeout status in one audit-ready ...
Forms

MARPOL Annex VI Fuel Changeover and Sulphur Compliance Log

Log the fuel changeover, vessel position, and BDN cross-check needed before entering an ECA under...
Forms

Hospice Election and Coordination Form

Hospice Election and Coordination Form template for documenting election details, plan of care, v...
Inspections

ADR Vehicle Equipment and Orange Plate Inspection

Use this ADR Vehicle Equipment and Orange Plate Inspection template to verify dangerous goods veh...
Sop

Ballast Water Exchange Contingency Procedure SOP

This SOP template guides a D-1 sequential or flow-through ballast water exchange when the BWMS fa...
Hr Policy

Anti-Harassment & Anti-Discrimination Policy

Anti-Harassment & Anti-Discrimination Policy template for defining prohibited conduct, reporting ...

Go deeper on the topic

Related concepts
  • Lockout/Tagout
    Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
  • Job Hazard Analysis
    Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
  • Near-Miss Reporting
    A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
  • AI Governance
    AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
Related guides

Ready to use this template?

Get started with MangoApps and use Declaration of Security Completion Form with your team — pricing built for small business.

Get Started
Customize with AI →