Monitoring frequency says how often a control should be checked. A test is that check. Without a run, the control has not been shown to work, however complete the written procedure is.
What the tests show
The tests list is every named test across implemented controls. It shows which are not tested, overdue, due within 30 days, or in date, and which are effective, partially effective, or ineffective. That is how you find a lapse without opening every control.
A run records effectiveness, a next review date, and evidence. The control is effective only when every test’s latest run is effective and still in date. A test that has not been run stays not tested. The next review date is suggested by the monitoring frequency. Changing that frequency does not rewrite a next review date that is already stored.
When you need to change it
The tests list, add and run a control test, and control test effectiveness describe the list, the run, and the rating.