An organization may ask a current or prospective external provider, including a separate division of the same organization, to submit a quality plan for a case. Requester and provider should both think through why a plan is being used and what it may deliver. The requester should use risk-based thinking about the nature of the case, how providers are assessed and chosen, and where benefits may lie, which can help both sides. Weighing the risks opens further choices when asking for plans: stating the results wanted rather than the methods and resources (as performance-based contracts do) leaves room for the provider to innovate in methods, practice and resources; setting only minimum controls and documented information lets the provider use its own processes and experience; and defining plan requirements for the case instead of demanding conformity with, for instance, ISO 9001 or another management system standard lets providers whose systems are at different stages of maturity take part. Sector examples of plan specifications appear in codes of practice issued by industries, in requests for offers and other public sources, but they need adapting to the case. Plan requirements can also sit within specifications for other plans, such as service, project, construction or production and installation management plans.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.