The Change Requests page logs requests to modify documents, processes and systems, with an approval workflow and implementation tracking (EN ISO/IEC 17025:2017 §8.3, §7.11.2).
Found under: ISO 17025 → Quality System → Change Requests.
| Button | Action |
|---|---|
| Add — Create a new record | |
| Columns — Show/hide table columns | |
| Filters — Open/close the filter panel. A red dot indicates active filters | |
| Export CSV — Download table data as a CSV file | |
| Orientation — Toggle between portrait and landscape printing | |
| Print — Generate a PDF of the current view | |
| Help — Open the help dialog | |
| Search — Quick search through table data |
Clicking the icon on each row shows:
| Field | Description |
|---|---|
| Request No. | Unique request code. Leave blank for auto-numbering. |
| Title | Brief description of the change request |
| Status | Submitted, Approved, Rejected, Implemented or Verified — colour-coded. Only the Lab Director or the Quality Manager may approve requests. |
| Priority | Critical, High, Medium or Low — colour-coded |
| Requester | The user who submitted the request |
| Request Date | Submission date |
| Related Document | The document affected by the change (linked to Document Control) (hidden column) |
| Approved By | The user who approved or rejected the request (hidden column) |
| Approval Date | Date of approval/rejection (hidden column) |
| Implementation Date | Date the change was applied (hidden column) |
| Description | Detailed description of the proposed change (hidden column) |
| Impact Assessment | Assessment of the change's impact (hidden column) |
| Notes | Additional remarks (hidden column) |
| Rollback Plan | Plan for reverting the change if implementation fails (field in the edit form, not a table column) |
| Verification Evidence | What was tested and with what result (field in the edit form, not a table column) |
The last status is not a rubber stamp. A request cannot move to Verified while Verification Evidence is empty: the standard expects a change to a system that affects laboratory data to be tested before it is considered safe, and this text is the proof.
The check also looks at the stored record, not only at what you sent — an edit that simply leaves the field out does not get around it.
The Rollback Plan answers the other half of the question: what we do if the change fails after it has been applied.
Points at — this page does not stand without these: