Preventive maintenance plans
Create a repeating visit plan, review generation activity, and treat requests the plan opens as ordinary maintenance requests.
A preventive maintenance plan is a repeating visit schedule on an asset or property. The platform opens requests on those dates. You set the plan, review generation activity, then run each request from its profile.
Plan and activity
Above the tabs, use Filters to search by plan name or narrow the list by status, service, frequency, asset, property, request type, and priority. The same Filters band stays on Generation Activity and narrows that log. There you can also filter by generation status, number of attempts, and due date. Clear the filters when nothing matches. The choices stay in the page address when you move between the two tabs, so a refresh keeps them.
Under preventive maintenance plans, create a plan in the wizard: place or asset, recurrence, and any services the screen shows. Save only what the form asks. The plan is saved only from the review step; pressing Enter in a field does not save it. If you close the wizard with ✕, Esc, or a click outside it before saving, it asks you to confirm before discarding your changes.
For maintenance that happens once a year, choose Annually as the frequency, then pick the Month and Day of month, for example 15 April every year. Days the chosen month never has cannot be picked. If you pick 29 February, the plan runs on 28 February in years that are not leap years. The request is created Lead time (days) before that date, so if this year's date has passed or is closer than the lead time, the first run is next year. The schedule preview in the review step shows the real first date.
In the coverage step, Select all chooses every asset or property that matches the current search, including ones not loaded yet. Leave the search empty to select the whole list. Deselect all clears only that search and keeps selections from another search. Refresh reloads that list only and keeps your selections. The asset list also has two filters: Asset type and Property, and each accepts more than one value. In the property filter the list follows the property hierarchy: expand any property to see the properties under it, while a search shows matching results in one flat list with the full path. Include sub-properties is on by default so assets in the selected properties and in every property beneath them are included. An applied filter shows a count on its button and a chip above the list; remove a chip to widen the list again. Select all applies to the filtered results, and when nothing matches you get Clear filters. These two buttons appear on the asset list only, not on the property list.
If your view is limited to some branches, the coverage step lists only the assets and properties of your branches. A notice gives the number of other places the plan covers in branches you cannot see; they stay in the plan when you save, and you cannot add a place from those branches.
Freezing a plan stops maintenance-request generation. The review step therefore shows no upcoming dates and identifies the frozen plan as the reason. The service list shows active services only. If the plan's service was deactivated, you can still save the plan as Frozen; to keep it active, choose an active service.
If the plan priority is allowed to bypass blackouts in the account settings, review keeps the original occurrence and generation creates the maintenance request without moving or skipping it because of the Working Calendar.
To reuse a similar plan, open Duplicate on the plan card. Confirm you want that plan with its coverage, schedule, Working Calendar settings, request template, generation settings, and execution style. The new name starts as the original plus “(copy)”; change it before you confirm. The copy stays frozen until you review and activate it. Only the coverage you can see is copied: places in branches outside your view are left out. Generation activity is not copied.
The Generation Activity tab shows what was generated recently. If a request was created, open its reference in the same row.
Check Reason / error when no request is generated. The activity record identifies an active request that already exists for that asset or property and service, or a Working Calendar scheduling problem. If every retry failed, the row says account administrators were notified. Attempts from before detailed reasons were retained are identified as historical failures without a detailed cause.
If “run today’s generation” appears, use it after you confirm the plan — not twice in one morning “just in case”.
Requests the plan creates do not notify people one by one, whatever the execution style. After each generation run, the technicians, the managers of each property or asset, and the request's Contact Responsible User get one notification per plan with the number of new requests, and the customer gets no WhatsApp message about the new request. Status changes after that notify as usual. See notifications.
Note: A request born from a plan is a full maintenance request: assignment, status, and invoice when required. Do not open a manual request for the same slot unless generation failed and a supervisor asked you to.
Read Inspection Plans if the round is a checklist rather than a repair visit, and maintenance requests to follow the number after it is generated.
Execution style
The Execution step, after Generation, decides how each cycle is carried out. Standard keeps one maintenance request per asset or property on its due date. Team visit gives each technician a work package on the due date, with a separate maintenance request for each of their assets. Spread over the period splits each cycle into phases, such as 1,000 assets a day over 3 days, and shares the requests across selected technicians. Team visit and Spread need Schedule anchor set to Calendar year or Custom date. Details: Spread a plan and split it across a team.
When the account uses branches, each selected technician must be assigned to every branch of the assets and properties the plan covers. If a technician is deactivated mid-cycle, their later requests go to the plan’s default assignment. If you change the frequency or the schedule anchor while a cycle runs, that cycle ends the day before the new one starts, and its lines that never got a request are Skipped.
The Cycles tab follows each cycle, its compliance, and its printed reports — Track a cycle and print reports.
What to read next
- Spread a plan and split it across a team — execution style, phases, and work packages.
- Track a cycle and print reports — Cycles tab, cycle board, field sheets, and reports.
- Working Calendar — working days and blackouts that move or skip generated requests.
- Inspection plans — when the round is a checklist, not a repair visit.
- Maintenance requests — follow the generated number like any other request.
- Notifications — the one summary per plan that replaces a notice for every generated request.