Document Change Order (DCO)

« Back to Glossary Index

Document Change Order (DCO)

A Document Change Order (DCO) is the formal, controlled mechanism a quality management system (QMS) uses to
propose, review, approve, release, and communicate changes to controlled documents—such as procedures (SOPs),
work instructions, forms, specifications, labeling/IFU content, and quality records templates. A DCO ensures that
the correct version is available at the point of use, that impacts are assessed before release,
and that there is a complete traceable history of what changed, why, when, and who approved it.

Controlled documents
Traceability
Impact assessment

What a DCO typically includes

  • Identification: document title, number, revision, owner, affected sites/lines/systems.
  • Reason & scope: problem/opportunity, regulations or CAPA driving the change, in-scope and out-of-scope items.
  • Change description: concise summary plus redlines/clean copies or marked-up excerpts.
  • Impact assessment: effects on processes, risk files, training, labels/IFU, software validation, suppliers, and records.
  • Approvals: required reviewers/approvers (e.g., process owner, QA/RA, manufacturing, service, labeling).
  • Effectivity: effective date, implementation window, superseded versions, retrieval/disposition of obsolete copies.
  • Post-release actions: training/qualification, system updates, communication plan, verification of implementation.
  • Attachments & references: impacted document list, CAPA/NC links, risk assessments, validation evidence.

DCO vs. ECO (what’s the difference?)

  • DCO controls documents (SOPs, WIs, forms, specs text). It can be used for label/IFU content updates when the underlying design does not change.
  • ECO (Engineering Change Order) controls product/design changes (parts, drawings, BOMs). ECOs often trigger associated DCOs to update the related procedures and records.
  • In many eQMS/PLM systems, ECO and DCO are separate workflows but linked for full traceability.

How the DCO process works (stepwise)

1) Initiation
Submit a change request with reason, scope, affected documents, draft updates, and proposed effectivity. Reference any drivers (audit, CAPA, complaint, regulation).
2) Impact assessment
Evaluate impacts on processes, training, risk management, labeling/IFU, software validation, supplier controls, records, and regulatory submissions as applicable.
3) Review & approval
Route to required functions (document owner, QA/RA, manufacturing/service, labeling). Resolve comments; record electronic or wet signatures per your QMS rules.
4) Release & effectivity
Publish the new revision, withdraw obsolete versions, communicate the change, and ensure the effective date aligns with training and system updates.
5) Implementation verification
Confirm the correct revision is in use at all points of use; complete required training; verify system/configuration updates; close any actions.
6) Records & retention
Store the DCO package (request, approvals, attachments, evidence). Maintain revision history and an auditable trail per retention requirements.

Good practices for robust document control

  • Use unique IDs and clear revisioning with change history visible on each controlled document.
  • Keep redline + clean versions in the DCO package for auditors and users.
  • Link DCOs to CAPA/NC, audits, risk files, and—when relevant—ECOs.
  • Align effectivity with training, labeling changes, and IT system updates to avoid split processes.
  • Prevent use of obsolete copies (stamp, watermark, or restrict access; remove printed copies from workstations).
  • Leverage eQMS with role-based approvals and electronic signatures where permitted.

Quick checklist

  • Reason, scope, and impacted documents clearly identified.
  • Impact assessment covers training, risk, labeling/IFU, suppliers, software validation, and records.
  • Required reviewers/approvers identified; signatures captured.
  • Effectivity and communication plan defined; obsolete versions removed.
  • Implementation verified and evidence filed; audit trail complete.

DCO — FAQs

When do I use a DCO vs. an ECO?
Use a DCO for updates to controlled documents (SOPs, WIs, forms, specs text, label/IFU content without design change). Use an ECO for product/design/BOM/drawing changes. Many changes require both: ECO for design + DCO for procedure/record updates.
What must a DCO contain at minimum?
Document ID/title/revision, reason & scope, change summary (with redlines/clean copy), impact assessment, approvers, effectivity details, and evidence of implementation (training/communications).
How should we manage training for a document change?
Identify all roles impacted; assign training on the new revision; set due dates aligned with effectivity; verify completion before or on the effective date and document competency if required.
Can minor editorial fixes bypass a full DCO?
Define “minor” in your SOP (e.g., spelling, formatting, non-technical clarifications). Many QMSs allow expedited review for editorial changes, but still require controlled release and versioning.
How do we prevent obsolete versions from being used?
Withdraw or restrict access to old files, watermark “OBSOLETE,” remove printed copies at workstations, and push notifications so users know which revision is effective and where to find it.
What about electronic signatures and audit trails?
When using an eQMS, ensure the system enforces unique user IDs, secure sign-off, time stamps, and tamper-evident records. Keep a complete change history and retain DCO packages per your retention policy.
How long should we retain DCO records?
Follow your retention schedule and applicable regulations. Retain at least for the period required to demonstrate traceability of changes that affect released product and post-market activities.
Does a DCO cover labeling/IFU updates?
Yes—when the update is to the controlled label/IFU document itself. If the change results from a design or performance change, coordinate with ECO, risk, and—if applicable—regulatory submissions.