Weekly reporting workflow

Turn weekly sales exports into Monday-ready reporting

Compare complete weeks, check the totals, and prepare charts and a short summary from your sales exports. Next week, upload the new file and keep the same metric rules.

Week-over-week comparisonsLeadership-ready summarySpreadsheet-first sales teams
Sales analytics dashboard and spreadsheet reporting workflow

Cadence

Weekly review

Best for

Sales ops, RevOps, ecommerce

A sample you can check

Keep the same metric rules when next week’s file arrives

Practice with four complete weeks. Then replace the sample with your next export, update the dates, and repeat the checks before the meeting.

Weekly sales reference

Synthetic data. This reference is calculated from the CSV to help you check your result; it is not a recorded AI-generated output.

Sep 28–Oct 4, 2026 · USD · compared with Sep 21–27

Net sales

$3,036.00

Distinct orders

10

Average order value

$303.60

Sales week over week

+18.59%

Net sales by week starting Monday

09-07 $2,048.00
09-14 $2,304.00
09-21 $2,560.00
09-28 $3,036.00
Inspect included order lines (13)
Completed orders in Sep 28–Oct 4. Repeated order IDs are separate lines of the same order.
Order IDLine IDRegionNet sales
S031L043North$150.00
S031L044North$100.00
S032L045North$156.00
S032L046North$104.00
S033L047North$156.00
S033L048North$104.00
S034L049South$200.00
S035L050South$300.00
S036L051South$350.00
S037L052South$404.00
S038L053West$350.00
S039L054West$376.00
S040L055West$286.00

Download, upload, then check

  1. Download the CSV: 64 lines, 48 orders, four weeks, USD only.
  2. Open the dashboard tool, sign in or create an account, and upload the downloaded file.
  3. Paste the request below. Check the totals and filters before sharing.

The download and reference are free to view. Dashboard generation requires an account and follows your plan’s limits. View current plans

Copy the sales dashboard request
Create a weekly sales dashboard from this CSV for a sales review.
First check date coverage, duplicate line_id values, missing fields, and currency.
Each row is an order line. Compare September 28–October 4, 2026 with September 21–27, 2026, using Monday-to-Sunday weeks.
Exclude cancelled orders. net_sales is already net of discounts and refunds; do not deduct them again.
Show net sales, distinct order_id count, average order value, and week-over-week change.
Add weekly trends, region and sales rep breakdowns, filters, and an order-line detail table.
Show calculation rules and the data-through date. If the comparison week is zero, mark percentage change unavailable.
Describe three changes supported by the numbers. Do not invent causes, targets, win rate, margin, or pipeline risk.

Exclude cancelled orders. Count unique order IDs, not rows. Net sales already includes discounts and refunds. Update the uploaded file for a new period; the preview does not connect to your sales system.

Why this workflow

Why weekly reporting keeps getting rebuilt by hand

The same job comes back every Monday: merge exports, clean labels, compare this week with last week, rebuild charts, then write the summary that leadership actually reads.

What comes in

CRM exports, ecommerce order files, rep spreadsheets, bookings tables, and channel breakdowns with slightly different structure every week.

What RowSpeak changes

Instead of rebuilding the workbook or presentation from scratch, the team can generate a report draft that is still reviewable before sharing.

What leadership gets

A cleaner read on revenue movement, segment changes, anomalies, and follow-up questions worth discussing in the weekly meeting.

How it runs

How the weekly workflow runs

Three steps from spreadsheet exports to a report the team can actually use.

Upload both complete weeks
01

Upload both complete weeks

Include the latest complete week and its comparison period. Check dates, duplicate line IDs, currency, and what each row represents.

Keep the reporting rules explicit
02

Keep the reporting rules explicit

Specify net sales, distinct orders, exclusions, and Monday-to-Sunday dates. Ask for regional changes and a summary backed by the numbers.

Check, share, then repeat next week
03

Check, share, then repeat next week

Reconcile key totals and filters. Save the request and corrections. Upload the next export, change the dates, and repeat the checks; this is not a scheduled data connection.

Weekly sales report preview
Output quality

What a strong weekly sales report should include

The output should be more useful than a KPI table. It should help the team understand what changed and what to do next.

  • Net sales, distinct orders, and average order value with calculation rules
  • Complete-week comparisons and region or rep breakdowns
  • Three observed changes with supporting numbers
  • Data-through date, missing inputs, and a source-total check
Who this fits

Best fit teams

This workflow is strongest when the team still lives in exported spreadsheets, but the reporting expectation already feels stakeholder-facing.

  • Sales ops teams preparing Monday reviews
  • RevOps teams consolidating pipeline or bookings updates
  • Ecommerce operators tracking weekly commercial performance
  • Founders or GMs still reviewing revenue from spreadsheets

When you need a connected reporting system

Choose a maintained CRM or BI setup for scheduled refresh, centralized permissions, and stable shared metrics. This workflow starts from uploaded snapshots.

Sales workflow image
Weekly reporting workflow

Move weekly sales reviews out of spreadsheet cleanup mode

Use the sample to check the workflow, then upload each new export with the same rules and updated dates.