Field Sales Activity Log Template: One Page That Makes Next Week Smarter

A field sales activity log template is a one-page table a rep fills in right after each call, visit, email or introduction, built so that next week's plan starts from what the entries say. The version below has eight columns and takes about two minutes per entry. The aim is not to prove you were busy. The aim is to make sure the next time you touch an account, you already know what changed and what you promised.

If you searched for this, you probably found spreadsheets with a dozen or more columns, many of them built for reporting up the chain. This one is shorter on purpose. Copy it into a spreadsheet, a notes app or a paper notebook. Your CRM stays the system of record for the account itself; this log is the working page you use between touches.

Why do most sales activity logs fail?

Most activity logs fail because they are designed for the person reading them later, usually a manager, instead of the person writing them. When the main job of a log is to show that calls and visits happened, entries turn into "Met with owner, went well, follow up soon." That line is true, and it is useless to the rep who walks in again in three weeks.

Three patterns show up again and again:

• Counting instead of recording. A column for "number of touches" rewards logging many shallow contacts. It says nothing about whether anyone learned something.
• No next step with a date. "Follow up" without a day is a wish. It will not surface on its own.
• No check on the original reason. You visited because something looked like it changed. Did it? If the log never asks, a stale reason keeps pulling the account onto your list.

A log that gets used is one the rep reads back before the next call. Everything below is built around that test.

What goes on a one-page field sales activity log?

A one-page log needs eight things: the date, the account, how you reached them, who you spoke with by role, what you learned and what changed since last time, a next step with a date, whether your reason was still true, and the source you checked. Anything beyond that tends to go unfilled.

The last row is blank on purpose. That is your starting line. Three notes on the columns that people skip:

• Spoke with (role). Write the role, not a phone number. Roles stay useful when people change jobs, and they tell you who to ask for next time.
• What changed since last time. One sentence. If nothing changed, write "nothing new." That is a finding too.
• Was the reason still true? Yes, no or partly. This is the column that makes next week smarter, and it is explained below.

How do you use it in two minutes after each call or visit?

Fill in the row within a few minutes of the call or visit, while you still remember it, in this order: who, what changed, what's next, was the reason true. Write in short phrases, not sentences. If an entry takes longer than two minutes, you are writing it for someone else.

1. Date, account, type, role. Ten seconds. Do it before you pull out of the lot or hang up.
2. What I learned, and what changed. One or two lines. Prefer facts you can act on (a date, a name of a role, a decision someone is waiting on) to impressions.
3. Next step and date. A verb and a day: "Send checklist, Oct 6." If there is no next step, write "none" and say why in the previous column.
4. Was the reason still true? Whatever pointed you at this account (a permit, a job posting, a bid deadline, an introduction) either held up, did not, or only partly did.
5. Source checked. Name the record or document you looked at before the contact. If you went in cold, write "none." It keeps you honest about which accounts you had a reason for.

This works the same for calls, visits, emails and introductions. A banker or an MSP that mostly works by phone and referral can use the same page. The "Call, visit, email or intro" column is there so you can see later which kind of touch produced the movement.

How do the entries look on a real account?

Here is how the first two sample rows work in practice, using two fictional accounts. Orlenby Family Dental is a fictional dental group in fictional Harlow County. It filed a tenant improvement permit in August for a second office and posted three clinical and front desk roles in September.

An MSP rep visits on a Tuesday. At the practice, the owner confirms the second office and says nothing has been decided about phones or networking. The rep's log entry says exactly that, marks the reason as still true, and sets one next step: send a short setup checklist on October 6. Three weeks later, that single row tells the rep what was said, to whom (by role), and what was promised. A bare "visited, follow up" would have told the rep nothing.

The fictional Town of Brackmoor is different. It posted a request for proposals for managed IT services on September 24, due October 14, and the only permitted contact is the procurement contact named in the RFP.

The same rep makes a call, not a visit, and logs it in the same table. The "Spoke with" cell holds the procurement contact's role, and the next step has two dated items: written questions by October 5 and the proposal on October 14. The log is also where the rep records a rule worth remembering: during an open solicitation, no one else at the town gets a call. That is a fact about the account, and it belongs on the page that gets read back before the next touch.

What is the Friday 15-minute review?

The Friday review is a 15-minute pass through the week's entries that decides what carries into next week. Read the rows from top to bottom once, then sort what you find into four buckets: follow-ups due, reasons that went stale, accounts to drop and patterns by area.

The review also feeds how you choose accounts. If three of four visits last week rested on a reason that held up, keep working that kind of reason. If most went stale, you are starting from old information, and you should prioritize accounts from fresher records. A reason that is only a few weeks old can behave very differently from one that is only a few days old, which is why the glossary entries on why now and trigger events are worth a quick read.

Tie the log to your openings too. When the entry says a public record changed, the best use of the next call is to open with that record. For how, see opening a sales call with a public record.

What should a manager do, and not do, with the log?

A manager should use the log to coach a rep on specific accounts and should not use it to count or police activity. The log works only if reps write honest entries, and they will not if the page is a scoreboard.

Do:

• Ask about one or two accounts each week: "What changed? What's the next step?"
• Look for rows where the reason was wrong and ask what source would have caught it.
• Help drop accounts that have stopped moving, so the rep's list gets shorter, not longer.
• Use the patterns to adjust coverage by area.

Don't:

• Grade reps by row counts or minutes spent. That teaches people to write more and say less.
• Require extra columns for the manager's report. Every added column lowers the share of entries that get filled in.
• Penalize a "no" in the reason column. A rep who marks a reason false has just saved the team a wasted visit.
• Ask for the log to be rewritten for presentation. Keep it about accounts, in the rep's own words.

If a manager needs pipeline numbers, those belong in the CRM. The log is for the next visit, not the forecast.

What can't a field log tell you?

A log only helps if it is short and honest, and even then it cannot tell you what you did not ask. If you never asked who approves a purchase, the log will not have the answer. It records what you noticed and nothing else, so a rep's blind spots become the log's blind spots.

Memory also decays quickly. An entry written the same day is usually specific. An entry written Friday for a Monday call is often a summary of a summary. If you cannot fill it in within a few minutes, jot three words in your phone and write the row that evening.

Finally, a log is not proof that a reason is current. "Was the reason still true?" records your judgment on the day. Public records change, and a posting or permit that looked solid on Tuesday may look different by the following Tuesday. Treat the column as a prompt to look again, not a verdict.

Primary sources: BLS Occupational Outlook Handbook: Wholesale and Manufacturing Sales Representatives · IRS: Publication 463, Travel, Gift, and Car Expenses. BLS describes the work as including travel, preparing reports and follow-up with customers, and some reps cover large territories. The IRS publication covers recordkeeping for business travel and car expenses; check the current edition before relying on a detail.

Where TIP fits

TIP (Territory Intelligence Platform) starts the loop from the other end. It gives a rep a short daily list of accounts worth a call or a visit, each with the reason, who to ask for, and the source behind it, and its own one-tap field log lets reps report back so the list improves. The template on this page is a generic habit, not TIP's format. It's one application of territory intelligence, and the habits above work with or without it. See how a Friday looks in the sample week, browse the industries TIP is built for, such as MSPs selling to local government, or read how evidence-backed sales recommendations show their sources. When you are ready, get early access to see a sample list for your territory.