2Dig Plain comparisons of crane signalling and jobsite communication tools

How to call stop during a lift for rooftop mechanical crews

Steps for rooftop mechanical crews to call stop during a lift, with what to have ready and common mistakes.

By 2Dig ยท

2Dig is published by the makers of OperatorLink, which is compared here alongside other tools.

Have the whole crew join one OperatorLink session from a phone browser, with the link or QR code shared by whoever starts it. [1] [1] Then press STOP, which releases every held direction on every phone and shows a full-screen alert to everyone else. [1]

OptionWhat it doesFeeCard fee
OperatorLinkShows STOP, HOLD and SLOW to the crew and passes button presses, chat and voice between phones in a browser [1]Currently free to use, no paid plan built yet [1]not published
Phone video call appnot publishednot publishednot published
Two-way radionot publishednot publishednot published

What you need before you start

Before the lift, the signal person and the rest of the rooftop crew need one agreed way to call STOP, and each person needs to know what it looks like. Give each crew member a phone with a working browser and a data signal for the whole shift, because the signals pass between phones over the phone network. [1] Name the person who starts the session and the person who shares its link or QR code, then send it only to people who should be on the lift. [1] A link stops working 12 hours after the first person joins, so a link from an earlier shift may no longer open the session. [1] An empty session is wiped after 3 idle hours, so start it when the crew is ready on the roof. [1] Agree that HOLD and SLOW stay on for the whole crew until the last person leaves, so everyone knows which signals are still active. [1]

Step by step

The steps below work with any signal method, so the crew can keep the same order whether it calls by radio, by phone or by hand.

  1. Name the signal person, and confirm every crew member knows who may call STOP and what STOP looks like.
  2. Choose how the signal reaches the crew: a radio, a phone session, or a hand signal, and keep the other two ready.
  3. Test the chosen method with the whole crew before the lift, sending each signal once, including STOP. Run the test from the spot where the lift will start, so the crew checks distance and noise, not just the device.
  4. Confirm everyone can see or hear the signal from where they stand on the roof, including anyone working near the edge.
  5. Agree on what the crew does after STOP: everyone stops moving, looks at the load, and waits for the signal person to clear it.
  6. Decide who clears any HOLD or SLOW that is still on, so nobody moves on a signal that no longer applies.
  7. Keep the fallback ready. If the phone or radio drops out, the signal person switches to a hand signal and says so out loud.
  8. At the end of the shift, close the session and confirm nobody is still acting on an old signal.

Tools that can do it

OperatorLink is made by the team that publishes this site. It shows STOP, HOLD and SLOW to the jobsite crew and passes button presses, chat and voice between phones in a phone browser. [1] [1] It runs in a phone browser with no app install. [1] The person who starts a jobsite shares a link or QR code, and the crew joins from it. [1] STOP releases every held direction on every phone and shows a full-screen alert to everyone else. [1] One-tap radio-style calls such as Go Ahead, Copy That and All Clear are sent as chat messages. [1] Anyone who joins can take part in a voice call run from the phone browser. [1]

A phone video call app is a second option. No facts here describe one, so check whether the crew can keep the call open for the whole shift, whether the signal person stays in view of the lift operator, and whether the phone locks its screen mid-lift.

A two-way radio is a third option. No facts here describe one, so check that the crew agrees on plain voice, that every member can be heard over equipment noise on the roof, and that the channel stays clear through the lift.

Match the option to the crew and the site, and decide what other signal method the crew will use if needed.

Common mistakes to avoid

Frequently asked questions

Is OperatorLink free to use for rooftop crews?

OperatorLink is currently free to use, and no paid plan is built yet. [1] Signals pass between phones in a phone browser, so each phone needs a working data signal for the whole shift. [1] Check that each phone has a working data signal before the lift.

What happens when STOP is pressed in OperatorLink?

STOP releases every held direction on every phone and shows a full-screen alert to everyone else. [1] HOLD and SLOW behave differently, since they stay on for everyone in the jobsite until the last person leaves. [1] On Android browsers, STOP also makes the phone buzz, but iPhone Safari ignores the buzz, so check the screen as well. [1] After any STOP, the crew waits for the signal person to clear it before moving.

How long does an OperatorLink jobsite link stay active?

A jobsite link stops working 12 hours after the first person joins it, so a link from an earlier shift may no longer open the session. [1] A jobsite with nobody in it is wiped after 3 idle hours. [1] For each new shift, start a fresh session and share its new link or QR code with the crew. [1]

Do OperatorLink STOP signals buzz on every phone?

Not on every phone. On Android browsers, signals such as STOP make the phone buzz, while iPhone Safari ignores the buzz. [1] An iPhone may therefore show the STOP alert only on the screen, which is shown to everyone else. [1] Check the sound and screen on every phone before the lift, and agree on a second way to get the signal, such as a hand signal, so nobody depends on a buzz alone.

Can OperatorLink voice calls run during a lift?

Anyone who joins the session can take part in a voice call run from the phone browser. [1] One-tap radio-style calls such as Go Ahead, Copy That and All Clear are sent as chat messages. [1]

OperatorLink is currently free to use, and no paid plan is built yet. [1]

Try OperatorLink

Sources

  1. OperatorLink's own description of itself (the product of this site's publisher)

Related comparisons