2Dig Plain comparisons of crane signalling and jobsite communication tools

How to confirm a cut section is supported before tree felling

Steps for tree removal crews to check that a cut section is supported before cutting, with what to have ready and common mistakes to avoid.

By 2Dig ยท

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

Before any cut, have one named person check that the section is held and supported, confirm it out loud with the crew, and only then make the cut. Keep the check on the ground at the tree, and keep a clear signal ready that the whole crew can see or hear.

OptionWhat it doesFeeCard fee
OperatorLinkShows STOP, HOLD and SLOW to the crew and passes button presses, chat and voice between phones in a phone 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 a cut, the crew needs one named person who checks the section and decides whether it is supported. That person needs a view of the whole section from a safe spot, not only the cut line. Have the holding line, the rigging and any cutting aids at the tree before the first cut, so the check uses the gear the crew will actually use. Agree on who calls a stop and how the crew will signal it if the section moves early. If the crew uses OperatorLink for signals, written messages and voice, check that each crew phone can open it in a browser, since button presses, chat and voice pass between phones in a browser. [1] Keep a hand signal or a radio ready as well, so the crew is not depending on one phone.

Step by step

  1. Walk the tree and mark the cut section you plan to remove.
  2. Look at what is holding the section, including the wood around the cut, any cracks, and any branches that may hang up when it lets go.
  3. Set the holding line or rigging on the section and check that it is snug and anchored to a point that can take the load.
  4. Have the person who checks the section confirm out loud that the section is supported and the line is holding.
  5. Clear the drop zone and make sure every crew member is in a known position.
  6. Agree on who gives the go-ahead for the first movement of the section.
  7. Before cutting, look again at the section and the line. If anything has changed, stop and reset.
  8. Make the cut, and keep the holding line under control until the section is down.

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] Nobody needs to install an app, because the page runs in a phone browser. [1] The person who starts a jobsite shares a link or QR code, and the crew joins from it. [1] The support check itself stays with the person at the tree. OperatorLink shows STOP, HOLD and SLOW to the jobsite crew and passes button presses, chat and voice between phones in a phone browser. [1] A HOLD signal stays on for everyone until the last person leaves the jobsite, so the crew does not have to resend it. [1]

A second option is a two-way radio, or agreed spoken calls given face to face and from the tree. Check that the person checking the section can be seen and heard by the rest of the crew from the tree.

Whatever the crew chooses, check that everyone agrees on plain spoken calls and that every member can hear them over the noise of the saw and the wind.

Match the option to the crew and the site, and keep a fallback ready.

Common mistakes to avoid

Starting a cut before the named person has finished the check and said so out loud. Judging the section from one side only, when it may look properly supported from the ground and still be weak from another angle. Relying on one phone for the STOP signal; keep a voice or hand option ready as well. Assuming every phone alerts the same way: on Android browsers, signals such as STOP make the phone buzz, while iPhone Safari ignores the buzz, so check the sound and screen on every device. [1] A jobsite with nobody in it is wiped after 3 idle hours. [1] Reusing an old link from an earlier shift, since a jobsite link stops working 12 hours after the first person joins it. [1] Forgetting that HOLD and SLOW stay on for everyone until the last person leaves. [1]

Frequently asked questions

Is OperatorLink free to use?

OperatorLink is currently free to use, and no paid plan is built yet. [1] Check that each crew phone can open the page before the shift. Keep a hand signal or radio as a fallback in case a phone drops out during a cut.

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] The crew should treat that alert as a reason to pause and look at the section again before any further movement. HOLD and SLOW behave differently, since they stay on until the last person leaves the jobsite. [1]

How long does an OperatorLink jobsite link stay active?

A jobsite link stops working 12 hours after the first person joins it. [1] A jobsite with nobody in it is wiped after 3 idle hours. [1] For a new shift, the person who starts the jobsite should open a fresh session and share the new link or QR code with the crew before work begins.

Do STOP signals buzz every phone in an OperatorLink jobsite?

On Android browsers, signals such as STOP make the phone buzz. [1] iPhone Safari ignores the buzz. [1] Check the sound and screen on every phone in the crew before the cut begins, so no one misses a STOP.

Can OperatorLink crew members talk by voice during a cut?

Anyone who joins the jobsite 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] Voice runs from the phone browser, so keep a hand signal or radio as a fallback. [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