Schedule A Territory: What the ZIP List Actually Commits You To

If Schedule C is the pricing engine of a FedEx Ground ISP agreement, Schedule A is the map: the definition of the Contracted Service Area you're responsible for. It often reads as an unglamorous list of ZIP codes and boundaries, which is why it gets skimmed at signing. But the territory is the one input that touches everything downstream — volume, density, fleet, labor, and what your operation is worth to a future buyer. Here's how to read it like it matters.

What it is

The Schedule A defines the geographic service area attached to your agreement — the area whose packages you are contracted to service. Alongside the other schedules (terms, rates), it's what makes a CSA a CSA: a specific territory, under a specific contract, with its own Schedule C rates. When people talk about "buying routes," the durable thing being acquired is, in large part, this defined service area and the agreement wrapped around it.

What the territory commits you to

• Coverage, not convenience. The service area is an obligation: the volume that arrives for it is yours to deliver, whatever the day brings. You staff and equip for the territory's demands — its geography decides your route count, vehicle mix, and how brittle your operation is when a driver calls out.
• The economics of its shape. Density is destiny in stop-based compensation. A compact suburban ZIP set and a sprawling rural one can carry similar package counts with very different miles, hours, and cost per stop. The ZIP list isthe density profile — read it with a map open.
• Its trajectory. Territories aren't static: subdivisions get built, retailers open and close, demographics shift. The volume a service area produces in three years is a function of what's happening on the ground there now — which is knowable, if you look.

What to check — before signing or buying

• Map every ZIP. Drive or at least virtually tour the boundaries. Note the share of dense residential vs. rural area vs. commercial, and where the terminal sits relative to the territory — stem time (terminal to first stop) is unpaid geography.
• Tie the territory to the settlements. For an acquisition: do the seller's settlement volumes make sense for this geography? Ask which parts of the territory produce the volume and what's changing there — construction, a new fulfillment pattern, a major shipper's plans.
• Confirm what document version you're reading.Like rates, territory definitions can be amended over the life of an agreement. Diligence on a stale Schedule A is diligence on a business that no longer exists; get the current one and note its effective date.
• Understand it per-entity. In a multi-CSA operation, each agreement has its own Schedule A. Know which territory belongs to which CSA code — it's the same join discipline that settlement checking requires, applied to geography.

Territory in the weekly numbers

After signing, the Schedule A mostly disappears from view — but its effects are in every settlement: your stops, your packages per stop, your revenue mix are all the territory expressing itself week by week. That's the level where Route Impact works — it tracks each CSA's weekly settlement series separately, so territory-level trends (densification, volume drift, mix change) are visible per entity rather than blended away, and contract analysis at renewal time can be grounded in what your actual territory has been producing. For the signing decision itself, nothing replaces reading the document and driving the map; the numbers just tell you, afterward, whether the territory is becoming more or less of what you bought.