← Help Center Observations

Two people, one fault — merging observations

Fold two observations of the same thing into one so both accounts are kept, on the Maintenance tab or in the Vessel Briefing, and take one back out if you were wrong.

The mate sees a weep at the shaft seal. The engineer sees the same weep and calls it a packing gland that wants adjusting. Those are two rows on the list, and they read as two faults — when in truth they are one fault described twice, and the second description is the one that tells you what to do about it.

Merging puts them together. The one you merge keeps everything it had — its words, who it is on, when it was logged, its photographs — and moves under the other as an account. The list shows one row instead of two, with a chip saying how many accounts it carries, and opening it shows every account in the words the person used.

It works in both places the boat keeps observations. The Maintenance tab's Observations section is the day-to-day list — that is where the crew log what they notice and where most merging happens. The Vessel Briefing watch list holds the lighter items a playbook run or an end-of-cruise debrief raised. The rules, the wording and the one-tap unmerge are the same in both; you cannot merge a row on one list into a row on the other, because they are different kinds of record.

Nothing is deleted and nothing is re-worded. A merge is a link, so unmerging puts the observation straight back on the list exactly as it was. That is deliberate: you should be able to merge on a hunch.

A merged row stops counting on its own. The open count, the blocker badge and the briefing all see one fault where they used to see two, which is the point — but the row is not resolved and nobody has fixed anything. It is still there, under the survivor, and Unmerge brings it straight back.

If you merge into an observation that has already been merged, yours joins the same group rather than forming a chain — everything ends up under one survivor.

Do not confuse merging with the recurrence chain. "Also seen by" means one fault described twice. "Recurring — 5th occurrence" in the drawer below it means the same fault happening again, months apart, and those stay separate rows on purpose: how often a thing comes back is exactly what you want to be able to count.

Promoting a merged observation to an Issue carries every account with it: the other descriptions are written into the Issue and their photographs come too, because the second account is usually the one that says what the yard should do.

Steps

  1. On the Maintenance tab — say they are the same thing

    Open the Maintenance tab, tap the row in its Observations section, and use “Same thing as…” under “Same thing, seen twice”. When more than eight are open, See all N observations opens the full list, where you can also press and hold a row and choose “Same thing as…”. Offered on observations only — a repair or a safety item is its own record, and merging two of those would quietly take one off the blocker badge. Crew and above can merge; vendors and guests can read the accounts but not change them.

  2. In the Vessel Briefing — the same move

    Open the Vessel Briefing and find the Observations section. Swipe an observation left and tap Merge, or press and hold it and choose "Same thing as…". There, merging is offered to whoever logged it and to captain-tier and above, the same as resolving.

  3. Pick the other one

    The list offers the other live observations, the ones on the same unit first because that is usually the answer. One tap and it is done. If it refuses, it says why in plain words — an archived or already-resolved row cannot be merged, and neither can two that are already part of the same group.

  4. Read both accounts

    Open the surviving row. Under "Also seen by" is every other account with who it is on, the day it was logged, its words and its photo count. An account that has since been resolved or archived says so.

  5. Take one back out

    Tap Unmerge beside any account, or open the account itself and tap Unmerge under “Part of another observation”. It returns exactly as it was — nothing was ever thrown away. Two things to know: an account that was resolved or archived while merged comes back resolved or archived, so it will not reappear on the live list until you reopen it; and on the Resolved list a merged row says “Part of another” and its action reads “Unmerge and reopen”, because reopening it without taking it out of the merge would leave it on no list at all.

Related

← All help articles