Two companies running the same software can get completely different results, and the difference is almost entirely here.
Why it matters
A planner has no opinion about pest control. Everything it knows about your operation arrives through rules. Leave them at their defaults and it will optimise confidently for a business that is not yours — and the output will be rejected every morning by people who cannot say precisely why it is wrong.
How you notice it slipping
Rules were set during implementation and never revisited, although the business has changed twice since. Nobody can produce the list. Overrides have become the real policy, which means the written rules describe a company that no longer exists.
What to do
Rules also have a cost in strictness. Every one narrows what the planner may do, so a rule carried for years out of caution can quietly be costing miles. The review is as much about removing rules as adding them.
Keep the list short enough to read in one sitting and review it when the business changes, not on a fixed date. The useful test is simple: when dispatch overrides the plan repeatedly in the same way, a rule is missing or wrong — the override is the specification nobody wrote down.