How Preventative Maintenance Really Works in Salesforce Field Service
In this Office Hours Insight session, Leigh-Anne Nugent brings the conversation back to core Field Service design and walks through the real architecture behind preventative maintenance. While the session opens with a practical reminder about mobile operating system support and upgrade discipline, the heart of the discussion is about maintenance plans, maintenance work rules, service contracts, and the data model choices that determine whether preventative maintenance will quietly work, or quietly fail.
LESSONS YOU CAN TAKE FROM THIS:
1. Preventative maintenance is more than turning on one feature
A strong takeaway from this session is that preventative maintenance in Salesforce Field Service is not a simple switch. It depends on a connected structure of records including assets, maintenance plans, maintenance assets, maintenance work rules, work types, work orders, and sometimes service contracts and opportunity data. If that foundation is not designed properly, the automation becomes much harder to trust.
2. The starting point is a business design decision, not just a technical one
Leigh-Anne highlights an important question early: where does the maintenance process actually begin? For some businesses, it starts with an opportunity and service contract. For others, it starts with the asset and the expected service cadence. That matters because the answer shapes how the maintenance plan is created, what gets linked to it, and how downstream work orders should be generated.
3. Maintenance work rules are powerful, but they require discipline
This session does a great job showing how flexible maintenance work rules can be. You can drive them by calendar frequency or by record-set criteria, and you can prioritize which rules should fire first. But with that flexibility comes complexity. Teams need to think carefully about monthly, quarterly, and annual overlaps, how work should be sorted, and whether they want work orders generated ahead of time or only after the previous one is completed.
4. Silent failure is one of the biggest risks in preventative maintenance
One of the most practical insights in the session is that preventative maintenance can fail without making much noise. If generation conditions are not met, or downstream automation breaks, the system may simply not create the work you expected. That is why feed tracking, chatter visibility, and careful page layout setup matter more than they first appear. Teams need a way to see what happened when work orders do not get created.
KEY TAKEAWAYS:
Preventative maintenance relies on a broader object model than many teams expect.
The process should be designed from the business lifecycle first, then configured in Salesforce.
Maintenance work rules can be calendar-based or criteria-based, and the rule order matters.
Generating work orders ahead of time versus after completion is a strategic choice, not just a setup preference.
Visibility into failures is essential because preventative maintenance automation can fail quietly.
