SubAscentVisit Website →
← Back to blog

Ball in Court Tracking for Trade Subs: Who Has the Submittal?

October 28, 2026
Ball in Court Tracking for Trade Subs: Who Has the Submittal?

Ball in court tracking means knowing, for every open submittal, RFI and change order, exactly who owes the next action and by when. For a specialty trade sub, the fix is one log where each item shows a named person, a due date and a timestamp for when the ball changed hands. Then you chase by exception instead of re-reading email threads.

Most searches for this phrase land on legal case software. This is the construction version: your fire protection shop drawings are sitting somewhere between you, the GC, the architect and the engineer, and you need to know where.

Subascent
Keep Submittals Moving Across Every Job
Track submittals, RFIs, and change orders by who owes the next action, so your trade team can follow up without digging through email threads.
Visit Subascent

TL;DR

  • "Ball in court" is the person or party who owes the next move on an item. It changes at every handoff, and so does the clock.
  • Track four fields on every item: who holds it, what they owe, the date it moved to them, and the date it is due.
  • Log the handoff the day it happens. A submittal that has been with the GC for nine days looks fine in your head and terrible on paper.
  • Chase early and in writing, and tie every delay to your schedule so you keep your time and cost rights.
  • A trade-sub tool beats a GC portal because you see all your jobs in one view, not one job at a time.

Table of Contents

What "ball in court" means on a submittal

The phrase comes from tennis. The ball is on one side of the net. Until that side hits it back, the other side can do nothing.

On a submittal, the ball starts with you. You assemble product data, shop drawings or samples and send them to the GC. The ball moves to the GC for a completeness check, then to the architect or engineer for review. After they respond, it comes back to the GC and then back to you for revisions or release to fabrication.

So at any moment, an item has one of a few holders:

  • You (the sub): preparing, revising or resubmitting.
  • The GC: reviewing, forwarding, or sitting on it.
  • The design team: reviewing against the spec.
  • The supplier or manufacturer: producing data, samples or a corrected drawing for you.

The last one gets missed. When your electrical supplier owes you a corrected cut sheet, the ball is in their court, and it still delays your submittal. Track it the same way.

Why the ball matters more to subs than to GCs

A GC's project coordinator watches one job. You are watching eight or twenty. Your submittal is also the first domino: the review time eats into your fabrication lead time, which eats into your install window.

Review delays compress fabrication and installation time

The subcontract puts the obligation on you. The ConsensusDocs 750 standard subcontract says a subcontractor must promptly submit required shop drawings, samples, product data and similar materials for approval. It also makes you responsible for the accuracy and conformity of your submittals, and says they must be sent consistent with the progress schedule so they do not delay the constructor or others. If you are late, that is on you. If the GC is late, you need the record to prove it.

What to record on every item

A ball in court log is not complicated. Four fields do the job, plus a history.

FieldWhat goes in itWhy it matters
Current holderA named person and company, not "GC"You know who to call
Action owedReview, forward, revise, resubmit, release"Waiting" is not an action
Date receivedThe day the ball moved to themStarts the clock
Due dateContract or schedule response timeTriggers your follow-up

Then keep the history: every time the holder changes, add a line with the date. Do not overwrite the old holder. When someone asks in March why the curtain wall submittal took 42 days, you want the row-by-row answer.

Two more fields earn their place:

  • Need-by date. The latest day you can get approval and still make lead time. Work backward from the install date through delivery and fabrication. A 12-week switchgear lead time means the approval deadline is not the review due date. It is much earlier.
  • Linked schedule activity. What does this item hold up? If the answer is "nothing for six weeks," it drops down the chase list.

A worked example: a sprinkler submittal

Say you are a fire protection sub on a four-story building. Here is how the log reads over a few weeks.

DayEventBall in courtDue
1Hydraulic calcs and shop drawings sent to GCGCDay 6
4GC forwards to architect and engineerDesign teamDay 18
18No response. You email the GC.Design teamDay 22
23Returned "revise and resubmit"YouDay 28
26Resubmitted with correctionsGCDay 31

Look at what the log shows. The GC held the package for three days before forwarding. The design team held it for 19 days. You held it for three. If your delivery date slips, you have a dated record of where the time went, and you chased on day 18 instead of day 40.

