Every Friday afternoon, the most dreaded thing in the sales group chat isn't difficult customers -- it's how to write the weekly report. Write too much and the boss doesn't have time to read it; write too little and the boss thinks you haven't been working. Nobody likes a running-log-style weekly report, but that's exactly what most salespeople write.
A good weekly report isn't about recording what you did -- it's about helping your boss quickly assess the business state and identify risks that need attention. This article gives you three templates covering different scenarios, ready to use as-is.
The Core Principle: Lead with Conclusions
No matter which template you use, there's one iron rule: put conclusions at the very top. When your boss opens your weekly report, the first thing they should see is this week's key results -- not who you met on Monday or how many calls you made on Tuesday.
The benefit of leading with conclusions: if your boss only has 30 seconds, a glance at the opening tells them how your week went; if they have 3 minutes, they can read on for details. If you bury the conclusion at the end, your boss might never see it.
Template 1: Data-Driven Weekly Report
Best for: Sales teams with clear KPIs, such as telesales and inside sales.
Structure:
I. This Week's Key Data
New leads: XX (target XX, completion rate XX%)
Effective conversations: XX (target XX, completion rate XX%)
Signed customers: XX (target XX, completion rate XX%)
Revenue collected: $XX (target XX, completion rate XX%)
II. This Week's Highlights
List 1-2 things you did well this week, for example: signed Company XX, the largest deal this month; a customer went from first contact to signed contract in just 5 days -- the key factor was XX.
III. This Week's Issues and Next Week's Plan
List 1-2 issues that need attention, for example: Customer XX was originally planned to sign this week but was delayed to next week due to legal review; new lead volume is below target, primarily because channel XX is underperforming -- next week's plan is to adjust XX.
Template 2: Project-Progress Weekly Report
Best for: Key account sales and project-based sales with long follow-up cycles and high deal values.
Structure:
I. Key Customer Progress
List by customer, with one sentence summarizing the current status for each:
Company XX -- Proposal presentation completed, awaiting technical evaluation, results expected next week.
Group XX -- Leadership has given verbal approval, legal review in progress, expected to sign before June 15.
Tech XX -- Customer raised new requirements, proposal needs to be revised, updated version submitted this week.
II. Resources Needed
List items that need support from your manager or cross-functional teams:
Customer XX needs the technical team to do an on-site demo -- please coordinate with the tech department for XX time.
Project XX involves custom development -- needs the product team to assess the timeline.
III. Next Week's Priorities
List 2-3 things that must be completed next week -- no more than 3. If you have more than 3, you haven't prioritized clearly.
Template 3: Concise Briefing Weekly Report
Best for: Small teams or scenarios where your boss prefers efficient communication.
The entire report should not exceed 5 lines:
1. This week's completions: XX signed, XX advanced to XX stage
2. This week's issues: Customer XX postponed decision, reason: XX
3. Next week's priorities: Push XX signing, develop XX new customer
4. Support needed: None / XX
5. One-line summary: Overall progress this week is on track / behind / ahead of expectations
The key to a concise weekly report is writing only one item per line -- don't cram multiple things into a single line. Your boss can grasp the highlights at a glance.
Three Common Mistakes
Mistake 1: Listing actions instead of results. "Made 30 calls this week, met 5 customers" -- these are actions, not results. What your boss cares about is: how many qualified leads did those 30 calls generate? What stage did the 5 customers advance to?
Mistake 2: Only reporting good news. Only writing about deals signed, not deals lost. Losing deals isn't the problem -- the problem is your boss not knowing about lost deals until month-end when the revenue gap surfaces. By then, it's too late.
Mistake 3: No next-step plan. The purpose of a weekly report is to let your boss know what you plan to do next week and what support you need. If there's only a retrospective with no plan, the weekly report becomes a diary and loses its management value.
Let Tools Auto-Generate Your Weekly Report
If you use Tuji to record daily customer follow-ups, communication logs, and signing progress, most of the weekly report data can be auto-aggregated: new customers this week, follow-up count, signed amounts, current status of each customer -- the system has already tracked it all. You just need to add your analysis and plans.
Writing a weekly report shouldn't be the most painful part of your week -- it should be a tool for managing your own business. Pick the right template, use the right tools, and get it done in 10 minutes.