CMMS Implementation Checklist — Everything You Need Before Go-Live
Most CMMS implementations that underdeliver do so because preparation steps were skipped, not because the software was wrong. This checklist covers every step — data preparation, configuration, team readiness, and go-live verification — so your QuipAssist implementation starts right.
A successful CMMS go-live is the result of preparation that happens before the first maintenance task fires in the system — complete and accurate equipment data, PM schedules configured for every equipment category, approval workflows set up correctly, the team oriented on the mobile interface, and QR codes printed and applied to physical assets. This checklist covers every preparation step across five phases: data preparation, platform configuration, team readiness, physical setup, and go-live verification. Use it as both a planning tool and a completion tracker.
Phase 1 — Data Preparation
Complete these items before opening QuipAssist for import. Data quality problems are significantly easier to fix in a spreadsheet than in a live system.
Complete Equipment Inventory
Compile every asset that will be tracked — from physical walkthrough, purchasing records, existing spreadsheets, and vendor records. Verify completeness: are there equipment categories that are not on the list? Assets in remote locations or storage that were missed? Equipment registered to the wrong location?
Standard Data Fields for Each Asset
For each asset, collect: equipment name, category, make, model, serial number, location within facility, purchase date, warranty expiration date, current condition status, and any custom fields your operation tracks (capacity, voltage, primary contact for service). Fill in as many fields as available — incomplete records are better than absent records, but complete is better.
PM Program Documented for Each Category
Before configuring PM schedules in QuipAssist, document what maintenance each equipment category requires and at what interval — from manufacturer manuals and regulatory requirements. This document becomes the PM configuration guide. If you do not have this documented before opening QuipAssist, configuration will be slower and the resulting program less complete.
Vendor List Compiled
List all service vendors with contact information, service specialties, and any known certification or insurance documentation. This feeds the vendor management module configuration and prevents the ad hoc vendor lookup that delays work order routing in the first weeks of operation.
Historical Data Decision Made
Decide which historical maintenance records to import into QuipAssist and which to archive separately. For assets with significant service history, importing key milestones (last major service, known recurring issues, warranty claim history) improves the AI troubleshooting accuracy from day one.
CSV File Prepared and Reviewed
Export your completed equipment list as a CSV file. Review for: consistent naming conventions, no duplicate entries, correct location assignments, and no blank required fields. A clean CSV produces a clean import. Errors in the spreadsheet become errors in the system.
Phase 2 — Platform Configuration
Complete these items in QuipAssist before inviting the team. Configuration gaps discovered after go-live are more disruptive to correct than configuration gaps discovered during setup.
Locations Created and Named Correctly
Create all locations in QuipAssist — each physical facility, building, or site that will appear in the system. Location naming should match the names your team uses operationally (not internal codes that require translation). Verify that every location in your equipment list has a corresponding location in QuipAssist before running the import.
Equipment Data Imported and Verified
Run the CSV import, review the AI field mapping, verify the import results, and spot-check individual records for accuracy. Correct any import errors before proceeding. Add equipment photos for high-priority assets — photos attached during implementation are available to technicians immediately rather than needing to be added later during field use.
PM Templates Built for Every Equipment Category
Create PM schedule templates — one per equipment category per maintenance interval — with the correct frequency, assigned role, advance reminder timing, and associated checklist. Apply templates to all assets in each category. Verify that every asset in the registry has at least one active PM schedule (unless it genuinely requires no scheduled maintenance).
Work Order Approval Workflows Configured
Define approval tiers, cost thresholds, and routing rules. Test each workflow by submitting a test work order and verifying it routes to the correct approver with the correct notification. Verify that escalation rules fire correctly for overdue tasks and unacknowledged approvals.
User Roles and Access Levels Set
Configure role-based access: which users can see which locations, which users can approve work orders at which cost levels, which users have view-only versus edit access. Verify that the access level for each planned user matches their operational responsibility before sending invitations.
Vendors Added to the Platform
Add all service vendors with contact information, service categories, and any available documentation (insurance certificates, license numbers). Link vendors to the equipment categories they service so they appear correctly in work order assignment interfaces.
Phase 3 — Team Readiness
All Users Invited and Accounts Created
Send invitations to all users — technicians, managers, and any other roles. Confirm that every invited user has clicked the invitation link, created their account, and downloaded the mobile app before go-live. Users who have not completed account setup on go-live day will not be able to use the system when tasks begin firing.
Mobile App Orientation Completed
Conduct a 30–60 minute orientation session covering the core daily workflows: viewing assigned tasks, completing a checklist via QR scan, submitting a work order, updating work order status, and recording parts used. Have each technician complete a test task during the orientation to confirm they can navigate the interface independently.
Work Order Submission Tested by Non-Technical Users
If non-maintenance staff will submit work orders (store associates, housekeeping staff, tenants), have a representative from that group submit a test work order through the QR code or web link process. Verify they can complete the submission without guidance and that the resulting work order routes correctly.
Manager Dashboard Walkthrough Completed
Walk managers and supervisors through the compliance dashboard, work order queue, and any reporting views they will use for oversight. Verify they can navigate to the information they need for their management responsibilities without requiring support.
Phase 4 — Physical Setup
QR Codes Generated for All Assets
Bulk-generate QR codes for all assets in each equipment category. Print on weatherproof label stock appropriate for the installation environment (outdoor equipment, wet kitchen environments, and high-touch surfaces require more durable label materials than office environments).
QR Code Labels Applied to Physical Assets
Apply labels to each physical asset in a location that is accessible for scanning by technicians performing maintenance — typically on a non-moving, accessible surface visible from the maintenance access point. Verify that each applied label scans correctly by testing with a phone camera before moving to the next asset.
Work Request QR Codes Posted in Relevant Spaces
For facilities where non-technical staff or members/guests will submit work requests, print and post QR code placards in common areas, conference rooms, kitchen areas, and any other space where issues are likely to be reported. Verify the QR codes open the correct submission form for each location.
Phase 5 — Go-Live Verification
First PM Tasks Firing Correctly
Verify that PM tasks are appearing in technicians’ task queues on the correct schedule — that the first wave of tasks after go-live reflects the correct equipment, the correct technician assignments, and the correct due dates. Correct any scheduling errors before they compound into multiple incorrectly scheduled tasks.
Parallel Operation Confirmed for First Week
Confirm with the team that QuipAssist and the previous system (or informal process) will run in parallel for the first 5–7 days — completing and recording maintenance events in both places to verify that QuipAssist data matches expected outcomes before the previous system is retired.
Support Contacts Identified
Confirm who team members should contact for QuipAssist questions during the first weeks of operation — an internal QuipAssist champion who has the most configuration familiarity, the QuipAssist support contact for platform issues, and any agreed escalation path for configuration questions that the internal champion cannot resolve.
30-Day Review Scheduled
Schedule a 30-day post-go-live review to assess: PM compliance rate in the first month, any recurring work order routing or notification issues, technician adoption quality, and any configuration gaps that operational use has revealed. The 30-day review is the implementation completion step — it confirms that the system is working as designed and identifies any adjustments needed before the parallel period ends.
Implementation done right the first time — from this checklist to full operational status.
QuipAssist’s free plan, AI-powered bulk import, template-based PM configuration, and onboarding support make every item on this checklist achievable within your first week. Start free, follow the checklist, go live with confidence.
