A training practice with one industry on the syllabus

Navigatewithai was founded in Singapore in 2026 because the maritime cluster was buying AI licences faster than it was building the habits to use them on regulated paperwork. Shore desks were being asked to summarise noon reports, draft observation responses and assemble emissions evidence, often with consumer chat tools and no verification routine. The gap was not awareness of the technology; it was the absence of teaching that started from a statement of facts, a recap or a bunker delivery note. The practice exists to close that gap for one industry, in a city that already concentrates owners, managers, brokers and bunker desks.

Navigatewithai is a training and coaching practice. We design and deliver desk-level programmes, half-day clinics and six-week embedded reinforcement for shore-side maritime teams. The work is teaching: collecting a redacted sample of the desk’s paperwork, running live exercises on those documents, and leaving a prompt pack and a verification routine that the desk can keep.

We are not a software vendor. We do not sell, resell or implement an AI platform, and we do not take a commission on licences. Tool choice stays with the company. The course is written so that the same patterns can be used in an enterprise tenancy or, where policy allows, in a carefully constrained public tool.

We are not an audit service, a claims bureau or a legal adviser. Course materials describe general practice. They do not replace charterparty terms, class rules, flag requirements or a company’s own SMS. Anything that leaves the office still needs a human signature from the desk that owns the file.

Clinics of up to eight seats are held at the HarbourFront office, which keeps a small group in one room with laptops, a shared screen and a printed pack of the redacted samples. Larger two-day cohorts and six-week embedded programmes run on-site at client offices across Singapore, so the documents stay inside the company’s own rooms and the trainer works to the house rules on printing, networks and visitors.

Remote cohorts are offered for Europe-facing desks and are scheduled in the early Singapore evening, so operations and chartering teams in overlapping time zones can join without a night watch. Remote delivery still uses the same sequence — model behaviour, guided run, unassisted run, verification — and still requires redacted samples two weeks ahead. We do not record sessions as a default, and we do not ask a cohort to paste live commercial data into a shared chat.

A maritime desk cannot treat a fluent paragraph as finished work. A model will invent a shifting time, misread a handwritten amendment on a scanned SOF, or tidy a near-miss until the facts have moved. The practice therefore binds itself to four rules that sit above any particular tool, and the course is built so that attendees can see those rules applied in the room rather than only written in a slide.

1. 1

   No client document leaves the exercise environment. Samples are redacted before they are used, and they are not copied into a consumer tool, a public corpus or a trainer’s personal account.

2. 2

   No course claims that a tool is compliant with class, flag, EU ETS, FuelEU Maritime, SIRE 2.0 or any other regime. Tools draft; the desk remains responsible for what is filed.

3. 3

   Every exercise output is checkable. A draft must point back to a clause, a log entry, a noon figure or a reading, and arithmetic is re-derived by hand at least once.

4. 4

   Materials are re-cut whenever a tool’s behaviour changes. Prompt packs are dated 2026 working notes, not a frozen manual, and cohorts are told when a pattern has been retired.

The facts below are the ones a visitor or a procurement desk usually asks for first. They are also the ones we put on a scoping-call note so that nobody has to hunt through a brochure for an address or a working hour. Delivery is in English; Mandarin-language handouts can be prepared on request for mixed shore teams, with the live session still run in English so that clause language stays aligned with the governing forms.

Request a scoping call