How to Track Subcontractor Tasks on Construction Projects

Mike had three crews on site and no idea what any of them had finished yesterday.

The framing sub said they were done with the second floor. The mechanical sub said they couldn't rough in the HVAC because framing hadn't been completed yet. The framing foreman said that was news to him.

By the time Mike got to the bottom of it, half a day was gone, one subcontractor was billing for standby time, and the mechanical foreman had gone home.

That's not a people problem. That's a tracking problem.

Most general contractors manage subcontractors through some combination of morning meetings, site visits, phone calls, and gut instinct. It works — until it doesn't. And when it doesn't, it usually costs you: rework, delay claims, or a blowup in the final weeks of a project when everything collides at once.

This guide is about building a real system for tracking subcontractor tasks — one that catches problems before they become expensive, without adding hours to your day.

Why Tracking Subcontractor Tasks Is Actually Hard

You're not tracking one person's work. You're tracking the interdependent work of 6 to 20 different companies, each with their own crews, their own schedules, their own subcontractors, and their own version of what "done" means.

The trades are sequential in some areas and parallel in others. A delay in one area ripples downstream in ways that aren't always obvious until the project is already in trouble.

Here are the real reasons subcontractor tracking breaks down:

Handoffs happen verbally. The GC tells the framing sub the deck is ready for them at the morning meeting. The framing foreman writes it on a scrap of paper, maybe. Two days later, nobody can confirm whether the conversation happened or what was agreed.

"Almost done" is not a unit of measurement. Subs often report progress in vague terms because they're managing their own crews and don't want to commit to a date they might miss. "We're probably 80% done" tells you almost nothing about when the next trade can start.

Scope creep compounds tracking problems. When a sub picks up additional work on site that wasn't in their original contract — adding a few outlets here, adjusting a duct run there — that work often doesn't get formally tracked. It just happens. Until it doesn't.

Photos don't always tell the truth. A framing photo might look complete but miss that the backing for the HVAC unit isn't in yet. Visual confirmation has limits.

Nobody owns the downstream risk. If framing is late, mechanical is delayed. But the mechanical sub's delay isn't tracked against framing — it's tracked against mechanical. The cause-and-effect chain gets broken.

The Three Systems Most GCs Actually Use

Let's be honest about what's happening on most job sites before we talk about what should happen.

1. The Whiteboard

Every site trailer has one. The whiteboard has the schedule, colored by trade, updated every few days. It's visible, collaborative, and works well for high-level awareness.

The problem: it's a snapshot. It tells you what was planned and roughly what's happened. It doesn't capture who confirmed what, when things actually finished, or why something slipped. And it disappears when someone erases it.

2. The Daily Log

A good project manager keeps a daily log — handwritten or digital — that captures what trades were on site, what work was completed, and any notable issues. These logs are valuable for documentation and dispute resolution.

The problem: they're written after the fact, usually at the end of the day, from memory. They capture what the PM saw. They don't capture what the PM didn't see. And reading a daily log to find out where a specific task stands requires searching through days of entries.

3. The Morning Standup

Daily check-ins with foremen are the lifeblood of most job sites. "What did you finish yesterday? What are you doing today? What do you need?" Simple. Effective.

The problem: verbal. Nothing is recorded. No accountability. The framing foreman says they'll be done with the second floor by Thursday. Thursday comes and they're not done. The GC has no record of the commitment, and the sub has no incentive to honor it. The conversation might as well not have happened.

What "Tracking" Actually Needs to Do

Before choosing a system, get clear on what you actually need to track:

Task completion. Which tasks have been finished, by whom, and when? Not "probably done" — actually done, confirmed, ready for the next trade.

Upcoming dependencies. Which tasks need to be complete before another trade can start? If mechanical needs framing done before they can rough in, that dependency needs to be visible and managed proactively.

Active commitments. What has each sub committed to completing by when? This is different from the master schedule. It's the rolling short-term promise: "We'll have the second floor framed by Thursday."

Blockers. What's preventing a trade from starting or finishing? Material not delivered. Inspection not cleared. Drawing not issued. These need to be surfaced and resolved fast, not buried in someone's inbox.

Changes. When work gets added, modified, or removed, that needs to be tracked — who authorized it, what was agreed, what the cost and schedule impact is.

The Short-Interval Schedule: Your Core Tracking Tool

