A visit report is the short version of a client meeting that a colleague can act on without asking a single question. It rarely fails through lack of will and almost always because it is supposed to be written from memory in the evening. This guide covers what belongs in it, when it should be written, and what changes when it is no longer written by hand.
Everyone in field sales knows the scene: four meetings in a day, the last one ending at 17:40, and the laptop for the reports sitting in the boot. What could be recalled word for word at 9 in the morning is a rough summary by the evening. That gap is exactly where the information the report exists for disappears.
What a visit report is and what it is really needed for
Before content and templates, it is worth asking who actually reads the report later. That determines what has to be in it.
More than a compliance exercise for sales management
The most common misconception is to see the visit report as a control instrument, as evidence that work happened. Its real purpose is transferability: it turns knowledge that only exists in one head into something others can use. When the responsible colleague falls ill, goes on holiday or leaves the company, the report is the difference between a maintained account and a fresh start.
What the company gets out of it
At company level the benefit shows up in four places. Communication between field and inside sales no longer needs phone calls, because the status is documented. Marketing can see across many reports which objections recur and which argument lands. Sales management sees where deals stall and why. And when a complaint arrives, there is a dated record instead of two conflicting recollections.
What you get out of it yourself
The often overlooked point: the report is your own preparation for the follow-up meeting. Picking up on a passing remark from the first visit makes you look prepared and attentive, and that beats any sales technique. Over time it also creates a pattern: which conversations led to closes for you, and which did not.
What belongs in every visit report
Seven fields make a report usable. If one of them is missing, questions come back later, and answering questions costs more time than filling the field in would have.
Date, location and attendees
It sounds trivial and it is the most common gap. Alongside date and time, attendees belong in the report with their function, not just their name. "Meeting with Mr Miller" is worthless; "Meeting with Mr Miller, technical purchasing, and Ms Sanchez, plant management" tells a colleague immediately how binding a commitment is. With several meetings on the same day, the purpose belongs there too.
Information about the customer
The starting position determines how everything that follows should be read. Which systems are in use, how is the department set up, is there an ongoing project blocking the decision? Changes since the last visit matter more here than the status quo, because they are the trigger for the next step.
Topics discussed and decisions taken
The core of the report, and the place where most people get too vague. Note the discussion, the questions asked and the answers given. Separate explicitly what was discussed from what was decided. "We talked about an expansion" and "The expansion will be ordered in the first quarter" are two entirely different statements, and only one of them supports a forecast.
Competitor information
The least completed and most valuable field. Which supplier is in play, what did they offer, which of their arguments has the customer adopted? On its own it is a footnote, across fifty reports it is market research nobody paid extra for.
Customer feedback and objections
This is where the uncomfortable material belongs too. Criticism of the product, complaints about lead times, doubts about price. A report containing only good news is a sales conversation with yourself. Record objections in the customer's own words where you can, because the wording reveals how firm the position is.
Opportunities and next steps
Finally the conclusion: which concrete opportunity has emerged, how large is it, and what happens next? Every task needs three things: what, who, by when. A task without an owner is a statement of intent, and one without a deadline gets overtaken by next week.
How to write it so somebody actually reads it
Completeness alone is not enough. A report nobody reads has no value, however thorough it is.
Clear and concise language
Short sentences, active verbs, no filler. A half-page report somebody reads beats a three-page one nobody opens. Cut everything that describes the meeting without saying anything about it: "It was a constructive conversation in a pleasant atmosphere" can go.
Separate observation from judgement
This is the most important craft rule and the most frequently broken. "The customer said the budget is committed until year end" is an observation. "The customer is not interested" is a judgement. Both are allowed, but mixing them makes your own assessment unchallengeable and the report unusable. Mark your conclusion as a conclusion.
Tasks with an owner and a deadline
Every meeting produces tasks, often on both sides. Record them with a description, a responsible person and a due date. Where those three things are written down, accountability follows on its own, and the most common cause of lost deals, the next step nobody chased, disappears.
When the report should be written
Timing determines quality more than the template does. Memory does not fade evenly, it fades first on the details that would have made the report valuable.
As early as possible, not on Friday evening
Ideally straight after the meeting, in the car or on the train. After two days the phrasings and undertones are gone; after a week you are summarising a memory rather than a conversation. Anyone who saves all their reports for Friday afternoon necessarily writes the weakest reports of the week.
The occasions where it is not optional
After a sales conversation with a concrete offer, after every first visit, for complaints and escalations, and whenever something was promised that will later be invoiced or renegotiated. In those cases the report is not a sales tool but a record. For pure routine visits with no new information it can be short; three lines will do.
Why visit reports still get skipped
After thirty years of templates, reminders and training, completion rates in many sales organisations are still low. That is not a people problem, it is a design flaw.
The effort falls on one person, the benefit lands with another
This is the heart of it. Writing costs the field rep 15 to 20 minutes per meeting, so more than an hour of unpaid follow-up work after a day with four meetings. The benefit accrues to sales management, marketing and inside sales. Distribute effort and benefit that way and low participation should surprise nobody.
Why appeals and better templates change little
Both attack the wrong point. A better template cuts the effort by a few minutes; an appeal cuts it by nothing. Only what structurally removes the effort works, not what increases the motivation to carry it. That is precisely why bonuses for complete reports rarely survive longer than a quarter.
What changes with automatic transcription
If the effort is the problem, the answer is not more discipline but a different order of operations. The report comes out of the conversation instead of being reconstructed from memory afterwards.
The report comes from the conversation, not from memory
If the meeting is recorded, you have a transcript afterwards from which the summary, the decisions and the tasks are generated automatically. At a client site this is technically harder than in a video call, because several people share one room. Linked smartphones solve that by giving every voice its own close microphone; Sally states an accuracy of up to 98.8 percent for this. How it works is on the page about transcription of in-person meetings. Anyone who has worked with a voice recorder until now knows the decisive difference: there you end up with an audio file, here with finished text.
Searchable rather than filed away
The second effect only shows after months. A body of transcripts is searchable, a folder of reports effectively is not. The question "which customers raised concerns about lead times this year" is a search query in the first case and a project in the second.
Straight into the CRM rather than a second form
A report that lives in a separate system becomes a second filing location. Sally pushes results into 8,000+ tools and therefore into the existing CRM system, so the report lands where the account history is kept anyway. Hosting is exclusively in Germany, and recordings need the consent of everyone present, because Section 201 of the German Criminal Code makes secret recordings a criminal offence.
Template: the visit report in seven fields
| Field | What goes in it | Typical mistake |
|---|---|---|
| Frame | date, time, location, purpose of the visit | missing when there are several meetings a day |
| Attendees | names with function and decision authority | surnames only, no roles |
| Starting position | situation at the customer, changes since the last visit | status quo recorded instead of the change |
| Topics and decisions | discussion, questions, answers, kept separate from commitments | conversation and decision blurred together |
| Competition | suppliers named, their arguments and price level | left empty because it is uncomfortable |
| Feedback and objections | criticism and doubts in the customer's own words | only the positives documented |
| Next steps | task, owner, deadline | task with no name or no date |
Conclusion
A good visit report is not an essay but a form with seven fields that somebody else can use without asking questions. Quality depends less on the wording than on the timing, and the timing depends on how much effort writing it takes.
That is why the most effective lever is not a better template but letting the report emerge from the conversation itself. Anyone who wants to test that on their own client meetings can try Sally free for 30 days. How recording works in rooms with several participants is explained in the article on transcribing in-person meetings.
