How do you coach a field rep to use their time in-territory well?
Coach a field rep to use territory time well by making them plan the territory like a portfolio, not a calendar. Tier every account by potential and buying stage, route to cut windshield time, require a written objective per visit, and measure where face time landed — not how many stops they made.
What territory time discipline actually is, and why it decides the number
Territory time is the only input a field rep genuinely controls. They cannot control the buying committee's budget cycle, the competitor's discount, or the procurement freeze in Q3. They can control which door they knock on Tuesday morning and what they intend to accomplish once they're inside. That makes the allocation of face time the highest-leverage coaching surface a field manager has, and it is chronically under-coached because it looks like an administrative topic rather than a selling topic.
The distinction worth teaching is between a calendar and a portfolio. A calendar answers "what am I doing Tuesday?" A portfolio answers "given finite capital — hours, drive time, relationship equity — where do I deploy it for the best expected return?" A rep running a calendar reacts: whoever called, whoever complained, whoever's on the way. A rep running a portfolio allocates: this account gets four hours this quarter because it has $80K of whitespace and an active evaluation; this one gets a quarterly phone check because it's fully penetrated and stable.
Three structural realities make this harder in the field than inside sales. First, the cost of a wrong choice is enormous — an inside rep who dials a bad prospect loses four minutes; a field rep who drives ninety minutes to a friendly, fully-sold account loses most of a selling day. Second, the feedback loop is slow and flattering. The friendly account is delighted to see the rep, offers coffee, complains about a support ticket, and the rep leaves feeling productive. Nothing about that hour signals waste. Third, field reps operate with far less supervision, so drift compounds quietly for months before it shows up as a missed number.

The two failure patterns have names worth using with reps, because naming a behavior makes it coachable. Windshield time is drive time that isn't structured — crossing the territory twice in a day, backtracking, taking a fifty-minute detour for a twenty-minute courtesy call. Happy-account drift is the gravitational pull toward customers who like the rep and who the rep likes back. Drift is not laziness. It's the entirely human preference for warmth over rejection, and it hits confident, well-liked reps just as hard as struggling ones — sometimes harder, because they have more warm relationships to hide inside.
What has changed by 2027 is the tooling floor, not the judgment ceiling. Route optimization inside Salesforce Maps, Badger Maps, Map My Customers, or Route4Me will sequence stops competently. RevOps teams increasingly push intent signals, product-usage data, renewal dates, and propensity scores into the CRM so an account list arrives pre-scored rather than blank. That handles the arithmetic. It does not decide whether this quarter's hours belong in the expansion account or the competitive displacement, and it cannot make a rep walk into a room where they expect to get told no. The rep's edge is judgment about *which* door, and that's precisely what the manager coaches.
One more framing to give the rep explicitly: territory time is a budget with a hard ceiling. Roughly 40 hours a week, of which maybe 22 to 28 are genuinely available for customer contact after admin, internal meetings, CRM hygiene, and proposal work. If drive time consumes eight of those, the rep has fourteen to twenty hours of actual face time per week. Framed as a number that small, reps stop treating a casual drop-in as free.

The coaching process, start to finish
Coaching territory use is not a conversation, it's a sequence. Skipping straight to advice — "you should plan better" — fails because you haven't established what kind of gap you're looking at. Run it in order.
Step one: observe before you diagnose. Pull the last three to four weeks of activity. You want three things: which accounts got in-person visits and how many each, the geographic sequence of those visits by day, and whether each visit produced a logged next step. Most CRMs with check-in or geolocation features give you this directly; if yours doesn't, ask the rep to reconstruct it from their calendar and expense mileage. Then ride along for a full day. Not a half day, not a customer-facing showcase day — a normal Tuesday. The ride-along is where you see routing and drift in real time.
Step two: diagnose the gap category. Territory-time problems fall into four buckets, and the coaching for each is completely different. Skill — the rep genuinely doesn't know how to build a tiered plan or a pre-call objective; they've never been taught. Will — they can build the plan and choose not to follow it, because the hard accounts are uncomfortable. Knowledge — they lack the data to prioritize; without spend history, whitespace, or stage visibility, every account looks equally worth an hour. System — the territory is 400 miles across, or was rebalanced badly, or the CRM is empty; the setup is broken and no amount of individual coaching fixes it.
The single fastest diagnostic is to ask, before each stop on the ride-along: "Why this account, why today, what's the objective?" A skill gap sounds like confusion. A will gap sounds like a good answer for the easy stops and a vague one for the hard accounts they aren't visiting. A knowledge gap sounds like "I don't actually know what they spend." A system gap sounds like "because it's the only account within an hour of here."

