Configuring Agreements in Work Order Management

Introduction: Why Agreements Matter

In the world of field service and asset management, an "agreement" is more than just a piece of paper or a digital record; it is the fundamental contract that dictates the relationship between a service provider and a customer. When we talk about configuring agreements, we are talking about the automated logic that determines what services are covered, how much they cost, and when they should happen. Without a well-configured agreement system, organizations often find themselves manually tracking warranties, missing out on recurring revenue from maintenance plans, or—worse—performing free work that should have been billable.

Proper configuration ensures that when a work order is generated, the system automatically understands the constraints of the customer's contract. It dictates whether a service call is covered by a flat-fee subscription, whether parts are discounted, and how the service level agreement (SLA) should be calculated. By mastering the setup of these agreements, you transform your service operation from a reactive, "fix-it-when-it-breaks" model into a proactive, predictable business that manages customer expectations with precision.

Understanding the Core Components of Agreements

To effectively configure an agreement, you must first understand the three distinct pillars that define how these contracts function within a management system: the Header, the Setup, and the Booking/Incident logic.

1. The Agreement Header

The header is the administrative backbone of the contract. It stores the high-level information that identifies the customer, the duration of the contract, and the status of the agreement. This is where you define the "who" and the "when."

• Customer Account: The entity responsible for payment or the recipient of the service.
• Start and End Dates: The lifecycle of the contract.
• Status: Whether the agreement is active, draft, or expired, which controls whether the system should generate work orders.
• Billing Account: Often the same as the customer account, but allows for scenarios where a subsidiary receives service while a parent company pays the bill.

2. Agreement Setup and Preferences

This section defines the operational rules. Do you want work orders to be generated automatically 30 days before a service visit? Do you want to consolidate multiple work orders into a single invoice? These settings prevent administrative bloat and ensure that your field team has the information they need well in advance of the actual appointment.

3. Agreement Bookings and Incidents

This is the "engine room" of the agreement. Agreement Bookings define the recurring schedule—such as "every first Monday of the month." Agreement Incidents, on the other hand, define the specific tasks, skill sets, and parts required for that visit. By linking these, you ensure that a technician arrives with the correct parts and the correct technical instructions every single time.

Callout: Agreements vs. Warranties While they often overlap, it is important to distinguish between them. A warranty is typically a passive record linked to a specific asset (e.g., a pump is covered for parts for two years). An agreement is an active, recurring engagement that often includes labor, scheduled preventive maintenance, and specific service level targets. You might have a warranty on a piece of hardware, but an agreement on the service labor required to maintain it.

Step-by-Step Configuration Guide

Configuring an agreement is a process of layering details. Follow these steps to ensure your setup is robust and functional.

Step 1: Define the Agreement Header

Start by creating the record that links the customer to your service organization.

1. Navigate to your Agreements dashboard and select "New."
2. Assign a descriptive name, such as "HVAC Preventive Maintenance - [Customer Name] - 2024."
3. Select the Service Account. This is the location where the work will be performed.
4. Set the start and end dates. Ensure these align with your fiscal year or the specific contract terms signed by the client.

Step 2: Create Agreement Booking Setups

This step is where you tell the system how often to perform work.

1. Within the Agreement, go to the "Booking Setups" tab.
2. Define the frequency (e.g., Monthly, Quarterly, Annually).
3. Set the "Work Order Type" (e.g., Preventive Maintenance).
4. Configure the "Generate Work Orders X Days in Advance." Setting this to 14 or 30 days gives your dispatchers ample time to adjust schedules if needed.

Step 3: Define Agreement Incidents

Agreement Incidents translate the contract into a "to-do list" for your technicians.

1. Inside the Booking Setup, add a new Incident.
2. Select the Incident Type (e.g., "Annual Inspection").
3. Associate the necessary "Service Tasks" (e.g., "Check filters," "Lubricate bearings," "Verify pressure gauges").
4. Associate the "Products" (e.g., specific filters or lubricants) that are covered by the agreement.

