A development team reviewing a proposed franchise unit also has to consider its commitments to nearby franchisees. Those owners rely on the terms of their grants when they plan their businesses. The team needs to understand where the new location would be and which rights apply there. The development team and affected owners need the same territory information to discuss the proposal.
| Geography | Source of authority | What overlap means |
|---|---|---|
| Signed grant | Agreement and its territory definition | A potential conflict to review against the actual rights and exceptions |
| Radius clause | The agreement's stated origin and distance rule | A geographic intersection requiring review under that clause |
| Modeled drive area | A chosen travel-time assumption | Shared modeled reach, which may differ from granted territory |
Start from the signed territory definition
Record the grant and exceptions
Create a master grant table before drawing. Include the Territory ID, franchisee or unit ID, status, effective date, agreement reference, boundary definition, and version. Use separate statuses for candidate, reserved, granted, and open areas. A proposed unit shouldn't look like an approved grant because it was added to the map.
Keep a separate record of the exceptions. They may concern sales channels, named accounts, outlet types, or other rights described in the agreement. Preserve the reference to the wording that applies so a reviewer can check it rather than relying on a short map label.
For U.S. franchises, review Item 12 of the disclosure document alongside the franchise agreement. FTC guidance separates promises about company or franchised outlets from other sales channels that are reserved. Internet sales and other reservations can affect what the territorial protection means. Check the wording that applies before saying an area is exclusive.
If the documents and the current map disagree, resolve that difference before treating either as the approved workfile. Ask the person who reviews agreements to explain a definition that is unclear. Keep that explanation with the grant record and its effective date.
Audit the ZIP ownership list
For a ZIP-defined grant, prepare a list connecting every ZIP code with its Territory ID and owner. Check repeated ZIP-to-owner pairs first. A row entered twice may make the assignment list longer without adding a second grant.
Then check ZIP codes assigned to different owners. Review those records against the agreements and exceptions. Two entries may reveal an error, an old record, or an arrangement made on purpose that you need to keep on record. Don't remove one simply to make the map look clean.
Keep ZIP codes as text so leading zeros survive. Preserve the original approved list and compare the working copy against it after a correction. A map of customer locations can't replace this list because some granted ZIP codes may contain no current customer pins.
Boundary Tool's My Group / Territory Data fill follows the category with the most markers in a boundary. That color doesn't prove exclusive ownership of the entire ZIP. Use the grant list and explicit assignments to check the franchise areas instead of treating the majority marker color as the authority.
Map the units and candidates
Prepare a file with headers for the unit and candidate locations. Keep a stable ID for each unit or candidate. Add its exact address, Type, status, and the Territory ID that applies. In Maptive, select Create New Map, name the review, and click Continue. Upload the file or paste it under Your Data, then select Map Now. Check the requested column matches and click Done.
To fix a location field, use Categorize Data. You can open it from the Data tab or a marker's gears. Put the address information in Section 1. Check the candidate pins against the actual properties. Keep the original approved grant file apart from this working map.
Build the agreed boundaries in Maptive
Select approved ZIP boundaries
For a manually colored ZIP map, open Map Tools and Boundary Tool. Select the boundary set and a fill option, then click Load Boundaries. Scroll to that set and choose Set Manual Fill.
Choose On Click, On Hover, or Lasso Tool and select Start. Use the approved ZIP list to check the boundaries you select. Click Save, choose the appropriate fill-group action, and click Done. For a new group, choose Create new Fill Group, enter its Name, and Save.
Add Boundaries to Existing Fill Group moves the selected boundaries into that group and removes them from their other fill groups. That matters when correcting an assignment. Check the grant list in the source file before making the move, since the color change itself isn't approval to transfer the ZIP.
If you need territories you can use again, open Map Tools and click Territories. Set Select Action to Create Territories, choose Create Territories Manually, and select Selection under Manual Method. Choose Boundaries and the ZIP boundary set. Enter the territory-group name and click Create Territory Group.
Select the approved boundaries using On Click, On Hover, or Lasso Tool and Start. After checking the selection against the grant list, click Save, name the territory, and Save again. Save and Create Another continues with the next territory. Use a name that connects each area to its Territory ID, rather than relying on the fill color alone.
Represent custom or mileage grants accurately
For a custom outline, choose Create Territories Manually and Drawing. Enter a group name and click Create Territory Group, then Start. Click to add the points of the agreed outline. Close it by clicking the starting point or double-clicking the map, then click Save. Name the territory and Save, or use Save and Create Another to continue.
Compare the finished shape with the agreement's definition. If the outline follows roads, property limits, or another described feature, inspect those edges carefully. A rough freehand outline should be identified and resolved before you present the map as the exact granted area.
For a distance clause, use Distance Radius Circles from Map Tools. Enter the agreed origin under Starting Location, set Proximity Within to the specified distance and units, and click Add Proximity Radius. Confirm the clause's distance convention before using the resulting circle as a map of that grant. A stated driving-distance condition and a circular distance screen may require different treatment.
Keep modeled driving reach in a separate view if the team needs it for market analysis. Drive Time Polygon Tool uses perfect conditions and excludes current and historical traffic. Its road-based reach doesn't replace the signed geography. Don't add an arbitrary buffer around a grant unless the actual agreement or approved planning rule calls for it.
Inspect each proposed location against grants
Find the candidate on the map and record which grant areas contain it or meet around it. Check the location against the Territory IDs and owner list in the source records. Then review the agreement wording that applies there and the exceptions on record.
Review adjacent grants too. A candidate near an edge may require a precise address or property-location check before the team can tell where it is. Keep the candidate ID attached to that finding, especially when a large property's mailing address places the pin away from the proposed unit.
For ZIP grants, confirm the candidate's ZIP against the approved assignment table. Check whether that ZIP is repeated across owners and whether a newer record has replaced either one. The map may show a single fill after manual assignment even while the source records still contain conflicting grants.
Keep a grant conflict apart from overlap between trade areas. Existing and proposed stores may have drive-time areas that cross while their granted territories remain separate. A grant can also include areas beyond the store's current modeled reach. Label each set to show what it means.
Record the result as clear, conflicting, or unresolved, with the evidence behind it. Those are review statuses in your workfile. Maptive doesn't interpret the franchise agreement or approve a legal exception. Send a definition that still needs to be resolved back through the agreement-review process before the location proceeds.
Apply only an approved territory change
Choose the edit that matches the decision
Once the change is approved, click the territory or its three-dot menu. Choose Edit Territory for drawing or drag-and-drop changes. Use Advanced Edit when selecting existing boundaries. Complex outlines may have too many points to drag the corners easily, so use the available selection method when it fits the outline.
Mark the approved area and click Save. Choose Reassign the drawn area between territories when that area should move to one destination territory. Click Done. Reassign adds the area to the selected territory and removes it from the other territories it overlaps.
Add the drawn area to an existing territory preserves overlapping geography. Use it only when the approved decision calls for that result. The similar-looking options can produce different ownership pictures, so inspect both the area you moved it to and the nearby areas affected after saving.
For a ZIP change, compare the final selected ZIPs with the amended assignment list. Confirm the map didn't move another boundary by mistake. Check every affected Territory ID, including areas that no longer contain the transferred geography.
Preserve the approval and effective date
Keep the old grant record, approval, updated definition, and effective date outside the map. Save the map version or territory-group name against that record so the team can identify which view represents the approved change.
Update the master assignment table as well as the shape. A geographic correction with an unchanged source list leaves the next import or review open to the same error. Have the agreement owner check any document changes you need on their own; editing Maptive doesn't amend the agreement.
Make it clear which grants apply now and which changes apply in the future. If a revision takes effect later, identify that date clearly in the review packet. People checking today's candidate need to know which territory definition applies now.
Share the reviewed area and supporting file
Export the supporting records through Export Data. Choose Export Entire Dataset for the intended complete review file, or Export Filtered Data for the selected records. Select .xlsx, .tsv, .csv, or Clipboard, then Export Now. Check that the Territory and unit IDs match the reviewed grant table.
For internal teams that meet the requirements, open the map's three-dot menu from the home screen and select Team Map Share. Choose the members and give them permission to view or edit. This requires multiple licenses bought together, and only one user can edit a map at a time. Assign the editor before the approved update is made.
For a franchisee outside the team, use the map's Share icon, choose Password Protected or Public, select the starting Map view and sharing method, then Copy. Check the exposed data columns, marker popups, and exports in Map Settings under Shared Maps/Presentational Maps before sending the link. Test the copied view outside the owner account.
A starting filter doesn't isolate access to one franchisee's records. Review the dataset being shared and use a separate review file that suits the recipient when the recipient shouldn't see the wider network. Send the candidate decision with the approved grant version and effective date. Include the exceptions that apply and the items that still need review so the next person uses the same territory definition.





