ESAC PGSA HELP Guidance 0.6.24-help.1 | Product 0.6.24 | Role: PGSA ASSESSMENT Review the assigned immutable submission and evidence. Resolve visible problems such as missing voyage dates. Record a modification, approval or rejection only with the required MFA and reason. A dispatched action is not a completed outcome; use the recorded server status. BOARDING Verify vessel, IMO and port dates, then assign primary and backup tracker phones in Voyage settings. Crew starts boarding and the app creates the first Check-in. Do not issue a separate Check-in merely to establish boarding. CHECK-IN Request later Check-ins with the authorised action and a recorded reason. Pending is not received. The crew row shows name, role and status; expand evidence/history only when needed. Automatic rules belong in Voyage settings. TRACKING MODES Normal is ordinary tracking. Enhanced and Coast Guard increase frequency temporarily; they are not emergency beacons. Choose the assigned phone, duration and reason, complete MFA where requested, then follow Sent, Received, Applied and Reporting. Sent confirms dispatch only. The phone-confirmed mode is authoritative. All three modes 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. OFFLINE UPLOADS Phones can encrypt and queue records offline. Last onshore upload is the latest server acknowledgement; Location age is the age of received GPS evidence. Check the active tracker and phone contact before issuing another command. PERMISSIONS One voyage approval covers later Check-in, heartbeat and mode requests while consent and Android permissions remain valid. Commands cannot override revoked consent or missing Android location access. LOCATION VISIBILITY Use the vessel map for the canonical track and Crew status for authorised individual evidence. Location age describes actual GPS evidence. Page refreshed only describes when the webpage last checked the server. TROUBLESHOOTING - Missing dates: return the application for correction before relying on automation. - No tracker: assign primary and backup phones in Voyage settings. - 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. - Raw session, lease, failover or command fields: open Technical details. Current web Help: https://maresac.com/esac-pgsa-guide.html