---
{"title": "Managing floor-team communication during curtain wall installs", "description": "Steps for curtain wall project managers to keep several floor teams in sync during installation, with tool options and common mistakes.", "url": "https://2dig.com/how-to-manage-communication-across-multiple-floor-teams-during-installation-for-curtain-wall-project-managers/", "date": "2026-11-07"}
---
Steps for curtain wall project managers to keep several floor teams in sync during installation, with tool options and common mistakes.

Curtain wall project managers can run communication across several floor teams from one shared jobsite session, which each team joins from a phone browser with a shared link or QR code. [^1] [^1] A plan that names who sends each signal, a backup method for when phone signal fails, and the rules for each signal is a sound starting point.

| Option | What it does | Fee | Card fee |
|---|---|---|---|
| OperatorLink | Shows 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 app | not published | not published | not published |
| Two-way radio | not published | not published | not published |

## What you need before you start

Before the first floor team starts, a curtain wall project manager needs a list of every floor team, the name of the person who leads each one, and one phone per team with a working browser and a data signal. The session runs in a phone browser, so no app install is needed. [^1] [^1]

Name one person to start the jobsite session and share its link or QR code with every team lead. [^1] A jobsite link stops working 12 hours after the first person joins, so note when the session opened and plan a fresh link for the next shift. [^1] A session with nobody in it is wiped after 3 idle hours, so restart it at the start of each shift if the crew has been away. [^1]

Decide which signals each floor team may send, and who has the final say on HOLD and SLOW, because those two stay on for everyone until the last person leaves the jobsite. [^1] Keep a written backup, such as a radio channel, for floors where the phone signal is weak.

## Step by step

1. Check that every floor team's phone has a working browser and a data signal before the hoist or crane starts, because the signals pass between phones in a browser. [^1]
2. Have the session starter open the jobsite from a phone browser. No app install is needed. [^1]
3. Share the link or QR code with each floor team lead, and have each lead join from it. [^1]
4. Confirm each team lead sees the same signals on their screen before installation begins. [^1]
5. Agree on the rule for HOLD and SLOW, since they stay on for every team until the last person leaves the jobsite. [^1]
6. Ask each team to send a move by holding its move button. If a move stops arriving for 2 seconds, the other phones drop it, so the sender keeps the button held while the load is moving. [^1]
7. Treat STOP as the first response to any unsafe move. It releases every held direction on every phone and shows a full-screen alert to all other teams. [^1]
8. At the end of the shift, have every team leave the session. An empty session is wiped after 3 idle hours. [^1]

## 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] One-tap calls such as Go Ahead, Copy That and All Clear are sent as chat messages, and anyone who joins can take part in a voice call run from the browser. [^1] [^1] On Android browsers, signals such as STOP make the phone buzz, while iPhone Safari ignores the buzz, so teams using iPhones need a screen and sound check before the lift. [^1] The page can also be added to a phone's home screen as a standalone app. [^1]

A phone video call app is a second option. No facts here describe one, so check whether it can stay open for the whole shift, whether the signal person's hands stay in view, and whether the phone locks its screen during a lift.

A two-way radio is another option to consider. No facts here describe one, so check whether every floor team can hear the channel over machine noise and whether the channel stays clear through the lift.

Match the option to the floors and the shift, and keep a fallback ready, since browser signals depend on each phone's data signal. [^1]

## Common mistakes to avoid

Assuming every floor team gets the same alert. On Android browsers STOP makes the phone buzz, while iPhone Safari ignores the buzz, so check sound and screen on each device. [^1]

Relying on one phone as the only source of STOP. Each floor team's phone needs its own data signal, so a single phone that loses signal leaves the other teams without that source. Keep a voice or hand backup.

Leaving HOLD or SLOW on after the lift. They stay on for everyone until the last person leaves, so clear them on purpose. [^1]

Letting a move continue without a fresh signal. A move that stops arriving for 2 seconds is dropped by the other phones, so confirm each move by voice or keep the button held. [^1]

Reusing an old link the next morning. A link stops working 12 hours after the first join, and an empty session is wiped after 3 idle hours. [^1] [^1]

## Frequently asked questions

### Is OperatorLink free to use for curtain wall installation teams?

OperatorLink is currently free to use, and no paid plan is built yet. [^1] The session runs in a phone browser, so each floor team's phone still needs a working data signal for the shift. [^1] Check the data plan on every phone before installation starts, since the signal is what carries the signals between teams.

### What does the OperatorLink STOP signal do across several floor teams?

STOP releases every held direction on every phone in the session and shows a full-screen alert to every other phone. [^1] HOLD and SLOW work differently, because they stay on for every team until the last person leaves the jobsite. [^1] Because a STOP reaches all teams at once, the crew can pause before anyone moves again. Confirm by voice or radio that each floor team has seen the alert before resuming any move.

### 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, so a session left empty overnight will not be there the next morning. [^1] Start a new session at the beginning of each shift and share the new link or QR code with every floor team lead.

### Does OperatorLink make phones buzz when STOP is pressed?

On Android browsers, signals such as STOP make the phone buzz. [^1] iPhone Safari ignores the buzz, so an alert on an iPhone may only be noticed on the screen. Check sound and screen settings on every phone before the first lift, and confirm each floor team lead has seen the full-screen alert.

### Can OperatorLink be used for voice calls between floor teams?

Anyone who joins the jobsite can take part in a voice call run from the phone browser. [^1] One-tap calls such as Go Ahead, Copy That and All Clear are sent as chat messages. [^1] Voice depends on each phone's data signal, so keep a radio or hand signal as a backup for floors where coverage is weak.

OperatorLink is currently free to use, and no paid plan is built yet. [^1] - [Visit OperatorLink](/go/start)

## Sources

[^1]: OperatorLink's own description of itself (the product of this site's publisher) (/go/start)
