An approved workflow is an assignment
Business units may designate tasks for AI assistance after the Center of Excellence approves the tool, input class and review route. A colleague assigned that workflow must complete it or record a reason it could not be used. An unread generated draft does not count as completion.
The non-use exception
A colleague may decline a required AI step when the input is restricted, the service is unavailable, the approved use case does not fit or a material output problem is identified. The colleague records the reason and continues through the approved manual route. The exception is reviewed for process improvement, not treated as disloyalty.
Performance and discipline
Managers may review repeated unexplained avoidance of a mandatory approved process. Conversely, raw prompt counts and automatic acceptance of generated output are not performance measures. Usual can discipline a colleague for knowingly bypassing a required control in either direction: using a forbidden service or claiming to have reviewed work that no human read.
The practical contradiction
The weekly adoption report asks who did not use AI. The monthly control report asks who used it without adequate review. Both reports may correctly identify the same person; neither report is permitted to issue a final finding without examining the work.
