How to Document an Outside Sales Role (The Rules Your Best Rep Never Wrote Down)

To document an outside sales role, stop trying to capture the relationship and capture the decisions instead: the route, the visit window, the sentence that works at the counter, and what happens when a good account goes quiet. Write each one at the grain of a single moment, not as a job description. Most attempts fail at the wrong altitude, listing responsibilities nobody can act on. The rep's real value sits in small rules he has never said out loud, and every one of them fits in a sentence.

Why Relationship Work Resists Documentation

Field roles get skipped in documentation projects because the output looks like personality. Someone walks into a doctor's office, people like them, work comes back. There is no screen to record, so the role gets a bullet list of duties and everyone moves on.

We sat with a physician liaison who had built his role from nothing. Nothing in his file explained why he visits offices on Tuesday, Wednesday and Thursday only, or never knocks before 9:30. He had never been asked. This is the same problem as an expert who will not document their work, except the expert is willing and nobody has framed a question he can answer.

A relationship role is not undocumentable: it is documented at the wrong grain.

Ask him to describe his job and you get "I build relationships with referral sources." Ask what he does in the first five seconds at a front desk and you get a move he has used hundreds of times. The role was never vague. The questions were.

What does an outside sales SOP actually contain?

An outside sales SOP is not one document. It is a short stack of procedures, each written at the grain of a single decision or moment, which is the rule we apply to every process we map. Five moments carry almost all the value.

1. Build the route. How you pick which accounts get a visit this week and in what order.
2. Research the office. What you look up before you walk in, and what disqualifies a stop.
3. Work the front desk. The opening move, the questions you ask, the closing question.
4. Deliver the offer. The one fact that changes behavior, and where you check it.
5. Respond to a drop-off. What you do when a reliable account quietly stops sending work.

Only one of the five is the visit itself, and the visit fails least often. What breaks is the thinking around it, which is where a field role differs from the sales procedures that make inside revenue repeatable. Each gets purpose, decision points, and steps, in that order.

---

Start With the Route, Then the Calendar Window

Write down how the week gets built first: the route is the only part of the role a new hire can execute on day one without judgment. Here is the sequence one liaison used to cover a whole referral base in a quarter.

1. Pull the referral report. Export the last year of referring providers and sort it top down by volume. This is the whole territory, ranked, in one file.
2. Spend month one at the top. Tier one accounts first, all of them, before anyone lower gets a visit. The full regular base was covered inside the first quarter.
3. Order stops by drive time. He uploads the export and prompts for the nearest accounts, ordered by driving route and capped at ten a day. He verifies every line by hand, because the list will happily include an office that closed. Company device, company-approved tool, company policy.
4. Fix the days. Visits happen Tuesday, Wednesday and Thursday. Monday and Friday are planning and admin.
5. Fix the hours. Nothing before 9:30 or 10. Nothing after 3.

A manager would strike that last step as micromanagement, and it is the most valuable line in the document. Even an office that opens at 7 is still gathering the day's referrals, and in his words their coffee has not kicked in. After 3 the front desk wants to leave. Write the window with its reason attached, because a rule without a reason gets broken by the first rep who is running behind.

He learned that window by walking into rooms at the wrong time.

Write Down the Sentence That Works

Every outside role has one fact that moves work in real time, and the SOP must name it, say where to find it, and give the sentence that delivers it. Here it is booking lag. One site was scheduling initial evaluations four to six weeks out while two others had slots the same week, and the number changes daily, so he checks it every morning before he leaves.

The sentence is close to scripted: you send a lot of patients to that location, they are booking four to six weeks out, but I have appointments this week and next at the other two. People write it down while he is standing there.

Three more questions belong in the same document. Who is the referral coordinator, asked at every new office, because that is the person who actually routes the work. Is there anything that you need from us, the closing line every time. And when a clinic's schedule goes soft, who are some top doctors you want me to go visit, asked internally, not in the field.

Capturing lines like these is the whole exercise in documenting a process that only lives in someone's head: you are after the words, not a summary of them.

The Details That Look Trivial and Are Not

Record a practitioner instead of a manager and you get detail no job description has ever contained. He brings a swag bag to first visits, one of everything from the giveaway drawer. Two items never come out of it: prescription pads and pens, because they stick around forever. That is a purchasing rule, a budget rule and a brand rule in one sentence, and it lived only in his head.

On repeat visits he brings food, and there is a rule for that too. Buy it fresh from a grocery or warehouse club, then move it out of the original packaging into plain pastry containers. Asked how he gets a busy front desk to engage, he named a repeatable move: compliment an accessory, not the person. Reps he has watched from a waiting room, he said, are like watching paint dry.

None of that sounds like an SOP until you onboard someone without it. It is why the expert who cannot explain what they do usually can, in detail, once you ask about one moment instead of the whole job.

Which name does the outside world use?

Ask the rep which words are safe to say outside the building, because internal vocabulary that leaks into a customer's office does real damage. One clinic has an internal nickname that appears on none of the company's public materials. Staff use it constantly. A new liaison would have used it in a doctor's office and confused everyone in the room.

So every documented outside role gets a two-column terminology table: what we call it, and what you say out there. Site names, service names, role titles, program names. It takes ten minutes and prevents the most avoidable first-week mistake there is, one concrete piece of why capturing tribal knowledge takes more than a stack of SOPs.

Document the Drop-Off Response, Not Just the Visit

The failure this role exists to catch is a reliable account going quiet, and it never announces itself. One provider stopped sending referrals after opening a competing service line. Nobody noticed until someone pulled the tracking report and compared it against the same period last year.

So the procedure is not "maintain relationships." It is: pull the referral report on a set day each month, compare it to last year to date, list every account whose volume dropped, and put those accounts at the top of next week's route. That turns an accident into a step on a calendar.

Escalation belongs in the same document. He does not prioritize chamber of commerce events, having traced two patients to them in total, and says so plainly. He still passes along anything worth the money, because that spend decision is the owner's.

When we document a field role at The Systems Effect, we record the person walking the route rather than the manager who approves the expense report, because the route holds the decisions. Start with one hour and one question: what did you actually do at your last three stops, in order. You will have the first two procedures before the hour is up, and a list of questions for the wisdom interview that gets the rest.

Frequently Asked Questions

How do you document a sales role that runs on relationships?

Document the decisions, not the relationship. A relationship role breaks into a few repeatable moments: how the route gets built, what you check before a visit, the opening and closing questions, the one fact you deliver, and what happens when an account goes quiet. Write each moment as its own short procedure and the role stops looking like personality.

What should a field sales SOP include?

At minimum: a route-building procedure with a cap on stops per day, the allowed visit days and hours and the reason for them, the questions asked at every stop, the one fact that moves work, and a drop-off response on a monthly trigger. Add a terminology table showing which internal words are safe to say in front of a customer. Keep each piece short enough to read on a phone in a parking lot.

How do you capture what a top performer says on a visit?

Ask about one specific visit rather than the typical visit. Generic questions get generic answers, so ask what happened at the last three stops, in order, and what was said at the counter. That is where the real material is: the compliment that opens a front desk, the booking-availability sentence people write down while you stand there, and the reason certain giveaway items never leave the bag.

Can a new rep follow a documented outreach route?

Yes, and the route is the fastest part of the role to hand over. One liaison built his territory plan from a single export of last year's referring providers, sorted top down, then ordered by drive time and capped at ten visits a day. He spent month one on the highest-volume accounts and covered the full regular base within a quarter. A new rep with that export, that cap and the visit window can work a real route in week one.