ESAC User Help

Boarding a vessel

Complete the first Check-in and approve voyage tracking.

For crew: open Voyages and select Start boarding for the correct vessel. The app creates the boarding Check-in; you do not need to wait for a separate PGSA request.

1. Confirm the vessel and ESAC reference.
2. Take and review the live photograph.
3. Read the voyage-tracking disclosure and approve only if you agree.
4. Submit and keep the screen open until Check-in received appears.

The Check-in evidence and tracking approval are separate records. Both states remain visible in the voyage card.

Completing a Check-in

A Check-in is complete only when the app shows a receipt.

1. Open the current Check-in from Home, Voyages or a notification.
2. Take a live photograph and select Use this photo.
3. Select Submit Check-in and wait for Check-in received.

A photograph or GPS fix on its own is not a receipt. If submission fails, keep the photograph on screen, reconnect and retry.

Tracking modes

Normal, Enhanced and Coast Guard change sampling frequency.

Normal is the ordinary voyage mode. Enhanced and Coast Guard collect and upload more frequently for a limited period. They are not emergency beacons.

A mode is current only after the phone confirms it. When a high-frequency period ends, the app continues to show the last confirmed state until the phone confirms Normal.

Offline recording and uploads

GPS records stay encrypted on the phone until the server confirms them.

Tracking can continue without a network connection when Android location access remains available. New records are encrypted and queued on the phone.

Saved does not mean uploaded. The voyage card distinguishes the phone queue from the last confirmed onshore heartbeat. Reconnect and use Upload now for an immediate retry; do not remove an active voyage while records are queued.

Permissions and privacy

The app asks only for access needed by the current task.

At boarding, Android asks for foreground location first. On Android 11 and later, Allow all the time is completed in system Location settings so tracking can continue when the app is closed.

The system camera opens only when evidence is needed; the app does not request separate camera permission. Notification alerts are optional, but turning them off can delay visible prompts. Privacy and Terms links remain available from the app menu.

Who can see location

Location is restricted to authorised people for the selected ESAC.

The selected Customer can see the canonical vessel track. The assigned PGSA and authorised Administrators can see operational tracker status needed to manage the voyage. Other customers and unrelated PGSAs cannot view it through the portal.

Location age describes the newest actual GPS evidence. Page refreshed describes when the browser last checked the server.

Pause, resume or revoke tracking

Choose the action that matches what you intend.

Pause stops GPS collection but retains voyage approval and the upload queue. Resume restarts the approved voyage after Android access is checked. Revoke tracking access removes this phone’s voyage authorisation until approval is granted again.

Troubleshooting

Use the displayed state and next action to recover safely.

• No voyage shown: reconnect, refresh and confirm that the crew link was approved for this account.
• Tracking needs attention: confirm precise location and Allow all the time in Android settings, then select Resume tracking.
• Saved records waiting: keep the voyage on the phone, reconnect and use Upload now.
• Mode not confirmed: keep the phone online and refresh; do not infer a mode from an old request alone.
• Check-in not confirmed: keep the photo on screen, reconnect and submit again. Look for Check-in received.

Administrator overview

Use the role Help that matches the workspace being reviewed.

For Administrators: Customer and PGSA workspace views remain read-only until a reason-bound Act as user session is started. Use Customer Help for application tasks and PGSA Help for assessment and voyage controls. Raw fields and audit history remain under Technical details.