A quality plan sets out how the organization will deliver a particular output (a product, process, service, contract or project). Plans are prepared where they are judged necessary to satisfy the needs and expectations attached to that case. With a management system already in place, a plan may be wanted because a customer asks for it or for other good reasons; with no such system, a plan can supply the framework for meeting the case's requirements and help the organization build its own system and processes. The organization should decide when quality plans are needed. Situations where they can be useful or necessary include: demonstrating how the quality management system applies to the case; meeting requirements set by customers, other interested parties or the organization itself; developing and validating new products, services or processes; showing inside or outside the organization how requirements will be satisfied; organizing and managing the work toward requirements and quality objectives; making best use of resources toward those objectives; reducing the risk of failing to meet requirements; controlling the setting up of a new or changed organization, site or partnership; giving a footing for monitoring quality compliance and assessing it; and operating where no management system exists.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.