Data-Quality Gate
The governed-revenue-model gate the pipeline council runs before trusting a forecast: hygiene-check every open deal, score the book, pass or fail.
Included with crocronjob . A seat without it sees an upsell here instead of the page.
Overview
Data-Quality Gate enforces the discipline a governed revenue model requires: a forecast is only as trustworthy as the pipeline it reads. Before the council trusts a rollup, the gate checks every open deal for the hygiene the model depends on, scores the book, and passes or fails, so a clean forecast can never be built on a messy pipeline.
What it is for, on the page. Under the headline, this page says what it produces, what makes it run, and where the output lands. Every Work page reads that line from one registry, so the three answers cannot drift from the page.
The hygiene checks
Each deal is checked for a real amount, a close date that is set and in the future, a stage, an owner, and recent activity. A missing field, a close date already in the past, or a deal untouched for a month is a concrete, checkable defect, not a vague sense that the data is off. Every issue names the specific deal and the specific problem, so fixing them is a worklist, not a hunt.
The gate
The book's data-quality score is the share of deals with no hygiene issues. The gate passes when that score is at or above the threshold (85 by default, because a governed model needs a genuinely clean book), and fails otherwise, with the worst offenders listed most-broken first. This is the go/no-go the pipeline council reads before it stands behind a number.
Deterministic
The gate is deterministic: the same pipeline always produces the same score and the same offender list, so the result holds up in a forecast review. It only ever reports defects that are actually present, and never invents a data problem to fail a book.