Comm log — post a quick note on a vendor, issue, or incident
Drop a short, dated, author-tagged note onto a vendor, issue, or incident without opening a full edit form.
Every vendor, issue, and incident has its own Comm Log thread. Tap into the entity, type a line in the compose row, tap Post. Each entry is signed with your own name on this boat (from your membership, or your crew card) and a relative timestamp; when theONE doesn't know your name it says so and won't post, rather than sign you as someone else. Newest entries are on top. Swipe-style isn't available here — use the small × button on a row to delete an entry. The × is on your own entries, and on everyone's for the owner or a manager holding owner authority; nobody else can delete another person's entry. The thread stays on this device — comm log entries are not among the record kinds theONE syncs.
Comm log entries on an incident or an observation are part of its record: the Claim packet card under Trace on the incident screen (and the Claim packet row on an observation) prints them, dated and with the author's name, in the packet's timeline — so "Called the yard, haul-out Thursday" reaches the adjuster without being retyped.
Steps
-
Open the vendor, issue, or incident
For a vendor: Mission Control's vendor card → tap the vendor, or find the vendor through the search box. That opens the vendor DRAWER, which is the only place a vendor's comm log lives — the vendor card under Settings → Vendors does not carry one, and there is no Vendors row in the hamburger.
For an issue: Maintenance tab → tap it. For an incident: open the incident record. In both, the COMM LOG section sits inside.
-
Type and Post
In the COMM LOG section, type into the 'Add a note…' field. Multi-line is fine — it grows up to about six lines. Tap Post. The field clears and your entry appears at the top of the list.
-
Delete an entry
Tap the small red × button on the right side of an entry. It asks first — "Delete this comm log entry?", with Delete and Cancel, and beneath it "You have 60 minutes to undo this from the banner. Nothing else on this record changes." Nothing goes until you tap Delete.
Once it does, the undo banner appears at the bottom of the screen reading "Deleted comm log entry" with a countdown, and "Tap UNDO to restore" under it. Tap UNDO inside the hour and the entry comes back in its own place in the thread, not at the end. It refuses rather than pretending, in two cases, both under the heading "Could not undo": if you have switched boats since the delete — "That comm log entry belongs to a different boat. Switch back to that boat to restore it." — and if the entry is already back — "That comm log entry is already on the record." The banner stays up either way. After the hour the delete is permanent.
-
What it's for
Quick context that doesn't deserve a full Issue or Addendum: 'Called Hank, ringing through Thursday', 'Owner approved spend up to $800', 'Replaced raw-water impeller, ran to temp — stable'. For anything that needs photos, status, severity, or formal record-keeping, use the Issue or Incident edit affordances instead.
Related
- Log an observationCapture what you saw, where, and how urgent.
- Issue lifecycle — open, in-progress, resolvedAn Issue moves through three states: open → in progress → resolved. Severity is low / medium / high / critical. There is no 'Closed' state — resolved is the terminal state.
- Claim packet — one PDF about one incident, for an insurer, a surveyor or a yardTurn one incident, observation or work order into one PDF built from what is already in theONE — pick who it is for, trim the sections, set the three privacy switches, generate, share.