To set recurring work order rules, define the priority scale first. In Microsoft Dynamics 365 Field Service, you choose a number from 1 through 10 to define the level of importance of the priority, according to Microsoft.
Key takeaways for how to set up recurring work orders and priority levels in field service software
- Set a priority scale from 1 through 10 to define the level of importance of the priority, according to Microsoft.
- Note that the recurring configuration is set to 12 months by default, according to ServiceTitan.
- Assign a Job Tag to generate reports based on specific project stages or priority levels, according to Housecall Pro.
- Use agreements to automatically generate work orders on a recurring schedule, according to Microsoft.
- Structure segments so they share a master job number with sub-numbers like #105-2, according to Housecall Pro.
Configure recurring work orders and priority levels in field service software
This guide details five specific rules for automating site maintenance and prioritizing urgent issues in your field service software. The first rule establishes the numeric range for priority levels. You must assign a value between 1 and 10 to indicate how critical a specific work order is to your site schedule, according to Microsoft. This numeric definition allows your team to sort tasks by urgency without relying on subjective labels.
The second rule involves setting recurring limits for maintenance tasks. You need to define the maximum duration and interval for these automated events to ensure they align with your inspection cycles. The third rule covers the use of job tags to organize different types of site work. These tags help filter reports and distinguish between routine maintenance and emergency repairs.
Setting up priority scales and colors
When configuring the priority scale for your site coordination software, you must define specific numeric ranges and visual indicators to distinguish urgent issues from routine maintenance. The "Define priorities for work orders - Dynamics 365 Field Service | Microsoft Learn" documentation provides the specific fields required for this setup. You begin by establishing the numeric value for each priority level. According to Microsoft, the "Priority Value" field requires you to "Specify a number from 1 through 100." This wide range allows you to create granular distinctions between different levels of site urgency, rather than being limited to a small set of options.
For example, if you are dealing with a critical safety issue or a major structural failure, you need a high-level indicator. The source suggests that "for an urgent priority, set the level of importance to 10." This specific example helps you calibrate where your most critical tasks sit on the scale relative to lower-priority maintenance items. You should map your site’s specific emergency protocols to these numeric values so that your team understands the severity immediately.
Visual clarity is just as important as the numeric value. You can use color coding to help supervisors and field technicians quickly identify the status of a work order. According to Microsoft, you should "Assign a custom color to each priority value." This allows you to create a consistent visual language across your entire project. For instance, you might choose red for the highest urgency levels and green for routine inspections.
The specific field for this action is labeled "Priority Color." The documentation states that for the "Priority Color" field, you must "Specify a color for the priority." By combining the numeric value with a distinct color, you create a two-part identifier that reduces the chance of miscommunication during fast-paced site operations.
Defining recurring schedule limits and intervals
In "Create and edit recurring service types," the default configuration for the recurring limit is set to 12 months, according to ServiceTitan. This baseline establishes the standard horizon for automated scheduling within that specific software environment. While the system allows for extended durations, the documentation notes that the absolute limit of this configuration is 36 months, according to ServiceTitan. However, the same source cautions that booking recurring service events past 12 months may impact account performance and is not recommended for most accounts, according to ServiceTitan. This distinction between the hard technical limit and the recommended operational boundary is critical for maintaining system responsiveness during peak site coordination periods.
Understanding how intervals calculate future dates helps prevent scheduling conflicts. For example, if the Recurrence Type is Monthly and the Recurrence Interval is 3, then recurring events are scheduled every 3 months, according to ServiceTitan. That monthly example gives you a quarterly cycle. Completion timing also matters when a crew finishes a task ahead of schedule. For example, if a daily recurring service event scheduled for August 10 is actually completed on August 8, the next recurring event is scheduled for August 9, according to ServiceTitan. In that example, early completion on August 8 produces a next event on August 9 instead of keeping the August 10 date.
To apply these rules to your site coordination workflow, review your current service agreements and align them with the 12-month recommended limit. If you require longer-term visibility, test the performance impact before extending beyond the default horizon. Check how early completions shift the next event, and confirm your automated schedules still match your physical inspection cycles. You can also record each completed visit in the Construction Daily Log Checklist for Supervisors.
Illustrative example: a quarterly inspection rule
This example uses round, illustrative numbers. A site team wants quarterly inspections. They set the Recurrence Type to Monthly and the Recurrence Interval to 3, so events fall every 3 months. They keep the 12-month default limit, which covers 4 inspections. They give an urgent repair a level of importance of 10 and a routine inspection a lower value such as 5. Each priority also gets its own color, so the two kinds of work are easy to tell apart on the schedule.
Reference table of software settings
The following table lists specific configuration values for recurring work orders and priority levels, drawn directly from the documentation of each named publisher. Each row cites the source that states the rule.
| Publisher | Setting | Value or Rule |
|---|---|---|
| Microsoft | Priority scale range | Choose a number from 1 through 10 to define the level of importance of the priority, according to Microsoft. |
| ServiceTitan | Default recurring limit | By default, this configuration is set to 12 months, according to ServiceTitan. |
| Housecall Pro | Tag based reporting | Once a Job Tag is assigned in Housecall Pro, you can generate reports based on specific project stages or priority levels, according to Housecall Pro. |
| Microsoft | Auto generation source | In Dynamics 365 Field Service, agreements automatically generate work orders on a recurring schedule, according to Microsoft. |
| Housecall Pro | Segment numbering system | All segments share a master job number with sub-numbers (such as #105-2), according to Housecall Pro. |
Using job tags and segments for organization
Job tags and segments structure how you organize site work in your software. Tags categorize individual jobs by type or stage, while segments break a larger project into numbered sub-parts that share a parent job number.
Tag-based reporting and filtering
In Housecall Pro, once a Job Tag is assigned, you can generate reports based on specific project stages or priority levels, according to Housecall Pro. These tags help categorize your jobs and can be used to filter and search within your reports, according to Housecall Pro. For example, Service, Maintenance, and Installation are all examples of job tags for the type of job being done, according to Housecall Pro. Assigning these tags allows you to isolate specific maintenance tasks from installation work when reviewing site coordination data. For inspection records, see our weekly safety inspection log guide.
Segment structure and numbering
Segments provide a different layer of organization. In Housecall Pro, all segments share a master job number with sub-numbers (such as #105-2), according to Housecall Pro. Each segment has its own job page where you can schedule, track, and invoice work separately, while still keeping everything organized under one parent job, according to Housecall Pro. This structure allows a single site project to be divided into distinct phases or areas, each with its own administrative page, while maintaining a unified record under the master number.
Applying tags and segments to site coordination
When setting up your site coordination workflow, use tags to classify the nature of each task, such as maintenance or installation, to enable filtered reporting. Use segments to divide complex projects into manageable sub-jobs, each with its own schedule and invoicing page, all linked to a single parent job number. This approach keeps recurring maintenance tasks and urgent site issues organized within the same software framework.
Review your current project structure and assign tags to existing jobs to enable stage-based reporting.
Automating work order generation from agreements
In Dynamics 365 Field Service, agreements automatically generate work orders on a recurring schedule, according to Microsoft. This mechanism removes the need for manual data entry when a service contract reaches its next scheduled interval. The system handles the creation process based on the parameters defined in the agreement record. You do not need to create each individual visit manually if the agreement is active and configured correctly. The automation relies on the specific recurrence rules set within the agreement itself.
Housecall Pro states that recurring jobs automatically create new jobs on a set recurrence — weekly, monthly, quarterly, or annually, according to Housecall Pro. This allows you to choose the frequency that matches your site maintenance plan. You can select the interval that best fits your operational needs without additional configuration for each individual job. The platform supports these four specific recurrence patterns for automatic job creation. You should verify that your selected recurrence aligns with your contract terms to avoid scheduling conflicts.
When configuring business rules in Oracle Field Service, note that search uses the first 40 characters of the search string, according to Oracle. If your search string exceeds this length, the system will only evaluate the initial portion of the text. You should keep your search criteria concise to ensure accurate matching.
In the same Oracle configuration context, you must select the property that defines the priority of an activity, according to Oracle. This step is required when setting up business rules that involve prioritization. The system requires you to explicitly choose which field or attribute determines the priority level. You cannot assume a default priority property without this selection. This configuration step is part of the broader business rules setup in the platform.
Your next step today
Open your current recurring service agreements and compare each recurrence with your site inspection schedule. Note any that run past 12 months, and confirm each priority has a value and a color.
FAQ
What is the maximum duration for recurring service events in ServiceTitan?
The limit of this configuration is 36 months, however booking recurring service events past 12 months may impact your account performance and is not recommended for most ServiceTitan accounts, according to ServiceTitan.
How do you assign a custom color to a priority value in Microsoft Dynamics?
Specify a color in the "Priority Color" field for each priority value, according to Microsoft.
What is the default configuration for recurring events in ServiceTitan?
By default, this configuration is set to 12 months, according to ServiceTitan.
How do job tags help with reporting in Housecall Pro?
Once a Job Tag is assigned in Housecall Pro, you can generate reports based on specific project stages or priority levels, according to Housecall Pro.
What happens if a recurring work order is completed early?
The next recurring event is scheduled from the early completion: if a daily recurring service event scheduled for August 10 is actually completed on August 8, the next recurring event is scheduled for August 9, according to ServiceTitan.