Most process documents are not rules
They are statements of intent. "Opportunities should be kept up to date" cannot be evaluated against a record, which is why it has never been enforced.
Learn what separates a rule that can be evaluated from a policy that can only be quoted, before you author any of your own.
Governance in this model is not a review layer bolted on afterwards; it is the rules, the routing and the evidence trail, and all three depend on rules that can actually be evaluated. Almost every organization already has documents describing how things should be done, and almost none of them contain rules in this sense.
The gap is specific: a policy states an intention, and a rule states a condition a record either meets or does not. "Opportunities should be kept up to date" is an intention that has probably been in a handbook for years without ever being enforced, because there is nothing in it to check. Turning that into something checkable is the skill this guide teaches and the next lesson makes you practice.
Read this one differently from a normal guide, because the next lesson has you write five rules of your own and its quality depends entirely on this. Pay particular attention to how a rule expresses its consequence and its exceptions, not just its condition, those are the parts people skip, and skipping them is what produces a rule that fires constantly and gets switched off within a fortnight.
It is also worth separating two things that feel connected and are not. Enforceable does not mean strict. A rule can be generous, with a long grace period and wide exceptions, and still be perfectly evaluable. The property that matters is whether the condition can be tested, not how demanding it is.

Now read the guide
This lesson is the orientation. The material itself lives on its own page, kept in one place so it stays current everywhere it is referenced.
You should be able to answer each of these from memory before opening it. Recalling the answer is what makes it stick; recognizing it when you read it does not.
A policy states an intention; a rule states a condition a record either meets or does not. "Opportunities should be kept up to date" has nothing in it to check, which is why it has never been enforced.
Covered in full: Writing rules agents can actually enforce →
No. A rule can be generous, with a long grace period and wide exceptions, and still be perfectly evaluable. The property that matters is whether the condition can be tested.
They are statements of intent. "Opportunities should be kept up to date" cannot be evaluated against a record, which is why it has never been enforced.
Read this as preparation, not as background. The next lesson is authoring, and the quality of your five depends on this one.
A rule can be lenient and still be evaluable. The property that matters is whether a machine can tell if it was met.
See agents carry the repeatable work of GTM across sales, marketing, customer success, and RevOps. Every action prepared, reviewed, and recorded. Fictional data, real product.
Explore the demo