Skip to main content
Procore

360 Reporting: Data Guide

  1. Last updated
  2. Save as PDF

Table of Contents

How Your Data is Organized

This guide introduces the fundamental concepts of data structure in 360 Reporting. Understanding these building blocks—from datasets and objects to joins and granularity—is the key to creating powerful and insightful reports.

Data Structure

When building a 360 Report, data is organized in a three-level hierarchy: Datasets, Objects, and Fields.

  1. Select a Dataset: Your first step is to choose the dataset to use. A dataset is the complete pool of data available for your report. You can only use data from dataset you select, although some fields are included in multiple datasets. 
  2. Find your Objects: Within a dataset, the system organizes information into objects. An object groups all the fields related to a specific item, like an RFI. This ensures all the fields you are working with have a consistent level of detail.
  3. Choose your Fields: Inside each object, you find fields. A field is the most granular piece of data, such as 'Title', 'Status', or 'Due Date.'

You can create 360 Reports at the company or project level using the datasets provided in this guide. 

Available Datasets

The available datasets in 360 Reporting include:

  • Financials 
  • Resource Management
  • Project Execution

  • Beta  User Activity

  • Beta  Directory & Portfolio

  • Beta  Preconstruction

Types of Fields

In 360 Reporting, fields are categorized by the type of data they contain and how you can use them.

  • Measure:  A measure is a field containing a numerical value, such as an amount, quantity, or number of hours. You use measures to perform calculations and aggregations, like summing costs or averaging hours.
  • Dimension: A dimension is a field that contains descriptive text, like a name, title, or status. You use dimensions to label, group, or filter your data. You cannot use them in mathematical calculations.
    • Hyperlinked Dimensions: Some dimension fields, like 'RFI Number' or 'Commitment Title,' are also hyperlinks. You can click them to open the source item in a new window.
  • Boolean: A boolean field holds one of two values: True (yes) or False (no). You use it to represent binary information, such as whether a commitment is 'Executed' or an RFI is marked 'Private.'
  • Date and Date/Time: These fields contain date or date with time values, such as a 'Due Date' or 'Date Created.'
     Important
    In 360 Reporting, date fields in project-level reports always use the project’s timezone. See Create a New Project. In company-level reports, they use the company’s timezone. See Configure Your Company Settings.

Granularity and Grain

To build powerful and insightful reports, it's crucial to grasp two fundamental concepts: granularity and grain.

  • Granularity: The Level of Detail. A report's granularity defines its level of detail. A low-granularity report shows high-level, summary information (e.g., totals for an entire project). In contrast, a high-granularity report shows fine-grained detail (e.g., individual transactions within that project).
  • Grain: The Focus of Each Row. The grain specifies what each row in a report represents. For example, if each row shows a unique RFI, the report's grain is 'RFI.'

How Report Grain Changes

In 360 Reporting, the grain of a report can change as you add more fields.

  • The grain changes whenever you add a new field. If you add the 'Project Name' field, each row becomes a unique project. If you then add the more granular 'RFI Number' field, the grain shifts so that each row represents a unique RFI.
  • The grain only changes when you add a descriptive (non-measure) field. If you add a measure (a quantifiable value like cost or quantity), the grain remains the same. The report aggregates the new measure to the current level of detail.

Joins

In Enhanced Reporting, joins create relationships between different data objects. For example, RFIs connect to a project, commitment line items belong to a commitment, and users are part of a company.

Joins allow you to pull fields from multiple related objects into a single report. For instance, the 'Company' object joins with the 'Commitment' object. This connection lets you pull any information about that company directly into your commitment report.

When you combine fields from joined objects, the report displays them in the same row. For example, a report can show the 'Project Name', 'Commitment Number ', 'Line Item Amount', and 'Budget Code' together in a single row because the objects are joined.

Direct and Indirect Joins

Objects can connect in two ways:

  • Directly: Such as a 'Commitment' and its 'Commitment Line Item' object. 
  • Indirectly: Through another object. For example, a 'Commitment' connects to a 'Budget Code' through the 'Commitment Line Item' object.

To display data from indirectly joined objects in the same row, you must include a field from the object that connects them. If you create a report with only 'Budget Code' and 'Commitment Name', the data will appear in separate rows. However, if you add a field from 'Commitment Line Item', all three objects will correctly appear in the same row.

 Note

