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
Architecture decisions
Workflows
0:000:00

Management Reviews Workflow

This guide describes the step-by-step process for conducting management reviews. Management reviews, per ISO 17025 §8.9.1, are periodic evaluations of the Quality Management System (QMS) by top management — typically on an annual basis. (§8.9.2 lists the required inputs; §8.9.3 covers the outputs.)


Prerequisites

Before you begin, make sure that:

#PrerequisiteWhyPage
1UsersRecording attendeesUsers
2QC DataData to reviewControl Samples

Step 1 — Navigation

Go to the Management Reviews page from the main menu. A table of existing records is displayed.

The visible table columns are:

ColumnDescription
Review No.Unique code (for example MR-YYYY-0001)
Review DateWhen the review was conducted
Conducted byThe user who conducted the review
StatusPlanned, In Progress, Completed or Approved
Next ReviewDate of the next scheduled review
There are also hidden columns (Period From, Period To, Attendees, Previous Action Status, Key Findings, Decisions, Action Items, Notes). You can show them from the column settings.

Step 2 — Plan the Review

Schedule the review at least once a year. Click the "+" button and create a record with status "Planned".

FieldDescriptionRequired
Review No.Leave blank for auto-numbering (for example MR-YYYY-0001)No
Review DateWhen the review will take placeYes
Conducted byThe user responsible for the reviewYes
Status"Planned"Yes
Period From / Period ToReporting period covered by the reviewNo
AttendeesManagement members and staffNo
Next ReviewDate of the next reviewNo
NotesAdditional remarksNo

Step 3 — Prepare the Inputs

On the review record you will find an "Inputs" section, with 14 separate free-text fields — one for each review input required by ISO 17025 §8.9.2:

Field
(a) Internal / external issues
(b) Fulfilment of objectives
(c) Suitability of policies and procedures
(e) Outcome of recent internal audits
(f) Corrective actions (CAPA) status
(g) Assessments by external bodies
(h) Changes in work volume / type
(i) Customer & personnel feedback
(j) Complaints
(k) Effectiveness of improvements
(l) Adequacy of resources
(m) Results of risk identification
(n) Outcomes of validity-of-results assurance
(o) Other relevant factors
Input (d) — status of actions from previous management reviews — is captured separately, in the Previous Action Status field (see Step 4).
Gather the data before the meeting so the review is efficient.

Step 4 — Conduct the Review

During the meeting, open the record and fill in:

  1. Previous Action Status — Which actions from the last review were completed
  2. Key Findings — What was identified when examining each input
  3. Decisions — What management decided
  4. Action Items — Summarize in the free-text "Action Items" field. For a structured record with owner, due date, category and status, save the review first and use the "+ New Action" button in the "Review Actions" section — this register feeds the approval gate in Step 5

Step 5 — Complete & Follow Up

After the meeting:

  1. Check that all fields are filled in
  2. Update the Status on the form (for example to "In Progress" or "Completed") as the review progresses
  3. Set the Next Review date (within 12 months)
  4. Follow up on assigned actions in the "Review Actions" section — create CAPA records if needed
  5. For formal approval, open the row's action menu (⋮) in the table and select "Approve". A documented reason is required, and only the Lab Director, Quality Manager or Reviewer role can perform it. Status moves to "Approved" and the record locks — this action cannot be undone. If the previous review still has open actions that haven't been carried over or cancelled into this one, approval is blocked unless a documented override is recorded by an authorized role
During ISO 17025 audits, assessors require documentation of at least one annual review with findings, decisions, and actions.

Step 6 — Search & Filtering

Type in the search field for quick text filtering.

Filter Panel

Click the filter icon to open the filter panel:

FilterTypeDescription
StatusSelectShow only one status
Conducted bySelectShow only reviews for a specific user
Max RecordsNumberRecord limit for print/export (default: 200)

FAQ

How often should reviews be conducted?

At least once a year per ISO 17025. Many laboratories conduct reviews semi-annually or quarterly depending on size and workload.

What should be reviewed?

QC results, audit findings, CAPA effectiveness, customer complaints, staff training, resource needs, deviations, and risk assessments. The goal is a holistic evaluation of the QMS.

Who should attend?

Senior management, the quality manager, laboratory heads, and anyone who can contribute to the agenda topics.

How does auto-numbering work?

If you leave the "Review No." field blank during creation, the application assigns the next available code (format MR-YYYY-NNNN). You can also enter your own code.

What's the difference between "Completed" and "Approved"?

"Completed" is just a status value you set manually on the form. "Approved" is the final, locked status — it can only be set via the "Approve" action in the row menu, requires a documented reason and a specific role (Lab Director, Quality Manager or Reviewer), and cannot be undone.