Cruise Ship Shore Excursion Tender Operations SOP
Cruise Ship Shore Excursion Tender Operations SOP template for managing passenger ticketing, boarding sequence, count verification, weather go/no-go checks, and last tender return communication.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Cruise Lines · Maritime Operations · Port Services · Hospitality
Overview
This SOP template covers the controlled workflow for cruise ship shore excursion tender operations. It starts with confirming operational readiness, then moves through passenger list validation, ticket issuance, boarding sequence communication, controlled boarding, passenger count verification, and the final weather-based go/no-go decision. The template is designed to produce a clear, auditable sequence that reduces confusion at the tender platform and gives each role a defined action and verification point.
Use this template when your ship is transferring excursion passengers by tender and you need a repeatable process for managing access, sequencing, and departure control. It is especially useful when multiple departments are involved, when passenger volumes are high, or when weather and sea-state conditions can change during the call. The structure also supports last tender return communication so guests and staff have the same expectation for timing.
Do not use this template as a substitute for local maritime law, port authority instructions, or ship-specific emergency procedures. It is not the right fit for situations where tendering is suspended entirely, where evacuation procedures apply, or where the operation is being handled by a third-party provider under a separate control process. If your operation has unique capacity limits, accessibility requirements, or security screening rules, those should be inserted into the relevant steps before use.
Standards & compliance context
- The template supports ISO 9001-style control of documented information by defining a repeatable procedure, role ownership, and recordable verification points.
- The count checks, controlled boarding, and escalation steps align with general maritime safety management expectations and help demonstrate operational control.
- Weather-based stop criteria and boarding-area controls support risk-based decision making consistent with shipboard safety procedures and port authority direction.
- If your organization uses formal safety management or quality systems, this SOP can be attached as controlled documented information with revision tracking and approval.
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
Steps
-
The deck officer verifies tender operating conditions and readiness
Confirm that weather, sea state, visibility, port instructions, and vessel maneuvering conditions are within the approved operating tolerance before any passengers are called to the embarkation area.
-
The tender coordinator reconciles the passenger manifest and excursion roster
Compare the active passenger list against the approved excursion roster and identify any missing, duplicate, or unauthorized names before ticketing begins.
-
The guest services team issues tender tickets only to authorized passengers
Issue a tender ticket or digital boarding authorization only after the passenger has been verified against the approved roster.
-
The tender coordinator communicates the boarding sequence and last tender return time
Announce the boarding order, any priority groups, and the exact last tender return time using the approved communications channel.
-
The deck officer controls the boarding area and confirms it is safe
Keep passengers behind the marked line, maintain clear access to the gangway, and verify that the embarkation area is free of slip, trip, and crush hazards before boarding is opened.
-
The tender coordinator boards passengers in the approved sequence
Board passengers in the assigned order and stop immediately if the sequence is disrupted, capacity is approached, or an unauthorized passenger attempts to board.
-
The tender marshal verifies the passenger count before departure
Count all boarded passengers and reconcile the total against the approved manifest before the tender is released from the embarkation point.
-
The bridge or designated authority evaluates weather changes and decides whether to continue
Review current wind, swell, lightning, visibility, and docking conditions and issue a clear go, delay, suspend, or recall decision before the next rotation begins.
-
The tender coordinator authorizes the next tender run
Release the next tender only after the prior verification steps are complete and the go decision has been confirmed by the designated authority.
-
The responsible officer escalates the non-conformance and suspends tender movement
Log the deviation, notify the master or designated authority, and keep the tender paused until the unsafe condition is resolved or the operation is formally suspended.
-
The tender coordinator verifies the return passenger count at last tender
Perform a final headcount, reconcile all returning passengers against the manifest, and confirm no one remains unaccounted for before the gangway is secured.
How to use this template
- 1. The operations lead copies the template, fills in the port name, tender capacity, last return time, and any local boarding restrictions, and removes any steps that do not apply to the voyage.
- 2. The tender coordinator assigns each role named in the SOP, confirms who owns passenger list control, count verification, and weather escalation, and records the backup contact for each role.
- 3. The guest services team and tender coordinator verify the excursion roster against the passenger manifest, issue tickets only to authorized passengers, and flag any mismatch as a non-conformance before boarding starts.
- 4. The deck officer and tender marshal run the boarding sequence exactly as written, control the boarding area, verify the passenger count before departure, and stop the process if the count, weather, or safety conditions fall outside tolerance.
- 5. After each rotation, the team reviews deviations, updates the last tender return communication if conditions change, and records any escalation, delay, or suspension decision for the voyage log.
Best practices
- Keep the passenger roster, ticket issue list, and boarding count in the same control point so staff are not reconciling three different sources at departure time.
- State the last tender return time in the same format every time and repeat it through guest services, the boarding area, and shipboard announcements.
- Require the tender marshal to stop boarding immediately when the count does not match, rather than trying to correct the mismatch after departure.
- Define the weather or sea-state tolerance in operational terms that the bridge and tender coordinator can apply consistently, not as a vague judgment call.
- Use one named role for the final go/no-go decision so there is no ambiguity when conditions change during the rotation.
- Document every deviation, delay, and passenger exception at the time it occurs so the next rotation starts with an accurate record.
- Train guest services to issue tickets only after roster verification, because premature ticketing is a common source of boarding disputes.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this SOP cover?
This SOP covers the day-of tender operation for cruise shore excursions, from confirming readiness and issuing tender tickets to boarding passengers, verifying counts, and communicating the last tender return time. It also includes the go/no-go decision point for weather or sea-state changes. Use it as the working procedure for controlled passenger movement between ship and tender.
Who should run this procedure?
The tender coordinator typically owns the workflow, with support from guest services, the deck officer, the tender marshal, and the bridge or designated authority. Each role should have a clear step, a verification point, and an escalation path. The SOP is most effective when one person is accountable for the final boarding decision and passenger count reconciliation.
How often is this SOP used?
It is used every time shore excursion tendering is conducted, including the first departure, intermediate rotations, and the final return. The same structure can be reused across ports, but the weather checks, local restrictions, and boarding sequence may change by call. If conditions change mid-operation, the SOP should be re-run from the decision point rather than assumed to remain valid.
How does this relate to safety and regulatory expectations?
The template supports documented information practices consistent with ISO 9001-style control of procedures and records, and it reinforces operational verification, escalation, and non-conformance handling. It also helps organize safety-critical checks such as controlled boarding areas, passenger counts, and weather-based stop decisions. If your operation uses local maritime procedures, port rules, or company safety management requirements, this SOP can be aligned to those controls.
What are the most common mistakes this SOP helps prevent?
Common failures include issuing tickets before the passenger roster is confirmed, boarding out of sequence, skipping the final count check, and failing to communicate the last tender return time clearly. Another frequent issue is continuing operations after weather or sea-state conditions have shifted beyond tolerance. The SOP makes those decision points explicit so deviations are visible and can be escalated.
Can this template be customized for different ports or ship sizes?
Yes. You can adapt the passenger thresholds, tender capacity limits, boarding area controls, local port restrictions, and weather tolerance criteria for each itinerary. Larger ships may need additional roles or a more formal queue control step, while smaller operations may combine responsibilities. Keep the verification steps intact even when the local details change.
How does this compare with ad-hoc tender boarding?
Ad-hoc boarding relies on memory and verbal coordination, which increases the chance of missed counts, unclear passenger priority, and inconsistent last-call communication. A written SOP creates a repeatable sequence, assigns ownership, and records the decision points that matter when conditions change. That makes it easier to train new staff and to review incidents or near misses later.
What should be integrated with this SOP?
This procedure works best when linked to the excursion manifest, passenger ticketing records, shipboard communication channels, and any weather monitoring or bridge reporting process. If your operation uses digital checklists or a runbook system, the count verification and go/no-go decision can be captured as required fields. That reduces gaps between the boarding area, guest services, and the bridge.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Overtime calculation is the process of applying federal, state, local, and contractual rules to hours worked to determine the correct pay — including...
-
Predictive scheduling laws — also called fair workweek laws or secure scheduling — require employers in covered industries to publish employee schedules...
-
Geofencing defines a virtual geographic boundary — a "fence" — around a work location. When an employee's mobile device enters or exits the fence, the...
-
Learn how organizations with hourly workers, union contracts, and shift differentials can apply compensation rules consistently and accurately at scale.
-
Interdisciplinary collaboration strategies for large health systems that improve care coordination, reduce errors, and boost team efficiency.
-
See how automated credential checks, labor rules, and real-time coverage tracking give charge nurses a schedule they can trust before every shift.
-
Learn how task management and real-time collaboration tools create an efficient business workflow — keeping teams connected, accountable, and productive.
Ready to use this template?
Get started with MangoApps and use Cruise Ship Shore Excursion Tender Operations SOP with your team — pricing built for small business.
