Cruise Ship MLC Drug and Alcohol Testing Consent Form
A cruise ship MLC drug and alcohol testing consent form for crew members to acknowledge testing rules, authorize specific test types, and record consent or refusal before collection.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Cruise Lines · Maritime Operations · Ship Management · Hospitality At Sea
Overview
This template is a crew consent form for cruise ship drug and alcohol testing programs governed by the Maritime Labour Convention and related flag state requirements. It captures the crew member’s identity, the basis for testing, the specific test types authorized, and a signed acknowledgment of the disclosure and refusal language.
Use it when you need a clear record that a crew member was informed about testing before collection, especially for pre-employment, random, post-incident, or reasonable-suspicion events. The structure supports progressive disclosure so you can show only the test basis and instructions that apply to the current situation, rather than presenting every possible scenario at once. It also helps create an audit trail by tying the consent to a named vessel, department, and date.
Do not use this as a general medical intake form or as a substitute for a full company drug and alcohol policy. It is not the right template if you are collecting clinical history, fitness-for-duty details, or broad health information that is not needed for the test authorization. Keep the form narrow, use required fields only where necessary, and include a clear statement of what happens after submission so crew members understand whether they will be directed to testing, reviewed by compliance, or routed for refusal handling.
Standards & compliance context
- Limit collection to the crew identity, test basis, and consent details needed for the testing program, consistent with GDPR Article 5 data minimization.
- If the form is used for safety-sensitive roles or incident follow-up, keep the wording aligned with the applicable Maritime Labour Convention and flag state rules.
- Use clear disclosure language for any PII collected and avoid adding unrelated health questions that are not necessary for the authorization.
- Preserve the signed record as part of the audit trail so you can show when consent or refusal was captured and which vessel or department it applied to.
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
Program Notice
This section explains why the form is being presented and sets expectations before the crew member reviews any personal fields.
- Testing Program Notice
- What happens after I submit?
- I have read and understand the testing program notice above.
Crew Member Information
These fields identify the correct person, vessel, and department so the consent record can be matched to the right assignment.
- Full Name
- Crew / Employee ID
- Job Title / Rank
- Vessel Name
- Department
Testing Authorization
This section defines the exact reason for testing and prevents the form from becoming a vague blanket authorization.
- Reason for Testing
- Testing Types Authorized
-
Additional Details for Reasonable Suspicion or Post-Incident Testing
Use this field only if the testing basis requires a brief explanation for the record.
Consent, Disclosure, and Refusal
This section records the crew member’s decision and the privacy acknowledgment that makes the authorization usable.
- Consent Statement
- I understand that my personal information will be used only for testing administration, compliance, and audit trail purposes.
- I understand that refusal to consent may result in removal from testing eligibility, delay in assignment, or other action permitted by law and policy.
- Signature
- Date
How to use this template
- 1. Set the program notice text to match your cruise line policy, flag state requirements, and the specific test event so the crew member sees why the form is being presented.
- 2. Configure the crew member information fields as required only where needed, using the correct field types for names, IDs, vessel selection, and department selection.
- 3. Use conditional logic in the testing authorization section to show only the relevant test basis and test types for pre-employment, random, post-incident, or other approved scenarios.
- 4. Add the consent, disclosure, and refusal language so the submission records either an explicit authorization or a documented refusal with an audit trail.
- 5. Route completed submissions to the designated HR, crewing, medical, or compliance reviewer and confirm the next step in the what-happens-after-submit message.
- 6. Review the signed record after submission, resolve missing fields or mismatched vessel details, and file the form with the related incident, onboarding, or testing record.
Best practices
- Mark only the fields you truly need as required, and keep optional fields optional so the form stays aligned with data minimization.
- Use a date picker for the consent date and structured choice fields for test basis and test types instead of free-text entry.
- Show conditional testing details only when the selected basis requires them, so crew members are not forced to read irrelevant policy language.
- Include a plain-language what-happens-after-submit line that explains whether the form triggers testing, review, or refusal escalation.
- Keep the disclosure acknowledgment specific to the data you collect and who will see it, rather than using broad, vague privacy language.
- Provide a refusal path that records the refusal without blocking submission, so the audit trail remains complete.
- Match vessel name and department to controlled lists where possible to reduce spelling errors and improve downstream routing.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
When should this consent form be used?
Use it before any drug or alcohol test that falls under your vessel’s MLC policy or flag state requirements, including pre-employment, random, reasonable suspicion, post-incident, or return-to-duty testing. It is meant to document that the crew member received notice and either consented or refused under the program rules. If your process already requires a separate medical authorization, keep this form focused on testing consent and disclosure acknowledgment.
Does this form apply to all crew members or only certain roles?
It should be used only for crew members covered by the testing program you have defined, such as safety-sensitive roles or positions subject to flag state testing rules. The template includes job title, vessel name, and department so you can scope the authorization to the correct person and assignment. If your policy differs by rank, vessel, or contract type, use conditional logic to show only the relevant fields and instructions.
How often should this form be completed?
Complete it whenever a new testing event requires fresh acknowledgment, such as a pre-employment screen, a random selection, or a post-incident test. Many operators also use a version at onboarding to document standing consent language for future testing, but the actual test basis should still be captured for each event. If your policy changes, update the form and reissue it so the crew member is signing the current terms.
Who should collect and review the form?
A designated HR, crewing, medical, or compliance representative should collect the form, verify the crew member’s identity, and confirm the test basis before the sample is taken. The reviewer should also check that required fields are complete and that any refusal is documented according to company policy. Keep the approval path clear so the form creates an audit trail rather than an informal note.
What privacy or data-minimization issues should I watch for?
Collect only the fields needed to identify the crew member, explain the testing basis, and document consent or refusal. Avoid adding unnecessary PII, health history, or free-text comments that are not required for the program, in line with GDPR data minimization and the minimum-necessary principle. If you collect any sensitive information, include a clear disclosure about who can access it and why.
What happens if a crew member refuses to sign?
The form should include a refusal acknowledgment so the refusal is recorded without forcing a signature. Your workflow can then route the case to the appropriate supervisor, crewing manager, or compliance lead for next steps under company policy and flag state rules. Do not leave the refusal as an empty form, because that creates gaps in the audit trail.
Can this form be customized for different test types or vessels?
Yes, and it should be. Use conditional logic to show pre-employment, random, post-incident, or reasonable-suspicion language only when relevant, and add vessel-specific or department-specific instructions where needed. You can also tailor the consent text to match your flag state, collective agreement, or provider workflow without changing the core structure.
How does this fit with other systems like HR or case management tools?
This template works well when linked to crew onboarding, incident reporting, or compliance case records. You can map the crew member fields to your HR system, send the submission to a compliance queue, and store the signed record as part of the audit trail. If you use integrations, make sure the downstream system only receives the fields it needs.
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...
-
See how connected 1:1 tracking, employee audit history, and LMS completion records turn scattered processes into verifiable workforce documentation.
-
See how bank branch managers use MangoApps scheduling to fill shifts, communicate policy updates, and eliminate last-minute coverage chaos.
-
Learn how AI-driven workflows close compliance gaps in hiring, field inspections, and compensation — before they become audit findings.
-
MangoApps Shifts & Schedules unifies frontline scheduling, time, and leave management in one native platform for faster, simpler operations.
Ready to use this template?
Get started with MangoApps and use Cruise Ship MLC Drug and Alcohol Testing Consent Form with your team — pricing built for small business.
