Home/Process library/From change to trained team
Process library · Quality managementFrom change request to trained team
A work instruction changes. The change is assessed and approved, the new version becomes effective, the old one is withdrawn, and everyone who works with it is asked to read and confirm it. Including the people on the shop floor who never log in.
See a change workflow in M-Files See the process
In short
In this scenario a manufacturer handles every change to a controlled document through a change request in M-Files for Quality. The request holds the impact assessment: which documents, products, processes and training are affected. After approval, the new version goes through review and approval and becomes effective; the old version is withdrawn. Learning rules then assign training by role, process, product line or site, and a major revision asks everyone involved to read and confirm it again. Training records show who completed what, including staff without a user account. SoftAdvice sets up and documents the process.
A new version is only finished when people work with it
A procedure has changed. On the shop floor, the old version is still pinned to the wall.
Procedures and work instructions change all the time: a new machine, a complaint, an audit finding. Publishing the new version is the easy part.
The hard part is knowing what else the change touches, making sure nobody still uses the old printout, and proving that every operator read the new version.
- Impact on documents, products and training
- One effective version, old ones withdrawn
- Training assigned by rules, not by memory
- Records for staff without a login
What happens with every change, and every year
Changes come in all year. The rules make sure the follow-up is the same every time.
Every change
Assess the impact
The change request lists the documents, products, processes and training it affects.
Every approval
Publish one version
The new version becomes effective as a PDF; the old one is withdrawn everywhere at once.
Every new version
Train the right people
Learning rules assign read-and-confirm or training to the roles and sites concerned.
Every new colleague
Start with the right set
A new role brings its own training assignments with due dates.
Every review period
Review the document
Documents come back for review when their review period ends.
From change request to trained team, step by step
The change, the documents and the training stay linked, so the auditor can follow the whole trail.
Request and assess
Anyone can raise a change request. The owner records the impact on documents, products, processes and training.
Approve
The process owner approves; for product changes the product owner and, where needed, regulatory or customer quality review it too.
Revise and release
The document goes through review and approval with an electronic signature, becomes effective, and the old version is made obsolete.
Train and record
Learning rules assign the training. People confirm in M-Files, or attendance is recorded for staff without a login.
Watch the process run
Every lane is a role. Follow one change from the request to the confirmed training, and see what M-Files does by itself.
A new machine, a complaint or an audit finding asks for a different way of working.
The change owner lists the documents, products, processes and training the change affects.
The process owner approves or rejects the change, with a reason that stays in the history.
The request is closed with its reason; nothing changes in the effective documents.
The author edits a new draft. The effective version stays in use until the new one is approved.
Reviewers comment, and the approver signs the new version electronically.
M-Files publishes the effective version as a PDF and makes the old one obsolete everywhere at once.
Learning rules assign read-and-confirm to every role, process or site linked to the document.
Colleagues confirm in M-Files. For staff without a login, attendance at a toolbox meeting is recorded.
M-Files keeps the training record and reminds whoever is overdue.
Change, document and training records are linked, ready for the auditor.
First understand. Then improve. Only then automate.
We design the process and its decisions first. Only then do we let the software carry the routine.
Judgement stays with your team
These steps need knowledge of the client, the product or the risk, so a person owns them.
- Request and assess impact
- Change approved?
- Revise the document
- Review and approve
- Read and confirm
What the technology carries
These steps run by themselves, and every action is logged.
- Publish, withdraw old version
- Assign training by rule
- Record, remind if overdue
The document and the training move together
Once a new version becomes effective, the training follows automatically. Overdue training shows up by itself.
Controlled document
Training
What the auditor can retrieve
Every step leaves a record, linked to the change. Nothing has to be collected afterwards.
| Step | Evidence | Who needs to act |
|---|---|---|
| Change request | The request with its reason and impact assessment on documents, products, processes and training. | Change owner |
| Approval | Who approved the change and the new version, and when, with electronic signature. | Process owner, approver |
| Release | The effective version as PDF, the date it became effective and the withdrawn version in the history. | Done by M-Files |
| Training | Who had to read or be trained, by which rule, and who confirmed when; attendance records for staff without a login. | Every colleague linked to the document |
From signing attendance lists to training that follows the document
The training coordinator no longer works out who needs to read what; the rules do, and overdue training is visible.
Before
- Changes approved by e-mail
- Old printouts still on the line
- Training matrix kept by hand
- Paper lists for the shop floor
Now
- Impact assessed in the request
- One effective version, old one withdrawn
- Training assigned by learning rules
- Records for everyone, with or without login
M-Files for Quality, set up for change and training
The quality solution from M-Files, configured and documented by SoftAdvice.
Change control
Change requests with impact assessment, approvals and links to every affected document and training.
Version control and PDF release
One effective version as a PDF; earlier versions stay in the history, never on the shop floor.
Learning rules and training records
Training assigned by role, process, product line or site, with records ready for the auditor.
Questions about this scenario
Do operators need an M-Files licence to be trained?
No. Training of people who are not system users, such as production or temporary workers, can be recorded too, for example with an attendance record from a toolbox meeting.
Is this a learning management system?
No. M-Files assigns training and keeps the records and course material. E-learning content and quizzes stay in your LMS if you have one.
What triggers retraining?
You decide. Typically a major revision of a document asks everyone linked to it to read and confirm again; a minor correction does not.
Can we stop people from printing controlled documents?
Yes, an optional module can block printing and downloading for selected documents, so the effective version in M-Files is the only one in use.
Who still works with last year’s instruction?
In a one-hour demo we show change control and training in M-Files, from request to confirmed training. Want to map your own process first? Discovery is the next step.
