The anatomy of a rule
A rule is a trigger, optional conditions, and actions. Three trigger kinds:
| Kind | Fires when | Example |
|---|---|---|
| Event | Something happens in the system | A new client is created → build their standard task group |
| Schedule | A cron-style clock says so | Every weekday 07:00 → chase clients with missing bank statements |
| Manual | Someone presses Run | Month-start → post the opening-balance journals |
AI-drafted, human-approved
Describe the rule in a sentence and the AI drafts the trigger, conditions and actions for you to review and edit before it ever runs. The draft is a starting point, not an authority — no rule runs until a person saves it.
Scoping
Rules can scope to specific clients or task groups, so “chase quarterly VAT clients” doesn’t bother the annual ones.
Test runs and history
Test a rule on demand and read exactly what it would do. Every real run lands in the history with its output downloadable — when a client asks “why did I get this reminder?”, the answer is a row, not a shrug.
TipStart with the chasing. A schedule rule that nudges clients for missing records is the highest-return automation most practices ship in week one.