Adding a measure (like a line item amount) from a joined object does not change the report's grain. In the example above, the report's grain remains 'Commitment,' and the line item's measure aggregates to that level.

Financials

The Financials dataset provides a comprehensive set of objects for reporting on every aspect of your project's financial lifecycle.

Objects in the Financials Dataset

Generate reports using the Financials dataset to achieve a comprehensive overview of a project's financial health by connecting data from initial budgets and contracts through to commitments, change orders, costs, and subcontractor invoices.

What you can see in this dataset depends on two levels of access in Procore:

  • Company Access: Objects in the dataset become available only after your company enables the corresponding tool in its Procore account.
  • User Access: Your specific permissions for each tool control which objects are available to you.
Area Objects Availability To
Budget Budget Change1 All Companies with Financial Management icon-external-link.png using Budget

1 ERP status fields available with ERP Integrations
Budget Change Adjustment Line Item
Budget Code
Budget Line Item
Monitored Resource
Change Events Change Event All Companies with Financial Management icon-external-link.png using Change Events
Change Event Line Item
Request for Quote
Request for Quote Quote
Request for Quote Response
Change Orders Commitments Change Order All Companies with Financial Management icon-external-link.png using Change Orders
Commitment Change Order Line Item
Commitment Potential Change Order
Commitment Potential Change Order Request
Prime Contract Change Order
Prime Contract Change Order Line Item
Prime Contract Change Order Markup
Prime Contract Potential Change Order
Commitments Commitments2 All Companies with Financial Management icon-external-link.png 
1 Objects are only available if using Change Orders
2 ERP status fields available with ERP Integrations
Commitments Line Item
Commitments Change Order1,2
Commitment Change Order Line Item1
Commitment Potential Change Order1
Commitment Potential Change Order Request1
Directory Company (Vendor)1 All Companies
1 ERP status fields available with ERP Integrations
Company Global Insurance
Company Project Insurance
Direct Costs Direct Cost All Companies with Financial Management icon-external-link.png
Direct Cost Line Item
DocuSign®  DocuSign® fields are available in Commitments, Change Orders, Invoicing, and Prime Contracts All Companies with Financial Management icon-external-link.png using DocuSign®
ERP Integrations ERP Job Costs Summary All Companies with Financial Management icon-external-link.png using ERP Integrations
ERP Status Fields are Available in Multiple Objects 2
Invoicing Owner Invoice All Companies with Financial Management icon-external-link.png  using Invoice Management
1 ERP status fields available with ERP Integrations
Owner Invoice Line Item
Subcontractor Invoice1
Subcontractor Invoice Line Item
Payments Contract Compliance All Companies with Financial Management icon-external-link.png and Invoice Management + Procore Pay 
Disbursement
Lien Waiver
Manual Hold
Payment Agreement
Payment Beneficiary
Payment Invite
Payment Issued
Payment Permissions
Payment Project Controls
Payment Received
Payment Requirement
Payment Requirement Settings
Sub-Tier
Sub-Tier Waivers
Portfolio Project1 All Companies
1 ERP status fields available with ERP Integrations
Project Roles
Prime Contracts Prime Contract2 All Companies with Financial Management icon-external-link.png
1 Objects are only available if using Change Orders
2 ERP status fields available with ERP Integrations
Prime Contract Line Item
Prime Contract Change Order1,2
Prime Contract Change Order Line Item1
Prime Contract Change Order Markup1
Prime Contract Potential Change Order1

 

How are objects in the Dataset Joined?

A join combines data from related objects into a single row. For example, directly connected objects like a 'Commitment' and its 'Commitment Change Order' are automatically joined. 

To connect objects without a direct link, add a field from a shared intermediary object to your report. For example, you can join an 'Inspection' and an 'Action Plan Item' by including a field from their common 'Action Plan Line Item Record'.

Join Table

This table shows how objects are joined. To check if two objects are connected, find one in the top row and the other in the left column. The cell where they intersect confirms if a join exists.

  • A 'Join' cell connects objects by combining their fields into a single row.
  • A 'Join (through third object name)' cell requires you to add a field from that object to combine the data into a single row.
  • A 'No join' cell indicates the objects are unrelated, so their data will appear in separate rows. An exception is when your report only uses measures from these objects.
Legend

  Join

  Join through numbered object

* Join through any line item object

