Recurring Work Orders: Setup and Management

In my experience, the teams that get the most value out of recurring work orders are the ones who take the time upfront to think through the full operational flow—not just the creation of the work order itself, but what happens after it's been running for six months, when your technician roster has changed, when your service offerings have evolved, and when your customers start asking for adjustments. I've seen too many implementations where the initial setup was rushed, and then the team spent more time cleaning up duplicate or misconfigured recurring jobs than they would have spent building it properly from the start.

What Recurring Work Orders Are Best For

Before we walk through the setup steps, let me frame what I typically recommend is the sweet spot for this feature. Recurring work orders excel for:

Preventive maintenance contracts — quarterly HVAC inspections, annual generator servicing, monthly fire suppression checks
Subscription-style services — weekly landscaping, bi-weekly cleaning, monthly pest control
Equipment monitoring — recurring calibration, filter replacements, lubrication schedules
Warranty and compliance tracking — scheduled inspections required for regulatory or insurance purposes

What I generally do not recommend is using recurring work orders for projects that have a definite end date with variable scope, or for situations where the customer, location, or required skills might change significantly from one occurrence to the next. In those cases, a template combined with manual scheduling often gives you the flexibility you need without the overhead of managing exceptions.

Creating Your First Recurring Work Order

The entry point for this is the Work Orders section of the main navigation. From there, select Create Recurring from the dropdown menu. You'll notice this opens a form that looks similar to a standard work order, but with an additional panel on the right side labeled Recurrence Pattern.

Step 1: Define the Core Work Order Details

Start with the customer, service location, and service type—exactly as you would for a one-time job. In what I've observed from implementations across different industries, the teams that struggle later are often the ones who skip the Work Order Template selection at this stage. If you have a template that includes your standard checklist, expected duration, and parts requirements, attach it now. It propagates to every instance in the series.

Step 2: Configure the Recurrence Pattern

This is where the configuration happens. You'll see several options:

Pattern Type	Best For	Key Consideration
Daily	Route-based services, equipment checks	Be careful with weekend scheduling—use the "Skip weekends" checkbox unless your operation runs seven days
Weekly	Regular maintenance rounds, cleaning services	Select specific days of the week; allows for multi-day patterns (e.g., every Monday and Thursday)
Monthly	Most common for HVAC, generator, elevator maintenance	Choose between "same date each month" or "same day of week" (e.g., "first Tuesday")
Yearly	Annual inspections, compliance audits	Consider setting these 30–60 days before the actual deadline to build in buffer time

The Range of Recurrence section lets you define either a fixed number of occurrences or an end date. What I typically recommend is starting with an end date rather than a fixed count, because it makes visualizing and communicating the schedule to customers more straightforward. You can always extend the series later.

Step 3: Technician Assignment Strategy

Here you have a decision point that will significantly affect your dispatching workflow. You can either:

Assign a specific technician to every instance—appropriate when you have dedicated account technicians or highly specialized skills required
Leave unassigned and handle through dispatch—better for teams with rotating coverage or when you're managing by availability rather than relationship
Use the "Preferred Technician" field—this flags a default assignee without hard-coding it, allowing dispatchers to override when needed

In my experience working with HVAC and facilities management teams, the preferred technician approach with unassigned fallback tends to create the least administrative overhead while preserving customer relationships.

Managing Existing Recurring Series

Once a recurring series is active, you'll find it under Work Orders → Recurring. The list view shows each series as a single row, with a count of upcoming and completed instances.

Editing a Series vs. Editing a Single Instance

This distinction trips people up, so I want to be explicit about it. When you open a recurring work order from the dispatch board or work order list, you're looking at a single instance. If you make changes here—reassigning the technician, updating the scheduled time, adding notes—you're affecting only that occurrence.

To modify the entire series, you need to:

Navigate to Work Orders → Recurring
Find the series and select Edit Pattern
Make your changes in the recurrence configuration panel
Choose whether to apply changes to all future instances or all instances including past (the latter is rarely what you want)

When you edit the pattern, FieldPulse will ask how to handle instances that already exist in the future. You can either regenerate them completely (losing any custom notes or assignments added to individual instances) or apply only the changes that don't conflict with instance-level modifications. What I typically recommend is the conservative option—apply non-conflicting changes only—unless you're doing a structural overhaul.

Handling Exceptions and Skips

Real operations don't run perfectly on schedule. Customers reschedule, technicians get sick, weather intervenes. For individual instances, you have several options:

Reschedule — moves the instance to a new date without affecting the overall pattern
Skip — removes the instance entirely; the next occurrence generates according to the original pattern
Cancel — marks the instance as cancelled but keeps it in the record for reporting purposes
Complete Early — records the work as done ahead of schedule; the next occurrence still generates on the original pattern date

The Skip function deserves particular attention because I've seen it used when Reschedule would have been more appropriate. Skipping removes visibility into the fact that service was due and not performed, which can be problematic for compliance tracking. Rescheduling maintains the audit trail.

Advanced Considerations

Seasonal Adjustments

For services that change intensity with seasons—think HVAC startups in spring and fall, snow removal prep, irrigation winterization—you have a few pattern management strategies. Some customers create separate recurring series for each seasonal phase, running spring/summer and fall/winter as distinct patterns with different service types and checklists. Others maintain a single series and use the Edit Instance capability to customize the work order details for seasonal variations.

Contract Renewal and Series Extension

When a service contract renews, you don't need to create a new series. Open the existing recurring pattern, update the End Date or Occurrence Count, and save. This preserves your historical reporting continuity. If the terms have changed—new pricing, revised scope—you can update the template association or add a note to the series description indicating the contract amendment date.

Reporting on Recurring Work

The standard work order reports include recurring work orders alongside one-time jobs. For analysis specifically focused on your recurring business, filter by the Is Recurring flag. This lets you calculate metrics like:

Percentage of revenue from recurring vs. reactive service
Completion rate on recurring instances (are your preventive contracts actually being executed?)
Variance from scheduled dates (how often are recurring jobs drifting from their intended pattern?)

Common Configuration Issues

From the support tickets I've reviewed, here are the patterns that cause the most confusion:

Duplicate series creation — happens when a team member doesn't realize a series already exists and creates a new one for the same customer and service. The recurring work order list has a filter for customer name; use it before creating new series.

Technician availability mismatches — the system does not automatically check technician availability against time-off or existing assignments when generating instances. It's worth reviewing the Upcoming Instances view weekly to catch conflicts before they become dispatch emergencies.

Time zone edge cases — if your operation spans multiple time zones, verify that the scheduled time on recurring instances reflects the local time at the service location, not the dispatch office time. This is configured in the customer record's location settings.