Process Governance, Compliance, Audit & Version Control Guides

Practical guides to controlled documents, SOP versions, audits, corrective actions, change control, compliance and process governance, with worked workflows.

Version Control

  • How to version control a document — How to version control a document in practice: pick a decimal-versus-whole-number scheme, print version, date and approver on every page, define what counts as a major change, and keep exactly one current copy.
  • How to track changes in a process — How to track changes in a process: QueryChart's Change Log names who edited a decision rule or threshold, the field's previous value, and its current value, so nobody reconstructs an edit from memory.
  • Document version control best practices — Document version control best practices for teams that already have a numbering scheme: keep it stable, fix where version, date and approver appear, stop parallel edits of the current copy, and log every no-change review.
  • Version control vs change control: what's the difference — Version control tracks which revision of a document is current and what changed; change control decides whether a proposed change is allowed to happen at all, and who has to approve it first.
  • Version control vs document control — Version control tracks successive states of a document; document control governs its full lifecycle from creation and approval to distribution and retirement. See a worked QueryChart process and practical steps for applying it.
  • What is document version control? — Document version control identifies the current approved document, preserves earlier revisions, and records who changed and approved each issue. See a worked QueryChart process and practical steps for applying it.

Document Control

  • How to create a document control process — How to build a document control process that governs the superseded copy as well as the new one: an identifier and a revision, one authoritative location, a withdrawal step, and a dated periodic review.
  • What is document control? — Document control is the set of rules and records that keeps the right approved document available while preventing obsolete copies from being used. See a worked QueryChart process and practical steps for applying it.
  • Document control checklist — A document control checklist tests whether a controlled item is identified, reviewed, approved, available, protected, current and properly retired. See a worked QueryChart workflow and the checks needed to use it.
  • How to create a document numbering system — A document numbering system gives each controlled item one stable identifier and each approved issue a separate revision, so identity never changes when content does. See a worked QueryChart workflow and the checks needed to use it.
  • How to maintain a document register — A document register is the authoritative index of controlled items, showing each ID, owner, effective revision, status, location and next review date. See a worked QueryChart workflow and the checks needed to use it.
  • How to manage obsolete documents — Manage obsolete documents by withdrawing them from points of use, marking their status, retaining required history and directing readers to the effective replacement. See a worked QueryChart workflow and the checks needed to use it.
  • How to set up document control — Set up document control by defining the inventory, owners, current location, approval authority and withdrawal points before moving existing files.
  • How to control documents and records — Control current instructions through review and issue; protect completed records through identification, retention, retrieval and authorized disposition.
  • How to create a controlled document — Create a controlled document with a stable ID, owner, scope, revision, review and approval evidence, effective date and current-copy location.
  • How to create a document review cycle — Create a document review cycle with named owners, risk-based due dates, change triggers, evidence of review and explicit keep, revise or retire outcomes.
  • Document control best practices — Practical document control habits for current-copy access, approval evidence, external documents, withdrawn issues and review exceptions.

SOP Management

  • How to version control an SOP — SOP version control means numbering every procedure revision, routing safety-critical changes through hands-on retraining and a signed checklist instead of read-and-acknowledge, and retiring the copy it replaces.
  • How often should SOPs be reviewed? — Review SOPs on a risk-based schedule and whenever a material event changes the work; there is no universal review interval for every organization. See a worked QueryChart workflow and the checks needed to use it.
  • How to approve an SOP — Approve an SOP only after technical accuracy, affected controls, exceptions and required training have been reviewed by authorized roles. See a worked QueryChart workflow and the checks needed to use it.
  • How to organize SOPs — Organize SOPs by stable ID, task and owner in one controlled library, with current status, effective revision and point-of-use links. See a worked QueryChart workflow and the checks needed to use it.
  • How to retire an SOP — Retire an SOP by deciding it is no longer applicable, approving withdrawal, removing every point-of-use copy and preserving its required history. See a worked QueryChart workflow and the checks needed to use it.
  • How to review an SOP — Review an SOP by checking its steps against real work, exceptions, controls and records, then record whether to reaffirm, revise or retire it. See a worked QueryChart workflow and the checks needed to use it.
  • What is SOP management? — SOP management controls the creation, review, approval, publication, training, revision and retirement of repeatable work instructions. See a worked QueryChart workflow and the checks needed to use it.
  • How to create an SOP management system — Build an SOP library with an inventory, process owners, approval authority, current-copy access, training triggers and a review schedule.
  • How to update an SOP — Update an SOP by documenting the trigger, assessing affected steps, reviewing a fixed draft, approving a new issue and withdrawing the old one.
  • SOP management best practices — Operate an SOP library with clear ownership, usable current copies, review triggers, change impact checks, training evidence and retirement controls.