The most effective tracking system most GCs use is the short-interval schedule, also called the three-week lookahead or the rolling schedule.

Here's how it works:

Each week (often on Friday), the project manager or superintendent sits down — ideally with the foremen — and builds out a detailed schedule for the next two to three weeks. Not the master schedule. Not the high-level bar chart. A task-level list of exactly what needs to happen, who's doing it, and when.

The short-interval schedule might look like this:

Every Monday, you walk the site against this list. Which tasks finished as planned? Which didn't? Why? The foremen update their own sections, and you update the master.

The power isn't in the spreadsheet. It's in the weekly conversation to build it. When you sit down with the mechanical foreman to plan next week, he tells you he's waiting on a duct supplier delivery. You find out a week earlier than you would have otherwise. You can adjust.

The Commitment Conversation: Getting Real Promises

One thing the schedule doesn't capture is the quality of the commitment behind each task.

"We'll probably get to it next week" is not a commitment.

"We'll have the second floor framed and decked by Thursday EOD" is a commitment.

These feel like the same thing in a morning meeting. They're not.

When you're building your short-interval schedule with the foremen, push for specific commitments. Not "by next week" — by which day? By which day will the predecessor task be complete so the downstream trade can start? Get the foreman to say the day out loud.

Then write it down. Not for leverage. For visibility.

Tony, a superintendent on a hospital expansion in Phoenix, started asking his framing foreman to text him at the end of each day with a simple message: "Done: [what they finished]. Tomorrow: [what they're starting]." It took about 45 seconds for the foreman to send. It saved Tony an average of two unnecessary phone calls per day — and created a running record of what was promised and when.

"I'm not using it against anyone," Tony says. "I just hate finding out on Thursday that something went wrong on Monday."

How to Structure Subcontractor Check-Ins

The daily standup is your most important tracking tool. Here's how to run it in a way that actually produces information:

Ask three questions:

1. What did you complete yesterday?
2. What are you working on today?
3. Is anything in your way?

Don't accept vague answers. "We're working on the second floor" is not useful. "We're completing the backing for the HVAC units on the south side of the second floor, expecting to finish by 2 PM" is useful.

Document it. Even just a quick note in your site log. Better: a short photo of the whiteboard after the meeting. Best: a field management app where foremen can check off tasks directly.

Make it short. Twenty minutes, max. If you're running 45-minute standups, you're having a different kind of meeting. Keep it tactical.

Include downstream trades when there's a handoff. If framing is finishing today and mechanical is supposed to start tomorrow, have both foremen in the same conversation. The handoff happens in person, not through a game of telephone.

The Inspection Bottleneck: Where Tasks Go to Die

On most construction projects, the inspection process is the single biggest source of task tracking failure.

Here's why: tasks don't close until they're inspected. But inspections are scheduled, they get rescheduled, the inspector shows up and calls a correction, and now that task is in limbo. The work is done, but it's not "done done."

Meanwhile, the next trade is waiting. The mechanical sub can't cover their ductwork until rough mechanical is inspected. The drywall crew is standing by. Every day of inspection limbo is a day of lost productivity somewhere else.

Track inspections as tasks with the same rigor as physical work:

• Inspection requested (date)
• Inspection scheduled (date and time)
• Inspection result (pass / correction noted)
• Correction completed (if applicable)
• Reinspection cleared

Assign someone to own each inspection through to completion. Not "framing is responsible for their own inspections" — someone specific on your team knows exactly where every active inspection stands at any given time.

Building a Tracking System That Foremen Will Actually Use

Here's the trap most project managers fall into: they build a tracking system for themselves that requires foremen to input data.

Foremen will not input data.

They're managing a crew of eight in 100-degree heat, making a hundred small decisions a day. They're not going to log into a software system and update task statuses. They'll do it once, maybe twice, and then they'll stop.

The systems that work are the ones that meet foremen where they are.

Text message check-ins. Simple. Every foreman has a phone. You don't need an app. Create a group text for each trade. Ask for a one-line end-of-day update. It's not perfect, but it's information you'd otherwise have to chase.

Photo-based updates. "Send me a photo when the second floor decking is done." Takes the foreman five seconds. Gives you documented confirmation. Easy.

Pre-populated checklists. If you're going to use an app, give the foreman a list that's already built — all they have to do is check things off. Don't ask them to create tasks. Give them the tasks and let them mark complete.

