Operations Engine · plain-English guide
How to read Hygiene
Hygiene crm data integrity. This guide explains what it produces, what each part means, and how it stays honest — so you can act on the output with confidence.
Takes
Pipeline data + audit scope
Gives
Hygiene report + forecast impact
The data it uses: A pipeline export — deals with stage, amount, close date, owner.
Watch how it works
How to read the output
Findings
Ranked blocker → warning → advisory. Blockers corrupt the forecast; advisory is cleanup.
Forecast impact
Raw pipeline value versus the value sitting on dirty rows.
Score
Whether you can trust the pipeline for a forecast at all.
The terms it uses
- Blocker
- A data problem that directly corrupts the forecast — missing amount, impossible stage, negative value.
- At-risk value
- The pipeline dollars carried by rows with blockers or warnings.
How it stays honest
Every agent separates what it measured from your data from what it inferred. You always know which is which.
Measured
- ✓Rows + field values
- ✓Severity ordering + blocker count (computed)
- ✓Score (computed)
Inferred
- ~Impact per finding
- ~At-risk value
- ~Verdict
Questions people ask
What counts as a blocker?+
Anything that makes the number wrong: missing or negative amounts, no close date, deals with no owner, stage that cannot coexist with the date.
Now read the real thing.
Run Hygiene on your own data and compare the output to this guide. If it matches, you can trust it.