Before You Begin: Define Success

Before touching the software, answer three questions that will guide every implementation decision:

• What problem is this solving? “We have no visibility into PM compliance” is a different implementation priority than “we need to reduce emergency repair costs” or “we need compliance documentation for our next audit.” The primary problem determines which features to configure first and what success looks like at 90 days.
• Who are the primary users? Field technicians who complete work orders have different workflow requirements than managers who review analytics. Both groups need to be designed for — but the field workflow is more adoption-critical because it determines whether the data that feeds the analytics actually gets captured.
• What is the minimum viable scope? The temptation is to configure everything at once. The implementation that succeeds configures the minimum scope needed to solve the primary problem, achieves high adoption on that scope, then expands. Define minimum viable scope before starting configuration.

Step 1 — Account Setup and Configuration (Day 1)

Configure the organizational structure before adding any equipment or users: create location records for all facilities, configure user roles and access levels appropriate for each team member, set up the work order priority tiers with the criteria specific to your operation, and configure the escalation rules that will route work orders to the right people. This configuration takes 1–3 hours and should be done by the implementation lead — not distributed to multiple people who may configure inconsistently.

Step 2 — Asset Registry Build (Days 1–3)

The asset registry is the foundation on which everything else rests. An incomplete registry produces a maintenance program with gaps; a registry with inaccurate data produces work orders routed to the wrong records. Build the registry through physical facility walkthrough — not from drawings, not from existing spreadsheets without verification.

For each asset record:

• Equipment category, make, model, serial number, asset ID
• Location (building, floor, room, or specific position)
• Installation date and purchase price if available
• Warranty terms and expiration
• Primary service vendor contact

QuipAssist acceleration: If an existing asset list exists in any spreadsheet format, use QuipAssist’s AI-powered bulk import — which maps any column structure to the registry fields. For organizations without any existing list, the walkthrough creates the list as a physical process. Either way, the asset registry should be complete before moving to Step 3.

Step 3 — QR Code Deployment (Days 2–4)

Print QR code labels for all registered assets and physically apply them to each piece of equipment during a second facility walkthrough. This step is often underestimated — it takes real time and requires deliberate label placement (visible, accessible, and durable). The QR code application is the physical transformation that makes the digital system actionable in the field. Technicians who can scan any piece of equipment and immediately access its record will use QuipAssist. Those who cannot will revert to informal approaches.

Label placement principles: Apply at a consistent location on each equipment type (eye level on the front panel for commercial kitchen equipment, on the equipment nameplate panel for HVAC units), where the label will be visible and accessible without requiring access to normally closed panels. Use weatherproof labels for outdoor or high-moisture environments.

Step 4 — PM Template Configuration (Days 3–7)

Configure PM tasks only for Tier 1 (highest-consequence) equipment in the initial implementation. For each Tier 1 equipment category:

1. 1

   Build the Checklist

   Reference the manufacturer PM manual for each equipment category. Build specific checklist items — action, standard, escalation criterion — not generic ones. Add reference photos where visual standards are difficult to describe in text.

2. 2

   Set the Interval

   Use manufacturer-specified intervals adjusted for your equipment’s actual utilization intensity. Configure advance reminders at 14 days and 7 days before due date for equipment where advance preparation is needed, 7 days and 3 days for standard PM.

3. 3

   Apply to Assets and Set Initial Due Dates

   Apply the PM template to all assets in the equipment category. Stagger initial due dates across 4–8 weeks rather than making everything due on day one.

Step 5 — Work Order Workflow Setup (Day 5)

Configure the work order submission and routing workflows: set up QR code work request submission, configure the routing rules for each equipment category and priority tier, set up vendor dispatch contacts for high-consequence equipment categories, and configure IoT alert-to-work-order automation if IoT sensors are being connected. Test the complete submission-to-assignment flow with a test work order before training the team.

Step 6 — Team Onboarding and Launch (Days 7–10)

Train technicians on the three workflows they will use daily: QR code scan for equipment access, PM task completion on mobile, and work order submission and closure. This training takes 30–60 minutes per technician and should be hands-on at actual equipment rather than classroom-style. Launch with a “shadow period” of 5–7 days where the team uses QuipAssist while keeping any existing informal systems running in parallel — catching setup gaps before full cutover.

Step 7 — Post-Launch Optimization (Days 30–90)

Frequently Asked Questions