Leverage the daily walk. Observation is underrated. A good superintendent who walks the site twice a day knows more about what's actually happening than any software system. The question is whether that knowledge gets captured somewhere.

When Things Go Off Track: The Early Warning System

The whole point of tracking subcontractor tasks is to catch problems early enough to do something about them.

Here's what an early warning system looks like in practice:

Day-old late starts. If a task was supposed to start Monday and it's Tuesday morning and there's no crew, that's a flag. Not a crisis — yet. Make a call. Find out why. Usually there's a reason: material delivery, traffic, crew pulling from another project. Usually resolvable. But you need to know on Tuesday morning, not Thursday afternoon.

Float consumption. Every project has float — schedule buffer. When you're burning float faster than your project is progressing, you're heading for trouble. The short-interval schedule should show you this in real time.

Dependency stalls. If a predecessor task is running late and a downstream trade has already mobilized, you're about to pay standby time. Get ahead of it. Have the conversation with the downstream sub before they show up. Rescheduling is always cheaper than standing by.

"We're almost done" for three days in a row. If a sub has been "almost done" with a task for multiple days, go see it yourself. Something is either harder than expected or the crew is running out of steam. Either way, you need to know.

The Difference Between Tracking and Micromanaging

Some GCs avoid tracking subcontractor tasks carefully because they worry about souring the relationship. "They're professionals. I hired them. If I'm looking over their shoulder every day, I'm going to push them away."

This is a real concern, but it confuses tracking with micromanaging.

Tracking is about information. You need to know where the project stands, not because you don't trust the sub, but because you're responsible for the whole project. Knowing that the mechanical rough-in is two days behind isn't micromanaging — it's basic project management.

Micromanaging is telling the sub how to do their work. Telling the foreman how to run his crew. Second-guessing their methods. That's different.

The framing is: "I need to know where you are so I can sequence the rest of the project. I'm not questioning your work — I just can't run a schedule blind."

Most experienced subs understand this. The good ones actually appreciate it. It means they're less likely to get ambushed by a GC who's disappointed because they didn't know what was happening.

Using Technology Without Overcomplicating It

There are dozens of construction management platforms on the market: Procore, BuilderTrend, Fieldwire, CoConstruct, and many more. They all have task tracking features. Some are excellent.

But the right tool depends on your project and your team.

For small to mid-size commercial GCs (under $10M in revenue, projects under $5M), the overhead of implementing a full construction management platform often isn't worth it. The tool creates more work than it solves.

For larger operations, a proper platform pays for itself in documentation, accountability, and time savings.

If you're evaluating tools, here's what to look for from a task tracking standpoint:

Mobile-first. If your foremen can't use it from their phones without training, it won't get used.

Simple task updates. A foreman should be able to mark a task complete in two taps. If it requires navigating menus or filling out forms, it will be abandoned.

Dependency visibility. The tool should show which tasks are blocking which other tasks. This is the most underrated feature in construction project management software.

Real-time notifications. When a task is marked complete, the downstream trade and the PM should know automatically. Not via a separate email thread — automatically.

Photo attachment. Evidence matters. The ability to attach a photo to a task completion is basic but essential.

Whatever you use, keep the setup minimal. Create the tasks you need to track. Don't build an elaborate hierarchy that takes an hour to navigate. The purpose is clarity, not comprehensiveness.

A Practical System for a Mid-Size GC

Here's a real-world system that works for a GC running 3-5 projects simultaneously with 8-15 subs per project:

Weekly: Build the 3-week lookahead with each foreman. Confirm commitments for the coming week. Identify dependencies and potential conflicts.

Daily: 20-minute morning standup with all foremen on site. Three questions. Document answers. Walk the site after the meeting.

End of day: Quick update from each foreman — what finished, what's carrying over, any issues. Text or app, doesn't matter.

As needed: Inspection tracking, change order tracking, delivery confirmations.

The daily walk is non-negotiable. No system replaces the superintendent who knows every corner of the job site.

The documentation habit is what separates good project managers from great ones. Not because you'll ever need to pull the records, but because the discipline of writing things down forces you to process what you're seeing. It makes you better.

Handling Disputes: Why Tracking Protects Everyone

Here's the business case for better subcontractor task tracking that goes beyond project management.

When something goes wrong — and it will — the question of who's responsible often comes down to documentation. If the framing sub claims mechanical couldn't start because the GC didn't give them access, and the GC claims framing wasn't done, who's right?