Step three: run the coaching conversation using GROW. Have the territory map and the account list — sorted by potential and stage — visible on screen. Under Goal, reframe time as the scarce asset: "If you only had three days in-territory this week, where would you go and why?" Under Reality, confront the actual routing with the data you pulled: "You visited this account three times last month and this higher-potential one zero. What did that cost us?" Under Options, make the rep generate solutions rather than receive them: "Give me three ways to structure next week so tier-1 and late-stage deals get face time and drive time shrinks. Which of these could move to a call?" Under Will, set an explicit standard and ask what's in the way: a tiered plan by Sunday night, a written objective on every in-person visit, and a target share of face time going to tier-1 and late-stage accounts.
Step four: install the cadence. One conversation changes nothing. The rhythm is weekly planning, monthly ride-along, quarterly territory review. Week one, the rep tiers every account A/B/C by potential and stage, and you pressure-test the rankings — expect the friendly accounts to be over-rated on the first pass, that's the tell. Weekly, the rep blocks the coming week before it starts: in-person for tier-1 and late-stage, phone or video for B and C, geographically batched, each visit carrying a written objective. Monthly, you're in the truck. Quarterly, you step back and ask whether the territory design itself is workable or whether you're coaching around a structural problem.
Step five: drill the specific weak muscle. Pick the drill that matches the diagnosed gap rather than running all of them. Tier-the-Territory: hand the rep their account list, give them fifteen minutes to sort A/B/C, then have them defend the top tier out loud — this surfaces comfort being mislabeled as potential. Route Race: give five accounts and have the rep sequence the day, then compare against the tool's optimized route; the delta in minutes is the argument. The Avoided-Account role-play: rehearse the opener and objective for the specific high-potential account the rep has been dodging — this attacks will directly, because the avoidance is usually about not knowing how to open. Phone-or-Field Triage: present ten accounts, rep decides which earn an in-person hour; this builds the judgment that everything else depends on.

What it costs, how long it takes, and the ranges to expect
Managers underinvest here because the cost looks invisible. Put numbers on it and the conversation changes.
The manager's time cost. A weekly plan review is ten to fifteen minutes per rep — a glance at the tiering and the routing, not a full meeting. The monthly ride-along is a full day including drive time and debrief, so a manager with eight field reps spends roughly eight days a quarter in the truck. That is the single largest line item and the one most often skipped. The quarterly territory review runs sixty to ninety minutes per rep with the map, the account list, and the whitespace data open. Total: about three to four hours of manager time per rep per month once the rhythm is established, front-loaded heavier in the first month.
The rep's time cost. Weekly territory planning takes thirty to forty-five minutes once the tiering exists — Friday afternoon or Sunday evening both work; what matters is that it happens before the week starts, not on Monday morning while already driving. The initial full tiering of a territory takes two to four hours depending on account count. Pre-call planning is three to five minutes per visit. Reps resist this arithmetic until you show them the alternative: a single badly-sequenced day burns ninety minutes of unnecessary drive time, which is three weeks of planning sessions paid back in one afternoon.

Time to see change. Routing improvements show up almost immediately — within one to two weeks, because geographic batching is mechanical and the rep can feel it. Face-time reallocation takes four to eight weeks, because the rep has to break relationship habits and open cold doors, and there's a genuine dip while they build access at accounts where they have none. Pipeline impact lags a full sales cycle; in a field environment with a three-to-six-month cycle, don't expect to read the revenue signal for a quarter or two. Set that expectation with your own leadership up front or the initiative gets abandoned at week six for looking flat.
Tooling. Route optimization and field-mapping tools are typically priced per user per month in the modest-add-on range rather than as a major platform line item, and most sit as an app on top of the CRM. Pricing moves and varies by seat count and contract, so check current vendor pricing rather than trusting a number in an article. The honest sequencing advice: buy the tool *after* the rep can tier a territory manually. A rep who can't prioritize accounts will use route optimization to visit the wrong accounts more efficiently, and you'll have paid for it.
Reasonable targets, held loosely. A common working standard is 60% or more of in-person visits landing on tier-1 and late-stage accounts, every tier-1 account touched at least once per quarter, and a written objective on 100% of in-person visits. Those are management standards, not benchmarks — set your own from your baseline. Measure where you actually are for four weeks first, then move the number ten points at a time. A rep at 25% face-time allocation who is handed a 60% target next week will either game the tiering or quietly ignore you.

