Organize information

Design a weekly sales tracker in Excel

Define activity, pipeline, outcomes, targets, and ownership without mixing their meanings

7 min setupTested with:ChatGPTReviewed: 2026-08-28

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

Sales workflow and usersMetrics and targetsData and status rules

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Design a weekly sales tracker in Excel.

Workflow, users, update cadence, and decisions:
[workflow]

Metrics, targets, currency, and date definitions:
[metrics]

Data, stage, and status rules:
[rules]

Separate row-level source data from weekly summaries. Define one row's grain and stable keys, required input columns, controlled lists, date ownership, and formulas. Distinguish activity, current pipeline, newly created pipeline, and closed outcomes. Return table layouts, validation, target-versus-actual calculations, overdue follow-up flags, PivotTable views, and a weekly review checklist. Prevent double counting when opportunities change stage or week.

Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

Sales workflow and users: Five account executives update opportunities every Friday. Stages: Qualified, Discovery, Proposal, Commit, Won, Lost. The manager reviews pipeline coverage, follow-ups, and closed revenue for the week.
Metrics and targets: Opportunity value in GBP; weekly won target £50,000; pipeline target is 3× the next four weeks' target. Activity counts are stored separately. Week starts Monday.
Data and status rules: OpportunityID is unique. Owner and Stage required. CreatedDate never changes; ExpectedCloseDate may change; ClosedDate required for Won/Lost. NextActionDate required for open stages. Won value counts only by ClosedDate.

Example output

Create an Opportunities Excel Table with OpportunityID, Account, Owner, Stage, ValueGBP, CreatedDate, ExpectedCloseDate, ClosedDate, NextAction, NextActionDate, LastUpdated, and ReviewReason. Use controlled lists for Owner/Stage and validation that closed stages require ClosedDate while open stages require NextActionDate.

Add WeekCreated, WeekExpectedClose, and WeekClosed helper columns using each distinct date. OverdueFollowUp: =AND(NOT(OR([@Stage]="Won",[@Stage]="Lost")),[@NextActionDate]<TODAY()). Keep TODAY-based flags separate from historical snapshots.

Weekly summary: WonRevenue = SUMIFS(ValueGBP,Stage,"Won",ClosedDate,week bounds); WonCount = COUNTIFS using the same rules; CurrentOpenPipeline = sum open opportunity values with expected close in the selected four-week horizon; Coverage = CurrentOpenPipeline / four-week target. A PivotTable shows Owner rows and Stage columns for current pipeline; another uses WeekClosed for Won/Lost outcomes. Never sum weekly snapshots of current pipeline. Friday review: uniqueness, missing required dates, stale updates, overdue actions, target gap, large-value changes, and source-to-summary reconciliation.

Why this works

1
Stable opportunity keys and explicit date meanings prevent pipeline from being counted as weekly revenue.
2
Separating inputs from summaries keeps formulas reproducible and edits auditable.

Check the result

Is each opportunity counted once in every intended measure?
Are created, expected-close, and actual-close dates used for distinct questions?
Do closed revenue totals reconcile to closed opportunity records?

More ways to explore