Skip to main content

Locations & Mapping

Locations and mapping define where work happens.

They connect projects, schedules, and resources to real-world places so teams can understand spatial context, plan efficiently, and avoid confusion.

What Is a Location?​

A location represents a physical place tied to work.

Examples include:

  • A property or parcel
  • A job site
  • A facility
  • A point of service
  • A general address or area

Locations give projects and schedules real-world meaning.

How Locations Fit Into the System​

Locations connect directly to:

  • Projects (where the work is happening)
  • Scheduling and dispatch (where people need to go)
  • Resources (travel and logistics)
  • Mapping and routing

They allow work to be viewed geographically, not just as lists and dates.

Properties and Sites​

Many projects are tied to a property or site boundary.

A property may include:

  • A boundary (polygon)
  • A reference point
  • An address
  • Jurisdiction or area context

Properties help define:

  • Scope
  • Jurisdiction
  • Site constraints
  • Reporting context

Mapping as a View​

Maps are a visual way to view existing data.

They do not create new information — they display:

  • Projects
  • Properties
  • Job locations
  • Scheduled work
  • Resource assignments

Changes made elsewhere appear on the map automatically.

Why Mapping Matters​

Mapping helps teams:

  • See where work is concentrated
  • Understand travel and proximity
  • Avoid scheduling inefficiencies
  • Coordinate field work
  • Provide spatial context during planning

It turns abstract data into something tangible.

Locations and Scheduling​

When work is scheduled:

  • Locations determine travel needs
  • Routes can be planned
  • Conflicts across geography become visible

This is especially important for:

  • Field crews
  • Inspections
  • Site visits
  • Multi-site projects

Locations vs. Projects​

Projects define what the work is.
Locations define where it happens.

A project may have:

  • One location
  • Multiple locations
  • Locations that change over time

Locations vs. Resources​

Resources move between locations.
Locations stay fixed.

Understanding this difference helps with:

  • Dispatch planning
  • Routing
  • Capacity management

Editing and Managing Locations​

Locations can be:

  • Created
  • Edited
  • Assigned to projects
  • Updated as site information improves

This allows the system to stay accurate as conditions change.

What Locations & Mapping Do Not Do​

Locations and mapping:

  • ❌ Do not define scope
  • ❌ Do not schedule work by themselves
  • ❌ Do not assign resources automatically
  • ❌ Do not replace project management

They provide context — not control.

Why Locations Matter Long-Term​

As data grows, locations enable:

  • Geographic reporting
  • Regional planning
  • Trend analysis
  • Better client communication
  • Smarter dispatch decisions

They future-proof the system for spatial insight.

What’s Next​

Now that work, people, time, and place are defined, the final concept explains how communication and history are tracked:

➡️ Communication & Activity

This ties everything together into a clear, searchable record.