You Need a System for Your Jobsite Locations
You’re standing on a sprawling construction site, plans in hand, and you need to assign a work order for the HVAC installation in the north wing of the third floor. Your foreman asks for the latest inspection report for the concrete pour at the southeast foundation. Without a clear system, this information gets lost in a sea of emails, spreadsheets, and handwritten notes.
This is where Procore’s Locations feature becomes your project’s single source of truth. Creating locations in Procore is not just an administrative task; it’s the foundation for organizing all your project data geographically. It allows you to tie documents, observations, tasks, and costs to specific areas of your build, making information instantly findable and actionable.
Whether you’re managing a multi-building campus, a high-rise with dozens of floors, or a linear project like a highway, a well-structured location tree is critical. This guide will walk you through the entire process, from initial planning to daily management, ensuring your team can track work with precision.
Understanding the Procore Location Hierarchy
Before you start clicking “Add,” you need to grasp the structure. Procore locations are organized in a parent-child hierarchy, much like a folder system on your computer. This tree structure allows for incredible detail and logical organization.
At the top, you have the Project Level. This is your entire jobsite. Beneath that, you create parent locations, which could be buildings, phases, or major zones. Under each parent, you can nest child locations for floors, wings, rooms, or even specific assets like mechanical rooms or elevator shafts.
The power of this system is that any item logged against a child location automatically rolls up to its parent. A punch list item for “Room 310” is also part of “Floor 3” and “Building A.” This enables reporting at any level of granularity your project requires.
Common Location Structure Examples
Your structure should mirror how your team thinks about the project. For a commercial office building, a typical tree might look like this:
– Building A
— Level 01 (Lobby)
— Room 101 (Reception)
— Room 102 (Conferenceroom A)
— Level 02
— Core (Restrooms, Elevator, Stairs)
— Tenant Fit-Out Zone 2A
For a civil infrastructure project, your locations might be linear:
– Project: Highway 101 Expansion
— Segment 1: MP 0.0 to MP 2.5
— Structure: Overpass A
— Drainage: Culvert System 1A-1C
— Segment 2: MP 2.5 to MP 5.0
Prerequisites and Permissions for Creating Locations
You can’t build the tree without the right access. In Procore, the ability to create and edit locations is controlled by granular user permissions. Typically, project administrators, superintendents, and project managers will have these rights.
To check or configure permissions, an admin must navigate to the Project level, select the Directory tool, and edit the permission templates for the relevant user roles. Look for the “Locations” section within the Admin tool permissions. Ensure the “Create,” “Edit,” and “Delete” boxes are checked for the roles that will be setting up the project’s geography.
Also, have your project’s drawings and specifications handy. The most effective location trees are built directly from the architectural floor plans and site diagrams. This alignment between the digital system and the physical plans reduces confusion in the field.
Step-by-Step Guide to Creating Your First Location
Now, let’s get into the software. The primary tool for this work is the Locations tool within your Procore project. Here is the exact process.
Accessing the Locations Tool
Log into your Procore project. From the main navigation menu, select “Locations.” You will be presented with a page showing your current location tree, which will be empty on a new project aside from the root project name.
Adding a Top-Level Parent Location
Click the “+ Add” button, typically found at the top of the locations panel. A form will appear. The only required field is “Location Name.” Enter a clear, consistent name, like “Building One” or “Site Work Phase 1.”
You can also add an optional “Location Code.” This is a short identifier (e.g., BLDG1, SEG-A) useful for reports and integrations. The “Parent Location” field will default to the project root, which is correct for your first top-level location. Click “Save.”
Creating Child Locations and Nesting
To add a child location, first select the parent location you just created in the tree view. Then, click “+ Add” again. The form will be the same, but you’ll notice the “Parent Location” field is now pre-populated with your selected parent.
Name the child location, for example, “Floor 02.” Add a code like “L02.” Save it. You have now created a hierarchy. You can continue this process, selecting “Floor 02” to add “Suite 200,” and so on, drilling down to the necessary level of detail.
Using the Import Feature for Speed
Manually creating dozens or hundreds of locations is tedious. For large projects, use the import function. Click the gear icon (Settings) in the Locations tool and select “Import Locations.”
Download the provided CSV template. This template will have columns for Location Name, Location Code, and Parent Location Name. Fill the spreadsheet by listing every location, using the parent’s name to establish the hierarchy. A location with a blank parent column will be created at the root level. Upload the completed CSV, and Procore will build the entire tree in seconds.
Integrating Locations with Other Procore Tools
Creating the tree is only half the battle. The real value comes from using locations to organize your work. Almost every major Procore tool can be linked to a location.
Assigning Locations to Documents and Drawings
In the Documents or Drawings tool, when you upload a file, you can select a location from a dropdown. This is perfect for storing floor-specific shop drawings, area-specific permits, or room finish schedules. Later, you can filter the entire document log by location to see everything relevant to “Building B, Level 4.”
Logging Observations and Punch List Items
When creating a daily report, observation, or punch list item in the relevant tool, you will find a location field. Selecting a precise location like “North Parking Lot, Light Pole #7” ensures the issue is geographically pinpointed. The assigned contractor knows exactly where to go, and you can run a report to see all open items for a specific wing or floor.
Tracking Costs and Budgets by Area
In the Budget and Commitments tools, you can assign cost codes to locations. This allows for powerful cost-to-complete tracking by project area. You can see if “Tenant Improvement Zone 5” is over budget while “Main Lobby” is on track, enabling targeted financial management.
Troubleshooting Common Location Issues
Even with a good plan, you might hit snags. Here are solutions to frequent problems.
Locations Not Appearing in Dropdown Menus
If you can’t select a location in the Observations tool, for example, first check your user permissions for that specific tool. You need “Standard” or “Admin” level access to the tool to use the location assignment feature. Also, confirm the location was created and saved correctly in the Locations tool itself.
Need to Reorganize or Move a Location
What if you placed “Mechanical Room 401” under the wrong floor? You cannot directly change the parent of an existing location. The workaround is to export your locations via CSV, correct the parent name in the spreadsheet, delete the incorrect location from Procore (if it has no data attached), and re-import the corrected list. Be cautious, as deleting a location with associated items like punch lists may not be allowed.
Maintaining Consistency Across the Team
The most common issue is inconsistent naming. One superintendent calls it “Level 3,” another uses “Floor 3.” This breaks reporting and filters. Establish a naming convention document before the project starts and distribute it. Use the import feature to enforce this convention, preventing manual entry errors.
Best Practices for Location Management
Follow these strategies to build a system that lasts the entire project lifecycle.
Start Early: Build your location tree during project setup, before significant field work begins. It’s much harder to retrofit location data onto thousands of existing items.
Keep It Simple, But Detailed Enough: Don’t create a location for every single electrical outlet if it’s not necessary. But do create locations for every distinct room, zone, and asset your team needs to track work against. Find the balance that matches your reporting needs.
Use Codes for Reporting: Location codes (e.g., B1-L3-RM310) are invaluable for custom reports and external system integration. They are often more reliable than names alone.
Train Your Crews: A location system only works if everyone uses it. Conduct a short training session for foremen and field engineers on how to select the correct location when logging issues. Make it part of your daily reporting routine.
Audit Periodically: Every month, review the location tree. As the project evolves and change orders are issued, you may need to add locations for new scopes of work. Keep the tree living and current.
Your Actionable Next Steps
Begin by gathering your project’s architectural drawings and site plans. Sketch out a proposed location hierarchy on paper or in a spreadsheet, mirroring the physical and logical breakdown of the project. Get input from your project management and field supervision teams to ensure it aligns with how they plan to manage work.
Then, log into Procore. If you have the permissions, navigate to the Locations tool and create your first top-level parent location. Use the import function with your prepared spreadsheet to build the rest of the structure efficiently. Finally, make it a rule: the next observation, document upload, or punch list item created must have a location assigned. This consistent practice will transform chaotic project data into a searchable, actionable geographic database, giving your entire team the clarity needed to build efficiently and accurately.