** Join through any line item object except Budget

  1. Budget Change
  2. Budget Change Adjustment Line Item
  3. Budget Code
  4. Budget Line Item
  5. Budget Modification
  6. Change Event
  7. Change Event Line Item
  8. Commitment
  9. Commitment Change Order
  10. Commitment Change Order Line Item
  11. Commitment Change Order Markup
  12. Commitment Change Order Request
  13. Commitment Line Item
  14. Commitment Potential Change Order
  15. Company (Vendor)
  16. Company Global Insurance
  17. Company Project Insurance
  18. Direct Cost
  19. Direct Cost Line Item
  20. ERP Job Costs Summary
  21. Lien Waiver
  22. Manual Hold
  23. Monitored Resource
  24. Owner Invoice
  25. Owner Invoice Line Item
  26. Payment Issued
  27. Payment Requirement
  28. Prime Contract
  29. Prime Contract Change Order
  30. Prime Contract Change Order Line Item
  31. Prime Contract Change Order Markup
  32. Prime Contract Change Order Request
  33. Prime Contract Line Item
  34. Prime Contract Potential Change Order
  35. Project
  36. Project Roles
  37. Request for Quote
  38. Request For Quote Quote
  39. Request for Quote Response
  40. Subcontractor Invoice
  41. Subcontractor Invoice Line Item
  42. Contract Compliance
  43. Payment Beneficiary
  44. Sub-Tier
  45. Sub-Tier Waiver
Financials Join Table

 

Resource Management

The Resource Management dataset allows you to analyze your team's productivity and its financial impact by connecting resource allocation and time tracking with key project data.

Objects in the Resource Management Dataset

Generate reports using the Resource Management data set to access a comprehensive collection of your company's project data. This data connects project financials, such as budgets and commitments, with resource allocation and time tracking to provide detailed insights into your overall operational performance.

What you can see in this dataset depends on two levels of access in Procore:

  • Company Access: Objects in the dataset become available only after your company enables the corresponding tool in its Procore account.
  • User Access: Your specific permissions for each tool control which objects are available to you.
Area Object Available to
Core Company (Vendor) All Companies
Crew Companies with access to Resource Management
Employee All Companies
Project
Budget Budget Change Companies with access to Financials
Budget Change Adjustment Line Item
Budget Line Item All Companies
Budget Code Budget Code All Companies
Change Events Change Event Companies with access to Financials
Change Event Line Item
Commitments Commitment Companies with access to Financials
Commitment Line Item
Commitment Change Orders Commitment Change Order Companies with access to Financials
Commitment Change Order Line Item
Commitment Potential Change Order
Commitment Potential Change Order Request
Commitment Change Order Markup
Direct Costs Direct Cost Companies with access to Financials
Direct Cost Line Items
Prime Contracts Prime Contract Companies with access to Financials
Prime Contract Line Items
Prime Contract Change Orders Prime Contract Change Order Companies with access to Financials
Prime Contract Potential Change Order
Prime Contract Change Order Request
Prime Contract Change Order Line Item
Prime Contract Change Order Markup
Production Quantities Actual Production Quantity Companies with access to Resource Management or Financials
Budgeted production Quantity
Change Event Production Quantity Companies with access to Financials
Prime Contract Change Order Production Quantity
Resource Planning  Resource Planning Assignment Companies with access to Resource Planning
Resource Planning Group
Resource Planning Job Title
Resource Planning People
Resource Planning Project 
Resource Planning Request
Resource Planning Time Off
Resource Planning Roles
Resource Planning Tags
T&M Tickets T&M Ticket Companies with access to Resource Management or T&M Tickets
T&M Ticket Equipment
T&M Ticket Labor
T&M Ticket Material
T&M Ticket Subcontractor
Timecard Entry Timecard Entry Companies with access to Resource Management

How are objects in the Dataset Joined?

A join combines data from related objects into a single row. For example, directly connected objects like a 'Commitment' and its 'Commitment Change Order' are automatically joined. 

To connect objects without a direct link, add a field from a shared intermediary object to your report. For example, you can join an 'Inspection' and an 'Action Plan Item' by including a field from their common 'Action Plan Line Item Record'.

Join Table

This table shows how objects are joined. To check if two objects are connected, find one in the top row and the other in the left column. The cell where they intersect confirms if a join exists.

  • A 'Join' cell connects objects by combining their fields into a single row.
  • A 'Join (through third object name)' cell requires you to add a field from that object to combine the data into a single row.
  • A 'No join' cell indicates the objects are unrelated, so their data will appear in separate rows. An exception is when your report only uses measures from these objects.

 

