Build the condition
Create the control in an editable standard using Add control. Keep it disabled while drafting.
Choose a suitable severity and category. Use Suggest only autonomy while reviewing the behaviour. For the full creation workflow, see Create a custom control.
Check the boundary, not just an easy example
These describe the comparison for a subject with eligible current evidence. The overall control also depends on its selected population and evidence coverage.
See what an override changes
Suppose a recorded count is six. It fails against Acme’s default maximum of five. If a deliberate client override sets the maximum to ten, that same count satisfies the new comparison. The environment did not improve. The expectation changed. Record why the exception is appropriate and read the effective value alongside the result. This diagram compares two configurations, not two simultaneous results. Alignr evaluates against the effective setting for that client. See parameters and client overrides for the editing and reset workflow.What this control cannot tell you
A low count does not establish that the remaining findings are low risk. Review severity, affected assets and scanner coverage separately. Counts from different scanner scopes may not be directly comparable. Checkpoint: you can identify the recorded count, effective maximum, source and observation time, and explain why the comparison was satisfied or failed.Next: test and roll out the control
Check representative evidence, missing observations and client settings before relying on the result.