A schedule of values (SOV) is a list that divides the contract sum into line items, each with a dollar value, so progress can be measured and billed line by line each pay period.
Plan reviews connect field conditions, drawings, and the next decisions on a job. AI-generated illustration.
A schedule of values is the billing backbone of a lump sum contract. The contractor splits the contract sum into parts (mobilization, site work, concrete, framing, drywall, mechanical, and so on) and assigns each a value. The total must equal the contract sum. Every month, the contractor reports the percent complete for each line, and that drives the pay application. On AIA projects, the SOV lives on the AIA G703 continuation sheet, which supports the G702 application for payment.
The owner or architect usually approves the SOV before the first billing. Once approved, it is hard to change, so getting it right early matters.
A schedule of values example
Say a GC has a $920,000 lump sum contract to build out a fitness center. Here is a simplified SOV and the third month's billing.
Example SOV with month three progress
Line
Scheduled value
Percent complete
Completed to date
General conditions
$96,000
30%
$28,800
Demolition
$38,000
100%
$38,000
Framing and drywall
$164,000
55%
$90,200
Plumbing
$118,000
40%
$47,200
HVAC
$146,000
35%
$51,100
Electrical
$132,000
40%
$52,800
Flooring
$91,000
0%
$0
Paint and finishes
$62,000
0%
$0
Specialties and closeout
$73,000
0%
$0
Total
$920,000
33.5%
$308,100
Approved change orders are added as new lines at the bottom, not blended into the original ones. That keeps the original contract and the changes separately visible, which helps everyone at closeout.
How to build a schedule of values that works
Match your cost structure. Lines should line up with your cost codes or at least roll up cleanly, so billing and job costing tell the same story.
Split big lines. A single $300,000 mechanical line is hard to measure. Break it into rough-in, equipment, and trim, or by floor.
Separate labor and material when allowed. It helps bill stored materials and makes percent complete easier to defend.
Include closeout and general conditions lines. They make sure some money is tied to finishing, which owners like.
Mirror your subs. Ask subs for SOVs that match your lines for their scope.
Common SOV disputes
The biggest one is front-loading: putting extra value on early work (mobilization, demolition, sitework) so the contractor collects cash ahead of actual cost. Architects and lenders look for it and may reject the SOV. The opposite problem is back-loading, which squeezes the contractor's cash flow. Other fights include lines too vague to verify and percent-complete claims that do not match what is on site. An honest, detailed SOV is the fastest way to get pay apps approved without haggling.
Subcontractors use the same tool one level down. A sub's SOV to the GC should match the GC's lines for that trade, or at least roll up into them cleanly. When the two do not line up, the GC has to translate every month, and translation is where short pays and arguments about percent complete start.
The contractor prepares it and submits it to the owner or architect for approval, usually before the first pay application.
Is the schedule of values part of the contract?+
It is often referenced by the contract and required as a submittal, but it is generally a billing tool rather than a pricing commitment for each line. Read your contract to see how it is treated.
Can the schedule of values change during the job?+
Change orders are added as new lines. Reallocating money between original lines usually requires the owner's or architect's approval.
What form is used for a schedule of values?+
On AIA projects, the G703 Continuation Sheet. Many owners and lenders accept a spreadsheet or software report with the same columns.
Justine and Nicole get deep on construction scheduling, the skill that separates profitable contractors from the ones constantly firefighting. They cover scheduling methodologies, common timeline killers, buffer strategies, and how to communicate schedule changes without losing client trust.
Starts muted when the player comes into view.
Read the full episode transcript
Published transcript from Scaling Legends. It may contain transcription errors. View the source transcript.
What if I told you that a single missing $50 city permit like on a Tuesday could cost a commercial construction firm $50 ,000 in lost profit by Friday? Oh, yeah. It happens all the time. Right. It's crazy. Usually, when we look at massive construction sites, our eyes go straight to the physical progress. The tangible stuff. Yeah, exactly. We see the concrete foundation being poured or the steel framing going up against the sky, the heavy machinery moving earth around. It all feels incredibly tangible. Right, because it is the ultimate physical manifestation of work. It's progress you can literally measure with a tape measure or just see from the highway on your morning commute. But then, if you look closely at the project manager's trailer sitting
on the edge of that dirt lot you realize the actual foundation of the entire build isn't concrete at all not even close it's a fragile invisible web of time the schedule and well welcome to this deep dive especially if you were a construction business owner listening right now glad you're here Whether you are scaling a regional firm or managing five active commercial sites or juggling 10 different residential development, today is for you. Absolutely. We're discussing construction industry topics for the Scaling Legends podcast. And our mission today is to really explore why mastering the project schedule is the ultimate core business skill. It's the whole ballgame. It really is. It's the defining line that separates highly profitable contractors from the ones who are just... Well, constantly burning out, putting
out fires. Right, because scheduling is far more than an administrative chore or some chart you print out and pin on a wall. Yeah. It is a rigorous profit protection strategy. I love that phrasing. Thanks. We are going to unpack the mechanics of what goes wrong on these sites and, I mean, more importantly, how to structurally fix those underlying issues. So we can actually grow. Exactly. The goal is to set up an operational architecture that allows a construction business to scale without... drowning in the chaos of overlapping delayed timelines. So before we can fix the schedule, we kind of need to understand the true financial stakes of getting it wrong. Yeah, let's start there. Because if you are managing multiple builds, you know the absolute pain of a cascading delay.
But why is the schedule considered the single most important document on any construction project? Well, fundamentally, it dictates the burn rate of your capital every single day. your company is active on a site you are carrying overhead. Well, heavy overhead. Right. You have heavy equipment rentals, liability insurance, site security, temporary utilities. Don't forget the management team salaries. Yes, all of that. And those fixed costs, they do not pause just because your mechanical contractor got delayed by a supply chain issue. They just keep ticking. Exactly. The longer you are sitting on that site, the more those daily fixed costs eat directly into the profit margin you calculated when you first won the bid. And we have a very stark look at this reality. Smart Business Automator's Market Intelligence Report
breaks down exactly how many days the average project runs over schedule. It's pretty eye -opening. It really is. And it details the heavy financial toll those specific overruns cost a company. When you start calculating the daily carrying cost of a site and then, you know, multiply it by a three -week delay. It gets ugly fast. Right. It stops being a conversation about, oh, we are a few days behind and becomes this terrifying realization of. Wait, we just lost our entire profit margin for this quarter. Precision is the only defense against that margin erosion. I mean, an inaccurate schedule means you are actively bleeding resources. You're paying for time you literally cannot use. It makes me think of, um... A traffic jam on a single lane bridge.
Oh, that's a good way to look at it. Right. Like if one car stalls out right in the middle, it doesn't just stop itself. No, it blocks everybody. Exactly. It backs up the cars immediately behind it and then the intersections behind them until eventually the entire surrounding town is in total gridlock. That stalled car is your delayed commercial build. And the gridlock town represents all your future projects. They cannot break ground. If we connect this to the bigger picture, that single lane bridge analogy perfectly illustrates the nightmare of resource misallocation. Yeah. Because when a major delay happens, a construction firm has to pivot its most valuable assets. You have to pull people from other jobs. Right. You have to pull an experienced superintendent from a brand new, highly profitable site just to go
manage the fallout on the old delayed one. Which is so frustrating. And like you have to extend the tower crane. rental for another month, which means you cannot use that same crane on the new job across town. So you're renting two cranes now. Exactly. You end up paying twice for the exact same slice of time, all while pushing your incoming revenue further down the calendar. It is a brutal cycle to be trapped in. It really is. So now that the financial stakes are crystal clear to anyone running a firm. What are the actual root causes making these schedules fall apart? The underlying issues. Right. We need to move from the symptom, which is hemorrhaging profit, to the disease itself. Well, our materials point to three major timeline killers that show up time and time again across the industry. OK,
leave them on me. The first is optimism bias. The second is the failure to buffer. And the third is ignoring dependencies. Okay, I have to push back on that first one. Go for it. Wait, isn't optimism a required trait for a builder? I mean... Because you have to be an optimist to look at an empty, overgrown dirt lot and see a gleaming 60 -unit apartment complex. Sure, absolutely. That takes immense vision and honestly risk tolerance. Yeah. So why is optimism bias so dangerous when it comes to the schedule? You are touching on a really fascinating paradox in construction leadership. Okay. We absolutely have to separate. leadership optimism from scheduling realism. You need that visionary optimism to win the bid, to secure the financing, and to
inspire your team. Right. You have to sell the dream. Yes. But the moment you sit down to write the operational schedule, you have to become a ruthless pessimist. A ruthless pessimist. Wow. Optimism bias in scheduling means you are subconsciously assuming every single subcontractor will show up exactly on the day they promised. Ah. That the weather will be perfect for 60 straight days and the city inspector will just stamp your permit the second you hand it across the counter. Which has literally never happened once in the history of the construction industry. Not once. Never. Yeah. schedule for the absolute best case scenario, you leave yourself zero margin for reality. Right. And that ties directly into the third killer we mentioned, ignoring dependencies. Because it's a chain reaction. Exactly. Construction
is a highly sequential process. You cannot put the roof on before the walls go up. Obviously. If you ignore the friction between those dependencies, you create a massive domino effect. Let's elevate this beyond just simple sequencing, though. Give me a high stakes example of how that dom Okay. Consider the mechanical, electrical, and plumbing rough ends the MEP phase. Classic bottleneck. Always. Let's say you have a minor delay with your HVAC contractor getting their custom ductwork delivered. Okay. It's just a three -day delay on sheet metal. No big deal, right? Sounds manageable. But because that ductwork isn't installed in the ceiling plenum, the drywall contractors cannot come in to close up the drop ceilings. Right. Right. Because the ceilings aren't closed, the
electricians cannot install the permanent lighting fixtures. And it keeps going. Yep. Because the lighting isn't in and the power isn't fully live, the low -voltage IT contractors cannot pull their fiber optic cables. Wow. A three -day delay on sheet metal just halted four different highly specialized trades and pushed your final occupancy permit back by a whole month. It's terrifying how fast it cascades. Yeah, it really is. The dependencies are so tightly woven that pulling one thread unravels the entire month. Exactly. If blind optimism and poor buffer planning are the core problems, what is the structural solution? Like, let's pivot to the actual frameworks used to build bulletproof timelines. Well, it really comes down to two primary methodologies that must be used in tandem. Right. The critical path
method and look ahead scheduling. The critical path method, or CPM, is essentially the macro view of the project, right? Right. It calculates the longest sequence of dependent tasks. But it seems to me the critical path isn't just a sequence. It's essentially... A tripwire. That's a great word for it. Because if your foundation pour is delayed by a single day, your final completion date moves back by a single day. Exactly. But if the exterior landscaping is delayed by two weeks, the completion date doesn't move at all. Right, because it's not on the critical path. The real aha moment for a business owner is realizing that 80 % of the tasks on a job site don't actually dictate the finish line. That is the exact strategic value of the CPM. 20 % of tasks that act as that
trick wire. So you focus all your energy there. You pour your management energy, your best personnel, and your contingency funds into protecting the critical path. The landscaping can wait. The elevator shaft construction cannot. Okay, so the CPM is the map for the entire journey. What about look -ahead scheduling? Look -ahead scheduling is the headlights on the car. Ooh, I like that. It is a micro view, usually a three to six week rolling window where the superintendent and project manager sit down and look exclusively at the immediate horizon. Just what's right in front of them. Right. They are not worrying about the roof installation if they are currently pouring the second floor slab. Yeah, that would be a waste of time. They are looking at the next month and asking very specific logistical questions
like, are the specific curtain wall materials physically in the local warehouse? Right. Are the framing crews confirmed for next? Tuesday, is the site prepped for the crane arrival. Getting into the weeds. Exactly. It translates the giant abstract CPM into actionable weekly operational steps. Okay, let's unpack this concept of building realistic buffers because that is where the magic seems to happen. It is crucial. We have these uncontrollable elements, right? Severe weather, supply chain shocks, city inspections. You have to build in time for them. You have to. It makes me think of a surge tank in a commercial plumbing system. Oh, interesting. Like if the water pressure spikes and rushes in too fast, the tank catches the excess volume so the pipes don't burst downstream.
It keeps the output pressure steady. A schedule buffer does the exact same thing for time variance. It absorbs the shock so the schedule doesn't burst. A surge tank is the perfect mechanical analogy. A buffer is strategically placed white space in your schedule to absorb the impact of the unexpected. Right. But the crucial distinction is where you place that tank. Okay, where do you place it? If you expect a concrete pour to take three days, you don't tell the queue they have five days. Right, right. Schedule it for three, but you don't schedule the next critical dependent task until day six. Ah, because if you just inflate the duration of every single task, Parkinson's law takes over. Exactly. The work will naturally expand to fill the time allotted. Right. If you give a crew five days to do a three
-day job, it will absolutely take them five days. Every time. And worse, if you artificially inflate the overall project duration to be super safe, you're going to lose the bid to a competitor who promises the developer a faster turnaround. That's the tightrope you walk. You have to place the buffers at the end of critical phases, aggregating the risk rather than padding individual tasks. That makes a lot of sense. And the financial impact of doing this correctly is staggering. Smart Business Automator's Market Intelligence Report clearly outlines how scheduling accuracy dramatically impacts project margins when these strategic aggregated buffers are used correctly. Wow. Yeah. Protecting your timeline with calculated buffers actually protects your profit margin just as effectively as negotiating cheaper materials.
That's incredible. But, you know, a perfect schedule on a spreadsheet is a beautiful thing. Sure is. But it rarely survives contact with reality. And reality in construction means dealing with other human beings. Ah, yes, the human element. Our materials highlight subcontractor coordination as the single biggest scheduling challenge that causes delays. It is arguably the hardest part of a general contractor's job. Really? Oh, yeah. You are relying on dozens of independent companies, all of whom have their own internal schedules. Right. Their own supply chain delays and their own severe labor shortages. They're fighting their own fires. Exactly. If your primary framing subcontractor is running two weeks late on a different developer's job across town, they simply do not show up to yours. It seems to me that
dictating a schedule from a trailer is doomed to fail then. because you have zero visibility into the trade's internal bottlenecks. None at all. Do successful managers force the trades to build the schedule with them? They do, using a methodology called pool planning. Pool planning, okay. It is a form of highly collaborative scheduling with trade partners. Instead of the general contractor sitting in the trailer and dictating the schedule downward. You know, emailing a spreadsheet and saying, you will be here on Tuesday. They bring the foreman of all the key subcontractors into a single room. I love the mechanics of this. It's like reverse engineering a bank heist. A bank heist. I like that. Right. Because you don't start at the beginning of the plan. You start at the vault. You look at the final objective and you work backward to figure out exactly when
the getaway driver needs to have the engine running and when the safecracker needs to be drilling the lock based on their own specific constraints. That is exactly how it works. In pool planning, you start with the physical milestone. Okay. Let's say the milestone is drywall complete on floor three. You work backward and ask the drywall foreman, what do you need from the electrical foreman before you can start? Oh, I see. And the electrician says, I need three days of uninterrupted access to the metal studs to run my conduit. So they figure it out together. The trades negotiate the handoffs directly with each other. It creates mutual accountability. Because they made the promise to each other. Exactly. Because the electrician just promised that timeline directly to the drywaller standing right next to him, not just to the general contractor. That shifts the entire dynamic from
top -down compliance to peer -to -peer commitment. It's a game changer. But the subcontractors are only half of the human element. The other half is the client, right? The developer or the owner. Yes, the ones writing the checks. Exactly. Communicating schedule changes to clients is a delicate art. How do you manage that relationship in a way that actually maintains trust when things go wrong? Well, what's fascinating here is understanding the psychology of the developer. Client trust is not actually lost because of a delay. Really? Trust is lost because of a surprise. That is a massive distinction. It's not the delay itself. It's the shock of the surprise. Construction clients, especially developers, are sophisticated. Right. They get it. They understand that severe weather happens. They read the news. They know
supply chains get backed up. They have their own investors and bridge loans to manage. A delay they know about two months in advance can be managed financially. Right. What they will not tolerate is finding out about a three -week delay two days before they expected the handover. Proactive communication is everything. So if you see a supply chain bottleneck forming with, say, the custom windows, you call the client immediately and say, hey, we are tracking a shipping delay that might push our building envelope closure back by a few weeks. Exactly. We are monitoring it and we'll keep you updated. You manage the expectation while the problem is still a possibility, not a crisis. Yes. And when you do have to deliver definitive bad news, you never deliver a problem without simultaneously delivering the architectural
solution. That's smart. You don't just say the windows are late. You say the custom windows are delayed in shipping by two weeks. However, we have re -sequenced the interior framing and rough -ins to happen concurrently in the unaffected zones, so the overall project completion date will only be pushed by three days instead of 14. Wow. You prove to them that you are still steering the ship, even if the wind completely changed direction. Exactly. You stay in control. But here is the breaking point for me. If a project manager is spending 15 hours a week just calling trades to update them on that single window delay and constantly adjusting spreadsheets manually, they don't have the bandwidth to look ahead. No, they don't. They are trapped in the present just acting as a human router for bad news. Is
that where the technology actually steps in? That is exactly the operational bottleneck that modern technology solves. The foundational human process is the weekly schedule review, right? It's a highly focused meeting with the field team and the office team to look at the data. But to make that meeting effective, you need instant, accurate data. Which you don't usually have. Right. You cannot rely on a superintendent trying to remember what happened three days ago. Yeah, that's a recipe for disaster. So the technical capabilities available to contractors right now are fundamentally changing how that data is processed. But let's look at the actual mechanism of how this works, moving beyond just like digital calendars or cloud storage. Take the request for information, the RFI process, as a prime example of this mechanical
shift. Okay, RFIs are notoriously painful. Historically, a project manager spends hours drafting a complex question for the architect because they have to hunt down all the context across... Dozens of files. Digging through PDFs. Right. Modern systems change the physics of that workflow. The AI actively scans the 400 -page architectural spec document, cross -references it with the specific dimensions logged in yesterday's digital field report, and auto -populates a draft RFI that includes the exact building code clause in question. It's doing all the heavy lifting of the cognitive administration. It extracts the data so the human doesn't have to hunt for it. Exactly. And it also revolutionizes the daily logs. How so? Well, superintendents are exhausted at the end of a shift, right? Yeah, they just
want to go home. Exactly. So their manual logs are often brief and lack detail. Modern tools use voice -to -text and field photos to capture the raw, messy reality of the site, and the AI synthesizes that into clear summaries. That's brilliant. it correlates the specific labor hours logged against the daily progress. If the AI can correlate labor hours against daily progress, then the most powerful part of this tech stack has to be the schedule risk detection. Oh, absolutely. It isn't just recording history. It's projecting the future. That is the ultimate paradigm shift. You transition from reactive paper chasing to proactive risk detection. The AI ingests the critical path schedule, reads the daily field logs, and notices that, hey, the concrete crew
has been 10 % slower than estimated for three consecutive days so it spots the trend it instantly flags that the major milestone two weeks out is now at high risk wow it identifies budget variances and cost movement early giving the project manager the exact data they need to intervene before the delay actually happens and when a client asks for a sudden change like you know moving a demising wall in the commercial fit out the software performs a change order impact analysis right it evaluates exactly how that specific change will disrupt the dependencies we talked about earlier calculating the impact on both the timeline and the cost so you can communicate that clearly to the stakeholder before they even approve it. Yes. It connects the field to the office without all the friction of manual data entry. It allows project managers to handle
significantly more volume because they are no longer buried in administrative busywork. Right. They can actually manage. You're managing the physical build, analyzing the AI's risk reports, and leading their teams rather than managing endless paperwork. So what does this all mean? It directly enables a construction company to scale its operations without linearly scaling its administrative headcount. It aligns everyone seamlessly. That's the dream. It really is. To recap our journey today, the schedule is not just an administrative chart on the wall. It is the absolute heartbeat of your profitability. By overcoming the natural optimism bias, building in strategic surge tank buffers, communicating proactively with your developers and trades, and leveraging modern AI workflows to detect
risk, protect your margins. And honestly, you protect your sanity. And that raises one final important question to leave you with. If modern technology can already intelligently predict your schedule risks and budget variances before you even step foot on the site, What other gut feelings or human intuition in the construction industry are actually just complex pattern recognition that AI will master tomorrow? Food for thought. If you enjoy this deep dive on scaling legends, make sure to subscribe, rate, and review the show on your preferred listening platform. Share this episode with colleagues, your project managers, or your operational team who would benefit from the discussion, and be sure to visit smartbusinessautomator .com.
