Collect feedback from shipping lines, hauliers and cargo owners and handle complaints fairly and visibly.
TRIGGERS - Use when a port operations manager needs a feedback & complaints handling for shipping lines, hauliers and cargo owners in ports and container terminals.
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Is that skill safe to install?
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
Are you the author of Port Operations Feedback Complaints?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/lionelsimai-port-operations-feedback-complaints)
---
name: port-operations-feedback-complaints
description: |
Collect feedback from shipping lines, hauliers and cargo owners and handle complaints fairly and visibly.
TRIGGERS - Use when a port operations manager needs a feedback & complaints handling for shipping lines, hauliers and cargo owners in ports and container terminals.
category: Port Operations
license: MIT
version: 1.0
---
# Feedback & Complaints Handling — Port Operations
Collect feedback from shipping lines, hauliers and cargo owners and handle complaints fairly and visibly. The deliverable is a feedback and complaints process with response standards and learning log.
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 feedback and complaints process with response standards and learning log.
- 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** - Invite feedback routinely — not only when things go wrong — and make it easy to give in ports and container terminals
2. **Step 2** - Acknowledge complaints quickly, thank the person, and explain the process and timeframe honestly
3. **Step 3** - Investigate from evidence in berth plans; separate the facts from the feelings, and respect both
4. **Step 4** - Respond with findings, an apology where warranted, and concrete remedies or explanations
5. **Step 5** - Log themes and feed them into quality work — repeated complaints about crane accidents are an early-warning system, not a nuisance
## 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 feedback and complaints process with response standards and learning log, 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.)