Service Area Optimization

Effective zone configuration goes beyond drawing boundaries and assigning industries. Optimizing your service areas means reducing unnecessary overlap, eliminating coverage gaps, using negative zones strategically, and structuring your zone hierarchy for operational clarity.

Coverage Analysis

The first step in optimization is understanding your current coverage. The Coverage tab's other-zones overlay shows all zones with their boundaries rendered on the same map. Boundaries from other zones appear as dimmed shapes with dashed outlines, each in that zone's color. Labels display the zone name and priority rating, making it easy to identify overlap patterns.

Use this view to answer key questions: Are there gaps between zone boundaries where customer addresses would not match any zone? Are zones overlapping unnecessarily, creating confusion about which zone's rules apply? Are negative zones positioned correctly to block non-serviceable areas?

Reducing Unnecessary Overlap

Zone overlap is not inherently bad — the priority system handles it cleanly. However, excessive overlap can lead to confusion and make it harder to reason about which zone's pricing and scheduling applies to a given address.

When two zones overlap and have the same priority rating, the tiebreaker logic becomes important. If you find yourself relying on tiebreakers frequently, consider whether the overlapping zones should be restructured. Options include adjusting boundaries to reduce the overlap area, differentiating priority ratings to make resolution deterministic, or merging overlapping zones if they serve the same business purpose.

Strategic Use of Negative Zones

Negative zones are your most powerful tool for controlling where you do not operate. Use them for areas with known access issues — rural roads that are too far from your base, gated communities where you lack access agreements, or areas affected by construction or natural disasters.

Create negative zones with descriptive names and clear documentation in the description field. "Rural Hills No-Go — roads unmaintained beyond mile marker 15" is much more useful than "Exclusion Zone 1" when someone reviews your zone configuration months later.

Remember that negative zones always win regardless of priority. A single negative zone boundary touching an address blocks all positive zones from servicing that address. Be precise with negative zone boundaries to avoid accidentally excluding serviceable areas.

Coverage Gap Management

Gaps in coverage mean customer addresses that do not match any zone. The default zone catches these addresses as a fallback, but relying heavily on the default zone usually indicates incomplete coverage configuration.

To identify gaps, compare your zone boundaries against the postal codes your customers commonly use. If a postal code falls outside all zone boundaries, consider extending an existing zone's boundary or creating a new zone for that area. The postal code visualization on the Coverage tab helps identify these gaps visually.

Zone Hierarchy for Organization

The parent-child zone hierarchy does not create automatic rule inheritance — it is purely organizational. Use it to group related zones under logical parents for easier navigation and reporting.

A common hierarchy structure uses geographic regions as parents (e.g., "Pacific Northwest"), metro areas as children (e.g., "Portland Metro," "Eugene Metro"), and specific neighborhoods as grandchildren (e.g., "Downtown Portland," "East Portland").

This hierarchy helps administrators quickly find the zone they need when managing a large number of zones. It also supports reporting at different geographic levels.

One of the most powerful optimization techniques is boundary sharing. Rather than drawing duplicate boundaries for overlapping zones, create a single boundary and link it to multiple zones. For example, the "Eugene City Limits" polygon might be linked to both the standard "Eugene Metro" zone (priority 50) and the "Premium Same-Day" zone (priority 75).

This approach ensures geographic consistency — both zones use the exact same boundary shape. When the boundary needs updating (e.g., city limits change), you update it once and both zones reflect the change.

Temporal Optimization

Use temporal boundaries and seasonal schedules to automatically adjust coverage over time. Summer lake service areas can activate in May and deactivate in September. Stadium surge zones can activate during game days. Holiday schedules can reduce operating hours during major holidays.

This temporal awareness reduces manual zone management and ensures your coverage adapts to seasonal demand patterns without constant administrator intervention.

Performance Considerations

Zone resolution runs on every customer booking, so boundary evaluation performance matters. Keep polygon boundaries reasonably simple — excessively detailed polygons with thousands of vertices slow down point-in-polygon calculations. Use postal code sets for simple service areas where polygon precision is not needed. Composite boundaries add computational overhead from set operations — use them only when the geographic modeling requires it.