Skip to content
Back to skills

Port Operations Follow Up Maintenance

ASecurity

Plan follow-up and maintenance so gains for shipping lines, hauliers and cargo owners are checked and sustained. TRIGGERS - Use when a port operations manager needs a follow-up & maintenance schedule for shipping lines, hauliers and cargo owners in ports and container terminals.

  • 38 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 12, 2026
toolsgorailsdocumentation

Works with

  • terminal
  • cli

Security analysis

A100/100

Scanned November 12, 2026

npx -y skills add lionelsimai/claude-skills-collection --skill port-operations-follow-up-maintenance --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Port Operations Follow Up Maintenance?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Port Operations Follow Up Maintenance
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lionelsimai-port-operations-follow-up-maintenance/badge)](https://www.skillsdirectory.com/skills/lionelsimai-port-operations-follow-up-maintenance)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: port-operations-follow-up-maintenance
description: |
  Plan follow-up and maintenance so gains for shipping lines, hauliers and cargo owners are checked and sustained.
  TRIGGERS - Use when a port operations manager needs a follow-up & maintenance schedule for shipping lines, hauliers and cargo owners in ports and container terminals.
category: Port Operations
license: MIT
version: 1.0
---
# Follow-Up & Maintenance Schedule — Port Operations

Plan follow-up and maintenance so gains for shipping lines, hauliers and cargo owners are checked and sustained. The deliverable is a follow-up schedule with intervals, checks and escalation triggers.
This skill is written for a port operations manager working with shipping lines, hauliers and cargo owners in ports and container terminals.

## When to use
- You are a port operations manager preparing, delivering or reviewing this part of your work in ports and container terminals.
- You need a defensible, repeatable approach that produces a follow-up schedule with intervals, checks and escalation triggers.
- A colleague, auditor or client asks how this was done and what evidence supports it.

## Key Concepts
| Term | Meaning |
|------|---------|
| Berth | the place where a vessel moors to load or unload |
| TEU | a standard unit equal to a twenty-foot container |
| Turnaround | the time a vessel or truck spends in port |

## Workflow
1. **Step 1** - Set follow-up intervals from the plan and from how berth utilisation is expected to move over time
2. **Step 2** - Define what is checked at each contact, using terminal operating systems where measurement is needed, and record it in berth plans
3. **Step 3** - Give shipping lines, hauliers and cargo owners clear guidance for the interval: what to do, what to watch for, when to make contact sooner
4. **Step 4** - Act early on warning signs — deterioration linked to crane accidents shortens the interval, never lengthens it
5. **Step 5** - Close the follow-up cycle formally when goals are met, with a summary and re-entry route if needs return

## Profession-Specific Components
| Component | Details for Port Operations |
|-----------|-------------------------------|
| Core documentation | berth plans; cargo manifests; equipment logs; incident reports |
| Core tools & equipment | terminal operating systems; cranes; handling equipment; gate systems |
| People involved | shipping lines, hauliers and cargo owners; the port operations manager; colleagues and other services in ports and container terminals |
| Primary record | berth plans — keep it current, dated and attributable |

## Output Format
**Context:** [Situation in ports and container terminals] | **Objective:** [What this must achieve] | **Audience:** [shipping lines, hauliers and cargo owners and other stakeholders]

The finished output is a follow-up schedule with intervals, checks and escalation triggers, structured as:
1. Summary of position and evidence
2. Detail, following the workflow above
3. Decisions, actions, owners and dates
4. Review point and escalation route

### Action Plan
1. **Immediate:** Confirm scope, consent and the evidence available in berth plans.
2. **Short-term:** Complete the workflow steps and record outcomes against berth utilisation.
3. **Medium-term:** Review results, close actions, and update local procedures in ports and container terminals.

## Success Metrics
| Metric | Target | Method |
|--------|--------|--------|
| berth utilisation | Agree a local target and track the trend | Measured from berth plans and reviewed on a set cycle |
| container turnaround | Agree a local target and track the trend | Measured from berth plans and reviewed on a set cycle |
| crane productivity | Agree a local target and track the trend | Measured from berth plans and reviewed on a set cycle |
| safety incident rates | Agree a local target and track the trend | Measured from berth plans and reviewed on a set cycle |

## Guardrails & Quality Checks
- Never let this happen: crane accidents.
- Never let this happen: cargo damage.
- Never let this happen: berth congestion.
- Work only within the competence and authority of a port operations manager; escalate or refer anything beyond it.
- Record facts and observations, not speculation, and keep records confidential to ports and container terminals's rules.
- Verify names, dates, figures and measurements twice before anything is issued or signed off.
- Use only real, verified information from the case in hand — never invent results, credentials or evidence.

## Example (illustrative)
A port operations manager in ports and container terminals applies this workflow for shipping lines, hauliers and cargo owners: they open
berth plans, work through the five steps using terminal operating systems, and close by recording
the outcome against berth utilisation and agreeing the next review date. (Illustrative example only —
replace with the real details of the case in hand.)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in tools →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.