Can a compliance tool be safer than doing it by hand?

The choices were automated regulation detection, templates applied at a chosen scope, or a checklist without enforcement. We had three weeks and one engineer against statutes carrying triple damages.

We chose templates with a human checking them before they went out. A compliance tool that is wrong is worse than none: property managers applying rules by hand knew they might be wrong, but a system that says they are covered when they are not turns an anxious guess into a confident mistake, and the statute does not care which was made. Automation would have had to be right on its own, which we could not prove in three weeks; templating puts a person between the system and the filing. It shipped, with Legal signing off on the language rather than an inference engine.

We considered applying based on the selected fee, dynamically detecting applicable regulations, or author-selected explicit scope. The first bulk-applied version did not scale beyond one portfolio shape. The second pulled in regulations to flag issues automatically; it solved scalability but was not technically feasible, and my note at the time was that it was too clever for its own good.

We chose explicit scope: the author chooses and can see whether a fee, policy, or disclosure applies at company, state, or community level. That adds work per rule, repeatedly across portfolios with hundreds of communities, so we included bulk edits across management-company levels, which partners had asked for first. Version three shipped and was the least interesting of the three.