How to Build a Weekly Field Sales Report Your GM Will Actually Read

Last month a sales ops lead in Jeddah forwarded me his weekly report. Twelve tabs. Forty-three columns. Color coding that only made sense to him. He said his GM "never reads it." I opened it and honestly? I didn't want to read it either.

That's the real problem with most field sales reporting. Not that the data is missing. It's that nobody can find the point.

Your GM has maybe four minutes for your report. Probably less. He's got a P&L review at 10, a distributor call at 11, and a WhatsApp thread with the RSM that won't stop buzzing. If your weekly sales report takes longer than a coffee to digest, it goes into the mental "later" folder. And later never comes.

So let me walk you through how we think about this. Not the fluffy version. The version that actually gets your report opened.

Start with the one number that changed

Here's the thing about a good weekly report. It answers a question before it's asked.

The question your GM is always silently asking: are we better or worse than last week, and why?

So lead with that. One line. "Coverage hit 91% this week, up from 84%, but strike rate dropped in the Northern route because two reps were out." That's it. That single sentence does more than twelve tabs ever will. It tells him the direction, the size of the move, and the cause.

I got this wrong for years, by the way. I used to think more data meant more credibility. Load it up. Show the effort. Turns out the opposite is true. A packed report reads like you're hiding something in the noise. A tight one reads like you know exactly what's going on.

Every field sales report template should open with what we call the "delta line." What moved, by how much, and the honest reason. Not "performance improved." That means nothing. "Van sales in Al Ain grew 12% because we added the new bakery cluster to the beat." That means something.

Show four numbers, not forty

Look, your GM doesn't care about forty metrics. He cares about a handful that tie to money and behavior. Pick these:

• Coverage — did reps visit the outlets they were supposed to visit?
• Strike rate — of those visits, how many turned into orders?
• Drop size / average order value — is each order getting bigger or smaller?
• Productive outlets — how many unique stores actually bought this week?

That's the spine of any weekly sales report for FMCG. Everything else is supporting evidence. If a metric doesn't explain one of those four, it goes in an appendix nobody reads (which is fine, that's what appendices are for).

And please, put a trend next to each number. A single week's figure is almost useless. 87% coverage means nothing on its own. But 87% when last three weeks were 79%, 82%, 84%? Now I see momentum. Show four weeks side by side and let the pattern do the talking.

One more thing on this. Compare against target, not just against last week. Growth from a terrible base still isn't good. I've seen teams celebrate a 15% jump while sitting at half of plan. The GM knows the plan number cold. If you don't reference it, he'll assume you're dodging it.

Explain the misses before he asks

This is where most reports lose the room. They report the good stuff loudly and bury the bad stuff in row 38.

Bad move. Your GM has been doing this longer than you. He can smell a hidden problem. And when he finds it himself, he stops trusting the whole report.

So do the opposite. Name the biggest miss up top, own it, and say what you're doing about it. "Riyadh route missed target by 18% — two reps quit mid-week, replacements start Sunday, RSM is covering the key accounts personally until then." That reads like leadership. Hiding it reads like a junior analyst.

Honestly, the reports that build the most credibility are the ones that admit the ugly parts fastest. Around 63% of the sales leaders I talk to say they trust a manager more when the bad news comes first. The other 37% are lying to themselves.

Here's a small trick that works. Add a "what I'd do with one more rep" or "what's blocking us" line. It turns your report from a scoreboard into a conversation. Your GM stops reading and starts thinking about resources. That's exactly where you want him.

Make it visual, make it short, send it the same time every week

A wall of numbers is a report nobody opens. A chart your GM can read at a red light is a report that gets acted on.

Use maps. If you're covering routes across Karachi or Dubai or Manchester, a heat map of visited vs. missed outlets says more in one glance than a coverage percentage ever could. This is one field sales reporting best practice teams skip because it feels like extra work. It isn't, if your tools do it automatically. Inside Zivni, the coverage map and the strike-rate breakdown just generate themselves from rep GPS check-ins and order data — no one's copy-pasting into a spreadsheet at 9pm on a Thursday. That's kind of the whole point of not doing this manually anymore.

And timing matters more than you'd think. Same day, same hour, every week. Monday 8am, or Friday 5pm — pick one and never move it. Your GM's brain will start expecting it. A report that arrives predictably gets read. A report that shows up whenever gets ignored, because there's no habit attached to it.

Keep the whole thing to one screen. If it scrolls forever, it's a database, not a report. The detail lives in your system for anyone who wants to drill down. The weekly summary is a headline, not the full newspaper.

Quick reality check before you rebuild yours. Open your last report and ask: could someone who wasn't in a single meeting this week understand what happened in under two minutes? If not, you don't have a reporting problem. You have an editing problem.

Most of us don't need more data. We need the courage to cut. Start there — what are three things you could delete from your next report without anyone missing them?