Franchise territory mapping software
Define every territory on a map, keep it identical to the schedule in the franchise agreement, mark what is sold, reserved and open for development, route every web enquiry and tracked call to the franchisee who owns the ground it came from, and answer “someone is selling in my territory” with a report instead of an argument.
Franchise territory mapping software is the system a franchisor uses to define the geographic territory attached to each franchise agreement, keep those territories from overlapping, show which territories are sold, reserved or available, and enforce the territory in day-to-day operations — most importantly by routing customer enquiries to the franchisee whose territory they fall in. In the United States the territory is described in Item 12 of the franchise disclosure document; everywhere else it is a schedule to the agreement. Either way it is a promise the franchisor has to keep for the life of the contract.
In most networks that promise lives in a PDF map attached to the agreement, a list of postcodes in a spreadsheet, and a development manager’s memory of what has been sold. That works for twenty locations. At two hundred it produces the classic disputes: two franchisees who both believe a suburb is theirs, a new unit sold into ground an existing owner thought was protected, leads from a border postcode going to whoever answered first, and a franchisee who cannot get a straight answer to “is anyone marketing into my area”. Every one of those disputes costs more than the software that prevents it.
Territory mapping inside a franchise ERP makes the map the single definition: the boundary the candidate is shown, the schedule printed into the agreement, the polygon the CRM routes leads by, the area the location’s website page and store locator serve, and the ground the reports measure performance on. This page sets out what the software has to do, the ways territories are defined, how encroachment is detected and how Gorilla Dash builds it into the platform the network already runs on.
Your franchise agreement defines each territory and the rights that come with it. Gorilla Dash enforces the boundaries and rules you configure and keeps the record of who was granted what and when; it does not interpret the agreement, and an encroachment report is evidence for a conversation with your franchise counsel, not a ruling.
Drawn once by development, then reused by legal, marketing, operations and reporting without ever being redrawn.
Head office lays out the market as territories before any are sold — by postcode groups, drive-time rings around a planned site, a population target, or hand-drawn polygons — and sees the whole country as sold, reserved, available and off-limits ground.
A new or edited territory is tested against every existing one the moment it is drawn. An overlap is shown on the map with the exact area in dispute and the agreement it conflicts with, and the boundary cannot be saved as exclusive until it is resolved.
When a candidate in the development pipeline chooses a territory it is reserved against their record, shown to other candidates as unavailable, and released automatically if the deal falls through or the reservation expires.
The territory schedule — the map image, the postcode list and the written description — is generated from the polygon into the disclosure document and the agreement. The contract and the map cannot disagree because they are the same object.
From opening day every web enquiry, tracked call, form and store-locator search is geocoded and assigned to the territory it falls in, so the franchisee who owns the ground gets the lead. The routing decision is logged and visible to both the franchisee and head office.
Sales, enquiries and marketing spend are reported by territory, and the encroachment report shows any lead, sale or campaign that crossed a boundary and where it went. When an owner raises a concern, the answer is a report, not a recollection.
A map on its own is a picture. Territory management is the map plus the rules, the status, the contract and the operational enforcement that make the boundary mean something.
Postcode or ZIP lists, a radius around an address, a drive-time or distance ring, a population count, a local-government area, or a polygon drawn freehand — with the written description in the agreement generated from whichever method was used.
Not every territory is exclusive. The system distinguishes exclusive territories, protected areas with carve-outs (national accounts, online sales, non-traditional venues), shared or open territories, and rights of first refusal, and applies the right rules to each.
Every boundary is tested against every other on save. Overlaps are blocked or flagged according to the territory type, and the encroachment report lists leads, sales and campaigns that crossed a line after the fact.
Sold, reserved, available, under negotiation, company-owned and excluded ground colour-coded on one map, with the reservation expiring automatically and the candidate record attached. Development sees what it can sell; leadership sees how much of the market is covered.
The map image, postcode list and description for Item 12 and the agreement schedule are produced from the polygon, versioned with the agreement, and regenerated when a territory is legitimately amended at renewal or transfer.
Every enquiry with an address, postcode or phone area is placed in a territory and assigned to its owner, with configurable fallbacks for the gaps: nearest location, round-robin among neighbours, or head office. Ambiguous cases are shown to both sides with the reason.
The brand’s store locator and each location’s website page serve the territory, not just the nearest pin — so a customer inside a territory is sent to its owner even when a neighbouring location is physically closer.
Revenue, enquiries, conversion, marketing spend and penetration per territory, so a territory’s value is a number: what it produces today, what a comparable territory produces, and what an unsold one is worth to the next candidate.
Territories nest: a master territory or area-development agreement holds the units beneath it, each with its own boundary and development schedule, so a regional developer’s obligations and the units they have opened are tracked on the same map.
Most networks use more than one. The method a brand chooses should match how the agreement describes the territory and how leads actually arrive.
| Method | How it is defined | Suits | Watch out for | In Gorilla Dash |
|---|---|---|---|---|
| Postcode or ZIP list | A set of postal codes owned outright | Home services, trades and delivery businesses where the customer’s address is known | Postcodes change and vary wildly in size; border postcodes need a rule | Selected on the map or imported; leads matched on the customer postcode |
| Radius | A circle of a set distance around the location | Retail and food with walk-in customers | Circles overlap where locations are dense and ignore rivers, highways and drive time | Drawn from the address; overlaps flagged on save |
| Drive time | The area reachable within a set number of minutes | Mobile services and anything where travel time matters more than distance | Shape changes as roads change; needs a fixed snapshot for the agreement | Computed and frozen as a polygon when the territory is reserved |
| Population or household count | Enough ground to contain a target number of people or households | Networks that size territories by demand rather than area | Census data ages; the boundary still has to be drawn somewhere | Used as a target while drawing; the saved polygon is what the agreement uses |
| Drawn polygon | A boundary traced by hand on the map | Anything irregular — a shopping strip, a river boundary, a carve-out around a national account | Needs a written description for the contract, not just a picture | Description and postcode list generated from the shape |
| Administrative area | A council, county, state or metropolitan boundary | Master and area-development agreements | Coarse; units within it still need their own boundaries | Nested territories: the area holds the units beneath it |
The territory and the dispute are illustrative; the sequence is how the map is designed to be used across development, legal and operations.
Month 0
Head office
Development lays out a new metropolitan market as nine territories sized by household count and adjusted by hand around the river and the highway. Two are reserved for company stores, one is excluded around a national account, six are available. The whole map is visible to leadership as covered, planned and open ground.
Month 2
The development manager
A candidate in the pipeline chooses the north-east territory. It is reserved against their record for 60 days and shown as unavailable to the other four candidates looking at the same market. The territory schedule — map, postcode list and description — is generated into their disclosure document without anyone redrawing it.
Month 4
Legal
The agreement is signed with the schedule generated from the same polygon. The territory’s status changes to sold, the candidate record becomes the location, and the boundary is now the rule the CRM will route leads by from opening day.
Month 9
The franchisee
The owner reports that a neighbouring location is quoting jobs in their suburbs. The encroachment report shows three enquiries from inside the boundary in the last month: two were routed correctly to the owner and are in their pipeline; one came in by a direct call to the neighbour and was logged there. Head office reassigns it, both sides see the record, and the conversation is over in a day.
Month 18
Leadership
The sold territories in the market are reported by revenue, enquiries and marketing spend per household. The remaining available territory is compared with the two most similar sold ones, and development goes to the next candidate with a number instead of a guess.
Every one of these starts with a boundary that exists in more than one place and agrees with itself in none of them.
The problem
A territory sold in 2019 and one sold in 2024 were drawn by different people from different postcode lists. Both agreements include the same suburb. Neither owner knew until a customer complained about being contacted twice.
What good looks like
Every boundary is checked against every other when it is drawn. The 2024 territory could not have been saved as exclusive over the 2019 suburb, and the conflict would have been shown to the development manager before the candidate ever saw a map.
The problem
The agreement schedule lists postcodes; the map attached to it was drawn by hand and does not match; the CRM routes by radius. Three definitions of the same territory, and the franchisee picks whichever suits the argument.
What good looks like
The schedule, the map and the routing rule are generated from one polygon. There is one definition, it is versioned with the agreement, and any amendment regenerates all three.
The problem
Web enquiries land in a shared inbox and are claimed by the fastest franchisee. Border postcodes are a free-for-all. The owners who lose out stop trusting the brand’s marketing, and the marketing fund becomes a fight.
What good looks like
Every enquiry is geocoded and assigned to the territory it falls in, with a logged reason. The fallback rules for gaps and ambiguous cases are configured once by head office and visible to every franchisee.
The problem
A new unit is sold into what an existing owner believed was a protected area under a right of first refusal. The owner is right, the agreement says so, and the brand now has a lawsuit and a resale to unwind.
What good looks like
Rights of first refusal, protected areas and carve-outs are territory types with rules. An attempt to reserve or sell into protected ground triggers the right-of-first-refusal workflow rather than a sale.
The problem
Development’s view of the market is a spreadsheet of sold territories and a feeling about the rest. The board asks how much of the country is covered, and the answer takes a week.
What good looks like
The map is the inventory. Sold, reserved, available and excluded ground is a filter, coverage is a percentage, and the available territories are listed with the performance of the sold ones most like them.
The problem
The website’s locator shows the nearest pin. A customer well inside one territory is sent to the neighbour because the neighbour’s shopfront is closer. The owner sees their own marketing feed a competitor.
What good looks like
The locator and each location page serve the territory, so a customer inside a boundary is sent to its owner. The nearest pin is a fallback for ground nobody owns, not the rule.
The map is not a separate tool. It sits in the same franchise ERP as the development pipeline, the disclosure documents, the CRM, the websites and the reports — which is why one polygon can be the boundary everywhere.
The polygon drawn by development is the schedule in the agreement, the routing rule in the CRM, the area the store locator serves and the ground the reports measure. Nothing is redrawn and nothing can disagree.
Web forms, tracked calls, appointment bookings and store-locator searches are captured by the platform with the customer’s location, so routing by territory is a rule on data Gorilla Dash already has rather than an integration project.
Every routing decision, every lead’s origin and every campaign’s reach are logged. The encroachment report is the same evidence for the franchisee and for head office, which is what ends the argument.
Sold, reserved and available ground on one map, reservations tied to candidates in the pipeline, and the value of an unsold territory estimated from the sold ones most like it.
Item 12 descriptions and agreement schedules are generated from the polygon and versioned with the disclosure document, so legal never re-types a postcode list and the candidate never sees a boundary the contract will not honour.
Location websites, local campaigns, SMS and email marketing from the platform are scoped to the territory’s customers, so a franchisee’s own marketing reaches their ground and the national fund’s campaigns are reported by the territory they produced revenue in.
Franchise territory mapping software defines the geographic territory attached to each franchise agreement on a map, keeps territories from overlapping, shows which are sold, reserved and available, generates the territory schedule into the disclosure document and the agreement, and enforces the boundary in operations by routing enquiries to the franchisee whose territory they fall in. It replaces the PDF map, the postcode spreadsheet and the development manager’s memory with one definition used everywhere.
Encroachment is a franchisor or another franchisee selling, marketing or opening inside ground an existing franchisee has exclusive or protected rights to. It is prevented in two places: at the boundary, where a new or edited territory cannot be saved over an exclusive one; and in operations, where every lead is routed by the territory it falls in and the encroachment report shows any lead, sale or campaign that crossed a line and where it went.
By postcode or ZIP list, a radius around an address, a drive-time ring, a population or household target, an administrative area, or a polygon drawn by hand — and most networks use more than one. Whichever method is used, the saved boundary is a polygon, and the written description, postcode list and map image for the agreement are generated from it.
Yes, because they are the same object. The Item 12 description and the agreement schedule are generated from the polygon and versioned with the disclosure document. If a territory is amended at renewal or transfer, the schedule is regenerated and the previous version is retained against the previous agreement.
Every enquiry the platform captures — web forms, tracked calls, appointment bookings, store-locator searches — is geocoded from the customer’s address, postcode or phone area and assigned to the territory it falls in. Head office configures the fallbacks for ground nobody owns and for ambiguous cases: nearest location, round-robin among neighbours, or hold at head office. The decision and its reason are logged and visible to both the franchisee and head office.
Carve-outs are part of the territory definition. A territory can be exclusive with exceptions for national accounts, online orders, non-traditional venues such as airports and stadiums, or a specific customer list, and the routing and encroachment rules honour the exceptions. What the agreement reserves to the franchisor is what the system reserves.
Yes. Territories nest, so an area-development or master-franchise territory holds the unit territories beneath it, each with its own boundary, status and development deadline. The developer’s obligation to open a number of units by a date is tracked against the units actually reserved and opened on the map.
Yes. The brand’s store locator and each location’s website page serve the territory rather than the nearest pin, so a customer inside a boundary is sent to its owner even when a neighbouring location is physically closer. The nearest location is the fallback for ground nobody owns.
Each franchisee sees their own territory, its boundary, the leads routed into it and the encroachment report for it. Head office and territory managers see every territory by name, scoped to the region they are responsible for. Development sees availability across the whole market. Visibility follows permissions, as it does everywhere else in the platform.
Territory mapping is part of the franchise development and compliance module, offered alongside the Gorilla Dash base platform (USD $52 per location per month with unlimited team members). Lead routing by territory for existing locations is available to every network on the platform. Talk to us about the development module and we will scope it with you.
Bring your territory list and we will show you the sold, reserved and open ground, a lead routed by boundary and the encroachment report — book a demo with our team.
Book a Demo