PM Zones

PM Zones (Settings > Entities > PM Zones) is a map on which management draw the territory of each project manager. When a job is created its address is checked against these zones and the matching PM is assigned automatically. Operations use it when PMs join, leave or swap areas.

What you see

• A Supervisor dropdown (the system’s internal name for project managers) listing every user with the Project Manager role, plus View All to see everyone’s zones at once. Each PM has a colour, and their zones are drawn in it.
• The Google map with drawing tools for a rectangle, circle or polygon.
• A toggle to show current active jobs as pins so you can see the spread of work.
• A dropdown with Clear last (undo the last shape), Remove selected, Delete All (all zones for the selected PM) and Reset Map (discard unsaved changes).
• Save, which writes the shapes for the selected PM.

What you can do

Draw or change a PM’s zones

1. Choose the PM in Supervisor.
2. Pick a drawing tool and draw one or more shapes over their area. Existing shapes can be selected and removed.
3. Click Save. You are asked to confirm before the zones are replaced.

Move an area between PMs

Remove the shape from the first PM and save, then select the second PM, draw the same area and save.

How it works behind the scenes

When the PM is assigned

The job’s latitude and longitude are tested against every zone:

• when a proposal is accepted and the job is created;
• when a job is created from the Planning Board or from the iPad;
• when a sub job is updated, unless the job has Set Project Manager Manually ticked on its edit page;
• when a job with no PM is used in a communication, so emails are never sent without a project manager.

If the point falls in exactly one PM’s zone that PM is assigned. If it falls in several, the PM with the fewest active jobs (and, on a tie, the lowest total value) wins. If it falls in none, no PM is set and the job appears unassigned for the office to handle.

Manual override

Ticking Set Project Manager Manually on the job (see Jobs) stops the zones from changing the PM later (ROCH-960). A housekeeping command can also flag jobs whose PM differs from the zone PM as manual so they are not silently reassigned. A separate command, Assign PM for unassigned jobs, works through jobs with no PM and applies the zones; it is run by the developers on request rather than on a schedule.

Visits and reallocation

When PM visits are reallocated to cover leave, the job can optionally move to the covering PM and remembers the previous PM for KPI purposes. See Project Manager Visits and KPI.

Tips and gotchas

• Zones only work when the job has coordinates. Jobs whose address failed to geocode show on the Job Map without a pin and will not be auto-assigned.
• Avoid overlapping zones unless you want the workload tie-break to decide; a job that “should have gone to” a particular PM usually sits in an overlap (ROCH-852).
• The drawing tools depend on Google Maps. If the map loads but you cannot draw, report it; a Google change broke drawing once before (ROCH-1990).
• Zones are saved per PM. Saving replaces all of that PM’s shapes with what is currently on the map.