The upstream cost nobody budgets. If the knowledge gap is real, this becomes a RevOps project before it becomes a coaching project. Getting account potential, whitespace, renewal dates, and stage data reliably into the CRM so a rep can tier from it is weeks of data work, not an afternoon. Scope that honestly rather than blaming the rep for not prioritizing off data that doesn't exist.
Where managers and RevOps teams get this wrong
Measuring visit count. The most common and most damaging error. Rewarding stops-per-week guarantees the rep maximizes cheap, close, easy stops — you have incentivized precisely the drift you're trying to fix. Measure where the time landed, not how much activity occurred.
Never riding along. Territory use cannot be coached from a dashboard. The dashboard shows that eleven visits happened. It does not show that four of them were coffee with a friendly buyer, or that the rep crossed the territory twice because they didn't want to call ahead and risk a "not today." A manager who hasn't been in the truck in a quarter is guessing.

Coaching a rep around a broken territory. If the patch is 350 miles across with forty accounts scattered evenly, no planning ritual fixes it. Some territory problems are design problems, and drilling the rep on tiering while the real issue is coverage is both ineffective and demoralizing — the rep knows the territory is the problem and now believes you don't. Escalate to territory design and say plainly that you're doing so.
Treating the tiering as permanent. Tiers set in January and never revisited become fiction by April. Accounts move stages, budgets appear, champions leave. Re-tier quarterly at minimum, and let the rep move an account between reviews with a one-line justification.
Letting "just checking in" stand. A visit without a written objective is a social call with a mileage claim attached. Requiring the objective is the cheapest intervention available and reliably shortens visits while raising the rate at which they produce a next step — because a rep who has stated a purpose asks for something before leaving.

Never naming the drift. No rep volunteers "I'm avoiding the hardest account because I think they'll say no." You have to name it, without contempt: "The warm accounts are easy and already sold. The hard ones are where the number is. What's the real reason you haven't been in there?" Managers skip this because it feels confrontational. Skipping it means the number stays trapped in the easy quartile permanently.
Confusing a full calendar with a productive one. Busy is comfortable for both parties. The rep looks committed, the manager feels the team is working. Neither of you is looking at whether the hours are landing anywhere that matters.
Ignoring the adjacent time drains. Territory coaching often surfaces that the rep loses six hours a week to internal calls, quoting, or CRM cleanup. That's not a coaching problem, it's an operations problem, and it belongs on the RevOps backlog — automate the quoting, kill the redundant standup, fix the CRM form. Fixing this frequently returns more selling hours than any routing improvement.
Choosing the right intervention: a decision framework
Not every territory-time problem gets the same treatment, and applying the wrong one wastes a quarter. Use the diagnosis to pick.

If it's skill, teach and scaffold. Give the rep a tiering template, do the first territory tier *with* them rather than assigning it, and review the weekly plan every Monday for the first month. Skill gaps close fast — typically three to four weeks — because the rep wants the answer and there's no resistance to overcome. Fade the scaffolding deliberately: week one you build it together, week four they submit and you spot-check.
If it's will, the coaching is about the specific avoided account, not about time management in the abstract. Lecturing a will gap on planning frameworks is wasted breath; the rep already knows what they should do. Identify the two or three high-potential accounts getting zero coverage, role-play the opener for the hardest one, go with them on the first visit if the avoidance is severe, and set a coverage floor that makes skipping visible. Expect four to eight weeks and a real emotional component — avoidance is usually about anticipated rejection or a past bad meeting, and it's worth asking what happened there.
If it's knowledge, stop coaching and go build the data. A rep cannot tier accounts by potential they can't see. This is a RevOps ticket: get spend history, whitespace, renewal dates, product-usage signals, and accurate stage data into a view the rep can sort. In the meantime, have the rep build a rough tiering from what they know and mark the unknowns explicitly — an imperfect tier list beats no prioritization, and the gaps become the data request.

