Playbooks
Playbooks are reusable port call templates. Define a standard set of service orders once, then apply the playbook to any new port call to pre-populate all orders with a single click. They eliminate repetitive setup and ensure consistency across recurring call types.
On this page
When to use playbooks
Playbooks are most valuable when your agency handles recurring call types. Examples:
- Container ship at Rotterdam — always requires pilotage, towage, mooring, customs clearance, and provisions.
- Tanker at Fujairah — bunkering, tank inspection, cargo survey, and STS operations.
- Cruise ship at Copenhagen — immigration, waste disposal, water supply, and shore excursion logistics.
Creating a playbook
- Navigate to Agency → Playbooks and click New Playbook.
- Give the playbook a descriptive name (e.g., "Container Call — Rotterdam").
- Add service order templates. For each template, specify:
- Service type (Pilotage, Bunkering, etc.)
- Default vendor (optional — can be assigned at application time)
- Relative timing offset (e.g., "ETA - 2 hours")
- Priority level and special instructions
- Click Save Playbook. It is now available for all agents in your organization.
Clone existing
Duplicate a playbook and modify it for a different port or vessel type.
One-click apply
Apply a playbook when creating a port call to auto-generate all service orders.
Override defaults
After applying, you can still edit individual orders — the playbook is a starting point.
Applying a playbook to a port call
- Create a new port call from Operations → New Port Call.
- In the creation form, select a playbook from the Apply Playbook dropdown.
- All template orders are generated instantly, with timing offsets calculated from the port call ETA.
- Review and adjust individual orders as needed — change vendors, modify timing, or remove orders that don't apply.
Editing and versioning
Editing a playbook does not retroactively change port calls that have already used it. Each application is a snapshot — the generated service orders become independent entities after creation.
This means you can safely update a playbook at any time without worrying about breaking existing port calls.
Best practices
- Name by call type + port — makes it easy to find the right template quickly.
- Leave default vendor blank for services where you rotate providers — assign at application time.
- Use relative timing (e.g., "ETA + 1h") instead of absolute times so the playbook works for any arrival schedule.
- Review quarterly — remove outdated service types and add new ones as your operations evolve.
Was this page helpful?