Skip to content
Connected Sailing

11 / Beyond the boat

Keeping Family Informed

Keeping my family closer to the day afloat.

See how it helps ↓
The story of a passage also matters to the people ashore.
The story of a passage also matters to the people ashore.
Explore all 13 subjects

How it helps me aboard Jocelyn

01

Share the essentials

Selected information can travel from my working passage to a shore-side view.

02

Make the report time clear

The view shows when the information was last updated, so an old report is not mistaken for a fresh one.

03

I keep private sharing deliberate

I choose the family or friends I involve and keep the private view separate from the public story.

01

A Safety Passage gives shore a factual view

A Safety Passage keeps the essential electronic log: received position and time, speed and course, available instrument readings and boat status. The website displays the latest received facts and retains the final log when the passage ends. The example below uses demonstration data in the existing website interface. It shows the record shore can read without publishing the skipper’s private observations or contacts.

02

Share the fuller passage with invited people

A Full Passage can add spoken and written observations, photographs, video and the richer passage context. The protected family view requires the skipper’s private link or password; it is separate from the public safety log. When I choose to publish a completed passage, the edited public story can bring photographs and observations together with the factual record and redacted planning context.

03

I read the time as well as the position

The website shows when a report was recorded or received. Internet access, instrument reception and successful uploads are different checks. A displayed position can be old, and a missed update can come from coverage, battery, GPS or equipment connection. A deliberate skipper welfare confirmation is shown separately. These views support the agreed shore-contact routine; they do not establish that a passage is safe.

04

The registered PLB alert connection

For Jocelyn’s registered personal AIS beacon/PLB, a supported signal received aboard can be retained as an incident and forwarded through the configured safety and family alert path while passage sharing is active. The shore page has an Enable emergency sound control: the visitor must allow that browser to make an alert audible. Reception, correct beacon identity, sharing, internet and the configured notification services all matter. Delivery status does not prove somebody has seen or heard the warning. Silencing an app or browser does not cancel the beacon or a shore alert. The website is an additional channel alongside the beacon’s emergency function and normal Coastguard arrangements.

My setup on screen

From Connected Sailing to the safety and family views.

The public safety view shows received facts and the registered PLB emergency-sound control. The fuller family view is private. The website example is explicitly labelled demonstration data; the app example is shown before sharing starts.

Existing Jocelyn website safety-log interface with clearly labelled demonstration data and emergency-sound control

The essential safety passage on shore

This is the existing website interface populated locally with demonstration data. It shows time, position, instruments, boat status and the Enable emergency sound control for the registered PLB alert path. It is not a live passage or an emergency.

Enlarge screenshot ↗
Connected Sailing Safety log and family view controls before creating a private link

I choose the private family view

The private family link gives invited people the fuller shared passage context. This is the actual setup screen before sharing starts; no private link or password is exposed.

Enlarge screenshot ↗

At a glance

  1. 01Share selected passage information
  2. 02Check its recorded time
  3. 03Keep people ashore informed