All guides

Create a boat and technical components

Components anchor counters, maintenance, documents and costs to the correct equipment.

Before you begin

  • Data plates or existing manuals
  • A short list of important onboard systems
  1. 1

    Use unambiguous names

    For repeated systems, use names such as Port main engine or Service battery 1 instead of broad labels.

  2. 2

    Copy manufacturer data

    Use the nameplate and mark uncertainty rather than guessing a model or serial detail.

  3. 3

    Attach counters

    Create engine hours and other readings on the exact component they measure.

  4. 4

    Connect evidence

    Attach manuals, invoices and installation photos so later work remains traceable.

Check the result

Another person should be able to distinguish engines, battery banks, pumps and other systems and open the matching evidence without asking. Review “Create a boat and technical components” once from another crew member’s perspective: labels, status and the next action should make sense without a verbal explanation.

If something goes wrong

Keep uncertain model numbers visibly unverified. Before removing a duplicate component, check whether maintenance events or documents still refer to it.

Keep data safe and traceable

For “Create a boat and technical components”, capture only information required for the task. Passwords, access tokens and complete payment details never belong in notes or screenshots. Every change should remain connected to the correct boat, a responsible person and a visible status. If two devices produce different versions, resolve the conflict deliberately; an earlier accepted record must not disappear without explanation.

After the first real use

After the first use, review the workflow against “Use unambiguous names”, “Copy manufacturer data”, “Attach counters”, “Connect evidence”. Add missing labels, sources or follow-up work in context. A short review at season change, after a crew change or when signing in on a new device is then enough. The guide remains useful without maintaining the same task in parallel private lists.