Getting Traffic Controllers to Use the Crew App: A Practical Rollout Plan

A crew app rollout succeeds when the first thing traffic controllers do in the app saves them time: seeing their shifts, accepting offers and submitting timesheets without paperwork. Start with a pilot crew led by respected team leaders, fix what annoys them, then expand over about four weeks, with a clear date when paper stops for each task.

This guide gives you a four-week plan, a toolbox talk script, a table of common objections and how to answer them, and a worked example of a rollout that hit trouble in week two. For choosing the software in the first place, see our guide to traffic control software.

Why crews push back on new apps

Resistance is rarely about technology. It usually comes from one of these:

• "It's more work." If the app adds steps to a shift without removing any, people will resist.
• Old phones and limited data. Some controllers run an old handset on a small prepaid plan.
• Confidence. Not everyone is comfortable with apps, and nobody wants to look slow in front of the crew.
• Privacy worries. "Is the company tracking me?" is a fair question. Answer it honestly.
• Bad timing. Launching in the middle of a busy week or a big night works program sets it up to fail.

Plan for each of these before day one, not after the complaints start.

The four-week rollout plan

This is an example plan for a small to mid-sized company with one or two depots. Stretch it for larger operations.

Add one task at a time. Asking people to learn shift offers, timesheets, pre-starts, SWMS sign-on and defect reports in the same week is the fastest way to lose them.

Week 0 checklist: set up before anyone is invited

Most rollout problems are set-up problems that crews discover first. Before the pilot starts, work through this list:

• Every worker's name, mobile number and email is correct, with no duplicates.
• Tickets, licences and expiry dates are loaded, so shift offers only go to qualified people.
• Regular clients, sites and meeting points are set up, so job details are complete.
• The timesheet and docket fields match what payroll and invoicing need.
• Two champions have used every task themselves on a real shift.
• The app has been tested on the oldest phone in the crew and on a slow connection.
• A paper fallback form exists, and the team leaders know how to use it.
• Someone in the office owns rollout questions and checks progress daily.
• A launch date is set that avoids your busiest week.

If any of these is missing on launch day, the first impression is an error message, and first impressions stick. Spending an extra few days on preparation is cheaper than winning people back after a bad start.

Pick the right first task

The first task decides how people feel about the app. Choose one that clearly helps the crew:

• Shift offers and acceptance. No more missed texts or calls at night. People see exactly where they are going.
• Timesheets. No more dropping paper off at the depot or chasing the office about missing hours. Our guide to digital timesheets and dockets explains what good records include.
• Job details. Address, meeting point, site contact and plan in one place.

Then add tasks that help the company and the safety system, once people are comfortable:

• Pre-start checks. See our pre-start checklist for traffic control crews.
• SWMS sign-on and signatures. Work on or next to a road used by traffic is high-risk construction work, so a SWMS is required before work starts. Our guide to SWMS for traffic control explains what it must include.
• Client docket sign-off and defect reports.

Toolbox talk script for launch day

Keep it short, practical and on a phone in people's hands. Ten minutes at morning pick-up works better than an hour in a training room.

1. Why: "This replaces the paper timesheets and the text messages for shifts. You'll see your shifts, accept them and put your hours in from your phone."
2. What it does not do: be clear about what the app records and what it does not. If you are unsure, check with the provider before the talk.
3. Show it: the team leader shows their own phone: open a shift, accept it, submit a timesheet.
4. Do it: everyone logs in now, with help. Do not let anyone leave without logging in once.
5. Safety rule: "Never use the app while you're controlling traffic or driving. Do it at the pre-start, on your break or at pack-down."
6. Help: "If it doesn't work, tell [champion] or call the office. Paper is still the backup this week."

Our guide to traffic control toolbox talks covers running briefings that people actually listen to.

Worked example: a rollout that stalled in week two

Example scenario: a traffic control company with around 40 controllers and two depots rolls out a crew app. The pilot in week one goes well: two crews led by experienced team leaders submit every timesheet in the app.

Week two: the problem. After the depot toolbox talks, about 70% log in. By Thursday, the office notices that about a third of timesheets are still arriving on paper. The allocator starts entering them by hand, which is more work than before.

Finding out why. Rather than send a reminder to everyone, the operations manager asks the two champions to find out. They come back with three reasons:

1. Several controllers have phones too old to install the app or with storage full.
2. Some use small prepaid data plans and do not want to use data at work.
3. A few find the login confusing and are embarrassed to ask.

The fixes:

• The company buys a small number of basic phones for those whose handsets cannot run the app and introduces a phone allowance under a written policy.
• The app works on the depot Wi-Fi at pick-up, so people can sync there; the company also reviews its data allowance.
• Champions sit with each person who has not logged in, one on one, at pick-up, rather than in front of the crew.
• The paper fallback stays for one more week, but only through the team leader, who enters paper timesheets in the app before leaving site.

Week four: paper timesheets stop. The fallback is documented: if the app is down or a phone fails, the team leader records the details on a paper form and enters them in the app the same day.

What gets recorded: who has logged in, who needs help, devices issued and the allowance policy. The rollout notes are useful again when the next task, pre-start checks, is added.

Answering the common objections

On privacy, be specific and honest. Tell workers what personal information the app collects, how it is used and who can see it. The OAIC has guidance on handling personal information. For phone allowances and work-related expenses, check obligations with the Fair Work Ombudsman.

Measuring whether the rollout worked

Track a few simple numbers each week:

• Percentage of crew who have logged in.
• Percentage of shifts offered and accepted in the app.
• Percentage of timesheets submitted in the app by end of shift.
• Number of paper fallbacks and the reason for each.
• Time from shift end to timesheet in the office.

If one crew or depot lags, ask the champion why before you send reminders. The reason is usually practical.

Next steps

Pick your two champion team leaders and one first task this week, and test the app on the oldest phone in the crew before launch. If you are looking for a crew app built for traffic control, TrafWise covers shift offers, pre-start checks, SWMS sign-on and digital timesheets in one place; you can start a free trial and pilot it with one crew.