Optimizing Adaptive Capacity after Go-Live

Overview

Once your initial Adaptive Capacity setup is in place and Scheduling is live, the work shifts from configuration to optimization. The early days of online bookings from Scheduling, CSR bookings from Contact Center, and automated assignments from Dispatch produce the data you need to make sharper decisions about caps, rules, exclusions, and settings.

This article doesn't repeat the procedural mechanics already covered elsewhere — instead, it focuses on the judgment layer: how to choose between the optimization tools Adaptive Capacity gives you, how to diagnose common problems in your reporting, and how to confirm a change has propagated across every workflow reading from the same capacity calculation. For the step-by-step mechanics behind any tool referenced here, see the linked articles.

Things to know

• The default capacity is 100%. You only need rules for exceptions or departures from your natural capacity — there is no need to build a rule for every job type or every condition.

• When two rules overlap on the same technicians, the most restrictive rule wins. A 0% rule and a 50% rule that match the same technicians will apply the 0% rule.

• 0% rules and soft caps behave differently in Dispatch. Dispatch hard-honors all-or-nothing rules (0% threshold) for technician-to-zone and technician-to-job-type assignments. Soft caps (1–99%) are guidance to the optimizer rather than hard exclusions.

• An audit trail is available for both Strategic Rules and Basic/Advanced Settings. You can download a .csv of who changed what and when, including before-and-after values for individual rules. This is essential when diagnosing unexpected booking behavior after a change.

• Tag-based rules require the tag on the job before clicking Get Adaptive Availability. Tags added after the availability check don't apply.

• Strategic Rules effects reflect everywhere Adaptive Capacity feeds. Capacity Reporting, Get Adaptive Availability in Contact Center Call Booking, and the Scheduling scheduler all read from the same calculation in real time.

• Atlas is available inside the Strategic Rules builder to accelerate rule creation. Atlas is powered by Titan Intelligence and is scoped specifically to Strategic Rules — it doesn't apply to Basic/Advanced Settings, Technician Exclusions, Manual Adjustments, or Capacity Reporting. When you need a rule built or adjusted, Atlas is the fastest path; when you're changing settings or diagnosing reporting, work directly in those areas.

Best practices

• Build rules sparingly. Start simple and get accustomed to what your natural capacity is before adding more rules.

• Build one rule at a time and test how it works. Too many rules that overlap with each other are hard to debug.

• If a behavior recurs week after week, use a rule instead of a manual adjustment. Manual adjustments are for one-off exceptions; rules automate recurring patterns. For example, if certain technicians work on a weekly schedule, configure a rule based on those technicians, the days of the week, and the time of day rather than re-applying manual adjustments each week.

• Use the audit trail to track changes. Before tightening a rule or changing a setting, download the audit trail so you have a clear before/after when reviewing.

• Review your rules at least quarterly, and any time your team composition, service area, or trade mix changes.

• Always review Atlas-generated rules before saving. Atlas is AI-powered and can make mistakes — it still needs a human to review its output. Correcting Atlas also helps it improve over time.

Step 1: Choose the right tool for the optimization you need

Adaptive Capacity gives you several different ways to adjust capacity. Choosing the right one for the situation is the single most important judgment in post-go-live optimization. The procedural mechanics for each are documented in the linked articles — the table below tells you which to reach for.

Tip: Many optimization needs can be solved by either a rule or a settings change. The cleaner choice is usually whichever sits closer to the root cause. If your dispatch model itself changed, fix calculation defaults; if a specific job type, time window, or technician group needs adjustment, build a rule.

Use Atlas to build rules faster

Previously, creating a Strategic Rule required manually selecting each condition (Business Unit, Job Type, Technician, Zone, Technician Type, Tag Type, Skill, Shift Type, Job Type Group) and calculating the capacity percentage yourself. Atlas removes both steps — you describe the outcome you want in plain language and Atlas fills in the rule for your review.

To use Atlas to build a Strategic Rule:

1. Go to Settings > Adaptive Capacity > Strategic Rules.

2. Click Atlas. 

3. On the New Rule screen, describe the rule you want. Atlas automatically fills out the conditions and threshold based on your prompt and lets you know if it finds any issues or inconsistencies.

4. Continue the conversation with Atlas to refine the rule until it matches what you need. 

