Projects Overview

Projects are organized into two levels: master projects and child projects.

Master projects serve as a general container and are not tied to any specific customer. Child projects, on the other hand, are customer-specific and always sit underneath a master project. A master project can have one or many child projects beneath it.

There are several ways this structure can be used. For example, you might set up a master project for an ongoing or open-ended order, with one child project created per customer. In a bid scenario, you could have one master project representing a job being competed for, with multiple child projects — one per competing customer — where only the winning customer's child project moves forward. You could also use a master project to group related jobs together, with each child project representing a different phase, site, or scope of work under that same umbrella.

Beyond organizing customers and bids, projects serve an important functional purpose: they store location information. Each child project can hold multiple locations. This is a required step before any order can be created — you must have a project in place first. A helpful way to think about the division of responsibility is that projects save location information, while orders save products and price lists.