Use Historical Ball-in-Court Reporting

Overview

Historical Ball-in-Court Reporting helps you see which party was responsible for taking action on a Change Order Request (COR) over time. Instead of only showing the current Ball-in-Court, this view helps you understand where a COR stalled, how long it stayed with each party, and how much value was tied up during the review process. 

Why it matters

When you are managing a high volume of CORs, it is hard to tell where delays are happening. Historical Ball-in-Court Reporting gives you a clearer view of accountability across the COR lifecycle so you can spot bottlenecks, follow up with the right party, and better understand financial exposure tied to pending review.

How it works

Clearstory uses COR status and stage changes to reconstruct a historical timeline of Ball-in-Court ownership. Each time a COR moves through the workflow, the reporting captures a new interval showing who was responsible during that period. This allows the system to report on ownership history instead of only the current state. 

Historical Ball-in-Court Reporting helps you analyze:

• Which party owned the COR at different points in time

• Whether a COR was in your court or waiting on another party

• The count and dollar value of CORs by court

• How long CORs remained with each party

• Trends across one project or multiple projects 

The reporting supports these Ball-in-Court categories:

• My Company

• My Contractor

• My Customer

• Owner 

Reporting is available in analytics under:

• Company-level
• Contractor Insights
• Customer Insights

Note: You can also switch between Sent and Received views to understand the difference between CORs your team sent out for review and CORs your team received and need to act on. 

How Ball-In-Court Is Determined

Ball-In-Court is uniquely mapped based off of the status and stage for sent and received CORs. Please note the below mapping for backend Ball-In-Court logic:

Sent CORs:

Received CORs:

Step-by-step instructions

1. Go to Analytics.

2. Open Ball-in-Court Historical in Company Level Reporting or under Contractor/Customer Insights.

3. Select the project you want to review, or choose multiple projects if you want a broader view.

4. In Company Level choose whether you want to see Sent or Received CORs.

5. Select a time range.

6. Review the dashboard results, including:

   
   

   1. court distribution

   2. exposure metrics

   3. time-in-court analytics

   

7. Click a chart segment to drill into the related COR log when you want to investigate a specific set of records. 

Tips and best practices 

• Review both count and dollar value metrics. A party may not be holding many CORs, but they may still be holding the highest-value requests. 

• Use time-based metrics such as time since submission, time spent in current court, and average time per court to identify recurring review slowdowns. 

• If you manage multiple jobs, use the multi-project view to compare patterns across projects and identify broader process issues. 

• Keep in mind that imported CORs are only tracked from the time they were imported, and deleted CORs are excluded from reports by default. Historical data may also be incomplete for some time ranges. 

FAQs

What does Ball-in-Court mean?

Ball-in-Court means the party currently responsible for taking action on a COR based on its status and stage. Historical Ball-in-Court Reporting extends that concept by showing who owned responsibility over time. 

What can I filter in the report?

You can filter by project, Sent vs Received, and time range. Your filters also persist between sessions. 

What metrics can I review?

You can review COR count, total dollar value, time since submission, time spent in the current court, and average time per court. 

Can I use this across multiple projects?

Yes. Historical Ball-in-Court Reporting supports portfolio-style analysis across multiple projects. 

Why might I see incomplete data?

You may see a warning if historical data is incomplete for the selected time range. In some cases, Ball-in-Court reporting may be unavailable if there is not enough historical data. 

Who can access this report?

Account Owners, Admins, and Project Managers can view and filter Ball-in-Court analytics and can export the data. Field Users have limited view and filter access and cannot export.