5. Review the rule carefully — Atlas is AI-powered and can make mistakes. Save the rule to activate it.

Example prompt patterns Atlas understands:

• "After 5:00 PM, my technicians should only work on No Cool and No Heat jobs"

• "Reduce HVAC capacity by 20% in July"

• "Decrease capacity for plumbing maintenance by 15% next week"

• "Block all non-emergency Plumbing jobs on Christmas Day"

• "Reserve 30% of HVAC capacity for quarterly maintenance"

• "Increase capacity for generator installs by 15% during hurricane season"

• "Reduce general capacity by 50% next week for the downtown office project"

When Atlas is especially useful in post-go-live optimization:

• Seasonal adjustments — describe the seasonal pattern in your data (e.g., "Decrease HVAC capacity by 20% during summer to account for longer repair times during heatwaves") and let Atlas handle the percentage math.

• Holiday and one-week rules — for short, specific windows, plain-language date references save building conditions manually.

• Complex conditions across multiple attributes — when a rule needs to combine a job type, a time range, a business unit, and a technician group, describing it in one sentence is faster than selecting each condition.

Tip: Train your team to use specific, clear phrases when typing requests into Atlas. Vague requests produce vague rules; specific requests produce accurate ones.

Note: Atlas is powered by Titan Intelligence and may generate inaccurate, incomplete, or outdated responses. Verify details before acting. Conversations may be stored to improve the service — avoid sharing sensitive information.

Step 2: Diagnose common reporting symptoms

Capacity Reporting will surface a handful of recurring symptoms post go-live. Each has a specific root cause and fix.

Symptom: A time slot you expect to be available is not showing as Available in Adaptive Availability

Three checks, in order:

1. Check the Dispatch Board for the technician and confirm there are no assigned or unassigned jobs or non-job events that consume capacity.

2. Depending on your calculation default settings, confirm the technician has the skills required for the job, is in the right zone, and is in the right business unit.

3. Check whether an Availability Threshold is set. The threshold adds minutes to the job duration for availability purposes — if your technician has 2 hours available, the job is 2 hours, and you've set a 30-minute threshold, the technician will not have enough time to complete the job within the buffer.

Symptom: 0/0 for all time slots and all business units in Capacity Reporting

This means Technician Shifts is configured for your account but no shifts have been created. To resolve:

• Create shifts for your technicians, or

• Ask Technical Support to turn off your Technician Shifts configuration so Adaptive Capacity can use your business hours in ServiceTitan to populate raw capacity.

Symptom: Red cells in Capacity Reporting indicating overbooking, but you know you still have capacity

Work through three steps:

Step 1 — Add hierarchy layers to the report. If the attribute you're using is a large bucket (for example, a business unit with 30 technicians under it), add a Technician hierarchy level to narrow down where the overbooking is coming from.

Step 2 — Review Capacity Produced and Capacity Consumed for the technicians causing the issue:

• Capacity Produced reflects the available working hours of your technicians.        

  • Make sure Technician Shifts are properly created for the technicians in question.

  • If Technician Shifts is not configured for your account, Adaptive Capacity assumes all technicians are available during your set business hours, leading to potential overbooking.

• Capacity Consumed includes all assigned jobs, potential unassigned jobs, and non-job events with timesheets.        

  • Stacked events double-count capacity. A job scheduled 9:00 AM–11:00 AM and another 10:00 AM–12:00 PM double-counts the 10:00–11:00 window for that technician.

  • Events booked outside a technician's shift also appear as overbooking. A non-job event from 8:00 AM–9:00 PM against a shift that starts at 9:00 AM produces 1 hour consumed / 0 hour produced, -1 open.

Step 3 — Resolve the overbooking:

• Create shifts for each technician that encompass all potential timesheet events.

• Refine non-job events — avoid assigning timesheets to non-job event time blocks on the Dispatch Board so Adaptive Capacity ignores the block.

• Target your filtering — use the Filter in Capacity Reporting to narrow down relevant technicians.

• Exclude specific technicians from scheduling calculations entirely (see Step 3 below).

Symptom: You're making the same manual adjustment in Capacity Reporting week after week

