Standard Work Checklists
It is 5:58 AM at the Dublin oral solid dosage facility. The night shift operator opens ProBeya on the HMI terminal next to Tablet Press Line 3. Her "Today's Checklists" view shows one item in red: the Start of Shift Equipment Check is due by 06:00. She opens it, works through the 14 verification points — lubricant levels, die condition, hopper seals, guard interlocks, dust extraction readings — entering a numeric value of 22.3 C for the compression room temperature (expected range: 20-25 C), confirming each safety guard, and noting in the comments that Die Station 7 shows early signs of wear. She clicks Submit at 06:04. The checklist is logged, her supervisor is notified about the die wear comment, and the compliance dashboard updates from 94% to 95% completion rate for the week.
Two floors up, the Production Manager will review this data during the TIER 2 meeting. No paper logbooks to photocopy. No illegible handwriting to decipher. No "I think someone checked it" ambiguity.
Why Standard Work Checklists Exist
In the Toyota Production System, standardized work is the foundation of all improvement. You cannot improve what is not standardized, and you cannot standardize what is not measured. Standard work checklists are the measurement layer: they confirm that the standard was followed, capture the data that proves it, and flag deviations before they become incidents.
In pharma manufacturing, the stakes are higher. EU GMP Annex 15 requires verification activities to be documented. FDA 21 CFR 211.68 mandates routine calibration checks. 21 CFR 211.182 requires equipment cleaning and use logs. These are not bureaucratic exercises — they are the controls that prevent cross-contamination, ensure product quality, and protect patient safety.
ProBeya's checklist module bridges the gap between the regulatory requirement ("verify and document") and the operational reality ("make it fast, make it consistent, make it auditable").
Creating a Checklist Template
- Navigate to a board and open the Checklists tab
- Click + New Checklist
- Fill in the template fields:
| Field | Description | Required |
|---|---|---|
| Name | Human-readable name (e.g., "Line 3 — Start of Shift Equipment Check") | Yes |
| Description | Purpose and scope of the checklist | No |
| Frequency | How often the checklist must be completed | Yes |
| Items | Array of verification tasks (at least one required) | Yes |
| Assignees | Users responsible for completing this checklist | No |
| Deadline Hour | Hour (0-23) by which the checklist must be completed | Yes (default: 17) |
Frequency Options
| Frequency | Expected Cadence | Pharma Example |
|---|---|---|
| Daily | Once per calendar day | Environmental monitoring plate reads |
| Shift | Once per shift (configured per site) | Line clearance verification |
| Weekly | Once per ISO week (Monday-Sunday) | Equipment calibration spot checks |
| Monthly | Once per calendar month | Fire extinguisher inspection |
Three Item Types for Richer Data Capture
Each checklist item is not just a tick box. ProBeya supports three response types that match real operational needs:
| Type | Description | Use Case |
|---|---|---|
| check | Binary yes/no, pass/fail | "Safety guard in place?" |
| text | Free-form text input | "Describe any anomalies observed" |
| number | Numeric measurement input | "Record compression room temperature (C)" |
Items can also carry an expected value field that displays guidance to the operator (e.g., "20-25 C" for a temperature check). This reduces errors by showing the operator what "good" looks like before they enter their reading.
Bad: "Check machine" Good: "Verify lubricant level on Press 3 main drive is between MIN and MAX marks on sight glass"
Bad: "Temperature OK?"
Good: "Record compression room temperature (C)" with expected value "20-25 C" and type number
Specific, measurable items reduce variability between operators and produce data that can be trended over time. Every checklist item should answer: What do you check, where do you check it, and what does good look like?
Assignee Configuration
- No assignees: The checklist is visible to all board members — useful for shared responsibilities
- Specific assignees: Only listed users see the checklist in their "Today's Checklists" view — use this for role-specific checks (e.g., only the shift lead completes the shift handover checklist)
Completing a Checklist
Today's Checklists View
- Open the Checklists tab on a board
- The Today view shows all active checklists assigned to you that are due in the current period
- Each checklist displays its completion status: pending or already completed
Filling in a Checklist
- Click on a pending checklist
- For each item:
- Check the box (for check-type items), enter a number (for numeric items), or type text (for text items)
- Optionally add a comment explaining any observations or exceptions
- Click Submit
All items marked as required must have a value before the checklist can be submitted. The system will display an error if required items are left blank. This prevents partial completions from being recorded as "done."
Duplicate Prevention
Each checklist can only be completed once per period (daily, shift, weekly, or monthly). If a checklist has already been submitted for the current period, the system returns a conflict error. This prevents double-counting in compliance metrics and ensures a clean 1:1 relationship between periods and completion records.
Worked Example: Line Clearance in Oral Solid Dosage
Line clearance is one of the most critical standard work activities in pharma manufacturing. Before a new batch can begin, every trace of the previous product must be removed from the line. Cross-contamination is a patient safety risk and a regulatory red line.
Checklist: "Line 3 — Line Clearance Verification"
- Frequency: Shift
- Deadline Hour: Line clearance must be completed before production start
- Items:
| # | Item | Type | Expected Value | Required |
|---|---|---|---|---|
| 1 | Previous batch documentation removed from area | check | — | Yes |
| 2 | All containers from previous product removed | check | — | Yes |
| 3 | Equipment surfaces visually clean (no residue) | check | — | Yes |
| 4 | Hopper interior inspected and clean | check | — | Yes |
| 5 | Die cavities inspected with flashlight | check | — | Yes |
| 6 | Dust extraction system checked and clean | check | — | Yes |
| 7 | Room label updated with new batch number | check | — | Yes |
| 8 | Differential pressure reading (Pa) | number | ≥15 Pa | Yes |
| 9 | Comments / observations | text | — | No |
When the operator submits this checklist, the system records who completed it, when, and every individual response. If Die Station 7 has residue, the operator marks item 5 as "no" with a comment, and the system blocks submission because it is a required item. The operator must clean the die, re-inspect, and then submit — exactly as the SOP requires.
Completion History
The history view provides an auditable log of all checklist completions:
- Open a checklist template
- Navigate to the History tab
- Browse completion records filtered by date range
Each record shows:
- Date the checklist was completed
- Completed by — the authenticated user
- Completed at — exact timestamp
- Responses — per-item check status, numeric values, text entries, and comments
This history is the digital equivalent of the paper logbook — except it cannot be lost, cannot be backdated, and can be searched and exported in seconds during an audit.
Missed Checklist Alerts
The Missed view shows checklists that were not completed by their deadline. A checklist is flagged as missed when:
- It is active (not deactivated)
- The current time has passed the deadline hour for the current period
- No completion record exists for the current period
Missed checklists appear with a red indicator on the compliance dashboard, enabling supervisors to take corrective action immediately.
A missed checklist is a leading indicator. One miss is a scheduling issue. Two consecutive misses is a process issue. Three consecutive misses is a management issue. Use the missed checklist trend to identify areas where workload exceeds capacity or where the checklist frequency needs adjustment.
Completion Rate Metric
The completion rate calculates compliance over a date range:
- Expected completions: Number of completions expected based on frequency and date range
- Actual completions: Number of completion records in the date range
- Rate: Percentage of expected completions that were actually performed (capped at 100%)
This metric integrates directly with KPI Boards. Track checklist completion rate as a People or Quality KPI on your SQCDP board. A target of ≥95% is standard for pharma manufacturing sites; world-class sites sustain ≥99%.
Managing Checklists
Updating a Template
Templates can be updated at any time. Changes apply to future completions only — historical records retain the item structure as it existed when the checklist was completed. This is important for data integrity: you can add an item to a checklist without retroactively making old completions appear incomplete.
Deactivating vs. Deleting
| Action | Historical Records | Compliance Impact |
|---|---|---|
| Deactivate (set isActive = false) | Preserved | No longer tracked as expected |
| Delete | Permanently removed (cascade) | Complete loss of audit trail |
Always deactivate rather than delete if the checklist has any historical completions. Deleting a checklist permanently removes all completion records — this would create a gap in your audit trail that is difficult to explain during a regulatory inspection.
Regulatory Context
Standard work checklists in ProBeya support compliance with:
- EU GMP Annex 11 Section 7.1: Verification and logging of GMP-relevant activities with electronic records
- 21 CFR 211.68(b): Written records of equipment checks, calibrations, and inspections
- 21 CFR 211.182: Equipment cleaning and use log requirements
- ICH Q10 Section 3.2.2: Monitoring of process performance through standardized verification activities
- ISO 13485:2016 Section 7.5.1: Control of production with documented procedures and defined criteria
The authenticated user identity, timestamp, and per-item response data create an electronic record that meets the "attributable, legible, contemporaneous, original, accurate" (ALCOA) principles required for GxP data integrity.
Permissions
| Action | Required Role |
|---|---|
| View checklists and completions | Any board member |
| Create/edit checklist templates | Board admin or workspace admin |
| Complete checklists | Assigned user or any board member (if no assignees set) |
| Delete checklist templates | Board admin or workspace admin |
| View missed checklist alerts | Board admin or workspace admin |
Related Features
- KPI Boards — Track checklist completion rates as KPIs on your SQCDP boards
- Action Log — Create follow-up actions for missed checklists or anomalous readings
- TIER Meeting Mode — Review checklist compliance during daily standups
- Escalation Engine — Escalate repeated missed checklists to TIER 2
- Routines — For more complex step-by-step procedures with photo evidence and signatures