Quality record

From OrganicDesign Wiki

This article is a stub. Stubs are articles that have not yet received substantial attention from the authors. They are short or insufficient pieces of information and require additions to further increase the article's usefulness. The project values stubs as useful first steps toward complete articles. Check Organic Design Conventions if new to the site. See Wiki workflow and Wikipedia:Stub for more details on this process. See all the stubs in Category:Stubs

Quality records are secondary outputs that provide the evidence that the appropriate activities took place and that the execution of those activities met the required standards.
Examples of quality records include:

• test logs
• minutes from meetings
• audit reports,
• engineering notebooks,
• action item lists,
• status reports.
• receipts
• email message(s)

For each quality record, I list:

• Owner
• Where that record will be maintained (e.g. project file, specific database)
• The minimum retention period for that record (the minimum length of time that the

record will be kept available for access)

For Aperious, a ticket is generated by a procedure and is tracked in the CRM, and it is reviewed regularly. See also deliverable.

• see also Work order

Microism of all issues here: the absolute need to track this and every essential task from inception to completion. See also History and Audit log.

each quality record indicates what ARTICLE created it. the name of the article helps in rule routing (going to the right source) and troubleshooting (what article has problems if it is missing data repetedly, etc). you will be able to set your view level of detail....