Scenario tracing for the MNZ Skipper Coastal Offshore (SCO) credential is a skill you can build deliberately: read the conditions, decide the governing constraint, state the action, and record why you chose it, using the structure real passage plans and logs follow. This guide teaches that routine across coastal tracing, offshore handovers, documentation, and professional standards of judgement. Work through the two traced scenarios below with paper and a timeline, then use the self-check rubric to see whether your answers separate what is required from what is simply good practice. Administrative details sit with Maritime New Zealand; this guide covers study content only.
Distinguish the three judgments a skipper scenario is really asking for
Every scenario asks you to make a legality call, a seamanship call, and a documentation call, and clarity depends on keeping the three separate in your answer.
Legality is the floor: what the rules forbid or require at that moment. Seamanship is the layer above: what a competent skipper would do given the same conditions. Answers lose clarity when these two are blended into one sentence, because it is then never clear whether the action is mandatory or merely wise. Label both before you write anything.
Practise by labelling. If a scenario shows a vessel approaching a narrow passage in strong tidal flow, first state the governing requirement in one sentence, then state the prudent addition, such as waiting a defined interval for slack water, marked explicitly as a choice rather than an obligation. If you can label each part, a reader of your answer can see both the rule you know and the judgement you exercise, and your documentation sentence then records both.
- One sentence for the governing requirement
- One sentence for the prudent addition, clearly marked as such
- One sentence for what you would record or communicate
Trace a coastal passage hour by hour instead of assessing it once
Coastal scenarios describe changing conditions; a single static assessment taken from the opening lines will not survive the middle of the passage.
A common tracing mistake is reading a scenario's opening conditions and approving the passage on that basis. If the scenario notes a weather change at a stated time, or a tide turning mid-afternoon, the sound answer is a plan that handles both states, not one that assumes the good state holds. Trace the passage on paper in hour blocks: position, weather, tide, traffic, and the decision points that fall in each block.
Worked scenario: a coastal leg of roughly four hours departs late morning in fair conditions, with the scenario noting a southerly change expected mid-afternoon and a tidal stream that runs hardest against the vessel in the final hour. A plausible mistake is to approve departure on the morning conditions alone and treat the forecast as background. The better decision is to state the departure with a defined turnaround point: if the change arrives before the vessel passes a named headland, the plan is to divert into a listed shelter. This matters because the diversion only works if you identify it while it is still available; by the final hour it is no longer an option.
- Hour blocks: position, weather, tide, traffic, decision point
- Mark every point where the plan branches
- Note the last moment each diversion is still available
Offshore watch work: rehearse the handover as a written skill
A handover is a routine that must transfer details reliably; practise it on scenarios where something stated hours earlier must reach the incoming watch.
Handover practice rewards a fixed checklist, because the pivot in a well-built scenario is something stated once, hours before the watch changes, that the handover script itself omits. If you read such a scenario once through, you will drop it too. Instead, read it twice: once for the situation, once hunting for any stated value, position, or instruction that the handover does not mention. That omission is what your answer turns on.
Worked scenario: an offshore leg notes, hours before a watch change, that the vessel is passing a marked obstruction to seaward, and that the autopilot is compensating for weather so the heading differs slightly from the course made good. The handover script mentions course and speed but not the obstruction or the steering method. A plausible mistake is for the incoming watch to accept the handover and steer to the heading shown, which closes on the obstruction. The better decision is a handover that states both the offset heading and the nearest hazard with a clearance distance. The error came from an incomplete routine, not from ignorance; a fixed handover checklist catches exactly this class of omission.
- Course, speed, heading and any autopilot compensation
- Nearest hazard and its clearance
- Anything stated earlier in the voyage that the handover omits
Methods and documentation: write answers the way logs and plans are actually structured
Log and passage-plan entries follow a fixed structure; learn the structure, not the wording, and never mix the two documents together.
Documentation practice rewards answers that look like real records: a time, a position, an action, and a reason. Do not write narrative prose; write entries. Each entry names what happened, when, where the vessel was, what was done, and why. This is also how you self-check: if an entry cannot state a reason, it is an observation rather than a decision, and the scenario probably expects more from you.
A useful comparison: a passage plan answers a question before the voyage, while a log entry records a decision during it. Both use times and positions, but the plan lists intended actions with contingency branches, and the log records what was done with the reasoning. Mixing the two, for example writing 'will monitor weather' inside a log entry, signals confusion. Practise converting one scenario into both documents; the differences become obvious and easy to reproduce under exam conditions.
| Document | Written when | Contains | Typical practice task |
|---|---|---|---|
| Passage plan | Before departure | Intended route, times, contingencies, decision points | Identify branches and abort points |
| Log entry | During the voyage | What happened, when, position, action taken, reason | Record a decision with justification |
| Handover record | At watch change | Course, heading, hazards, instructions to next watch | Spot the omitted item |
Professional standards in marginal scenarios: name the pressure, then decide
Standards questions ask what a responsible skipper owes the crew and vessel, which goes beyond rule compliance and beyond external schedule pressure.
Treat fitness to proceed as a decision with stated inputs, not a feeling. In a paper scenario where the skipper has already been on passage for a long stretch, the crew is tired, and conditions are marginal, the prudent decision may be to delay or shorten the leg. Write it as a decision with a reason: name the cumulative fatigue, the weather trend, and the review time at which you would reassess. An answer that simply says 'proceed with caution' shows neither judgement nor a standard.
Distinguish duty to the crew from convenience or outside expectation. Build this into your practice deliberately: use scenarios that include a schedule pressure, such as a berth booking or an appointment ashore. In your written answer, name that pressure explicitly and then set it aside in favour of the safety inputs you identified. Then document the decline: what conditions you considered, what you decided, and when you would review. This converts an ethical instinct into the same structured record the documentation practice rewards.
- Name the external pressure before discounting it
- State the decision with the conditions and inputs behind it
- Set a review time and record it
Case analysis: separate fixed facts from conditions that change mid-scenario
Before tracing, sort a scenario's details into fixed facts, changing conditions, and stated instructions; each category drives a different part of your answer.
Fixed facts are things that will not change during the passage: the vessel's characteristics, charted depths, a named hazard, the crew available. Changing conditions are the weather, tide, traffic, and the vessel's position over time. Stated instructions are orders or notes given earlier in the voyage that still bind the watch. Confusing these categories is where traces break down: treating a stated instruction as background, or a changing condition as fixed, produces an answer that is internally consistent and wrong.
Practical check: take any scenario and mark each sentence F, C, or I as you read. Then verify your plan responds to every C at the time it changes, and carries every I forward to the watch or decision it affects. If a C has no corresponding decision point in your hour blocks, you have found a gap. This sorting takes minutes and turns an unstructured narrative into an inventory you can audit before you commit to an answer.
- F: fixed facts such as vessel, charted features, crew
- C: changing conditions needing a decision point each
- I: stated instructions that must be carried forward
Build the routine with a three-week traced-scenario sequence and a self-check rubric
Convert domain knowledge into fluent answers by tracing one scenario daily and scoring it against a fixed rubric until the routine is automatic.
Practical exercise: take one coastal scenario and sketch its track with hour blocks, marking each decision point and the last moment it remains open; then take one offshore scenario and write its handover checklist from memory before re-reading the scenario. Expected observations on early attempts: you miss the mid-passage weather or tide change and omit at least one handover detail, usually the autopilot compensation or an instruction from earlier in the voyage. By the second week, you should catch both on the first read, which is the learning milestone this rubric exists to measure.
Adaptable sequence: in week one, work on core domain content and practise labelling requirement versus prudent addition on short prompts. In week two, trace one scenario daily, alternating coastal and offshore, and score each against the rubric. In week three, convert the same scenarios into passage plans, log entries, and handover records, then finish with timed full traces. Readiness check for study purposes: you are in good shape when you can complete a trace that identifies two or more decision points while still open, writes entries that each state a reason, and reproduces the handover checklist without prompting. These are learning milestones, not predictions of any exam outcome.
- Rubric: at least two decision points identified while still open
- One sentence for the requirement, one for the prudent addition
- Every log entry states time, position, action, and reason
- Passage plan branches and abort points marked
- Handover checklist written from memory covers the scenario's omitted detail
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.