Pre-start checklists

GPS-stamped, on-site compliance. Run your team through the checks — and have the record to prove it.

Why GPS matters

A pre-start checklist signed at the office is worth little if the hazards exist on-site. RopeLogix stamps every submitted pre-start with the GPS co-ordinates of the device at the moment of submission.

At audit time, this proves the check happened at the work site — not the day before in a warm office. Inspectors ask; now you have the answer.

If GPS is unavailable or blocked (underground access, dense structure), the app will ask you to confirm your site from your assigned jobs, recent sites (last 7 days), or manual entry. This geofence override is recorded in the audit trail alongside the pre-start.

The 8 sections

Every pre-start is structured into 8 IRATA-aligned sections. Each section contains its own typed checks — not a generic list of yes/no questions. The 8 sections are fixed; your answers within each section are recorded verbatim in the audit trail.

  1. 1
    Site & Access — site name, job reference, supervisor on-site, and Section 1 metadata recorded at time of submission.
  2. 2
    Anchors — primary anchor inspected and approved, backup anchor inspected and approved. Photo evidence can be attached to each.
  3. 3
    Rigging — 4 checks: hardware inspected, rope condition verified, configuration matches rescue plan, edge protection in place.
  4. 4
    Personal PPE — per-technician fitness-for-duty checks: slept adequately, no impairment, hydrated, no injuries, mentally fit.
  5. 5
    Comms — primary channel, backup channel, two-way tested, emergency contact on hand.
  6. 6
    Weather — wind speed (km/h), forecast, temperature, lightning risk, rain expected. A soft warning appears at wind speeds above 40 km/h.
  7. 7
    Rescue Plan — rescue equipment confirmed on-site: pick-off kit, spare rope, first aid kit, AED location, emergency contacts visible.
  8. 8
    Sign — supervisor confirmation and crew sign-on (see below).

Running a pre-start

  1. 1.The supervisor (or designated team leader) opens RopeLogix and taps New pre-start.
  2. 2.Select the job or site. If it's not in the list, type the site name in Section 1.
  3. 3.Work through each of the 8 sections with the crew assembled. Record answers and add notes where anything needs flagging.
  4. 4.Tap Submit. The GPS stamp is applied at this moment. The record is created and locked for editing.
No answers are recorded in the audit trail and visible to supervisors. They do not technically block submission — if your organisation's policy requires resolution before proceeding, that is a process control. The app records every answer and your supervisor can review.

40 km/h wind threshold

The form surfaces a soft warning the moment a tech enters a wind speed above 40 km/h. The check doesn't hard-block submission — pause and reconsider, don't just tap through. If you're still going, the warning is on the record alongside the answer.

Signing the pre-start

After tapping Submit, a separate sign-on step begins. Each technician on the job opens the pre-start card from their own account on their own device and taps Sign pre-start.

To sign a pre-start, you need a sign-off PIN. Set one under Settings → Sign-off PIN. If you have not set one yet, the app will guide you through onboarding before you can sign.

The Team sign-off roster on the pre-start card shows who's signed and who's still pending — green-checked chips for signed, dim/Pending chips for not-yet. Each technician signs from their own account.

Revisions: only before the first signature lands. A pre-start can be revised (with Save revision) only while the record is still unsigned. Once any technician signs, the pre-start is immutable — that's the IRATA / ISO 22846 audit case. Conditions changed mid-shift? Submit a fresh pre-start, not a revision.

Finding past pre-starts

Open a job, then tap the Pre-starts tab to view that job's pre-start history. Each record shows the GPS co-ordinates, all section answers, and the full signature list. Tap any entry to view or download the PDF.

Was this helpful?

Email [email protected]