Signing things

Context 1: In-app signing

Most documents — SWMS sign-on, pre-start acknowledgement, logbook counter-sign — can be signed directly in the app by any team member with an account.

1. 1.Open the notification or tap the document in your queue.
2. 2.Read the document in full. Scroll to the bottom.
3. 3.Draw your signature in the pad using your finger or stylus.
4. 4.Tap Confirm and sign. Done.

Context 2: Supervisor email link

When a supervisor is off-site, they receive an email with a link to review and sign a logbook entry or SWMS. No app login is required. The link opens a secure review page in any web browser.

The supervisor reads the document, draws their signature on the pad, and taps confirm. The signed record is immediately reflected in the app.

Context 3: Public token URL (SWMS crew sign-on)

For SWMS crew sign-on, a supervisor can share a public token link with the crew — useful when distributing to people who aren't yet in the system (e.g. workers from a sub who don't have RopeLogix accounts).

The person opens the link on their phone, reads the SWMS, enters their full name and optionally their role, and draws their signature. No account required.

These responses are tracked on the SWMS — the supervisor can see the full sign-on list including external signatories. Public links expire after 30 days.

Context 4: On-the-spot proxy sign

The supervisor walks up to a crew member at the site, hands them the device, and the crew member draws their signature there and then. No notification, no PENDING request, no email — the signature is captured immediately as already-signed.

Use this when the crew member doesn't have RopeLogix on their own phone yet, when reception is patchy, or when you simply need a witnessed signature on the spot.

The dispatch flow on a logbook entry now offers three primary CTAs depending on which channel you pick: Send signing request via Inbox, Send signing request via Email, or Send signing request via Inbox + Email. Beneath each member sits a secondary Sign now (in person) — hand them your device disclosure for the on-the-spot path.

1. 1.The supervisor opens the SWMS / pre-start / logbook entry and taps Sign now (in person) — hand them your device.
2. 2.Pick the crew member from the team list.
3. 3.Hand the device to the crew member. They draw their signature.
4. 4.Tap Confirm. The audit log records both people: the supervisor as the witness, the crew member as the signer.

Why every technician signs each form

Every safety form on a job — SWMS, pre-start, toolbox talk — shows a Team sign-off (N of M signed) roster with one chip per team member. Green-checked = signed. Dim/Pending = not yet.

Per-document sign completion is visibility, not a hard per-document gate — supervisors can see the gap and chase before activating the job. Job activation itself, however, has hard pre-conditions (approved SWMS, assigned supervisor, team of two, anchor cert). Make sure your documents are signed before activating.

Each technician signs from their own account on their own device. Don't hand the device around for signatures — that pattern is reserved for the on-the-spot proxy flow described in Context 4 above. ICOP attendance evidence is per-individual: the record needs to show that each technician personally confirmed they read the form and understood it.

Evidence captured with every signature

Every signed document on RopeLogix carries a tamper-evident evidence record. Even when the signer is on a public-token link without an account, the following are stored:

• ● When: ISO timestamp at the moment Confirm was tapped.
• ● Where: GPS lat/lng + accuracy radius (if the signer granted location permission). Missing GPS is recorded explicitly — never silently faked.
• ● From: IP address + browser/device user-agent. For in-app (attestation) signatures, a device ID and metadata are also captured.
• ● Who: for in-app signs, the account and their IRATA level from their profile at signing time; for email and public-token signs, the name (and optionally role) the signer entered; for on-the-spot, both the crew member and the supervisor coordinator.

What signing actually attests to

Every signature in RopeLogix is a declaration that:

• ● The signatory has read and understood the document.
• ● The information they provided (name, hours claimed) is accurate to the best of their knowledge.
• ● For supervisors signing a logbook entry: they are satisfied the work happened as described and the hours are correct.

Signatures are timestamped and cannot be altered or deleted once submitted. This is a feature, not a limitation — it's what makes the record meaningful.

Viewing all signatures on a document

Open any signed document and tap Signature audit trail. You'll see every signatory, their drawn signature, the time they signed, and (for app signatures) their account details. This is the record that goes into an audit pack.