Audit

  • How to conduct an internal audit — Conduct an internal audit by defining criteria and scope, assigning an independent auditor, sampling evidence, recording findings and checking corrective actions. See a worked QueryChart process and practical steps for applying it.
  • How to manage audit findings — Manage audit findings by recording the requirement and evidence, assigning an owner, agreeing an action, and verifying that the gap is closed. See a worked QueryChart process and practical steps for applying it.
  • How to track corrective actions — Track corrective actions with an owner, due date, linked finding, progress evidence, escalation rule and a separate effectiveness check. See a worked QueryChart process and practical steps for applying it.

Audit Trails

  • Audit trail vs version history — Version history shows successive content states; an audit trail records the wider sequence of actions and decisions surrounding those states. See a worked QueryChart process and practical steps for applying it.
  • What is an audit trail? — An audit trail is a time-ordered record of consequential actions: who did what, when, to which record, and what state resulted. See a worked QueryChart process and practical steps for applying it.

Compliance

  • How to document compliance procedures — Document a compliance procedure by linking each required action to its trigger, owner, control objective, evidence and exception route. See a worked QueryChart process and practical steps for applying it.
  • What is compliance management? — Compliance management turns applicable obligations into owned controls, repeatable procedures, evidence, monitoring and a route for exceptions. See a worked QueryChart process and practical steps for applying it.

Policies & Procedures

  • Policy vs procedure vs SOP — A policy states the rule or intent; a procedure describes the required sequence; an SOP is a standardized procedure for a repeatable task. See a worked QueryChart process and practical steps for applying it.

Change Control

  • How to create a change control process — How to design a change control process: define your change categories, keep the pre-approved list short, require a rollback plan, and draw the emergency route rather than pretending it does not exist.
  • What is change control? — Change control is a formal path for proposing, assessing, approving, implementing and verifying a change before it is closed. See a worked QueryChart process and practical steps for applying it.

Approvals

  • How to create a document approval workflow — How to build a document approval workflow that routes before it signs: classify the change, let the document type set its reviewers, and give an editorial revision a route that skips review.

Process Governance

  • How to create a process governance framework — Create a process governance framework by assigning owners, approval rights, review triggers, version rules and a consistent route for exceptions. See a worked QueryChart process and practical steps for applying it.
  • How to maintain a process library — Maintain a process library with one approved copy per process, clear ownership, searchable metadata, review triggers and archived history. See a worked QueryChart process and practical steps for applying it.
  • What is process governance? — Process governance defines who owns a process, who may approve changes, how current versions are published and how performance is reviewed. See a worked QueryChart process and practical steps for applying it.

Process Documentation

  • How to keep process documentation up to date — Keep process documentation current with a named owner, scheduled and event-driven reviews, change approval and a check against actual work. See a worked QueryChart process and practical steps for applying it.

Quality Management

  • How to create a CAPA process — How to design a CAPA process: separate correction from corrective action, gate full investigations on risk, require a verified root cause, and check effectiveness before closing.

ISO

  • Document control for ISO 9001 — For ISO 9001, document control means making necessary documented information identifiable, suitable, available where needed and protected through its lifecycle. See a worked QueryChart process and practical steps for applying it.
  • Version control for ISO 9001 — Version control for ISO 9001 makes the effective issue of documented information identifiable and connects each change to review and approval evidence. See a worked QueryChart process and practical steps for applying it.

GRC

  • How to create a risk assessment process — How to design a risk assessment process: agree the criteria and appetite before scoring, describe risks as cause, event and consequence, score inherent and residual separately, and approve acceptance.

Browse all Process mapping guides