In quality management, a document can provide information used to plan or perform work, while a record preserves information about activities, results or decisions. The categories overlap within documented information, but the distinction helps explain why revising an instruction differs from correcting historical evidence.
The documentation guide describes their relationship. Do not classify solely by file extension: a spreadsheet can contain an instruction, a blank form, completed records or several of these with different control needs.
Begin with purpose rather than appearance
Ask what the information does. A work instruction explains how to perform an activity or apply criteria. A completed check records what happened in a particular case. A policy expresses direction, while a review record preserves decisions and their basis.
The same system can hold all of these. An electronic workflow may display current instructions and retain approvals. Treating the entire application as one document can obscure the different responsibilities and integrity needs.
A file’s age is not decisive. An old instruction may remain current, and a newly created record can already be historical evidence of an event.
Understand the transition from form to record
A blank form structures future information capture. Its design can be reviewed, approved and revised. Once completed, it contains evidence about an identified case and needs protection of that meaning.
Changing the form for future work should not silently alter previous entries. If a new field is added, earlier records should not be made to appear as though the information was captured at the original time when it was not.
| Item | Primary purpose | Typical control concern |
|---|---|---|
| Current instruction | Direct an activity | Approved version available at use |
| Blank check form | Structure information capture | Suitable fields and current design |
| Completed check | Preserve a result | Context, integrity and retrieval |
| Approval entry | Record an authorised decision | Identity, authority and timing |
| Superseded instruction | Explain an earlier arrangement | Historical status and restricted current use |
The examples are illustrative. The organisation should identify the actual purpose and controls rather than rely on labels alone.
Revise operational information deliberately
A revised instruction can change methods, acceptance criteria or responsibility. Evaluate the effect on users, work in progress, training, forms and related systems. Determine when the new arrangement applies.
Users need to distinguish current, draft and superseded status. A recent modification date may not establish approval or applicability. An effective date and controlled source can be useful depending on the context.
The revision control article explains why a change should be considered as an operational event, not only a version-number update.
Correct records without rewriting history
Records can contain errors and may need correction. Preserve an appropriate trail so a later reviewer can understand the change and its basis. The method should reflect consequence and the medium used.
Do not backdate an authorisation or create a replacement that falsely suggests an activity was documented at the time. If a later review was performed, identify it as such and explain what it establishes.
An accurate correction can improve evidence quality. Concealing the original entry or uncertainty can undermine reliability, even when the new value looks more complete.
Set retention according to need
An instruction may be maintained for current use while superseded versions are retained where necessary to interpret earlier work. Records may need retention for operational, customer, contractual, legal or regulatory purposes.
Do not assume every item shares one universal retention period. Identify the purpose and applicable obligations. An investigation or other relevant hold can affect disposal decisions.
Retention should preserve usable information. A record without its case reference or applicable criteria may be difficult to interpret even when the file remains available.
Evaluate evidence in context
A current procedure shows an intended arrangement; it does not prove that every case followed it. A completed record can support a conclusion about a particular activity while having limits regarding wider system effectiveness.
The record control explanation examines context, access and integrity. Auditors should connect information to actual criteria rather than treat signatures or document volume as automatic proof.
If an expected record is absent, determine whether it was required and whether other authorised evidence exists. Absence of a preferred form is not always absence of the activity, but missing required evidence can itself be consequential.
Use the distinction to improve the system
Review where people confuse changing a template with changing completed records, or where historical information is presented as current instruction. Clarify responsibilities and system behaviour at those points.
The distinction is useful because it protects two different needs: reliable direction for current work and truthful evidence of past work. A good information system supports both, with changes and corrections that preserve meaning rather than merely make files look consistent.
A system view can change while the underlying historical record remains intact. Confirm what an export or report actually represents before assuming that a changed display means the evidence was altered. Evaluate the data, context and correction trail together.