TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I like having a Quality Manual that briefly states the governing regulations, standards, business needs, and heck, who knows, maybe even ethics and values. All of these are requirements. The Quality Manual describes briefly (there's that word again) how each quality procedure (output) answers specific requirements (inputs) and how the quality procedures interact. All of this is de rigueur for regulated quality systems.
The "justification" for a procedure is that there's a policy that requires it. Your policies need to be written in a way that makes clear to the reader that they mandate specific procedures.
The justification for a policy is "because someone said so," that someone being either your upper management, some govt regulator, your customers, the ISO or other higher power that scares the bejesus out of your company's employees.
Doc-To-Help: The Quickest Way to Author and Publish Online Help, Policy & Procedure Guides, eBooks, and more using Microsoft Word | http://bit.ly/doctohelp2015