Monday, 8:40am. Your manager wants to know what changed and what is at risk. Behind that sits a third question they will not ask directly: are we going to make the quarter. Before you hand any of this review over, you need to know which parts stay yours, because the third question is the one that gets you into trouble if you let a tool answer it.
By the end of this lesson you can: split the weekly review into three tasks and score them on the fit test, name the one that stays human and defend it with the deciding factor, and rank your four data sources by trust.
Three tasks wearing one name
| What moved | Which deals are at risk | Are we calling the quarter | |
|---|---|---|---|
| Volume | 5. 60 open deals, 26 snapshot weeks | 5. Every open deal, every week | 1. One decision |
| Checkability | 5. Two snapshots, arithmetic | 4. Every flag is checkable against the row that fired it | 1. Nothing to check it against until the quarter ends |
| Judgment density | 1 | 2, once the rules exist | 5 |
| Cost of being wrong | 2. Corrected next week | 3. A wrong flag wastes an inspection | 5. Your credibility, and somebody's hiring plan |
| Specification cost | 2 | 3. An hour to write the rules | 5. You cannot write down what "right" looks like in advance |
| Verdict | Hand it over | Hand it over, with evidence on every flag | Human. Permanently. |
The third column fails on checkability, and low checkability is a veto no matter what the other rows say. There is no source of truth to compare a forecast call against until the period closes, and by then the call is not needed. A better model does not fix that.
This module builds columns one and two. L6.4 gives you the words to defend column three to your VP.
Four sources, four levels of trust
Confident wrong flags come from treating everything in the folder as equally true. Rank your sources, out loud, in the brief. All four sources below came in your practice pack's data folder; if you have not downloaded the pack from the course page, do that first.
1. Pipeline snapshots are facts about the record. pipeline_snapshots.csv is a weekly
photograph of open pipeline: one row per open opportunity per Monday, 1,383 rows over 26 weeks
from 2026-02-02 to 2026-07-27 (DATA-DICTIONARY.md). If a snapshot says the close date was
2026-06-30 on 28 April, that is what the record said that day. It is the only source where "what
changed" has an unambiguous answer, which is why movement is built on it. But facts about the
record are not facts about the deal: the snapshot says the close date moved, not that the deal
moved.
2. The opportunity file is current state, not history. opportunities.csv tells you where a
deal is now. It has 528 rows and 524 distinct opportunity_id values, because the intended
primary key is not unique in the file (DATA-DICTIONARY.md). If you have not done Module 5 on
this data, do it before you build a roll-up on it.
3. Activity records are facts about logging behaviour. This one catches people.
activities.csv tells you what somebody wrote down. A rep who runs three good calls and logs
none looks dormant. A rep who logs every unanswered voicemail looks busy. duration_minutes is 0
for emails and notes, and contact_id is blank for internal notes (DATA-DICTIONARY.md), so a
deal can look active in a week where nobody spoke to the customer at all. L6.4 shows a real deal
in this dataset where that happens.
4. Call notes are written for a human reader. Sixteen files, mixed .txt and .md,
inconsistent headers, fragments, action items buried in prose, one filename with spaces
(DATA-DICTIONARY.md). Rich, unstructured, and an agent will read them confidently.
And one planted warning: one call note contradicts the CRM. answer-keys/PLANTED-ISSUES.md
in your pack, which you open only after attempting the lab, documents it
under the class note-crm-contradiction: for opportunity OPP-007372 on account ACC-02826,
the note states an amount, a close date and a stakeholder role the CRM rows flatly disagree with,
and claims the record has been updated when it has not. Every other statement in every other note
agrees with the CSVs.
There is no single correct answer to "what is this deal worth". The right output names both numbers, says which system is authoritative for which field, and raises the gap. "Summarise the deal" gets you one source, stated with confidence. This instead gets you the most useful line in the pack:
Movement comes only from pipeline_snapshots.csv.
Current state comes only from opportunities.csv.
Engagement comes from activities.csv and is described as "logged activity",
never as "engagement".
Call notes are evidence, never a source of a number. Where a note and a CRM row
disagree, report both values and flag the conflict. Do not reconcile silently.
Read-only, and why that is good news
The entire pack is read-only: it reads exports from 10-data/ and writes markdown into
30-output/pipeline/. Cowork reads, creates and modifies files only inside folders you have
granted, so the blast radius of a wrong flag is a wrong sentence in a file you have not sent yet.
That is why you can iterate fast: wrong ten times on a Monday morning, at no cost. The moment
this workflow writes next steps back into the CRM, it becomes a Module 5 promotion decision with
a named approver and a tested reversal, not a thing you tune casually.
Worth knowing: two product facts shape the design.
- Nothing fires when a stage changes. The pack is a cadence you run or schedule. A deal that goes wrong on Tuesday is caught the following Monday. That latency is a number you accept in writing; Module 8 makes you write it down.
- There is no memory between sessions. Next Monday's session knows nothing about this one.
The rules file is the memory, which is why
risk-rules.md, the rules file you create in L6.3, is a file and not a habit.
Parallel tasks run genuinely in parallel, each with its own context and file access: useful when you want movement and risk computed at the same time. Any hard cap on how many is unverified, so plan for "several", not a number.
Try this now
Point Cowork at revenue-workspace/. In 10-data/, place pipeline_snapshots.csv,
opportunities.csv, activities.csv, and the notes/ folder, all copied from your pack's data
folder. Do not put the compensation plan
or the board deck in there: the directory boundary is the boundary.
Then run the inventory, before any analysis:
Read 10-data/pipeline_snapshots.csv. Report: total row count, the list of
distinct snapshot_date values in order, and the row count for each date.
Report nothing else. Write no file.
What you should see: 1,383 rows across 26 Mondays, 2026-02-02 through 2026-07-27, between 45 and 61 rows a week. Two things to notice before you analyse anything.
First, the history starts on 2026-02-02, not in January. Older weeks age out of the warehouse
(DATA-DICTIONARY.md). Any "year to date" statement from this file is wrong.
Second, the weeks of 2026-04-13 and 2026-04-20 both hold exactly 50 rows. That proves nothing by itself, but you want it in front of you before you start, and L6.2 is about what it turns out to mean.
What you keep
Two lines for the top of 40-reference/risk-rules.md, once you create it in L6.3:
- Trust ordering: snapshots for movement, opportunity file for current state, activities as logged activity only, notes as evidence and never as a number.
- Human-only, permanently: the forecast call, the decision to inspect a rep, the decision to discount, and the judgment of whether a champion is real. Reason: no source of truth exists to check the output against, which is a veto under the fit test.
Check yourself
- A colleague builds "deals with no engagement in 30 days" from
activities.csv. Name two different ways that flag can be wrong, one in each direction. - Your manager asks for pipeline created year to date from the snapshot file. What do you say?
- A call note says a deal is at 54,000 EUR and closing on 12 August. The CRM says 78,000 EUR and 22 September. What does your pack print?
Where this goes next
L6.2 builds the movement table and the reconciliation line that proves it, then breaks it on a week that never happened.