The organization should work out where quality plans could help or are needed: to show how its QMS applies to a specific case; to satisfy statutory, regulatory or customer requirements; when new products or processes are being developed and validated; to show inside or outside the organization how quality requirements are going to be met; to organize and run activities so quality requirements and objectives are met; to make the best use of resources; to reduce the risk that requirements are missed; as a basis for monitoring compliance and assessing it; or where no documented QMS exists. An organization whose QMS is established may find it already meets these needs and decide a separate plan is unnecessary.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.