SiSu RevOps

M5  /  L5.4  /  about 14 minutes

Reconcile, then sample, then earn the write

Your audit is done, your duplicate list is banded, and the output looks good. That is the dangerous moment. A wrong hygiene pass looks exactly like a right one: same columns, same confident tone, same tidy counts. Then somebody puts your number next to the board pack, the two disagree, and you find out in the meeting.

What you will be able to do

  • Reconcile an audit against its source so every row is accounted for.
  • Choose a sample size you will actually run every month, and defend it.
  • Read the exceptions file as a statement about your brief, not the data.
  • State the conditions under which this workflow could write to the CRM, with the reversal plan to match.

Reconcile first: everything gets accounted for

Sampling is the check people reach for. It is the second check. The first is free and catches what sampling cannot, because sampling only looks at rows you already know about. Reconciliation has three parts:

  1. Row accounting. Every row in the export is clean, defective in one or more named classes, or written to exceptions. Total the three against the source. In the shipped opportunity file: 528 rows, 524 distinct records, 65 records failing at least one check, 459 clean. The lines must sum to the distinct count. If not, the accounting is wrong before the analysis starts.
  2. Referential accounting. Every ID in your duplicate list and proposed-changes file exists in the source. An agent that invents an ID is rare. One that carries a truncated ID through a join is not.
  3. Cross-source accounting. One number in your output is rebuilt from a different source and shown to match. This catches the silent failures, and it is the subject of the breakage below.

Sample ten rows, on purpose

The temptation is ten rows per class. With ten classes that is a hundred manual checks inside a pass meant to save you time, and the course rule forbids it: if checking costs more than doing it by hand, do not hand it over. The sample that survives a real month:

  • 10 rows in total, allocated across defect classes in proportion to class size, minimum one row for any class with at least one member. A class of 14 gets three rows, a class of 4 gets one.
  • Plus every auto-band duplicate pair above a stated ARR threshold. You pick the threshold and write it in the field-policy.md you started in L5.2. A merge on a Tier 1 account gets looked at every single time.

When somebody asks why the sample is not bigger: the correct sample size is the one you will actually run every month. A twenty-row sample you skip in December is worth less than a ten-row sample you never skip. Either way, record the result in the run log: ten rows checked, N errors found, which classes.

The exceptions file is feedback on your brief

Anything the pass cannot resolve goes to exceptions.csv with the record ID and the reason. It does not guess. Read it like this:

What you see What it usually means
Empty, on messy data The brief gave the agent no way to say "I do not know". Suspect silent guessing.
A handful of rows with distinct reasons Healthy. This is the file working.
40% of the file, one repeated reason Your field policy is wrong, not the data. Fix the definition.

In this dataset the honest exceptions on the opportunity pass are OPP-006774 and OPP-006894, whose account_id values resolve to no account, so no test needing the account applies. Two rows out of 528 is what a healthy exceptions file looks like.

The shape that makes review possible

proposed-changes.csv, which your pass writes to 30-output/hygiene/, is the deliverable. It is draft-only: a human reviews it and a human applies it, through your CRM's normal change process.

Columns, exactly:

Column Why a reviewer needs it
record_id What is changing
object accounts, contacts or opportunities
field Which field
current_value So they do not have to open the CRM
proposed_value The change
reason Plain English, one line
rule The rule ID from field-policy.md that produced it
confidence_band auto or review, from L5.3

The rule column makes bulk review possible: a reviewer sorts by rule, reads one example, and accepts or rejects 60 rows at once. Without it they read 60 unrelated decisions, stop after eleven, and your pass never gets applied. That is the difference between a pass a manager approves and one they do not, and the module quiz in the interactive app tests exactly this.

Earning the write, and the reversal plan

You write this as a paper exercise in Part A of the exercise sheet in labs/LAB-05 of your practice pack (start with its README), whatever your role, and the module quiz in the interactive app tests it.

The workflow may be proposed for promotion from draft-only to writes-to-system only when all of these are true:

  1. It has run clean on three consecutive passes, with the run log to show it.
  2. Sampling found no errors in the auto band across those passes.
  3. The reversal path has been tested on a small batch: export the before state, apply, confirm you can restore, write down how long the restore took.
  4. A named approver signs each run. Not a role. A person, per run.
  5. The run log captures what changed, per record, before and after.

Then the part that is not a checklist item. The audit trail for a CRM write initiated through Cowork is the one you build. The Compliance API and Audit Logs do not cover Cowork. Enterprise has an admin dashboard, an Analytics API with per-day usage and per-user activity, RBAC, spend limits, and OpenTelemetry events covering tool and connector calls, files read or modified, and whether an action was approved manually or automatically, all SIEM compatible. That is real telemetry, genuinely useful, and not a compliance audit log. If your organisation needs the second one, this workflow stays draft-only and the import goes through your CRM's normal change process. Say both halves to your security reviewer. They will find out anyway, and better from you.

Cadence, because there is nothing to trigger on

There is no event trigger, no "when a record changes, run this". A hygiene pass is therefore weekly or monthly, chosen by you, and the lag before your pass notices a bad record is a number you accept, not a problem you solve. Large exports also consume allowance quickly, out of a pool shared with chat and Claude Code: a second argument for one batched monthly pass over constant small ones. Module 8 designs the cadence, including what happens the month it does not run.

Try this now

Run the reconciliation and the sample:

OUTCOME
Reconcile the audit against source and produce the verification sample.

INPUTS
10-data/opportunities.csv, 10-data/accounts.csv,
30-output/hygiene/audit-2026-08-06.md, 30-output/hygiene/exceptions.csv

