Documentation
Tutorials
Workflows
Kebab actions
Daily Work
Dashboard & Reports
Quality Control
ISO 17025
Reagents & Storage
Logs
Contacts
Billing
Analysis Setup
Settings
Initial Setup
Help & Reference
Standards
Architecture decisions
Positioning
ISO 17025
0:000:00

Change Requests

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.

Toolbar

ButtonAction
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

Record Actions

Clicking the icon on each row shows:

  • Edit — Open the edit form
  • Preview — View record as PDF
  • Download PDF — Download the record as a PDF file
  • Send Email — Send the record as a PDF attachment via email
  • Delete — Delete the record (with confirmation)

Fields

FieldDescription
Request No.Unique request code. Leave blank for auto-numbering.
TitleBrief description of the change request
StatusSubmitted, Approved, Rejected, Implemented or Verified — colour-coded. Only the Lab Director or the Quality Manager may approve requests.
PriorityCritical, High, Medium or Low — colour-coded
RequesterThe user who submitted the request
Request DateSubmission date
Related DocumentThe document affected by the change (linked to Document Control) (hidden column)
Approved ByThe user who approved or rejected the request (hidden column)
Approval DateDate of approval/rejection (hidden column)
Implementation DateDate the change was applied (hidden column)
DescriptionDetailed description of the proposed change (hidden column)
Impact AssessmentAssessment of the change's impact (hidden column)
NotesAdditional remarks (hidden column)
Rollback PlanPlan for reverting the change if implementation fails (field in the edit form, not a table column)
Verification EvidenceWhat was tested and with what result (field in the edit form, not a table column)

"Verified" means we tested it (§7.11.2)

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.

Connects to

Points at — this page does not stand without these:

Notes

  • Only the Lab Director or the Quality Manager approves requests.
  • Related Document links the change to the controlled document it affects. See Document Control.
  • See also: Security, Deviations.