This chapter builds the habits that turn a technically correct answer into a chief's answer: what to say the moment you walk aboard, what evidence to reach for when asked if something is fit for service, and who to call before a plant problem becomes a class, flag or commercial one.
A Class II candidate is examined on whether the plant can be made safe. A Class I candidate is examined on whether the department can be run — and the examiner listens for four things in every answer, in this order: is the plant safe, are the people accounted for and protected, is the paperwork correct and evidenced, and what is the commercial consequence. Stopping after the first of those is the single commonest reason a technically capable candidate is referred, because it answers the wrong question. The examiner already assumes you can fix the plant; the oral is testing whether you can run the department around that fix.
This does not mean reciting all four every time regardless of relevance — a straightforward valve failure with no downtime does not need a commercial paragraph bolted on. It means noticing, as you speak, which of the four your answer has left silent, and closing that gap before the examiner has to ask for it. An examiner who has to prompt "and then what?" after an otherwise competent technical answer has already marked the candidate down, because the prompt itself is evidence the candidate did not think chief-level thoughts unprompted.
Every scenario answer has a shape: safe plant, informed people, correct paperwork, understood commercial consequence — in that order, but none of them optional. Train yourself to hear which one your own answer just skipped.
"You've just joined as chief — what's the first thing you do?" is close to a guaranteed question, and the examiner is not looking for a single right first action so much as a complete list delivered with the calm of someone who has actually done it. The list itself is not exotic: certificates and their expiry dates, conditions of class and when each one falls due, the state of the planned maintenance system and which jobs are overdue rather than merely due, critical spares against the ship's own spares list, running hours on major machinery, outstanding defects and their status, bunker quantity and quality on board, the ship's own peculiarities that do not show up in any manual, and an honest read of the department's competence.
What separates a strong answer from a weak one is not the content of the list — most candidates already know it — but the order and the confidence. Deliver it as something you would genuinely do on your first afternoon aboard, not as an exam answer recited from memory, and the examiner moves on quickly.
The commonest way to lose marks on a "how would you know" question is to answer with a verb instead of evidence: "I would check the oil condition," "I would inspect the mounting," "I would verify the alignment." Every one of those sentences is true and every one of them earns nothing, because none of them says against what standard the check is made, what tool or test produced the number, where the result lives, or whose signature stands behind it. The chief's answer replaces the verb with four nouns: the test performed, the record it produced, the tolerance or standard it was measured against, and the person who verified it.
Practise turning "I would check it" into a full sentence before the oral, not during it. "Is the tail shaft fit to run?" becomes: the last withdrawal survey report, the wear-down readings against the maker's tolerance, and the surveyor's endorsement — not a general assurance that it "looked fine." "Is the crew competent for this operation?" becomes: their certificates, the toolbox talk record, and a demonstrated drill, rather than a rota showing the right ranks are on watch. The pattern generalises to almost any fitness-for-service question the paper can ask, which is why it is worth drilling as a reflex rather than reconstructing it live under pressure.
"I would check it" is not an answer. The test, the record, the tolerance, the verifier — that is the answer, every time the real question is "how do you know?"
Knowing who to involve, and how early, is examined as directly as any technical topic, because it is where an otherwise competent chief can do the most damage. The candidates who struggle are rarely the ones who escalate too readily — examiners do not penalise a chief for telling the master, the company, class, the flag administration or the P&I club about something that turns out to be minor. They penalise the chief who tries to resolve a matter that was never theirs to resolve alone: negotiating a class condition without a surveyor, deciding a hull crack does not need reporting, or settling a fuel-quality dispute with the supplier before the company's commercial and legal people are even aware it exists.
Each of those five parties has a distinct role, and a strong answer names the right one rather than a generic "I would inform the office." The master owns the safety of the ship and needs to know first, always, even when the matter looks purely mechanical. The company owns the commercial and resourcing consequence. Class owns whether the ship remains in compliance with its notation, and only class can vary or waive a condition of class. The flag administration owns statutory compliance and is the party a class or safety matter may ultimately need to be reported to. The P&I club owns the exposure once there is injury, pollution, cargo damage or third-party liability in the picture. Naming which of the five a given scenario actually calls, and in what order, is the skill being tested.
An examiner who presses a correct answer is not signalling that it is wrong — pressing is a standard technique to see whether the candidate actually understands the position or is merely repeating a memorised line. Two failures are visible from the same follow-up question: folding, where the candidate reverses a sound answer the moment it is challenged, and stonewalling, where the candidate repeats the same words louder without engaging with what was actually asked. Only one of the two counts against the candidate for the right reason — a chief who cannot be talked out of a correct decision under pressure is exactly the chief the certificate is meant to produce — but stonewalling looks similar enough from the front of the room that it is worth telling the two apart.
The way through is to treat the follow-up as a request for the reasoning, not a verdict on the answer. Restate briefly why the original position holds, add whatever new information the follow-up actually contains, and change the answer only when that new information genuinely changes the situation — not because the questioning became uncomfortable. A candidate who says "my answer stands, and here is the reasoning again, because nothing you've just said changes that" is demonstrating judgement under pressure, which is precisely what a chief's oral exists to test; a candidate who says "actually, on reflection, I'd do it your way" with no new fact to justify the reversal is demonstrating the opposite.
Both walkthroughs below are judgement scenarios, not calculations — read them for the reasoning chain and the escalation decision, not for a formula to memorise.
You are chief engineer on a bulk carrier, four days' steaming from the nearest port with suitable repair facilities. During the weekly engine survey routine, the second engineer reports that the crankshaft deflection reading on No. 3 unit has risen for the third week running and is now above the maker's stated maximum. The engine is running normally: no abnormal noise, no vibration the watch has noted, and the lub oil analysis from the same week shows nothing unusual. The second engineer asks whether this goes in the defect list for the next port or needs to go further than that. What do you do, and who do you tell?
Vessel: bulk carrier, mid-ocean, 4 days from nearest suitable port No. 3 unit deflection readings, three consecutive weekly checks: 0.20 mm, 0.29 mm, 0.38 mm Maker's maximum permissible deflection: 0.25 mm No abnormal noise, vibration, or lub oil analysis findings Ship is in class, with an approved condition-monitoring procedure for crankshaft deflection
What do you do, and who do you tell?
First separate the two questions the second engineer has actually bundled together.
Is the unit safe to keep running right now, and does this go beyond an entry on the defect list. They do not have the same answer.
The trend matters more than any single reading.
| Week | Reading | Maker's max |
|---|---|---|
| 1 | 0.20 mm | 0.25 mm |
| 2 | 0.29 mm | 0.25 mm |
| 3 | 0.38 mm | 0.25 mm |
And it is already unambiguous against the maker's limit.
Immediate action is plant-level and does not wait for anyone's permission.
Increase the monitoring frequency on No. 3 unit, reduce load if the trend continues, and brief the watch on what to report immediately if noise or vibration appears. None of that requires informing anyone beyond the master, because it is still within the chief's own authority to run the plant safely.
The class question is separate.
And it is the one a Class II answer would miss. A deflection reading outside the maker's tolerance, on a class-monitored parameter, is a condition that may affect the machinery notation whether or not the engine has actually failed — the notation is at risk from the trend, not only from a breakdown. Waiting for a hard alarm before reporting it hands class a fait accompli instead of a chance to advise on safe operating limits.
Deciding to report now.
While the plant is still running normally, is also the commercially sound choice: it gives the company and class time to arrange a survey and parts at the next suitable port, rather than an emergency deviation later.
AnswerIncrease deflection monitoring on No. 3 unit and reduce load if the trend continues — that is a plant decision taken now, without waiting for instruction. In parallel, inform the master and the company immediately, and report the deflection trend to class as a condition that may affect the machinery notation, requesting their guidance on safe operating limits until the unit can be opened up and surveyed at the next suitable port.
The trap: treating this as purely an engineering entry for the defect list because the engine is still running normally — and only involving class once a hard alarm or failure forces the issue.
You took command of the engine department three weeks ago on a product tanker. A Port State Control officer boards, reviews the Oil Record Book and the ODME/OWS 15 ppm alarm test records, and finds that the last recorded functional test is overdue against the ship's own PMS interval. The officer says this out loud in front of your second engineer and mentions the possibility of detention while they consider it. What do you do?
Joined this ship as chief engineer 3 weeks ago PMS interval for the ODME/OWS 15 ppm alarm functional test: every 30 days Last recorded successful functional test: 40 days ago No entry in the Oil Record Book suggesting the system was bypassed PSC officer has raised the possibility of detention and is waiting for a response
What do you do?
The officer has stated a suspicion.
Not a finding, and the first job is not to argue with it but to establish what the records actually show — arguing before the facts are on the table only reads as defensiveness.
Pull the PMS history.
The Oil Record Book together and do the arithmetic the officer has implied rather than assumed.
Ten days overdue with no suspicious entries in the record book is an administrative lapse in the testing schedule — serious, and the vessel's, but categorically different from a deliberate bypass of pollution-prevention equipment, and the two must not be left blurred in front of the officer.
Three weeks in command does not excuse the finding.
And saying so to the officer would sound like an excuse rather than a fact — the correct use of that fact is internal, when explaining to the company how the gap arose and what changes under the new chief.
This is a PSC deficiency.
And it is reported and handled the same way regardless of how minor it looks: run the functional test now, in the officer's presence if they will observe it, and treat the office as needing to know before the officer leaves the ship, not after.
AnswerRun the ODME/OWS 15 ppm alarm functional test immediately, invite the PSC officer to witness it, and record the result. Inform the master and the company at once — a PSC deficiency is reported regardless of how minor it looks. Agree the corrective action and closure evidence with the officer in writing before they leave the ship, rather than treating a passed test alone as the end of the matter.
The trap: debating the officer's suspicion of a bypass instead of producing the test, the record and the PMS history — and treating the deficiency as closed once the officer disembarks, without a written, evidenced closure on file.
Four-part answerPlant, people, paperwork, commercial — in that order, all four presentTaking overCertificates, conditions of class, PMS overdue jobs, spares, hours, defects, bunkers, peopleFit for service?State the test, the record, the tolerance, and the verifier — never just “I'd check it”Major failure at seaMake the plant safe, inform master, assess options, bring in company and class before deciding the repairDamage affecting classReport at first opportunity; follow an approved procedure; survey followsPSC deficiencyEstablish the facts, agree the corrective action, evidence it, close it out in writingEscalation ladderMaster → company → class → flag → P&I — early involvement is never a mark against youUnder pressureRestate the reasoning; change the answer only for a genuine new fact, not for discomfort