That's a sign the adjustment should be a rule. Manual adjustments are for one-off exceptions. If certain technicians work on a recurring weekly schedule, configure a rule in Settings > Adaptive Capacity > Strategic Rules based on those technicians, the days of the week, and the time of day. The rule automates what you've been doing manually.

Step 3: Choose the right technician exclusion method

Removing a technician from capacity calculations sounds straightforward, but Adaptive Capacity gives you several methods and each has trade-offs. The right choice depends on what's already on in your Calculation Defaults and what else you plan to do with that technician.

To exclude non-managed technicians

Go to Settings > Adaptive Capacity > Settings and turn off the Default to include non-managed technicians' capacity in Availability Calculation toggle.

To exclude managed technicians

Pick one of these four methods based on your setup:

Related: Technicians who work across business units

If your technicians are assigned to BUs but can work on jobs outside those BUs, use one of these methods:

• (Recommended) Use skills and ignore business units. Set up skills to denote which technicians can perform which job types. Then go to Settings > Adaptive Capacity > Settings and turn off Default to include Business Units in Availability Calculation. Availability is then driven by skills, not BU constraints.

• (Optional) Use Business Unit Groups. If business unit groups are set up for your account, turn on Default to honor Business Unit Groups over Business Units. Capacity is filtered by Business Unit Group instead of individual BU. For example, technicians in the HVAC Install BU are shown as Available for jobs tied to both HVAC Install and HVAC Service if both BUs are grouped under the HVAC Business Unit Group — provided the technician is skilled for the job type and in the right zone.

Step 4: Verify changes propagated across the connected workflow

After any meaningful change to rules or settings, confirm every connected workflow is reading the same picture. Because Adaptive Capacity feeds the scheduler, Contact Center Call Booking, and Dispatch from the same calculation in real time, a misalignment is almost always a configuration issue rather than a sync issue.

• Scheduling — From your scheduler, click Test and Preview and book a test job for the affected date and job type. Confirm the slots offered match what your dispatcher sees in Capacity Reporting for the same time window.

• Contact Center — From the Call Booking screen, click Get Adaptive Availability and confirm the same slots appear there.

• Dispatch — Confirm the test job lands on the Dispatch Board (or in Calls > Bookings, depending on your Services Offered setting) with the correct business unit, tag, and job type. If you have all-or-nothing rules in place, confirm Dispatch is honoring them — a restricted technician should not be assigned to a blocked zone or job type.

Note: If you can't run Test and Preview, complete any incomplete configuration sections first. The scheduler flags missing required information at the top of each setup screen.

Tip: If a rule or setting change doesn't appear consistent end-to-end, the most common cause is an unintended interaction with another rule or setting — not a sync delay. Re-check the most restrictive rule that matches the affected technicians, and re-check your Calculation Defaults.

How optimized Adaptive Capacity flows through ServiceTitan Max

Because every workflow reads from the same Adaptive Capacity calculation, an optimization change you make once flows everywhere:

• Scheduling — The online scheduler offers customers only the slots Adaptive Capacity confirms are bookable, including all refinements from your rules, exclusions, and Basic/Advanced Settings.

• Contact Center — CSRs see the same availability in the Call Booking screen via Get Adaptive Availability. Tags configured in Advanced Settings become available as filters; warnings flag slots only available because of rule loosening when that setting is on.

• Dispatch — Automated assignment honors your 0% rules as hard exclusions and respects soft caps as guidance, against the same eligible-technician calculation.

• Marketing — Jobs booked through Scheduling and Contact Center continue to flow attribution back to Marketing via the Scheduling Pro tag and campaign rules configured at go-live. Capacity changes in Adaptive Capacity do not change the attribution path.

• Atlas — Available in the Strategic Rules builder to draft or update rules from plain-language descriptions. Atlas is the conversational interface into Titan Intelligence for capacity planning: you describe the outcome you want, Atlas fills in the conditions and threshold, and you review before saving. It doesn't replace judgment on what to change (that's what Step 1 and Step 2 are for) — but once you know the rule you need, Atlas is the fastest path to building it.

Want to learn more?

• See Configure Adaptive Capacity for Smart Dispatching in ServiceTitan Max (prerequisite)

• See Set up capacity and availability with Scheduling Pro in ServiceTitan Max

• See Use Atlas in Adaptive Capacity Strategic Rules