Without documentation: both sides have verbal accounts that contradict each other. The dispute drags on. Legal fees accumulate. Relationships are damaged.

With documentation: you have the daily log showing what was inspected and when, the text records showing the handoff conversation, and the short-interval schedule showing what was planned and what actually happened. The dispute gets resolved in hours, not weeks.

Subcontractors who know you keep good records behave better. Not because they're dishonest — most subs are professionals — but because clear documentation creates mutual accountability. Nobody wants to make a claim that's going to be refuted by their own text messages.

Rachel, a project manager at a regional commercial GC, had a roofing sub claim they'd been delayed waiting for structural steel that the GC was supposed to provide. The GC's project manager pulled the delivery records, daily logs, and text messages. The steel had arrived on time. The roofing sub had simply been pulled to another project.

The dispute was resolved in one meeting. "Having that documentation made the conversation easy," Rachel says. "We didn't have to argue about what happened. We could just look at it."

Subcontractor Scheduling vs. Task Tracking: Knowing the Difference

One clarification that's worth making explicit: the project schedule and the task tracking system are different tools.

The schedule (whether it's a Gantt chart, a bar chart, or a lookahead) shows you the plan. When things are supposed to happen. What sequence the work should follow. It's forward-looking.

Task tracking shows you what actually happened. Which tasks got done, when, and by whom. It's backward-looking, but it feeds into adjusting the schedule when reality deviates from the plan.

You need both. The schedule without task tracking is a plan that nobody checks against reality. Task tracking without a schedule is a log without context.

The short-interval schedule is the bridge between them: a forward-looking plan at task level that gets updated based on actual completion.

The Real Bottleneck: Communication Between Trades

After years of watching construction projects succeed and fail, the biggest single cause of subcontractor task tracking problems isn't tools, schedules, or systems.

It's communication between trades.

When the framing sub finishes an area, does the mechanical sub know? How? When? When the electrical sub hits an issue that's going to delay them, does the GC know immediately, or does it come out in the Friday meeting after two days of downstream impact?

The best task tracking system in the world is only as good as the communication it's built on. The short-interval schedule helps because it forces a regular conversation. The daily standup helps because it gets everyone in the same room. The text message check-in helps because it creates a direct line.

But you can't automate communication. You have to build it.

The GCs who do this best treat the job site as a communication system, not just a construction system. They know that the morning standup isn't just about status updates — it's about making sure the framing foreman and the mechanical foreman actually understand each other's plans. That's where problems get caught.

Conclusion: A System Is Better Than Hustle

Tracking subcontractor tasks on a construction project is hard. The work is complex, the people are independent, and the conditions change daily.

But the alternative — managing by instinct, chasing phone calls, discovering problems when it's too late to fix them cheaply — is harder.

The right system doesn't have to be sophisticated. A short-interval schedule, a daily standup, and a consistent habit of documentation will take you further than any software subscription. The discipline of running the same check-in, every morning, and writing down what you find is what separates a GC that controls their projects from a GC that reacts to them.

Mike, the superintendent from the opening story, added one thing after his HVAC standby incident: every morning, he walks framing and mechanical into the same conversation. "Tell him what you finished yesterday and what you're starting today. Right now, while I'm here."

It takes five minutes. Nobody argues about what was communicated. The handoffs happen in front of a witness.

The next three projects have had zero standby claims.

Quick Reference: Subcontractor Task Tracking Checklist

Daily:

• [ ] Run morning standup (20 min max)
• [ ] Document task completions and upcoming commitments
• [ ] Walk the site against the short-interval schedule
• [ ] Confirm any inspection status changes
• [ ] Get end-of-day update from foremen

Weekly:

• [ ] Build/update the 3-week lookahead with foremen
• [ ] Identify upcoming dependencies and potential conflicts
• [ ] Review float consumption
• [ ] Confirm material deliveries for coming week

As Issues Arise:

• [ ] Document any delays, blockers, or changes in writing
• [ ] Confirm handoffs between trades in person
• [ ] Address "almost done" claims with a site visit
• [ ] Track inspection status through completion

Convoe is a project management tool built for construction teams. If you're managing subcontractor tasks across multiple projects and want a cleaner way to track commitments and dependencies without adding overhead to your day, see how Convoe works for construction GCs.