If it's system, escalate rather than absorb. Document the specific structural problem — drive times between accounts, account count per rep, coverage gaps — and take it to whoever owns territory design. Coaching harder against a broken structure burns the rep's trust. Where redesign isn't possible this year, the honest interim move is to formally shrink the coverage expectation: name the accounts the rep is *not* going to cover in person, so effort concentrates instead of spreading thin everywhere.
When it's mixed — and it usually is — sequence rather than parallelize. Fix system and knowledge first, because they're preconditions; a rep can't be blamed for failing to prioritize off missing data or an unworkable patch. Then skill. Then will, last, because will coaching only lands once the rep can't point to a legitimate structural excuse.
A useful escalation ladder for persistent cases: coach and observe for one full cycle; if no change, tighten the standard and shorten the review loop to weekly; if still no change after two cycles, the question shifts from coaching to fit — either the territory is wrong for this rep or this role is wrong for this rep. That's a longer conversation, but pretending an eight-month coaching loop is still coaching serves nobody.
Related questions
What should a field rep's weekly territory plan actually contain?
Tiered account list with A/B/C rankings, the specific accounts getting in-person time and why, the geographic sequence by day, a written objective for each visit, and the B/C accounts getting phone or video instead. One page, built before the week starts.
How do you measure territory time without micromanaging?
Track outcomes, not surveillance. Face-time allocation to tier-1 and late-stage accounts, advance rate per visit, tier-1 coverage per quarter, and pre-call planning rate. All four describe where effort landed and whether it worked — none require watching a dot on a map.
Does this coaching apply to hybrid or inside-outside roles?
Yes, with the drive-time math removed. The portfolio logic, tiering, pre-call objectives, and drift toward friendly accounts all persist in hybrid roles. The lever changes from routing to calendar defense — protecting blocks for hard accounts rather than optimizing a route between them.
When is a territory-time problem actually a territory-design problem?
When drive times between adjacent accounts routinely exceed an hour, when account count per rep makes quarterly coverage arithmetically impossible, or when two reps' patches overlap. If the plan can't be built, the problem is the patch.
How does RevOps support field-rep time discipline?
By supplying the data the tiering depends on — account potential, whitespace, renewal dates, stage accuracy, usage signals — and by removing administrative drag. Every hour RevOps automates out of quoting or CRM entry converts directly into available field time.
FAQ
How often should a field rep do territory planning?
Weekly, in a thirty-to-forty-five-minute block on Friday afternoon or Sunday evening — before the week starts, not during it. The deeper tiering exercise is quarterly. Daily adjustments are fine and expected, but a rep planning only monthly will spend the tail of each month reacting rather than allocating.
What if the rep says they don't have time to plan?
That response is itself the diagnosis — it means they're already reactive. Start with a fifteen-minute Monday block rather than arguing for forty-five, then ride along and show them the drive time a single bad sequence cost. One recovered afternoon pays for a quarter of planning sessions, and the argument makes itself.
How do I tell a skill gap from a will gap?
Ask the rep to walk you through their tiers and explain the logic behind this week's stops. Can't articulate the logic at all? Skill. Articulates it clearly and then visits the friendly accounts anyway? Will. A single ride-along usually settles it — watch where they drive and listen to how they talk about the accounts they're skipping.
Should we buy route-optimization software?
Eventually, but not first. Mapping and routing tools reliably cut drive time and are worth the seat cost — after the rep can tier a territory on their own. Buy it before that and you've funded more efficient visits to the wrong accounts. Manual tiering first, tooling second.
What's the single biggest time-waster in field sales?
Happy-account drift: spending face time on customers who are friendly, close, and already fully sold, rather than on high-potential or late-stage accounts where presence changes the outcome. It's rarely deliberate — it comes from missing potential data plus an understandable preference for warmth over rejection. One ride-along makes it visible.
My rep plans well but still wastes time. Now what?
Look at execution rather than planning. The usual culprits are thin pre-call preparation, no written objective per visit, and no recovery plan when a meeting ends thirty minutes early. Add a post-visit debrief — "what did you learn, what's the committed next step?" If they can't answer, the plan was decoration.
Sources
- Harvard Business Review — Getting Beyond the Myths of Sales Force Effectiveness
- Salesforce Blog — sales and field productivity resources
- Badger Maps Blog — field sales routing and territory management
- RAIN Group Blog — sales productivity and time management research
- Map My Customers Blog — field sales best practices
- McKinsey — Growth, Marketing & Sales insights
- Gartner — Sales practice research and insights
- Bain & Company — Customer Strategy & Marketing insights
Related on PULSE
- [How do you coach reps to manage their own energy and time?](/knowledge/cg0149)
- [How do you coach a rep to improve one skill at a time?](/knowledge/cg0173)
- [How do you coach reps across multiple time zones?](/knowledge/cg0186)
- [Top 10 Questions to Assess a Rep's Time Management and Prioritization](/knowledge/cg0927)
- [Top 10 questions to assess a sales rep's time management habits](/knowledge/cg0877)
- [Top 10 questions to explore a rep's time management habits](/knowledge/cg0832)










