Patterns on this vessel — recurring causes the app spotted
Read the recurring cause-and-effect shapes on your vessel so you can fix the root, not just the latest symptom.
Every observation, issue, and incident you log becomes a 'signature' the app fingerprints. When three or more similar signatures emerge — say, an alternator pulley repeatedly throwing belt dust — the app surfaces it as a recurring pattern on TODAY and in the Patterns on this vessel report.
Steps
-
Where the patterns surface
TODAY — the TODAY chip at the top of Mission Control — shows two pattern tiles: a quiet 'Patterns on this vessel' entry row that always appears when at least one pattern exists, and a loud red alert section for clusters that meet the high-prevalence threshold (3+ members AND either ≥50% escalated or 2+ still open).
-
Open the full report
Tap either tile to open the report, headed Patterns on this vessel. Trip Detail carries the same quiet entry row at the bottom of a trip. Every cluster shows the recurring entity type (e.g. 'Issue'), member count, escalation rate, resolution rate, and the most recent emergence date.
-
Dismiss an alert you've already handled
On the red alert section, tap the trailing × on an alert row to dismiss it. The dismissal is persistent — the alert won't re-surface unless the cluster's member set changes materially.
-
Sunday-evening digest
If you grant notification permission, the app schedules a Sunday 6 PM local-time digest summarizing the week's pattern picture. The body refreshes after every engine event so a captain who skipped the app for a few days still gets a current snapshot.
-
Why patterns matter
A single observation tells you 'this thing happened.' A pattern tells you 'this thing keeps happening — fix the root cause.' Patterns make recurring vendor issues, parts that wear early, or operating-condition mistakes visible before they become a haul-out.
Related
- Log an observationCapture what you saw, where, and how urgent.
- Observation vs. Issue — what's the difference?Same tab, two intents. Use the right one.
- 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.