Legend

  Join

  Join through numbered object

* Join through any line item object

** Join through any line item object except Budget

  1. Actual Production Quantity
  2. Budget Code
  3. Budget Line Item
  4. Budgeted Production Quantity
  5. Change Event
  6. Change Event Line Item
  7. Change Event Production Quantity
  8. Commitment
  9. Commitment Change Order
  10. Commitment Change Order Line Item
  11. Commitment Change Order Markup
  12. Commitment Change Order Request
  13. Commitment Line Item
  14. Commitment Potential Change Order
  15. Company (Vendor)
  16. Crew
  17. Direct Cost
  18. Direct Cost Line Item
  19. Employee
  20. Prime Contract
  21. Prime Contract Change Order
  22. Prime Contract Change Order Line Item
  23. Prime Contract Change Order Markup
  24. Prime Contract Change Order Production Quantity
  25. Prime Contract Change Order Request
  26. Prime Contract Line Item
  27. Prime Contract Potential Change Order
  28. Project
  29. Project Roles
  30.  Resource Planning Assignment
  31. Resource Planning Group
  32. Resource Planning Job Title
  33. Resource Planning People
  34. Resource Planning Project
  35. Resource Planning Request
  36. Resource Planning Time Off
  37. Resource Planning Roles
  38. Resource Planning Tags
  39. T&M Ticket
  40. T&M Ticket Equipment
  41. T&M Ticket Labor
  42. T&M Ticket Material
  43. T&M Ticket Subcontractors
  44. Timecard Entry
2025-06-12_Resource Management_ join table.png

Project Execution

The Project Execution dataset provides a detailed view into your project's daily operational health by connecting on-site activities with core administrative records.

Objects in the Project Execution Dataset

Generate reports using the Project Execution data set to track the day-to-day progress and documentation of your projects from the field. This data connects on-site activities like daily logs and photos with critical project management processes like RFIs, submittals, and inspections to create a complete operational record.

What you can see in this dataset depends on two levels of access in Procore:

  • Company Access: Objects in the dataset become available only after your company enables the corresponding tool in its Procore account.
  • User Access: Your specific permissions for each tool control which objects are available to you.
Area Object Available to
Action Plans Action Plan Companies with access to Action Plans
Action Plan Approver
Action Plan Line Item
Action Plan Line Item Assignee
Action Plan Line Item Record
Action Plan Line Item Record Request
Action Plan Line Item Reference
Action Plan Receiver
Change Events Change Event Companies with access to Financials
Change Event Line Item
Commitments Commitment Companies with access to Commitments
Commitment Line Item
Coordination Issues Coordination Issue Companies with access to Coordination Issues
Correspondence Correspondence Companies with access to Correspondence
Correspondence Assignee
Correspondence Distribution List
Correspondence Response
Correspondence Schedule Task
Daily Log Daily Log Accident

Companies with access to Daily Log
Daily Log Completion
Daily Log Construction Report
Daily Log Delay
Daily Log Delivery
Daily Log Dumpster
Daily Log Equipment
Daily Log Inspection
Daily Log Manpower
Daily Log Note
Daily Log Observed Weather Condition
Daily Log Phone Call
Daily Log Plan Revision
Daily Log Productivity
Daily Log Quantity
Daily Log Safety Violation
Daily Log Scheduled Work
Daily Log Scheduled Work Task
Daily Log Visitor
Daily Log Waste
Documents Folder/Document Companies with access to the Documents tool
Folder/Document Watcher
Company Folder/Document
Drawing Drawing Companies with access to Drawings
Drawing Markup Link
Equipment Equipment Companies with access to Equipment
Forms Form Companies with access to Forms
Incident Incident Companies with access to Incidents
Incident Distribution Member
Incident Record
Incident Injury Body Part
Incident Action
Incident Alert
Incident Witness Statement
Inspection Inspection Companies with access to Inspections
Inspection Assignee
Inspection Distribution List
Inspection Item
Inspection Item Activity