That is the whole value. The log turns "I think they have it" into "they have had it since the 4th."

One response is not always the end of a step

A wrinkle that trips up subs: when several reviewers are assigned to the same step, the item may move on after the first response. The mechanical engineer might respond and the electrical engineer may never open it. If the spec requires both to review, ask the GC how the review is routed, and note in your log which reviewers have actually responded.

The same applies to the stamp. There is a difference between where an item sits in the workflow and the formal decision issued on it. An item can be "back with the GC" in the workflow and still carry only a partial review. This matters on custom items such as glazing, where fabrication-ready window shop drawings have to be accepted as drawn before anything is cut. Do not release to fabrication on a workflow status. Release on the written decision.

How to chase without burning the relationship

Tracking is half the job. The other half is moving the ball without annoying the person who controls your payment.

  1. Set the chase date when you submit. If review is due on day 14, put your follow-up on day 12 or 13. Do not wait for the due date to pass.
  2. Chase the holder, not the whole thread. Write to the person who owes the action. Copying six people dilutes it.
  3. Ask a specific question. "Can you confirm the architect has received package 07 and when you expect comments?" gets answered. "Any update?" does not.
  4. Tie it to the schedule. "Sprinkler heads need approval by the 14th to hold the ceiling install on the 3rd." Now it is a project issue, not a nag.
  5. Escalate in writing, once. If the second chase goes nowhere, send a short notice that the delay affects your schedule and ask for a response date.

On communication paths, remember that ConsensusDocs 750 says project communications ordinarily go from the subcontractor to the constructor unless the subcontract says otherwise or there is an emergency. Do not go around the GC to the architect unless your contract or the GC allows it. Ask the GC to chase, and let your log show you asked.

Protect your time and money

Delay claims turn on paper. One trade press summary of contract language notes that under the AIA A201, a contractor that fails to provide a submittal schedule is not entitled to extra compensation or time based on slow submittal processing. The takeaway for a sub: give the GC a submittal schedule early, in writing, and keep it current. Your ball in court log is the evidence that you submitted on time and that someone else held the ball.

Before a dispute, have a lawyer who handles construction contracts read your actual subcontract. Notice requirements and time limits differ job to job, and this article cannot tell you what yours says. Our subcontract agreement review checklist is a good place to find the clauses to take to them.

Trade by trade: where the ball gets stuck

The same log works in every trade, but the sticking points differ.

  • Electrical and low-voltage: Gear and panel submittals wait on the manufacturer, then on engineer review. Lead times drive everything. Track the need-by date first.
  • Plumbing and HVAC/mechanical: Equipment submittals go through several reviewers, and coordination drawings add another loop. AGC's spatial coordination guidance says mechanical, electrical, plumbing and fire protection participants must fully participate, and puts coordination drawing review, fabrication duration and delivery lead times in the coordination schedule. Treat each of those as its own tracked item.
  • Fire protection (sprinkler): Hydraulic calculations and shop drawings often go to both the engineer and the authority having jurisdiction, so there are two holders after the GC.
  • Masonry and concrete: Mix designs, rebar shop drawings and mortar and unit samples. Samples feel small, but a rejected color sample can stall a whole wall.
  • Drywall, painting, flooring, insulation: Many items are samples and finish selections. The ball often sits with the owner's rep or architect for weeks.
  • Glazing: Long lead times and engineered drawings mean any resubmittal is expensive.
  • Roofing, framing, steel/rebar: Fabrication-driven. If detailing is not approved, the mill or shop does not start.

For a deeper walk through the whole process, see our guide to the submittals workflow with general contractors and the seven steps to fix the construction submittal process.

Spreadsheet, email or software

There are three ways subs track this today.

Inbox and memory. Free and fast, until your estimator is out sick or a thread gets buried. You find out an item stalled when the GC calls about the schedule.

A spreadsheet. A solid start. A sheet with the four fields above beats nothing. Its weakness is that nobody updates it at 4:30 on a Friday, and it does not remind anyone of anything.

Job software built for subs. The log updates as the item moves, due dates trigger reminders, and you can filter to "items waiting on the GC" across every job. Good systems record each response with a timestamp, so you rebuild nothing later. Construction Executive's 2026 reporting points out that disconnected systems, email-based decisions and missing approval logs force teams to reconstruct project records and raise delay and dispute risk. That is exactly the cost of an inbox log.