Tip: Use Incident Templates Avoid creating custom tasks from scratch for every agreement. Create a library of "Incident Types" that represent your standard service offerings. This allows you to update the standard procedure for an "Annual Inspection" in one place, and have it reflect across all active agreements.

Leveraging Entitlements for Precision

Entitlements are the specific "rights" a customer has under an agreement. If an agreement is the contract, entitlements are the individual clauses within that contract that grant a discount or a service level.

Configuring Entitlement Rules

Entitlements are usually applied at the work order level. When a work order is created, the system checks the customer's active agreements and applies the relevant entitlements. You should configure these based on:

• Asset Coverage: Is this specific piece of equipment covered?
• Service Type: Does this agreement cover emergency repairs or only scheduled maintenance?
• Pricing Discounts: Does this agreement provide a 15% discount on labor or parts?

Practical Example: The "Gold" Service Level

Imagine a customer on a "Gold" contract. Their entitlement might be configured as follows:

• Priority: High.
• Response Time: 4 hours.
• Labor Discount: 100% (Included in the monthly fee).
• Parts Discount: 20% off list price.

When you create a work order for this customer, the system automatically flags it as "High Priority" and applies the pricing adjustments to the quote or invoice. This eliminates the need for the technician or the billing department to manually look up the contract terms.

Technical Implementation and Data Logic

For developers or system administrators, understanding how these objects relate in the database is vital for troubleshooting. Most modern field service platforms utilize a relational model where the Agreement is the parent, and Bookings and Incidents are child records.

Sample Pseudo-Code for Agreement Generation

When the system generates a work order from an agreement, it is essentially performing a transformation of data. Here is the logic flow in pseudo-code:

function generateWorkOrder(agreementId) {
    let agreement = database.getAgreement(agreementId);
    let bookingSetup = agreement.getBookingSetup();
    
    // Check if the current date is within the generation window
    if (isWithinWindow(bookingSetup.nextRunDate, bookingSetup.advanceDays)) {
        let workOrder = new WorkOrder();
        workOrder.accountId = agreement.serviceAccount;
        workOrder.agreement = agreement.id;
        workOrder.priority = bookingSetup.priority;
        
        // Add incidents defined in the agreement
        let incidents = bookingSetup.getIncidents();
        incidents.forEach(incident => {
            workOrder.addIncident(incident);
            workOrder.addTasks(incident.tasks);
            workOrder.addProducts(incident.products);
        });
        
        workOrder.save();
        updateNextRunDate(bookingSetup);
    }
}

This logic highlights why it is crucial to have clean data. If your bookingSetup has missing incident definitions, the generated work order will be empty, leading to frustrated technicians and confused customers.

Comparison of Agreement Types

Best Practices for Agreement Management

1. Maintain a Standardized Incident Library

As mentioned earlier, consistency is key. If you have 500 agreements, you do not want 500 different ways to perform a "Filter Change." Create a master list of Incident Types that include pre-defined tasks and product requirements. This makes reporting much easier because you can aggregate data across all customers to see, for example, how much time is spent on "Filter Changes" globally.

2. Automate the Expiration Workflow

An expired agreement that isn't renewed is lost revenue. Configure your system to send alerts to the account manager 60, 30, and 7 days before an agreement expires. This proactive communication is a standard industry practice that significantly improves renewal rates.

3. Use "Agreement Booking Dates" for Visibility

Most systems allow you to see the "Booking Dates" generated for the entire term of the agreement. Review these annually with the customer. If they have a facility shutdown in July, you can easily move the scheduled maintenance date in the system to avoid a conflict.

4. Audit Your Entitlement Logic

Periodically run a test work order for your major customers. Does the system correctly apply the discounts? Does it flag the correct priority? Testing these rules once a quarter ensures that a configuration change elsewhere in the system hasn't accidentally broken your contract logic.