Inspection Item Comment
Inspection Item Reference
Inspection Item Signature Request
Inspection Schedule
Inspection Schedule Assignee
Inspection Schedule Distribution List
Inspection Signature Request
Instructions Instruction Companies with access to Instructions
Core Location All Companies
Project
Meeting Meeting Companies with access to Meetings
Meeting Item
Meeting Attendee
Meeting Item Assignee
Observation Observation Companies with access to Observations
Observation Activity
Observation Distribution Member
Photo Photo Companies with access to Photos
Punch List Punch Item Companies with access to Punch List
Punch Item Assignee
Punch Item Ball in Court
Punch Item Distribution Member
RFI RFI Companies with access to RFIs
RFI Assignee
RFI Ball in Court
RFI Distribution List
RFI Response
Schedule Schedule Lookahead Companies with access to Schedule
Schedule Lookahead Task
Schedule Task
Schedule Task Change
Schedule Task Request
Schedule Calendar Item
Specifications Specification Section Companies with access to Specifications
Submittal Submittal Companies with access to Submittals
Submittal Approver
Submittal Ball in Court
Submittal Distribution List
Task Task Companies with access to Tasks
Task Activity
Task Assignee
Timesheets Timecard Entry Companies with access to Timesheets

How are objects in the Dataset Joined?

A join combines data from related objects into a single row. For example, directly connected objects like a 'Correspondence' and its 'RFI' are automatically joined. 

To connect objects without a direct link, add a field from a shared intermediary object to your report. For example, you can join an 'Inspection' and an 'Action Plan Item' by including a field from their common 'Action Plan Line Item Record'.

Join Table

This table shows how objects are joined. To check if two objects are connected, find one in the top row and the other in the left column. The cell where they intersect confirms if a join exists.

  • A 'Join' cell connects objects by combining their fields into a single row.
  • A 'Join (through third object name)' cell requires you to add a field from that object to combine the data into a single row.
  • A 'No join' cell indicates the objects are unrelated, so their data will appear in separate rows. An exception is when your report only uses measures from these objects.
Legend

*RFIs join to Correspondence through the Correspondence Origin RFI ID. Therefore Correspondence and RFI can only appear in the same row if the Correspondence originated from the RFI. RFI’s that originate from Correspondence will not appear in the same row.

  Join

  Join through numbered object

  1. Action Plan
  2. Action Plan Approver
  3. Action Plan Line Item
  4. Action Plan Line Item Assignee
  5. Action Plan Line Item Record
  6. Action Plan Line Item Record Request
  7. Action Plan Line Item Reference
  8. Action Plan Receiver
  9. Change Event
  10. Change Event Line Item
  11. Commitment
  12. Commitment Line Item
  13. Company Folder/Document
  14. Coordination Issue
  15. Correspondence*
  16. Correspondence Assignee
  17. Correspondence Distribution List
  18. Correspondence Response
  19. Correspondence Schedule Task
  20. Daily Log Accident
  21. Daily Log Completion
  22. Daily Log Construction Report
  23. Daily Log Delay
  24. Daily Log Delivery
  25. Daily Log Dumpster
  26. Daily Log Equipment
  27. Daily Log Inspection
  28. Daily Log Manpower
  29. Daily Log Note
  30. Daily Log Observed Weather Condition
  31. Daily Log Phone Call
  32. Daily Log Plan Revision
  33. Daily Log Productivity
  34. Daily Log Quantity
  35. Daily Log Safety Violation
  36. Daily Log Scheduled Work
  37. Daily Log Scheduled Work Task
  38. Daily Log Visitor
  39. Daily Log Waste
  40. Drawing
  41. Drawing Markup Link
  42. Equipment
  43. Folder/Document
  44. Folder/Document Watcher
  45. Form
  46. Incident
  47. Incident Action
  48. Incident Alert
  49. Incident Distribution Member
  50. Incident Injury Body Part
  51. Incident Record
  52. Incident Witness Statement
  53. Inspection
  54. Inspection Assignee
  55. Inspection Distribution List
  56. Inspection Item
  57. Inspection Item Activity
  58. Inspection Item Comment
  59. Inspection Item Reference
  60. Inspection Item Signature Request
  61. Inspection Schedule
  62. Inspection Schedule Assignee
  63. Inspection Schedule Distribution List
  64. Inspection Signature Request
  65. Instruction
  66. Location
  67. Meeting
  68. Meeting Attendee
  69. Meeting Item
  70. Meeting Item Assignee
  71. Observation
  72. Observation Activity
  73. Observation Distribution Member
  74. Photo
  75. Project
  76. Punch Item
  77. Punch Item Assignee
  78. Punch Item Ball in Court
  79. Punch Item Distribution Member
  80. RFI*
  81. RFI Assignee
  82. RFI Ball in Court
  83. RFI Distribution List
  84. RFI Response
  85. Schedule Calendar Item
  86. Schedule Lookahead
  87. Schedule Lookahead Task
  88. Schedule Task
  89. Schedule Task Change
  90. Schedule Task Request
  91. Specification Section
  92. Submittal
  93. Submittal Approver
  94. Submittal Ball in Court
  95. Submittal Distribution List
  96. Task
  97. Task Activity
  98. Task Assignee
  99. Task Distribution Member
  100. Timecard Entry
