360 Reporting: Data Guide
- Last updated
- Mar 24, 2025
- Save as PDF
Table of Contents
- How Your Data is Organized
- Available Datasets
How Your Data is Organized
Data Structure
Enhanced Reporting organizes data in a hierarchy structure:
- At the bottom of the hierarchy are Fields. Fields are a single piece of information associated with a specific aspect of the data being stored. For example, if we have data about RFIs, the number, title, and due date are all fields. When added to a report, each field is shown as a column, and the data in it as rows.
- Fields are organized into groups called Objects. The fields within one Object are all the same level of granularity (see below for more about granularity). A tool may have one or more objects associated with it. Within Enhanced Reporting, fields are grouped under the object they belong to in the column picker.
- Objects and fields they contain are further organized into Datasets. Each Dataset includes all the objects/fields of data available to combine in one report. Data cannot be combined between datasets, however, Datasets often contain overlapping fields. When you are creating a new Enhanced Report, you start by selecting the dataset you wish to build a report from.
Available Datasets in 360 Reporting:
- Financials dataset
- Resource Management dataset
- Project Execution
-
Beta User Activity
Types of Fields
- Measure: A measure is a field that contains a quantitative value or numerical data. Measures are often used to perform aggregations or calculations. Examples of measures include amounts, quantities, and hours.
- Dimension: A dimension is a type of field that provides descriptive information about the data being stored. They cannot be used in calculations. They often have values that are strings. Examples of dimension fields include user name, RFI title, commitment number, project description.
- Hyperlinks: Some dimensions, such as name, number, title, and ID, are hyperlinked fields. Users can click on these fields to open the item in a new window. Other examples of these fields include RFI Number, Commitment Title, and Subcontractor Invoice ID.
- Boolean: A boolean is a field that can only contain two values: true (or yes) and false (or no). Booleans are often used to represent binary data. Examples of boolean fields include the executed field on a commitment and the private field on an RFI.
- Date and date time: Date and date time fields contain date or date time values. Examples of date fields include due date and date created. Note that in Enhanced Reporting, date fields in project level reporting use the project timezone and date fields in company level reporting use the company timezone.
Granularity and Grain
- The Granularity of a report refers to the level of detail or specificity of the data shown in that report. For example, a report that has a low level of granularity may show information that is rolled up per project, whereas a report with a high level of granularity shows the details of that project.
- The Grain refers to what each row in a report represents. For example, if each row shows a unique RFI, the grain of the report is RFI.
- In Enhanced Reporting, the grain of a report changes based on the field that the user adds. For example, if the user adds the field project name, each name will be reflected on a unique row and the grain of the report will be project. If the user then adds the field RFI number (which is more granular than project), the grain will change so that each unique RFI number is its own row, and the grain of the report is RFI.
- Note that in Enhanced Reporting, the grain of a report only changes when a non-measure field is added. If a measure is added to a report, the grain won’t change and the measure will be aggregated to the level of granularity shown in the report.
Joins
- The objects in Enhanced Reporting have relationships to one another. For example, RFIs are created on a project. Commitment line items are contained within a commitment and have a budget code. Users belong to a company. All of these relationships are called joins.
- Joins allow users to pull in all fields related to joined objects. For example, Company joins to Commitment, reflecting the company that will complete the contract. Instead of the Commitment having a field called Company, Company is an object that joins to Commitments, and allows a user to pull in all information related to that company.
- When fields from two or more objects that are joined are combined in a report, those fields will appear in the same row. For example, the report below shows project name, commitment number, commitment line item amount, and budget code all in the same row because these four objects are joined.
- Objects can be directly joined, as in the case of commitments and commitment line items, or they can be joined through other objects. For example, a commitment is joined to budget code through the commitment line item object. In a report, to see data appear in the same row, fields from the objects that are directly joined must be added. The first example below shows a report with budget code and commitment name. They do not appear in the same row because no fields from the object they join through (commitment line item) have been added to the report. The second example shows the report with commitment line item, where all three objects appear in the same row. Notice that the granularity of the report is still the commitment, even though I have added a field from the commitment line item, because the field from the line item is a measure and thus does not change the granularity of the report.
Financials
Objects in the Financial Dataset
Not all objects are available to all companies. See below for what objects are in the dataset and who they are available to. Not all users see all objects in a company, please see permissions for more information on how a user’s tool permissions impact what objects are available to them in the dataset.
| Area | Object | Available to |
|---|---|---|
| Core | Company (Vendor) | All Companies |
| Project | ||
| Budget | Budget Change | All Companies |
| Budget Change Adjustment Line Item | ||
| Budget Line Item | ||
| Monitored Resource | ||
| Budget Code | Budget Code | All Companies |
| Change Events | Change Event | All Companies |
| Change Event Line Item | ||
| Request for Quote | ||
| Request for Quote Quote | ||
| Request for Quote Response | ||
| Commitments | Commitment | All Companies |
| Commitment Line Item | ||
| Commitment Change Orders | Commitment Change Order | All Companies |
| Commitment Change Order Line Item | ||
| Commitment Potential Change Order | Companies/projects using two or more tiers of commitment change order | |
| Commitment Potential Change Order Request | ||
| Contract Compliance | Attachment Count | Companies with access to Payments |
| Date Updated | ||
| Effective At | ||
| Expires At | ||
| ID | ||
| Name | ||
| Notes | ||
| Send Expiration Notification | ||
| Status | ||
| Type | ||
| Direct Costs | Direct Cost | All Companies |
| Direct Cost Line Items | ||
| Directory | Company Global Inusrance | All Companies |
| Company Project Insurance | ||
| Docusign | Docusign Fields are Available in Multiple Objects1 | Companies with the DocuSign® Integration |
| ERP | ERP Job Costs Summary | Companies with an ERP Integration |
| ERP Status Fields are Available in Multiple Objects2 | ||
| Owner Invoices | Owner Invoice | Companies with access to Invoicing |
| Owner Invoices | ||
| Payments | Contract Compliance | Companies with access to Payments |
| Disbursement | ||
| Lien Waiver | ||
| Manual Hold | ||
| Payment Agreement | ||
| Payment Beneficiary | ||
| Payment Invite | ||
| Payment Issued | ||
| Payment Permissions | ||
| Payment Project Controls | ||
| Payment Requirement | ||
| Payment Requirement Settings | ||
| Payments Beneficiary | ||
|
Sub-Tier |
||
|
Sub-Tier Waiver |
||
| Prime Contracts | Prime Contract | All Companies |
| Prime Contract Line Items | ||
| Prime Contract Change Orders | Prime Contract Change Order | All Companies |
| Prime Contract Potential Change Order | Companies/projects using two or more tiers of prime contract change orders | |
| Prime Contract Change Order Request | ||
| Prime Contract Change Order Line Item | All Companies | |
| Prime Contract Change Order Markup | ||
| Subcontractor Invoices | Subcontractor Invoice | Companies with access to Invoicing |
| Subcontractor Invoice Line Items |
1Docusign fields are available in the commitment, commitment change order, commitment change order request, commitment potential change order, owner invoice, prime contract, prime contract change order, prime contract change order request, prime contract potential change order, and subcontractor invoice objects.
2ERP status fields are available in the budget change, commitment, commitment change order, Company, Prime contract, Prime contract change order, Project, and Subcontractor invoice objects.
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 commitment change order is joined to a commitment, and 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 Inspection and an Action Plan Item do not have a direct relationship, but a field from an Action Plan Line Item Record 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 third object name),” 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).
Join Table
Resource Management
Objects in the Resource Management Dataset
Not all objects are available to all companies. See below for what objects are in the dataset and who they are available to. Not all users see all objects in a company, please see permissions for more information on how a user’s tool permissions impact what objects are available to them in the dataset.
| 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 | ||
| 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?
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 commitment change order is joined to a commitment, and 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 Inspection and an Action Plan Item do not have a direct relationship, but a field from an Action Plan Line Item Record 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 third object name),” 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).
Join Table
Project Execution
Objects in the Project Execution Dataset
Not all objects are available to all companies. See below for what objects are in the dataset and who they are available to. Not all users see all objects in a company, please see permissions for more information on how a user’s tool permissions impact what objects are available to them.
| Area | Object | Available to |
|---|---|---|
| Change Events | Change Event | Companies with access to Financials |
| Change Event Line Item | ||
| Correspondence | Correspondence | Companies with access to Correspondence |
| Correspondence Assignee | ||
| Correspondence Distribution List | ||
| Correspondence Response | ||
| Drawing | Drawing Revision | Companies with access to Drawings |
| Drawing Markup Link | ||
| Incident | Incident | Companies with access to Incidents |
| Incident Distribution Member | ||
| Incident Record | ||
| Incident Injury Body Part | ||
| Incident Action | ||
| Incident Alert | ||
| 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 | ||
| Punch Item Comments | ||
| RFI | RFI | Companies with access to RFIs |
| RFI Assignee | ||
| RFI Distribution List | ||
| RFI Response | ||
| Schedule | Schedule Lookahead | Companies with access to Schedule |
| Schedule Lookahead Task | ||
| Schedule Task | ||
| 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 |
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 Correspondence is joined to an RFI, 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 Inspection and an Action Plan Item do not have a direct relationship, but a field from an Action Plan Line Item Record 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).
Join Table
User Activity
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 User Activity Dataset
The User Activity Dataset will give you the option to create 360 Reports using data that reflects user actions in Procore. Audit the activity of users working in your company by viewing activity data of specific tools, actions, users, and more over a period of time.
This information will help administrators and managers better understand how Procore is being used at their company, and audit employee activities in cases of mistakes or misuse of the platform.
How is User Activity Reporting Different Than The User Sessions Legacy Report?
-
Customize your own report by choosing your own fields and filters.
-
Access more data points related to your company’s user activity such as Actor Email, Event Type, and Event Name.
-
Access to user actions in Procore using a more flexible time frame filter of 31 days, as opposed to only 7 days in Legacy Reporting.
- 360 Reporting allows you to see user activity that takes place within Procore's mobile applications.
- Only show the necessary data by filtering on any dimension or date field without needing to add it as a column.
| 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 Name | Text |
| Project Number | Text |
| Tool Name | Text |
| Url | Text |
| User Email | Text |
| User ID | Number |
| User Name | Text |
| User Type | Text |