Setting Up Routine Contracts and Maintenance Planning
Build service contracts and routines from CRM, preview generated work, and move ready routine work into Scheduler.
Before you start
- The customer account exists in CRM.
- The relevant sites, systems, and assets are linked to the account.
- Scheduler is enabled when you want to generate routine work.
Expected outcome
Routine service commitments are visible on the customer account and can be previewed before inspections or planner tasks are generated.
Open the account routine workspace
- Open
Customers. - Open the customer account.
- Select the
Routinestab. - Review the summary cards for contracts, active routines, due soon, overdue, and next due.
The routines panel is account-owned. Use it to define the recurring commitment before asking Scheduler to create visits.
Create a service contract
- Select
Add Contract. - Enter the contract name.
- Set the status: draft, active, paused, or ended.
- Assign an owner when one person should review renewals.
- Set contract start, contract end, next review, and renewal notice days where known.
- Add notes that explain the commercial wrapper.
- Save the contract.
Use a service contract when multiple routines should sit under the same maintenance agreement or renewal review. A routine can still exist without a contract wrapper.
Create a routine
- Select
Add Routine. - Enter a routine name.
- Choose a service contract when the routine belongs to one.
- Set status to active when it should generate work.
- Choose the service line.
- Choose the covered scope: account, site, system, or asset.
- Select the matching site, system, or asset when the scope requires it.
- Set frequency: annual, six-monthly, quarterly, monthly, weekly, or custom.
- Add anchor date and next due date.
- Choose work type: inspection or scheduler task.
- Set the inspection type or task type.
- Add the default field resource, duration, flex days, crew size, access equipment, out-of-hours flag, industry override, and notes where relevant.
- Save the routine.
Routines should be scoped as tightly as the operational work requires. An account-level routine is useful for generic customer work; asset-level routines are better when the job must be tied to a specific asset.
Pause, resume, and review routines
- Pause a routine when the customer pauses the commitment but the history should remain.
- Resume a routine when it should generate future work again.
- End a routine when it should no longer be part of the live maintenance plan.
- Use the upcoming windows list to review due dates before generating work.
Paused and ended routines are not the same. Pause is temporary; ended is a lifecycle decision.
Preview routine generation
- Open an active routine.
- Select
Preview. - Choose the target month.
- Run the preview.
- Review ready rows, warning rows, and blocked rows.
- Read each blocker before generating work.
- Confirm the preview only when the rows are correct.
- Select
Generate Ready Work.
The preview is required before generation. It protects the planner from creating visits when a routine has no due date, points at inaccessible site/system/asset scope, or uses a default field resource who cannot receive scheduled field work.
Understand what generation creates
Routine generation creates either inspections or scheduler tasks, depending on the routine work type.
- Inspection routines create inspection work with the configured inspection type.
- Scheduler task routines create planner tasks with the configured task type.
- Generated work carries routine identity and generation period so duplicate generation can be avoided.
- Next due dates are advanced after generation.
- Scheduler must be available for generation actions to appear.
Generated work should still be reviewed in Scheduler before field deployment. A generated row is not automatically the same as a confirmed customer appointment.
Work routine health prompts
Routine health prompts highlight maintenance setup that needs review.
| Prompt | What it means |
|---|---|
| Contracts needing review | A service contract is close to or past its review window. |
| Routines without assets | A routine points at a site or system where the asset register is incomplete. |
| Sites missing contacts | Routine work exists but the site lacks useful contact context. |
| Blocked generation | A routine could not safely generate work without correction. |
Use prompts as triage. Fix the owning customer, site, asset, or routine record rather than dismissing the signal by default.
Troubleshooting
| Problem | What to check |
|---|---|
The Preview action is missing | Confirm Scheduler is enabled for the workspace and the routine is active. |
| Generation is blocked | Check scope, due dates, target month, and default field-resource eligibility. |
| The wrong work type is generated | Edit the routine work type and the inspection or task type before previewing again. |
| A routine is overdue but no job exists | Preview generation for the target month and check blockers. |
| Routine billing is not appearing in Finance | Recurring contract charge candidates are not enabled yet; Finance currently uses accepted quote and completed work-order candidates. |
Reference surfaces
- Use Customers for the CRM account route and routine panel.
- Use Scheduling for generated work after it enters the planner.
- Use PPM Forecast to see future routine pressure once generated or target-month work exists.
Using Collaboration, Notifications, and Activity Feed
Use the notification bell and the Collaboration activity feed to keep cross-resource changes visible without relying on memory or inboxes.
Handling Customers, Quotes, Work Orders, and Finance
Move from inspection findings to commercial follow-up using CRM, quotes, work orders, and organization-level receivables.