What to look for in any tool:

  • A current-holder field on each item, visible in a list
  • Due dates with automatic reminders
  • A "waiting on me" view for your own team
  • An activity history that cannot be quietly edited
  • Submittals, RFIs and change orders in one place, since they share the same holders
  • Mobile access, so the foreman can see what is approved before ordering material

One more reason to prefer a sub-focused tool: portals run by a GC show you only that GC's job. Our look at why construction software built for subs differs from GC tools explains how that plays out when you run a dozen jobs for six different contractors.

Use the log to spot problems early

Once you have a few months of dated handoffs, the log tells you things.

  • Average days per holder. If one GC consistently holds items eight days before forwarding, build that into your submittal timing on their next job.
  • Resubmittal rate. Many rejections on one trade mean your submittal checklist needs work, not the reviewers.
  • Aging. Sort open items by days since the ball moved. Anything in the top few gets a call.

Construction Executive reported in May 2026 that submittal cycle time, RFI age and volume, and change orders can serve together as early-warning signals for project risk. You do not need a data team. Sorting your own list by age does most of it.

The Federal Transit Administration's January 2025 guidelines make a related point for public work: submittals, document control, schedule control and information systems are project-management activities that should be managed together. The same logic holds on a private job, where schedule and submittals live on different screens in most shops. Our four-step document control guide shows how to keep the files behind the log in order, and if overlapping crews are the problem, see how to resolve subcontractor scheduling conflicts.

Our perspective

We built Subascent for specialty trade subs because the tools on the market assume you are the one running the project. They show the GC's view of the ball. A sub does not need a view of one job. A sub needs to know, this morning, which five items across fifteen jobs are costing money.

Here is what we think after talking with trade owners and estimators:

  • The log is a habit before it is software. If your team does not note a handoff the day it happens, no tool saves you.
  • The most valuable column is the date the ball moved, not the status. Status words drift. Dates do not.
  • Submittals, RFIs and change orders should sit in one list by holder. Your project manager does not think in modules. They think "what am I waiting on?"
  • Foremen need a short answer: approved, not approved, not yet. They do not need the review chain.

Start with a spreadsheet if that is all you can do this week. Just start.

— Dave

Tracking the ball in Subascent

Subascent is job and bid management software for specialty trade subcontractors. Submittals, RFIs and change orders live in one place with due dates, reminders and a history of every handoff, so your project manager can see what is waiting on the GC across all jobs. Foremen get the free CrewTrack mobile app with the subscription. If you want to see it with your own jobs in it, start from the Subascent site and try it before you commit.

Setting up your first log: a one-week plan

You do not need a rollout. Do this in a week.

  1. Monday: List every open submittal and RFI across your jobs. Pull them from email, your folders and the GC portals you have logins for.
  2. Tuesday: For each, find the current holder and the date it moved to them. If you cannot tell, ask the GC. That is your first useful chase.
  3. Wednesday: Add need-by dates, working backward from install through lead time.
  4. Thursday: Sort by age. Chase the top five.
  5. Friday: Agree on one rule: any handoff gets logged the same day. Assign one owner per job.

Then review the list for 15 minutes at the same time every week. The meeting is short because the log does the talking.

FAQ

What does ball in court mean in construction?

It names the person or party who owes the next action on an item, such as a submittal, RFI or change order. It changes as the item moves between the sub, the GC, the design team and suppliers. The holder is the one who needs to act, so that is who you chase.

Who has the ball after a submittal is rejected?

It returns to you, the sub, for revision and resubmission, usually through the GC. Your clock restarts, and the schedule impact of the revised cycle starts to build. Log the date it came back and set a resubmittal due date the same day.

How often should I follow up on a submittal?

Chase once shortly before the response is due, then again soon after if there is no answer. Make each message specific: the item, the holder, the date you need it and what it holds up. If a second chase fails, escalate in writing once and keep the record.

Can I track ball in court in a spreadsheet?

Yes. Use columns for item, current holder, action owed, date received and due date, and add a new row for each handoff. It works for a few jobs. Once you run many jobs, reminders and cross-job filters become worth having.

Sources