ESAC PGSA Help

Assess an application

Review the submitted record, then record one clear decision.

1. Open an assigned application and verify its immutable submission and evidence.
2. Resolve visible problems, including missing voyage dates, before relying on automatic actions.
3. Request a modification, approve or reject using the available action.
4. Complete MFA and enter the required reason or note; wait for the recorded result.

A dispatched action is not the same as a completed outcome. Use the status shown after the server records the decision.

Prepare for crew boarding

Confirm the voyage and tracker assignments; crew starts boarding.

For PGSAs: verify the vessel, IMO and port timeline, then assign primary and backup tracker phones in Voyage settings. Keep authorised controls and change reasons in the portal.

The crew app creates its own boarding Check-in when the crew member selects Start boarding. Do not issue a separate Check-in merely to establish boarding. Missing voyage dates must be corrected where the warning appears before automatic Check-ins can be trusted.

Request and review a Check-in

Later Check-ins may be requested after voyage approval remains valid.

Use the relevant Crew action to request a later Check-in and record the reason. A request is pending until the crew phone submits evidence and the portal shows it as received.

The main crew row shows name, role and Check-in status. Expand its evidence/history view when the task requires more detail. Configure event-based automatic Check-ins under Voyage settings.

Issue and confirm tracking modes

The phone-confirmed mode is authoritative.

Normal is the ordinary mode. Enhanced and Coast Guard increase sampling and upload frequency for a limited period; they are not emergency beacons.

1. Open the selected ESAC and confirm the assigned phone.
2. Choose the mode, duration and reason, then add the operational note.
3. Complete MFA if requested and issue the command.
4. Watch Sent → Received → Applied → Reporting. Sent confirms dispatch only.

Normal, Enhanced and Coast Guard use the same voyage tracking approval, so changing mode does not request a second crew permission. If the crew has manually disabled tracking, the phone receives a resume alert instead.

If a high-frequency period ends, wait for the phone to confirm Normal. Never infer the current mode only from an expired or pending command.

Interpret offline recording

Queued phone records are different from confirmed onshore uploads.

A crew phone can continue encrypting records while offline. Last onshore upload is the most recent server acknowledgement; Location age is the age of the latest received GPS evidence.

If the upload is stale, check the active tracker and phone contact before issuing another command. Ask crew to reconnect and use Upload now; do not tell them to remove the voyage while records are queued.

Consent and device permissions

An authorised command cannot override missing consent or Android access.

One crew voyage approval covers later Check-in, heartbeat and mode requests while consent and device permissions remain valid. Android foreground and background location are granted incrementally; Android 11 and later completes background access in system settings.

If crew pauses tracking, a resume request can be surfaced. If tracking access is revoked, later commands cannot collect location until the crew member approves again. Camera access is used only for live evidence.

Location visibility

Use the vessel map for monitoring and Crew status for individual evidence.

The selected Customer sees the canonical vessel track. The assigned PGSA and authorised Administrators can see operational tracker status needed for that ESAC. Other customers and unrelated PGSAs cannot access it through the portal.

Location age is based on actual GPS evidence. Page refreshed is only when the webpage last checked the server. Switch to Crew status for the authorised per-crew evidence/history view.

Troubleshooting

Resolve actionable warnings before opening diagnostics.

• Missing voyage dates: return the application for correction; automatic Check-ins cannot rely on an incomplete timeline.
• No active tracker: assign primary and backup phones in Voyage settings and confirm that a phone approved tracking.
• Mode not confirmed: check phone contact and command stage; do not repeatedly issue the same command.
• Stale location: compare location age, last onshore upload and active tracker, then ask crew to reconnect.
• No Check-in evidence: confirm that a request exists and remains open, then ask crew to submit until Check-in received appears.

Use Technical details only when raw session, lease, failover or command history is needed for diagnosis.