1. Label & Packaging Compliance
  2. Features
  3. Document Control and Training
Feature · Document Control and Training

Document Control and Training

Maintain the label standards people work from and retain acknowledgments against the revision they read.

OverviewDocument Review
Label & Packaging Compliance · Document Control and Training

Document Review

Approval waits for the quality approver

New
TitleVersionEffective dateDocumentStatus
Review cd-579Rev A13 OctDCM-959Review
Review cd-847Rev B21 OctDCM-531Review
Review cd-175Rev C05 OctDCM-378Review
Review cd-761Rev D11 OctDCM-224Review
Review cd-956Rev E25 OctDCM-699Review
6 of 6 records
Review cd-579Controlled documents · CD-77093
Review
VersionRev A
Effective date13 Oct
DocumentDCM-959
Example screen with sample data

What you can do

Put the reviewed instruction beside the work

Document Controller maintains controlled specifications, procedures and label standards. Each document carries a title, version, effective date, attachment and review state. Quality Approver reviews the revision under the agreed document policy before staff use it as an approved instruction.

Training acknowledgments connect a person to the exact document record and the date they acknowledged it. This gives Auditor a clear answer when asking which revision a person read. Acknowledging an earlier version should not be presented as acknowledgment of a later change to the allergen review procedure.

How the work is organized

  • Document revision. Draft identifies preparation and Review identifies a revision awaiting the agreed decision. Approved and Obsolete distinguish usable instructions from superseded material.
  • Effective date. Document Controller records when the instruction takes effect and coordinates the handoff with the teams that use it. A future effective date needs an agreed operating plan.
  • Person acknowledgment. Record the person, the linked document and when the acknowledgment occurred. Retain that connection when the instruction is revised so the history remains interpretable.

What to agree during setup

Agree how titles and versions identify a document across revisions. Decide who owns the source attachment and who approves its content. The document review should consider whether a change affects the label check plan, inspection requirements or the evidence expected from an Inspector.

Document Controller and Quality Approver should also agree who needs to read each change. Acknowledgment history records completed acknowledgments; managers still need a defined audience before they can judge coverage. Decide how that audience is maintained as part of the rollout and how staff receive the new instruction.

Check the handoff on an actual case

Revise the instruction for checking multilingual allergen statements. Document Controller creates the revision with its attachment and intended effective date, then presents it for review. Quality Approver examines the wording and approves it under the agreed policy. Staff should be able to identify the approved revision before conducting the next affected inspection.

Record an Inspector’s acknowledgment against the new document. Ask Auditor to follow the acknowledgment to the exact revision and compare it with an older acknowledgment. The older entry should continue to describe what the person read at that time. It should not be changed merely because the document title remains familiar.

Finish the rehearsal by examining a draft replacement. Confirm that staff can distinguish the pending revision from the currently approved instruction. Then agree when the older document becomes Obsolete and how its attachment remains available for explaining earlier inspection work. The review is complete when the team can follow both the current instruction and its historical use.

What your team sees

  • Document Review — Document revisions awaiting the agreed content approval.
  • Training Acknowledgment History — People and acknowledgment dates linked to the document revision they read.

Follow the work through

Use audit and document follow-up, then rehearse the changed instruction through inspection and disposition.

What it keeps track of

Data model
Controlled documents
Version-controlled specifications, procedures and label standards
Training acknowledgments
Records that a person acknowledged a controlled document revision
People
Staff and contractors who perform inspections, audits, reviews and approvals

Who uses it

Permissions
Document Controller
Maintains revisions and acknowledgments.
Quality Approver
Approves document content under the agreed policy.
Auditor
Reads the revision and acknowledgment history during follow-up.

Set up Label & Packaging Compliance your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started