When the scheme adopts a new or changed requirement that touches a client, the body must make sure every affected client hears about it. It must verify that clients have implemented the changes and take the actions the scheme requires. It must also consider other changes that affect certification, including changes the client starts, and decide what action is appropriate. The action can include evaluation, review, a decision, revised certification documentation to extend or reduce scope, or revised surveillance documentation. Those actions must follow the relevant parts of the process, and the records must include the reason for leaving any of them out, for example where a changed requirement is not a product requirement and no evaluation, review or decision is needed.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.