Common Pitfalls and How to Avoid Them

Pitfall 1: The "Over-Configured" Agreement

Some administrators try to put too much detail into a single agreement. They create unique incidents for every single asset, leading to thousands of records that are impossible to manage.

• The Fix: Use "Asset Categories." Instead of an incident for "AC Unit Model X," create an incident for "General AC Inspection" and use the system's ability to filter by asset type.

Pitfall 2: Ignoring Billing Recurrence

An agreement is only as good as its ability to generate revenue. Many users set up the service schedule but forget to configure the "Invoice Setup."

• The Fix: Always link your agreement to a billing product. Ensure the invoice frequency matches the service frequency if you are bundling costs, or keep them separate if you bill for parts consumed during the visit.

Pitfall 3: Manual Override Habit

Technicians or dispatchers often manually change prices or priorities on work orders because they "know" the contract. This creates a disconnect between the system data and the reality of the contract.

• The Fix: If users are constantly overriding, it means your configuration is wrong. Use the override as a signal to go back and update the agreement settings to reflect the actual business practice.

Advanced Configuration: Managing Multi-Site Customers

For large customers with multiple locations, managing individual agreements for every site is an administrative nightmare. Instead, utilize "Parent-Child" account structures to manage agreements at the corporate level.

1. Create a Master Agreement: Link this to the corporate headquarters.
2. Define Scope: Specify that the agreement covers all locations under the parent account.
3. Use Territory Logic: Configure the system to automatically assign work orders to the nearest technician based on the specific location's territory, even if the agreement is held at the parent level.

This allows you to manage the contract terms in one place while maintaining operational flexibility at the local level. If the corporate office negotiates a 5% increase in labor rates, you only have to update the Master Agreement once, and the change propagates to all child locations.

Frequently Asked Questions

Q: Can an agreement cover multiple assets?

Yes. Most modern systems allow you to associate multiple "Customer Assets" with a single agreement. You can define an incident that applies to all of them or create specific incidents for specific assets within the same agreement.

Q: What happens if a customer wants a one-time service that isn't in the agreement?

The agreement should be configured to handle "Covered" vs. "Non-Covered" work. When creating a work order, the system should allow you to select if the work is part of the agreement or a separate, billable call.

Q: How do I handle parts that are not in the standard incident?

In your work order configuration, ensure that you allow for "Ad-hoc" product additions. Even if an agreement is defined, your technicians should have the flexibility to add parts if they encounter a unique issue, provided the system is configured to flag those as "Billable" if they fall outside the agreement scope.

Key Takeaways for Success

• Agreements are the Source of Truth: Treat the agreement as the primary contract. If it isn't in the agreement, it shouldn't be assumed as "free" or "covered."
• Standardization is Your Best Friend: Never reinvent the wheel for every customer. Use Incident Templates to keep your service delivery consistent and your data clean.
• Automate to Reduce Errors: Use the system’s built-in generation tools to create work orders in advance. This removes the human element of "forgetting" to schedule a maintenance visit.
• Entitlements Ensure Profitability: Use entitlement rules to automatically apply discounts and SLAs. This protects your margins by ensuring that only authorized services are provided without charge.
• Proactive Renewal Management: Your agreement system should be a sales tool. Use expiration alerts to keep your revenue stream stable and your customers happy.
• Audit Regularly: Configurations can drift over time. Conduct quarterly reviews of your agreement logic to ensure that your system-generated work orders match your actual service contracts.
• Think Scalably: Always design your agreement structures with the "Parent-Child" model in mind. Even if you only have one customer today, building a scalable architecture now will save you hundreds of hours later as you grow.

By following these principles, you move beyond simple record-keeping. You build a robust foundation that supports your field service team, improves customer satisfaction through clear expectations, and ensures that your business remains profitable by accurately accounting for every service provided. Configuring agreements is not just a technical task; it is a strategic business activity that defines the quality and reliability of your service organization.