Chapters · 5 of 8
- 01 · Choose the Level of Automation
- 02 · Respect Permissions, Consent, and Ownership
- 03 · Preview Before Changing Important Data
- 04 · Decide Where People Approve
- 05 · Add Volume, Spend, and Time Limits
- 06 · Plan for Stop, Undo, and Recovery
- 07 · Test Unsafe Requests
- 08 · Capstone: Approve a Safe Automation Plan
About 16 min · Lesson and activity
Chapter 5 of 80 complete
Add Volume, Spend, and Time Limits
Meter through one gate, defer rather than drop, and publish what the control does not cover.
3b · volume spend and time limits
Limit workload, spend, and runtime
Start with the example, then try it yourself. The last case is optional practice.
See the situation
Start with the situation below. Next, we will work through an example together before you try the activity.
The case
A cap separated from the enablement decision
An operating limit must show its counted units, deferred work, and spend it cannot observe.
- Daily cap
- Configured, correct, enforced
- Where it is displayed
- A settings page two clicks away
- Where rules get enabled
- A different page
- Times anyone checked it before enabling a rule
- Not measurable, and the answer is obvious
- Over-limit behavior
- Records flagged deferred, re-processed next cycle
Your place saves as you go.
Chapter 5 of 80 complete