RFI_join_June_25.png

User Activity

Objects and Events in the User Activity Dataset

The User Activity Dataset gives you the option to create 360 Reports using data that reflects user actions in Procore. Track your team's activity by tool, action, or user over any time period. This information helps leaders understand how their company uses Procore. They can also use it to review employee activity to correct mistakes or investigate activities.

 Tip

What's the difference between the User Activity Report and the User Sessions Report? With the User Activity Report, you can:

  • Get a longer, more complete history. You can track activity over 31 days—a major increase from the 7-day limit in the User Sessions Report—and view actions from both web and mobile apps.

  • Build highly specific reports. Create a custom view with the exact fields you need. You can then filter by any data point (like 'Actor Email', 'Event Name', and 'Event Type') to get granular insights, even without adding those fields as columns.

Objects and Events work together to provide a complete, detailed history of all activity within your account. By linking an event to its object, you can construct a powerful audit trail to understand the full lifecycle of any item or user.

Objects

Objects act as a master directory, defining the who and what in the system, such as users, projects, and documents.

Object Format
Company Name Text
Count Number
Device Type Text
Event Date Date 
Event ID Text
Event Name Text
Event Subtype Text
Event Timestamp Date
Event Type Text
Is API Yes/No
Object ID Number
Project Is Demo Yes/No
Project Name Text
Project Number Text
Tool Name Text
URL Text
User Email Text
User ID Number
User Default Permission Template Text
User Is Active Yes/No
User is Authorized Bidder Yes/No
User Job Title Text
User Last Log In Date Date
User Log In Email (different from User Email) Text
User Name Text
User Role Text
User Type Text

Events

Events provide the chronological story, logging every action or "what happened", like user logins, documents created, or projects updated.

Event Definition
Allow Grant of permissions or access.
Assign Assignment of a task, resource, or permission (usually to a person).
Close Closure of a session, task, or resource.
Create/Update Creation or modification of data or resources.
Delete Deletion, or in some cases archiving, of data or resources.
Download Download of an item, by a user.
Execute Execution of a command, script, or process.
Export Export of data to another format or location.
Include Addition or inclusion of data or persons into a system or process.
Link Establishment of a link or association between data or resources.
Move Relocation of data or resources.
Notify Notification being sent or triggered.
Other Event that does not fit into the other predefined categories.
Publish Publication of data or resources, or making them available.
Reject Rejection of a request, submission, or change.
Remove Removal of an association or link to data or resources.
Reset Reset of a configuration or state.
Sign Signing or approval of a document or request.
Submit Submission of data or a request.
Sync Synchronization of data between systems or locations.
Upload Upload of data or resources to a system.
Validate Validation of data or a request.
View Viewing or accessing of data or resources.
Withdraw/Void Withdrawal or voiding of a previously submitted or approved item.

Directory & Portfolio

 In Beta
The User Activity dataset in 360 Reporting is currently available as an open Beta. For instructions on how to create a 360 Report with this dataset, see Create a User Activity Report in 360 Reporting.

Objects in the Directory and Portfolio Dataset

The Directory and Portfolio dataset can report on comprehensive directory data across companies, users, projects, insurance, comments, and distribution groups. Use this data set to create custom reports so you can transform raw operational data into data-driven decision making. 

Not all objects are available to all companies and users. See below for what objects are in the dataset and who they are available to. See permissions for more information on how a user’s tool permissions impact what objects are available to them.

 

Area Object Available to
Directory Company (Vendor) All Companies
User
Portfolio Project
Directory Company Global Insurance
Company Project Insurance
Company Comments
Company Distribution Group
Contact
Project Distribution Group
Permissions Project Permissions
Company Permissions

