Your hierarchy is the backbone of everything else in Pack Command Center. Get it right and reports roll up cleanly, permissions land where they should, and adding a new location is a five-minute job. Get it wrong and you spend months untangling numbers that never quite add up. Here's how to model your real company with the Organization, Business, Branch, Department, Team and User levels.
Updated July 2026 · 6 min read
The mistake most teams make is bending their company to fit the tool. Do the opposite. Sketch how your business actually works today — the brands you operate, the physical locations you dispatch from, the departments that own the work — and then map each of those onto a level in the hierarchy. The six levels run top to bottom: Organization, then Business, then Branch, then Department, then Team, then User. Each level rolls its numbers up to the one above it, so the shape you choose here is the shape of every report you will ever run.
A Business is a distinct brand or company — its own name, logo, licensing and often its own books. A Branch is a location or service area that operates under one of those businesses. If you run "Tap's Pest Services" and "Tap's Lawn Care" as separate brands with separate customers, those are two businesses. If you run one brand out of three cities, that is one business with three branches. The quick test: if it has its own logo and invoices, it is probably a business; if it shares the brand but has its own crew and territory, it is a branch.
Below the branch, Departments group the kinds of work you do — sales, service, install, office — while Teams are the actual crews or pods inside a department. You do not need a department for every job type; use them where the distinction changes who sees what or how you want to measure results. A good rule is to add a level only when it answers a question you will actually ask, such as "how did the install department perform last month" or "which service team closed the most tickets."
Permissions follow the hierarchy, so assign each person at the lowest level that still gives them everything they need. An owner sits at the Organization or Business level and sees everything beneath it. A branch manager is scoped to their branch and rolls up only their own locations. A technician lives on a team and sees their own jobs. Assigning roles this way means a manager cannot accidentally see another region's numbers, and a new hire inherits the right access the moment you place them on the correct team.
The first is flattening everything — dumping every location, crew and department into one big list because it feels simpler at setup. It is, until you try to compare regions or lock down permissions and discover there is no structure to filter on. The second is nesting too deep, inventing sub-teams and sub-departments that mirror an org chart no customer ever sees. Every extra level is something to maintain and something to click through in a report. Aim for the shallowest hierarchy that still separates the numbers you need to compare.
Once the structure mirrors reality, everything downstream gets easier. Revenue, review scores and job counts roll up automatically from user to team to branch to business to organization, so you can drill from the top-line number straight down to the crew that drove it. And when you open a new location, you add one branch under the right business and it inherits the roles, departments and reporting rollups already in place — no rebuild required. The hour you spend modeling the hierarchy correctly is the hour that lets you scale without ever touching it again.
Explore how Organization, Business, Branch, Department, Team and User levels drive reporting and permissions across every location.