Timing Rule Updates

Updating rules in Chateau is a powerful tool, but the timing of when you make those changes can have a significant impact on technician workflows and tour management.

Why Avoid Mid-Month Rule Changes?

Performing rule updates mid-month or near the end of month can unintentionally disrupt inspection operations and lead to inefficiencies. Below are the primary concerns:

1.  Components Will Be Removed from Tours
   
    
   • When you update rules mid-cycle, components that are currently part of built tours may be automatically removed and rescheduled based on the new rule logic. This disrupts the current month’s planning and execution.
      
2. Even Unchanged Components Can Be Affected
   
    
   • Even components that do not have a frequency change under the new rule may still be removed from their existing tours. This is because rule updates prompt Chateau to re-evaluate all components, which can push them back to the schedule regardless of changes.
      
3. Increases End-of-Month Stress
   
    
   • Having to rebuild tours near the end of a month—especially when completion deadlines are near—adds unnecessary pressure to coordinators and technicians. This increases the likelihood of scheduling errors or incomplete coverage.

Best Practice: Plan Rule Updates for the Start of a Month or Quarter

To avoid disruption:

• Schedule rule updates for the first day of the month or quarter.
• Communicate rule change plans to your coordination team in advance.
• Rebuild tours only after new rules have gone into effect to maintain alignment.

This practice helps ensure:

• Stability in current inspections
• Consistency in performance metrics
• Less manual rework and last-minute changes

For help reviewing or implementing rule changes in Chateau, contact LDARtools Support.

Related Articles:

• Tour Building Best Practices
• Understanding Rule Management in Chateau

Backdating a Rule Applied Date

If a rule was assigned with the wrong effective date — or components were added and approved before a rule was assigned — Chateau will not open leaks for backdated inspections because it sees no active rule at the time of inspection.

What you can do yourself: If the rule was assigned today and you need it to have been effective on an earlier date, this typically requires a data modification from LDARtools Support.

To request a backdated rule fix: contact support@ldartools.com and include:

• Database name
• Rule name
• The date the rule should have been effective
• The LUnit or component list affected

Common scenario: Components were imported and approved before a rule was assigned, then backdated inspections were added. Chateau sees no rule in effect at the time of those inspections and will not create leaks. A data modification can correct the rule assignment date.