How are objects in the Dataset Joined?

Objects that have a relationship are linked by a join. When two objects in Enhanced Reporting are joined, they appear in the same row in a report. For example, a Company is joined to an User, therefore they will appear in the same row. Sometimes, two objects aren’t directly joined, but are joined through a third object. In this case, a field from that third object must be added to a report to show the connection between the first two. For example, an Company Distribution Group and a Company do not have a direct relationship, but a field from the User that does have a direct relationship with both will be added to a report, all three objects will appear in the same line.

The table below shows the joins of the objects in the dataset. To determine if two objects are joined, search for one across the top and the other on the side. The cell that corresponds to the column and row of the objects tells you if they are joined.

  • If the cell shows “Join”, the objects are joined directly and fields from these objects will appear in the same row.
  • If the cell shows “Join through numbered object,” the objects are indirectly joined through a third object. A field from that third object must be added to the report to see the data in the same row.
  • If the cell shows “No join,” the objects do not have a relationship and data will not appear in the same row (the exception to this is if only measures from these objects have been added to the report).
Legend

  Join

  Join through numbered object

  1. Company (Vendor)
  2. User
  3. Project
  4. Company Global Insurance
  5. Company Project Insurance
  6. Company Comments
  7. Company Distribution Group
  8. Contact
  9. Project Distribution Group
  10. Tool Configuration
  11. Project Permissions
  12. Company Permissions
  13. Project Granular Permissions
  14. Company Granular Permissions

NOTE: Company level permissions does not show permissions to custom tools. Project level permissions does not yet show permissions to correspondence or any custom correspondence types.

* Join only for project contacts
  1 2 3 4 5 6 7 8 9 10 11 121314
1  
         2  2      2 222
2                      
3                 *     
4                      
5                      
6                      
7 2                    
8 2   
               
9
   *                
10                      
11  2                    
122
132
142

Preconstruction

 In Beta
The User Activity dataset in 360 Reporting is currently available as an open Beta. For instructions on how to create a 360 Report with this dataset, see Create a User Activity Report in 360 Reporting.

Objects in the Preconstruction Dataset

Generate reports using the Preconstruction data set to gain insights into your project's early-stage financial planning. This data connects your estimating and bidding information, allowing you to track bid packages and analyze cost estimates to make more informed decisions before breaking ground.

What you can see in this dataset depends on two levels of access in Procore:

  • Company Access: Objects in the dataset become available only after your company enables the corresponding tool in its Procore account.
  • User Access: Your specific permissions for each tool control which objects are available to you.
Area Object Available to

Estimating

 Estimate

Companies with access to the Estimating tool.
Estimate Budget Included Item
Estimate Budget Item 
Estimate Layer
Estimate Layer Group
Estimating Project
Estimate Adjustment
Project Note
Project Task
Project Document

Bidding

 Bid

Companies with access to the Bidding tool.
Bid Form
Bid Item
Bid Package
Contract

How are objects in the Dataset Joined?

A join combines data from related objects into a single row. For example, directly connected objects like a 'Bid' and its 'Bid Form' are automatically joined. 

To connect objects without a direct link, add a field from a shared intermediary object to your report. For example, you can join an 'Estimating Project' and an 'Estimate Layers' by including a field from their common 'Estimating Layer Groups'.

Join Table

This table shows how objects are joined. To check if two objects are connected, find one in the top row and the other in the left column. The cell where they intersect confirms if a join exists.

  • A 'Join' cell connects objects by combining their fields into a single row.
  • A 'Join (through third object name)' cell requires you to add a field from that object to combine the data into a single row.
  • A 'No join' cell indicates the objects are unrelated, so their data will appear in separate rows. An exception is when your report only uses measures from these objects.
Legend

  Join

  Join through numbered object

  1. Estimate
  2. Estimate Budget Included Item
  3. Estimate Budget Item
  4. Estimate Layers
  5. Estimate Layer Groups
  6. Estimating Projects
  7. Estimate Adjustment
  8. Project Note
  9. Project Task
  10. Project Document
  11. Bid
  12. Bid Item
  13. Bid Package
  14. Contract
  15. Bid Form
  1 2 3 4 5 678910 11 12 13 14 15
1                      
2           3
 3         
3                      
4          
 5        
5           5           
6351
71
8
9
10  
 
             
11    3    5           11  
12                     15
13                      
14             11        
15               11