OUTPUT SHAPE
Append to 50-runs/RUN-LOG.md under a dated heading:
  1. Row accounting: source rows, distinct records, records with >=1 defect,
     clean records, exception records. State whether they reconcile.
  2. Referential check: count of IDs in duplicates.csv and proposed-changes.csv
     that do not appear in the source. Expected 0.
  3. Cross-source check: for account ACC-02858, compare accounts.arr_usd against
     the amount on the most recent Closed Won opportunity converted at the fixed
     rate for that account's currency. Report both numbers.
  4. Sample: 10 records, allocated across defect classes in proportion to class
     size, minimum 1 per non-empty class. Print record_id, class, and the field
     values a human needs to verify it.

CONSTRAINTS
Do not fix anything found here. Report only.

What you should see: the cross-source check on ACC-02858 (Vireo Retail PLC) resolves. arr_usd is 121,920, the account bills in GBP, and the most recent Closed Won renewal OPP-006984 is 96,000 GBP. 96,000 times 1.27 is 121,920. They tie exactly. That is your tripwire: one account, about forty seconds, and it fails loudly the moment somebody sums an amount column without converting it.

When this goes wrong

Break it yourself

Ask for the simplest thing a leader ever asks for. No deduplication instruction, no currency instruction. Run it.

From 10-data/opportunities.csv, give me total Closed Won by fiscal year and the
total open pipeline.

What comes back

You get 16,830,000 for total Closed Won. A clean number, nicely formatted, and wrong in two directions at once.

Direction one: it double counts. opportunity_id is meant to be the primary key of opportunities.csv and is not unique in the file (DATA-DICTIONARY.md in your pack's data folder says so explicitly). Four IDs appear on two rows each, with different amounts: OPP-006790 (9,000 and 11,000 EUR), OPP-006886 (57,000 and 71,000 USD), OPP-007099 (69,000 and 55,000 USD), OPP-007110 (15,000 and 14,000 USD). All four are Closed Won, so all four are counted twice. Deduplicating on the key brings the raw total to 16,679,000.

Worse than the size of the error: you cannot tell which row is right. Keep the lower amount of each pair and the converted total is 17,965,560 USD. Keep the higher and it is 17,996,720 USD. The 31,160 USD gap depends entirely on a choice nobody made deliberately. This is why the guard sends collisions to exceptions rather than picking a row.

Direction two: it adds three currencies together. opportunities.amount is in the account's local billing currency and accounts.arr_usd is in USD (DATA-DICTIONARY.md). Summing the amount column treats a EUR deal and a USD deal as the same unit. Converting properly, at the fixed rates in the data dictionary (EUR 1.08, GBP 1.27), takes the deduplicated Closed Won total to 17,980,560 USD.

And a third thing, hiding inside the second. Four opportunities carry a currency label that contradicts their account: OPP-006697, OPP-006729, OPP-007089 and OPP-007326, all labelled USD on accounts that bill in EUR (answer-keys/PLANTED-ISSUES.md in your pack, class SUBTLE currency-mismatch, which you open only after attempting the lab). Even a careful analyst converts these four the wrong way. Using the account as the authority moves the Closed Won total again, to 17,995,680 USD.

Nothing in any of those outputs looks broken. Every one is a plausible number somebody would put in a board pack.

The check that catches it

Take OPP-007089, on account ACC-03089 (Quarrybank Hospitality Group SL, Spain, billing EUR).

  • The opportunity row says 25,000 USD.
  • The account's arr_usd says 27,000.
  • 25,000 times the EUR rate of 1.08 is 27,000.
  • And the renewal on the same account, OPP-006747, records the same 25,000 labelled EUR.

The account's own USD figure only reconciles if the deal is read as EUR. The currency label on that row is wrong, and the reconciliation says so without anybody noticing a suspicious-looking row. That is the difference between a check and a hunch.

The guard

Three lines in the brief, permanently:

  1. Deduplicate on the primary key before any aggregation, and write every collision to exceptions.csv with both amounts and the reason duplicate primary key, amounts disagree. Do not pick a row silently.
  2. Treat accounts.currency as the authority over opportunities.currency, convert with the rates named in the brief, and flag every row where the two disagree as its own defect class.
  3. Put both checks inside the reconciliation section, so they run every month rather than the month you remembered.

Then re-run and confirm the three numbers move the way you predicted. A guard you did not watch fire is not a guard.

What you keep

  • 30-output/hygiene/proposed-changes.csv and 30-output/hygiene/exceptions.csv.
  • A 50-runs/RUN-LOG.md entry with the reconciliation result, the sample result and the ten record IDs you checked.
  • In 40-reference/field-policy.md: the promotion checklist, the named approver, the reversal procedure and the ARR threshold above which every auto-band merge is reviewed individually.
  • 20-briefs/crm-hygiene-audit.brief.md, complete, with the three guards in it.

Check yourself

  1. Your audit reconciles perfectly: every class count checks out, the sample of ten found no errors, the totals agree with each other. Name one thing that could still be badly wrong, and the check that would find it.
  2. A colleague proposes promoting the workflow to direct CRM writes after one clean run, because the sample found nothing. List the promotion conditions not yet met.
  3. Your exceptions file has 214 rows out of 528, all with the reason "cannot determine required fields for this record type". What do you change, and where?
  4. Your security reviewer asks: "if this ever writes to the CRM, what is the audit trail?" Answer in three sentences, including what Enterprise telemetry does and does not give them.

Where this goes next

The exercise sheet in labs/LAB-05 of your practice pack (start with its README) runs the whole pass on the shipped dataset, then on your own export behind the redaction gate, and scores how much of the planted mess you caught. M6 takes the data you can now trust and asks what changed this week.