If your team spends hours wrangling spreadsheets and trading emails about who’s hitting which customer this week, you’re not alone. Field teams waste a lot of time just trying to coordinate. This guide is for anyone who wants to cut the confusion and actually work together using shared routes in Badgermaps. Whether you’re managing a crew or you’re out in the field yourself, shared routes can save you hours and prevent dropped balls. Here’s how to set things up — and what to watch out for.
Why Shared Routes Matter (and When They Don’t)
Let’s be honest: not every team needs to share routes. If you’re a solo rep or your team covers totally separate territories, you might not need this feature at all. But if you ever:
- Cover for each other when someone’s sick or on vacation
- Split big territories
- Onboard new reps who need to learn the ropes
- Have managers who want visibility on what’s happening
...then sharing routes is a lifesaver. It kills the “who’s going where?” guessing game, and everyone can see the same plan. But if you’re just looking to micromanage your team, or you’re worried about adding more process for no reason, skip it. Use shared routes when they solve a real headache.
Step 1: Get Your Team on the Same Badgermaps Account
This sounds obvious, but it’s a sticking point. Shared routes only work if your team is set up under the same company (or team) account in Badgermaps. Here’s what to double-check:
- Everyone needs their own Badgermaps login — sharing logins is a mess and will break things.
- All users should be listed under your company’s account, not random individual accounts.
- If you’re not sure, ask whoever manages your subscriptions, or check under “Team” in your Badgermaps dashboard.
Pro tip: If you’re still in the free trial phase, make sure you’re testing shared routes with the right team setup — otherwise, you’ll waste time.
Step 2: Build and Save a Route
Before you can share anything, you’ve got to have a route worth sharing. Here’s how:
- Add stops: Upload your customer list (CSV, Excel, or manual entry). Double-check addresses — Badgermaps is good, but it’s not magic.
- Create your route: Select the customers you want to visit, set your starting location, and let Badgermaps optimize the order.
- Save the route: Give it a name that actually means something. “Tuesday Route – North” beats “Route 1” every time. You’ll thank yourself later.
What matters here: Don’t overcomplicate things. If you only need to swap one or two stops with a teammate, you don’t need to re-create the whole route. Just adjust and save.
Step 3: Share Your Route with the Team
Here’s where the magic (and, occasionally, the confusion) happens.
- Open the route you want to share.
- Look for the “Share Route” or “Team Sharing” option. This is usually near the top of the route details. If you don’t see it, make sure you’re on the web app — sometimes mobile versions hide features.
- Choose who gets access:
- You can share with specific teammates or with the whole team.
- Decide if they can just view the route or edit it. (Be careful: “Edit” means they can change stops, rearrange order, or even delete the route.)
- Send the invite or confirm sharing. The route will show up in their Badgermaps dashboard almost instantly.
What works: Sharing with edit access is great for teams that genuinely collaborate. If you’re worried about someone accidentally nuking your hard work, stick to view-only.
What to ignore: Don’t bother emailing exported routes as PDFs or spreadsheets unless your team refuses to use Badgermaps. That just re-creates the old headache.
Step 4: Communicate Changes (Don’t Assume)
Here’s where most teams trip up. Just because a route is “shared” doesn’t mean everyone checks it before hitting the road. Avoid the classic “I didn’t see that update!” mess:
- Use route notes or comments to flag important changes: “Swapped stop 4 for Friday – see notes.”
- If it’s a big change (like a territory swap), ping your teammate directly — text, Slack, whatever works.
- Set expectations: Does your manager want a heads-up before you change shared routes? Make it clear now, not after someone gets blindsided.
Pro tip: If your team is new to shared routes, run a quick 15-minute meeting to show everyone how to find, open, and use shared routes. Saves you hours of “how do I…?” emails later.
Step 5: Track Progress Without Micromanaging
One of the selling points of shared routes is visibility. You can see who’s completed which stops, add notes, and update statuses. But here’s the honest take:
- Managers: Don’t use shared routes to hover over every move your team makes. It’s tempting, but it’s a fast way to kill trust.
- Reps: Update stop statuses and notes as you go. It’s not busywork — it actually helps when things change last minute, like a customer rescheduling.
- If you’re tracking metrics (like visits per week), don’t rely solely on shared routes. Use reports or exports for the real numbers.
Step 6: Handle Handoffs and Coverage the Smart Way
The real test of shared routes is when someone’s out sick, you’re onboarding a new rep, or you need to shift coverage fast.
- To hand off a route: Share it with the covering teammate and flag any tricky stops in the notes (“Gate code needed,” “Customer prefers mornings”).
- For onboarding: New reps can shadow a shared route before tackling their own. It’s a lot less stressful than starting from scratch.
- When things change: If a customer drops off or priorities shift, update the shared route. Don’t bother with endless email chains — just edit and save.
Pitfall to avoid: Don’t delete old routes unless you’re 100% sure nobody needs them for reference. It’s not like you’re running out of space.
What Works Well (and What to Watch Out For)
Shared routes save time when… - Your team actually looks at them before starting the day. - Everyone agrees on naming conventions and who’s responsible for changes. - You use them for real collaboration, not just as a management tool.
They fall apart when… - People ignore updates and keep using old printed routes. - Too many people have edit access and overwrite each other’s work. - You try to force the feature on a team that’s not ready or doesn’t need it.
Keep It Simple, Iterate as You Go
Don’t try to roll out shared routes to your entire team in one go if you’re not sure how it’ll work. Start with a couple of people, see what trips you up, and tweak your process. Most teams find it takes a few weeks to get the hang of things — that’s normal. Keep your naming simple, communicate openly, and don’t be afraid to adjust if something’s not working.
Shared routes in Badgermaps can save you a ton of hassle, but only if you use them where it makes sense. Start small, keep things clear, and focus on what actually helps your team stay coordinated — not just what looks good in a demo.