# Pre-Audit Checklist (Example Framework) **URL:** \ **Category:** Facility Maintenance\ **Created:** [February 9, 2026, 4:19pm UTC](https://forum.cybermetrics.com/t/pre-audit-checklist-example-framework/142 "2026-02-09T16:19:13Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![aavila](https://avatars.discourse-cdn.com/v4/letter/a/a6a055/32.png) [@aavila](https://forum.cybermetrics.com/u/aavila)\ **Post date:** [February 9, 2026, 4:19pm UTC](https://forum.cybermetrics.com/t/pre-audit-checklist-example-framework/142/1 "2026-02-09T16:19:13Z")
**Facility Maintenance, Asset Care & CMMS** _This is an example guide. Actual audit expectations may vary by industry, regulatory body, and risk profile._ * * * **1. Asset Management – Example Expectations** **What auditors usually want to see (example):** - A list of critical assets that matches what exists in the field - Asset records that show location, status, and ownership - Evidence assets are actively managed, not just listed **Example questions:** - “How do you know all critical assets are accounted for?” - “How do you prevent duplicate or unmanaged assets?” **Industry notes:** - Manufacturing: focus on production-critical assets - Healthcare: life-safety and clinical support equipment - Facilities: HVAC, electrical, fire systems * * * **2. Preventive Maintenance (PM) – Example Review** **What this often looks like:** - PM schedules exist for critical assets - PMs are running automatically, not manually tracked - Overdue PMs are visible and explainable **Example questions:** - “How do you know PMs are being completed on time?” - “What happens when a PM is late?” **Industry notes:** - Pharma/FDA: documented justification for late PMs - Facilities: seasonal and weather-driven PMs - Utilities: usage-based or meter-driven PMs * * * **3. PM Compliance vs PM Effectiveness (Example)** **Auditors may look for:** - PM completion rates - Evidence PMs are adjusted based on failures - A feedback loop between PMs and corrective work **Example evidence:** - PM frequency changes tied to failure history - Notes explaining why a PM task was added or removed **Key takeaway:** High compliance with poor outcomes raises questions. * * * **4. Work Orders – Example Traceability** **What “good” looks like:** - Work orders move through clear statuses - Completed work orders include who did the work and when - Supporting notes, labor, or parts are recorded **Example questions:** - “Show me the history of work on this asset.” - “How do you prevent work from being closed without documentation?” * * * **5. Service Requests – Example Control** **Typical expectations:** - Service requests are tracked in one system - Requests aren’t lost in emails or phone calls - Requests are either approved, rejected, or converted **Example scenario:** - A department submits a request → maintenance reviews → work order is created (or justified not to) * * * **6. Calibration (If Applicable) – Example Evidence** **What auditors often ask for:** - A list of calibrated instruments - Calibration intervals and due dates - Completed calibration records **Example documentation:** - Pass/fail results - Test point data or range calculations - Performer and reviewer acknowledgement **Industry sensitivity:** - FDA / ISO labs: very high scrutiny - Facilities: limited to specific safety instruments * * * **7. Procedures & Checklists – Example Usage** **What this may look like:** - PMs and calibrations reference documented steps - Checklists match how work is actually performed - Acknowledgements are used where required **Example questions:** - “How do you ensure technicians follow the approved method?” - “What changes when a procedure is updated?” * * * **8. Parts & Inventory – Example Oversight** **Auditors may review:** - Availability of critical spares - Parts tied to PMs or recurring repairs - Evidence inventory supports maintenance strategy **Example risk area:** - Missed PMs due to unavailable parts * * * **9. User Access & Controls – Example Review** **Common expectations:** - User roles are defined - Administrative access is limited - Actions are traceable to individuals **Example question:** - “Who can change maintenance or calibration data?” * * * **10. Change Control – Example Practices** **What auditors like to see:** - PM changes documented - Calibration interval changes justified - Configuration changes controlled **Example explanation:** - “We increased this PM frequency after repeat failures.” * * * **11. Reporting & Evidence – Example Readiness** **Typical requests:** - PM completion reports - Asset maintenance history - Calibration history **Best practice:** - Reports are easy to generate and understood by more than one person * * * **12. Exceptions & Deviations – Example Handling** **Auditors expect:** - Late or missed work to be visible - Explanations documented - Corrective actions tracked **Key insight:** Documented exceptions show control—not failure. * * * **13. Field Reality Check – Example Walkthrough** **What often happens:** - Auditor selects an asset - Reviews its CMMS record - Verifies it physically in the field **Alignment matters more than perfection.** * * * **14. Final Example Self-Check** Before an audit, try this: - Pick one asset - Review one PM - Review one corrective WO/CM - (If applicable) review one calibration If the story is clear and consistent, you’re likely in good shape. * * * Audits aren’t about having **zero issues**. They’re about proving you have **process, visibility, and control** —and that your CMMS reflects reality. Many of these audit questions aren’t about doing _more_ work—they’re about whether your CMMS tells a clear, defensible story. When asset records, PMs, work orders, and exceptions all connect, audits become conversations instead of interrogations. **Thoughts:** • Which area gives you the most trouble during audits: PM compliance, documentation, or asset accuracy? • What’s the _first_ thing an auditor usually asks for in your facility? • Do you prepare for audits continuously—or scramble right before?