A workshop manual library needs a way to answer two questions quickly: where is the document, and what evidence connects it to the machine or task? A folder full of vaguely named files makes both questions harder. A simple register gives each document a stable identity while keeping unanswered applicability questions visible.
The workflow below is an editorial suggestion for organizing documents. It does not establish machine compatibility, authorize copying or replace the applicable manufacturer’s instructions.
Give each document one register entry
Start with the documents already held legitimately by the workshop. Assign each one a short internal reference, such as DOC-001. Keep that reference stable when the storage location changes. A second copy of the same document should point to the same entry; a different edition should have its own entry connected to the earlier one.
| Register field | What to record |
|---|---|
| Internal reference | A stable reference used in the file name or shelf label |
| Document identity | Title, publisher, publication number, language and stated edition or revision |
| Document type and scope | The contents or section relevant to the intended task |
| Applicability evidence | Where the model or serial-range statement was verified, or the question still open |
| Location and access | The controlled file location or physical shelf, and who maintains access |
| Review history | Date checked, reviewer, result and any related document entry |
If the edition is not stated, write “not stated” rather than guessing from a file’s creation date. Our guide to checking a manual’s edition and revision explains what to inspect before recording those fields.
Keep evidence separate from a convenient label
A folder named after a machine is useful for navigation, but the name itself is not an applicability check. Use a field such as “verified against the stated serial range” only when the document actually supports that entry. Otherwise record “awaiting confirmation” and the specific missing information.
Keep machine identifiers in the workshop’s private records. A public article, shared screenshot or broadly accessible folder does not need a customer’s serial number. For selection questions, use the model and serial-number matching guide before changing the register’s applicability status.
Preserve a readable change history
When another edition arrives, add a separate entry and link it to the earlier one. Record what was checked and why the workshop chose a document for the relevant machine or task. Do not label an older document “superseded for all machines” unless the publisher’s applicability information supports that conclusion.
Move unreviewed documents to a clearly marked review area. Keeping them outside the normal working set reduces the chance that someone mistakes a newly received file for a checked reference. Retain earlier editions only where the workshop has the right to keep them.
Test retrieval before relying on the system
- Ask someone other than the person who built the register to find one document from its internal reference.
- Confirm that the selected entry opens the intended file or points to the correct physical copy.
- Check that the cover and contents agree with the register, including the language and publication number.
- Check any backup under the same access and licensing limits, and confirm that the restored copy is readable.
- Record broken links, missing copies and unresolved questions with a named person responsible for following up.
If the intended task needs a different document type, correct the request before reorganizing the folders. The service manual versus parts catalog guide offers a starting point for identifying that distinction.
A useful library is one that makes identity, location and uncertainty easy to see. Review the register when a machine, document or storage location changes, and keep the evidence behind each decision available to the people who use it.
