Declaration of Security Completion Form
Declaration of Security Completion Form for recording ship-port interface security measures, responsible parties, and sign-off in one place. Use it to document what was agreed, who owns each action, and when the declaration was completed.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Maritime Shipping · Port Operations · Terminal Security · Marine Logistics
Overview
This Declaration of Security Completion Form template records the security agreement between a ship and a port facility for a specific interface. It is built to capture the vessel and port identifiers, interface date and times, applicable ship and port security levels, the measures agreed by both parties, the owner of each measure, and the final signatures that confirm completion.
Use this template when a ship-port interface requires a formal security declaration, when security levels change, or when you need a clear record of who accepted which responsibilities. It is especially useful for port calls where access control, screening, restricted areas, patrols, or communications procedures must be documented in one place. The form also supports an audit trail by tying the agreement to named contacts and a signature datetime.
Do not use this as a general incident report or a broad port operations checklist. If you only need a simple arrival log, this form is more detailed than necessary. It is also not the right template if you do not need to record security measures or sign-off between two parties. Keep the fields focused on the specific interface, use conditional logic where possible, and avoid collecting unrelated PII beyond what is needed to complete the declaration.
Standards & compliance context
- This template supports an audit trail by documenting the parties, measures, and sign-off for a specific ship-port security interface.
- Keep data collection aligned with GDPR Article 5 data minimization by collecting only the identifiers and contacts needed to complete the declaration.
- If the form is used in a regulated maritime workflow, preserve the completed record according to your retention and review procedures.
- Use clear consent or acknowledgment language in the submission notice so signers understand what they are confirming and why the data is collected.
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 sets the purpose of the submission and confirms that the signer understands the declaration is being recorded for a specific security interface.
- Purpose of submission
- I confirm the information provided is accurate and may be retained for compliance and audit trail purposes.
Vessel and Port Identification
This section ties the declaration to the correct ship, facility, location, and time window so the record can be matched to the actual interface.
- Vessel name
-
IMO number
Enter the vessel’s IMO number if available.
- Port facility name
- Port location
- Date of ship-port interface
- Interface start time
- Interface end time
Security Levels and Applicable Measures
This section documents the security posture and the exact measures agreed, which is the core of the declaration.
- Ship security level
- Port facility security level
- Agreed security measures
- Other security measures
- Primary party responsible for implementation
Responsible Parties and Contacts
This section identifies who is accountable and how the ship and port teams can reach each other during the interface.
- Ship security officer name
- Port security officer name
- Ship contact phone
- Port contact phone
- Primary contact email
Declaration and Sign-off
This section provides the formal confirmation that both parties reviewed the details and accepted the recorded security arrangement.
- Declaration statement
- Ship authorized signature
- Port authorized signature
- Date and time of completion
How to use this template
- 1. Enter the vessel and port identification details, including the vessel name, IMO number, port facility name, location, and the interface date and times.
- 2. Record the applicable ship and port security levels, then select or describe only the security measures that apply to this specific interface.
- 3. Assign an owner to each agreed measure so the ship and port sides know who is responsible for carrying it out or verifying it.
- 4. Add the ship security officer, port security officer, and working contact details so the parties can resolve issues during the interface.
- 5. Review the declaration statement, confirm the details with both parties, and capture the ship and port authorized signatures with the signature datetime.
Best practices
- Use date and time fields for the interface window so the record is precise and easy to audit.
- Keep the security measures section specific to the actual call and avoid vague phrases like "as required" without naming the action.
- Use conditional logic to show extra fields only when a higher security level or special measure applies.
- Mark only the truly required fields as required and leave optional fields available for exceptions or local practice.
- Assign one clear owner to each measure so accountability does not get lost between ship and port teams.
- Capture the declaration and signatures as close to the interface as possible to reduce later disputes about what was agreed.
- Limit contact fields to the minimum necessary for operational follow-up and avoid collecting unrelated personal data.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this Declaration of Security Completion Form used for?
This form records the security arrangements agreed between a ship and a port facility for a specific interface. It captures the vessel and port identifiers, applicable security levels, agreed measures, responsible contacts, and final signatures. Use it when you need a clear audit trail of what was agreed before or during the ship-port interface.
When should this form be completed?
Complete it before the interface begins whenever possible, or as soon as the security measures are agreed and confirmed. If the security level changes during the call, update the form to reflect the revised measures and sign-off. It should not be treated as a generic after-the-fact note if the agreement is meant to govern active operations.
Who should fill out and sign the form?
The ship security officer and the port facility security officer are the primary parties to complete and sign it. In some workflows, a designated operations contact may help enter the details, but the responsible security parties should verify the content before sign-off. The form should make it clear who owns each agreed measure.
What information is essential and what should be left out?
At minimum, include the vessel name, IMO number, port facility name, interface date and times, security levels, agreed measures, and the names and contacts of the responsible parties. Keep the form focused on what is needed to document the security arrangement and avoid collecting unrelated PII. If your process does not require a field, leave it optional or remove it.
How does this template help with compliance and audit trails?
The form creates a dated record of the security agreement and sign-off, which supports internal review and external audit readiness. It also helps show that the parties aligned on responsibilities and measures for the specific interface. Keep the completed form with your operational records so it can be retrieved if questions arise later.
Can I customize the security measures section for my port or vessel type?
Yes. The security measures section is intended to be adapted to your operating procedures, local requirements, and the actual interface conditions. Use conditional logic or a multi-select list if you want to standardize common measures, and keep an open text field for unusual or site-specific actions.
What are common mistakes when using this form?
Common mistakes include leaving the security level fields blank, using vague wording for agreed measures, and failing to name the owner for each action. Another frequent issue is collecting extra personal data that is not needed for the interface record. The form works best when each field is specific, required fields are limited to essentials, and the sign-off is completed immediately.
How is this better than tracking security agreements by email or ad hoc notes?
Email threads are easy to lose, hard to compare, and often leave gaps in accountability. This template gives you a consistent structure for the same data every time, which makes review, handoff, and retrieval much easier. It also reduces the chance that a critical measure was discussed but never formally recorded.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
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 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...
-
Learn how to run a successful business with remote employees using proven strategies to boost autonomy, productivity, and engagement.
-
Transform business with AI strategies that automate work, boost productivity, and help teams stay competitive faster.
-
See how MangoApps Online Forms digitizes company paperwork—automated workflows, secure data tracking, and mobile access for every employee, including...
-
See how bank branch managers use MangoApps scheduling to fill shifts, communicate policy updates, and eliminate last-minute coverage chaos.
Ready to use this template?
Get started with MangoApps and use Declaration of Security Completion Form with your team — pricing built for small business.
