---
title: "Project Operations: Change Order Requests (CORs) report template"
slug: "project-operations-change-order-requests-cors-report-template"
updated: 2026-10-16T02:56:24Z
published: 2026-10-16T02:56:24Z
canonical: "help.servicetitan.com/project-operations-change-order-requests-cors-report-template"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.servicetitan.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Project Operations: Change Order Requests (CORs) report template

## Overview

The Project Operations: Change Order Requests (CORs) report helps project managers gain visibility into all change orders across projects, making it easier to identify delays, track approvals, and analyze the impact of change orders on project performance.

---

### 

#### Who uses this feature

- Project managers (PMs), Construction Executives
- Primarily for Residential Construction and Commercial Construction business types

#### Feature configuration

- Account configuration is required to use this feature. Please contact [Technical Support](http://go.servicetitan.com/ask) for details.
- The ability to create custom reports depends on the ServiceTitan package your company is subscribed to. If you don’t have the option to create a custom report, it may not be included in your package. Contact [Technical Support](http://go.servicetitan.com/ask) for details.

## Things to know

- Each row in the report represents a change order.
- If you’re unsure which columns you want to include in your report, use the [Reporting Dictionary](/v1/docs/reporting-dictionary) to search for appropriate data fields.
- You can use this template to create as many custom reports as you need. Each report created from the template is independent and can be run or scheduled without needing to recreate it from the original template.

## Top Report Use Cases and Best Practices

| **Role** | **Use Case** | **Best Practice** | **Data fields involved** |
| --- | --- | --- | --- |
| Project Manager | Stay Ahead of Overdue Change Orders Across My Jobs. Protect schedule and margin by clearing overdue CORs before they snowball. | Surface change orders that are open and past due so you can drive them to closure: - Filter *Change Order--Status (Options)* to exclude *Closed* so you only see open CORs. - Filter *Change Order--Overdue (Y/N)* to only include *Y*. - Sort by *Change Order--Days Overdue (#)* in descending order to focus on the most overdue items first. - Use *Change Order--Priority* and *Project Name* to identify which high-priority CORs on which projects need attention in your weekly planning and coordination meetings. | - Change Order--Status (Options) - Change Order--Overdue (Y/N) - Change Order--Due Date - Change Order--Days Overdue (#) - Change Order--Priority - Project Name - Project Manager - Project Status |
| Project Manager | Close Out Resolved Change Orders Quickly. Reduce admin clutter and keep your change order log accurate and actionable. | Focus on CORs that appear to be decided but are still sitting in an open status: - Filter *Change Order--Status (Options)* to *Sent* and *Responded* to see CORs waiting for a final decision. - Sort by *Change Order--Created Date* or *Change Order--Due Date* to highlight items that have been hanging out the longest. - Within that list, coordinate with the general contractor (GC)/owner or internal decision makers to either get the change order approved, rejected, or updated so it can move to *Closed* status. - Use *Change Order--Subject* and *Change Order--Scope of Work* to quickly recall context when following up. | - Change Order--Status (Options) - Change Order--Created Date - Change Order--Due Date - Change Order--Subject - Change Order--Scope of Work - Project Name - Customer Name |
| Project Manager | Coach Your Team on Change Order Hygiene. Understand who is creating CORs and whether the field and office are using the tool consistently. | Review recent change orders to understand how different teams are using the system: - Filter *Change Order--Created Date* to a recent period (for example, the last 30–90 days). - Group or sort by *Change Order--Created By* and *Change Order--Created In Field/Office* to see whether CORs are primarily initiated by office staff, field staff, or a mix. - Cross-check *Project Name, Project Business Unit, Project Manager,* and *Customer Name* to spot projects or groups where change orders are under-reported or not being captured in the system. - Use these insights in PM and foreman coaching conversations to clarify expectations for when CORs should be created, and to recognize teams that consistently log changes. | - Change Order--Created Date - Change Order--Created By - Change Order--Created In Field/Office - Project Name - Project Business Unit - Project Manager - Customer Name |
| Construction Executive | Measure Change Order Cycle Times by PM and Business Unit. Benchmark how quickly CORs move from creation to closure across the organization. | Use closed change orders to compare cycle times across PMs, business units (BU), and customers: - Filter *Change Order--Status (Options)* to *Closed* so you analyze full cycle times only. - Review *Change Order--Days To Close (#)* grouped by *Project Manager, Project Business Unit,* and *Customer Name*. - Look for patterns where certain PMs, BUs, or customers consistently have higher *Days To Close*, indicating process gaps, staffing constraints, or external negotiation friction. - Use these findings in PM one-on-ones and BU reviews to share best practices from top performers and align on specific process changes or support needed for outliers. | - Change Order--Status (Options) - Change Order--Days To Close (#) - Change Order--Created Date - Change Order--Close Date - Project Manager - Project Business Unit - Customer Name |
| Construction Executive | Identify Projects with High Change Order Risk. Spot jobs with concentrated COR volume or overdue items that may impact schedule and customer relationship. | Use change order metrics to spot projects where CORs are piling up or aging out: - Filter *Project Status* to *In Progress* so you focus on active jobs. - Filter *Change Order--Status (Options)* to exclude *Closed* to look only at open CORs. - Group by *Project Name* or *Project Number* and review counts of CORs where *Change Order--Overdue (Y/N)* is *Y* or *Change Order--Days Overdue (#)* is high. - Combine this view with *Project Health* and *Project--Planned Completion Date (Date)* to decide which projects to place on the executive watch list and where to engage directly with the GC or owner. | - Change Order--Overdue (Y/N) - Change Order--Days Overdue (#) - Change Order--Status (Options) - Change Order--Priority - Project Name - Project Number - Project Status - Project Health - Project--Planned Completion Date (Date) |
| Construction Executive | Understand Change Order Volume by Customer and Project Type. Use COR data to inform estimating assumptions, fee strategy, and staffing for different kinds of work. | Analyze historical change orders to understand typical volume and approval effort by work type and customer: - Filter *Change Order--Created Date* to a longer lookback window (for example, the last 6–12 months). - Use *Change Order--Number* as the atomic unit and count change orders by *Project Type, Project Business Unit,* and *Customer Name.* - Within each segment, review average *Change Order--Days To Close (#)* to understand how much approval effort and negotiation time is typical. - Feed these insights back into estimating, pricing, and staffing so that project budgets, markups, and overhead assumptions reflect the real change order load for each segment. | - Change Order--Number - Change Order--Created Date - Change Order--Days To Close (#) - Project Type - Project Business Unit - Customer Name |

## Create a Project Operations: Change Order Requests (CORs) report

Follow the steps to [create a custom report](/roofing/docs/create-custom-reports) based on the template and select the columns to include in your report. You only need to create the report once. After it's created, you can share it with others who may need to access the information in the report, edit report columns, and more.

## Report data fields

This template has the following data field sections:

- **Change Order Details:** Additional information about the change orders. Examples: *Change Order Description* and *Change Order Scope of Work*.
- **Project Details:** Additional information about the project. Examples: *Project Status, Project Planned Completion Date, Project Manager*
- **Customer Details:** Additional information about the customer. Examples: *Customer Name, Customer Address.*
- **Location Details:** Additional information about the location. Examples: *Location Name, Location Address*

For detailed descriptions of the data fields, please refer to the [Reporting Dictionary](/roofing/docs/learn-about-report-data-fields-in-the-reporting-dictionary-1).

> [!TIP]
> **Tip:** Hover over the name of the column to see a short description.

## Report filters

You can use filters to set the scope of the report before running it, so you only see the results you want in the report.

- **COR Status:** Filters the report based on the current status of the change order. Options include: *Draft, Sent, Responded, Rejected,* or *Approved*. You can select one or multiple options to view change orders at specific stages of progress, for example, to focus on items needing responses or review only rejected change orders for analysis.
- **COR Created From Date - To Date:** Use this filter to include only change orders with a created date between the dates you specify. This allows you to focus only on change orders created during a specific timeframe.
- **Project Status:** Use this filter to include only projects with specific statuses. Options include: *Bid, Canceled, Completed, Hold, In Progress, Pending Scheduling,* and *Scheduled*. You can select one or multiple options to narrow the report results based on the stage of the project lifecycle.
- **Project Manager:** Use this filter to include only projects managed by specific project managers. You can select one or multiple project managers to focus on work assigned to certain individuals or teams.
- **Project Health:** Use this filter to include only projects with a specific current health status, as reported in the most recent daily log. Options include: *None, On Track, At Risk*, and *Off Track*. You can select one or multiple options to track performance across various project conditions.

When you're finished setting the filters, click **Run Report**.

![](https://cdn.document360.io/961862ab-d0f2-4d91-bb62-a62ee8184eff/Images/Documentation/project-operations-change-order-requests-cors-report-template-image-c0wu1jax.png?sv=2026-02-06&spr=https&st=2026-11-01T19%3A50%3A55Z&se=2026-11-01T20%3A50%3A55Z&sr=c&sp=r&sig=gjC5FpBbVptrADsRzPqhSN%2FOiN51VNWWKTEEqVVh36M%3D)

> [!TIP]
> **Tip:** Click **Edit Columns** to add and remove columns. For further customization, you can also [arrange report columns and apply filters](/roofing/docs/run-filter-and-export-reports#filter-and-arrange-a-report).

## Want to learn more?

- See [Edit custom reports](/v1/docs/edit-custom-reports)
- See [Run, filter, and export reports](/v1/docs/run-report)
- See [Schedule reports](/v1/docs/schedule-reports)