Straight into the service manual page
WrenchQuarry
More

3 items a schedule of values must show for a multi-visit job

WrenchQuarry Editorial Team · Published · 16 min read · How these guides are written

The answer: three items every schedule of values must show

The federal clause sets three things a schedule of values for a multi-visit job should show: a value for each major activity needed to finish the work, all direct and indirect costs built into those values, and enough detail that the person paying can check each payment request. The federal construction clause GSA 552.236-15, Schedules for Construction Contracts sets out those same requirements and adds rules on how activities are sized and timed.

Required itemWhat the payer asksClause basis
A value for each major activityWhat is being paid for?Assigning values to each major activity necessary to complete the work
All direct and indirect costs in those valuesWhether the total is completeValues must include all direct and indirect costs
Enough detail to check each paymentWhether a specific payment can be verifiedSufficient detail to enable the Contracting Officer to evaluate applications for payment

The clause is written for federal construction contracts, so it does not govern a repair invoice or a residential install by its own force. Its logic still fits any job billed in parts, because a multi-visit bill is only as useful as the lines it is built from. Each of the three items answers a different question a payer will ask. The first asks what is being paid for. The second asks whether the total is complete. The third asks whether a specific payment can be verified. The sections below take each item in turn, then cover the rules on activity size and duration that sit alongside them.

Assigning a value to each major activity

The clause requires the contractor to prepare and submit for approval a cost breakdown of the contract price, called the schedule of values, assigning values to each major activity necessary to complete the work. The phrase that matters most is "necessary to complete the work." A line belongs on the schedule because the job cannot be finished without it, not because it is a convenient place to park money.

For a multi-visit job, the visits usually map onto the activities. A three-visit equipment replacement might break into removal of the old unit, setting and connecting the new unit, and startup and testing, with a separate line for any closeout work such as final cleaning or documentation. Each line gets its own value, and the values together make up the agreed price of the job. If the lines do not add back to the total you quoted, the breakdown is not doing its job.

The clause also treats the schedule as something submitted for approval, not something the contractor simply keeps internally. That means the breakdown should go to the client or their representative before the first visit, while the job is still being scoped. Agreeing on the lines early makes later billing disputes easier to avoid, because both sides have already accepted what each line represents.

Major activities are the units of the schedule, not every small task on the job. Listing each fastener or each trip to the supply house would bloat the schedule without helping anyone evaluate progress. The useful level is the one where a completed activity is clearly visible to someone walking the site.

Putting direct and indirect costs into every line

The clause states that values must include all direct and indirect costs, although a separate value for bond costs may be established. That sentence sets a completeness test. Every value on the schedule has to carry the full cost of the work it describes, not just the part you find easy to attribute.

Direct costs are the ones you can tie to a specific activity: the technician's labor on a given visit, the materials installed that day, and the equipment used for that task. Indirect costs are the shared expenses that keep the business running across all the visits, such as office time, insurance, vehicle upkeep, and general supervision. These are harder to assign, and that is where many schedules quietly leak money. If the indirect costs are left out of every line, the schedule totals less than the job actually costs, and the shortfall shows up as an uncovered expense at the end.

The clause gives a specific option for bond costs. They may be shown as a separate value, which keeps them visible and easy to check. If you do not break them out, they still have to be captured somewhere in the schedule, because the completeness rule applies to all costs. The choice is about presentation, not about whether the cost counts.

The practical method is to spread each indirect cost across the activities it supports, using a basis you can explain if asked. You do not need a complex allocation model. You need a method consistent enough that the same kind of cost lands in the same kind of line from visit to visit, and that the totals reconcile back to what the job actually costs you.

Detail enough to check each payment request

The clause says the schedule of values must contain sufficient detail to enable the Contracting Officer to evaluate applications for payment. On a private job, the equivalent reviewer is the client, a property manager, or whoever signs off on the bill. The test is the same: can that person look at a payment request and see what work it pays for?

Sufficient detail means a line describes the work in terms that can be checked against what happened on site. A line that says only "Phase 2 complete" tells the reviewer almost nothing. A line that names the work completed, such as the connection of supply and return lines and the pressure test on the new system, gives the reviewer something specific to confirm. The description should match the way the work is actually done and inspected.

This is also where the schedule earns its keep across several visits. When each payment request points to lines that were defined before work started, the reviewer is comparing the bill to an agreed plan rather than arguing about what counts as done. Disputes shrink when both sides can point to the same wording.

Detail is not the same as length. A schedule can be exact and still short. The goal is that every line passes the same check: a person who was not present can read it, match it to completed work, and approve the amount without asking the billing office to explain it.

Limiting each activity to a sensible duration

The clause adds that activities shall be sufficiently detailed and limited in duration so that the work can be planned and coordinated, the reasonableness and realism of the schedule can be evaluated, progress can be monitored accurately, and schedule impacts can be analyzed reliably. Detail and duration are treated together. A long, vague activity is hard to plan around and nearly impossible to measure while it is underway.

The table below compares the two rules that govern how an activity is sized: the detail-and-duration rule just quoted, and the rule on how durations are set, which is covered in the next section. Each is measured against the same three questions.

MeasureDetail and duration limitDuration basis
What it governsHow detailed each activity is and how long it lastsHow long each activity is expected to take
What it must supportPlanning, coordination, monitoring of progress, and evaluation of whether the schedule is realisticResources and site conditions are accounted for, not assumed away
What it must allowReliable analysis of schedule impactsResources and site conditions are accounted for, not assumed away

In practice, this means a multi-visit job should be split so that each activity can start and finish within a stretch you can monitor. If a single line runs across three visits with no visible milestone, you cannot tell on the second visit whether the job is on track. Splitting it into a removal activity and a set-and-connect activity gives you two checkpoints where progress and delay become visible. When a delay happens, you can see which activity it touched, which is what an impact analysis needs.

Basing durations on real resources and site limits

The clause requires that activity durations shall be based upon reasonable and realistic allocation of the resources required to complete each activity, given physical and logistical constraints on the performance of the work. This ties the schedule to the actual conditions of the job rather than to an optimistic estimate written on the day of signing.

Resources means the people, equipment, and specialist trades an activity needs. A removal that requires two technicians and a lift cannot be given a duration that assumes one technician with a hand truck. The duration has to reflect the crew you can realistically field for that activity. If the crew is shared across several jobs, the allocation should reflect the time they can give this one.

Constraints are the conditions that limit how fast the work can move. Physical constraints include access to the work area, tight spaces, and the need to shut down a system before work can begin. Logistical constraints include the delivery of parts, the timing of inspections, and the hours when the building or site can be entered. A duration that ignores these is not realistic, even if the crew is capable of the work in a vacuum.

Writing constraints into the schedule also protects the billing. If a visit runs long because of a condition that was noted in the duration basis, the reviewer can see that the delay was foreseeable and planned for. If the same delay was not anticipated at all, the schedule makes that visible too, which is exactly what the clause is designed to allow.


Recording a mutually agreed suspension of time

Multi-visit jobs sometimes stop for reasons that may be outside either side's control or chosen by one party: a part is backordered, a building closes for a holiday, or the client asks to hold the work for a few weeks. How that pause is recorded matters, because the time it covers affects how the remaining lines are planned and billed. It describes a suspension of time to participate as "a mutually agreed suspension of time," and ties that wording to a defined term: the "working day" definition 2.2.3 in Section 1-1.07B, "Glossary," of the Standard Specifications.

Two features of that wording carry over to a private job. First, the suspension is mutual. Neither party declares it alone, because both sides agree to it. Second, the term points to a named definition, so the parties are not left to guess what the pause covers. A pause agreed on the phone and never written down is mutual but has no named definition behind it.

The quote does not spell out a billing effect, and it comes from a state transportation manual, not a rule for residential or commercial repair work. What it does show is a discipline worth copying. When a job pauses by agreement, write down that it was agreed, the dates it covers, and which definition of time the schedule uses. Then the lines on either side of the pause can be read against the same record. Your contract decides what a pause means for payment. The schedule should make the pause visible enough that the decision is easy to make.

Monthly estimates until the final payment

Texas Department of Transportation guidance on estimates gives a plain cadence: "Continue generating estimates monthly until the final estimate/payment is generated." The instruction is short, but it offers two things a multi-visit job can borrow: a regular rhythm and a defined end point. Estimates keep coming on a set schedule until the one that closes out payment is issued.

For an install or repair billed across several visits, a monthly estimate works as a checkpoint. At the end of each month, the office compiles the lines completed to date, matches them to the schedule of values, and issues an estimate for that period. The client sees progress against agreed lines, not one large bill at the end or a loose invoice whenever a visit happens to close. Because each estimate ties back to the schedule, the reviewer can compare it with the previous one and see what was added.

The cadence also prevents a common drift, where work continues for months while the paperwork waits for a finish line. Monthly estimates keep billing moving alongside the work. They run until "the final estimate/payment is generated," so the series has a defined last item, and the office knows when it is complete.

The quote comes from a highway agency's manual, so treat the monthly interval as one model rather than a requirement for your trade. A job that finishes in two visits may need no monthly estimate at all, while a job that runs across a season likely does. The principle that carries over is a regular interval with a clear last issue.

The acceptance-date progress estimate

The second TxDOT quote describes a different kind of estimate: "A progress estimate can be generated through the acceptance date paying the mobilization, any remaining barricades, and any final quantity adjustment items (if applicable)." Read closely, it defines the scope of one estimate. It runs through the acceptance date, the point when the work is accepted, and it can pay three kinds of items: mobilization, remaining barricades, and final quantity adjustments.

Acceptance is the moment the owner or client formally agrees the work is complete enough to close out. For a multi-visit job, that is usually the walk-through after the last visit, the sign-off on testing, or the client's written acceptance of the finished install. The schedule of values should name that event so the estimate has a fixed boundary. Without a named acceptance date, "the end" becomes a matter of argument, and the closing estimate can sprawl.

The estimate also covers items that surround the work as well as the work itself. Mobilization is the cost of getting resources to the site and setting up. Remaining barricades are protective items still in place near the end. Final quantity adjustments true up the quantities actually used against those planned. Each is easy to forget while attention stays on the main activities, which is why the quote names them.

The phrase "if applicable" matters. A given job may have no barricades and no quantity adjustments, and the closing estimate then covers only what remains. Decide in advance which closing items apply to your work and list them on the schedule, so the acceptance-date estimate is a short, checkable bill.

Monthly and acceptance-date estimates side by side

The two TxDOT quotes describe estimate types that can work together rather than compete. The table combines the quoted facts with illustrative job scenarios and one reading of the two quotes.

Estimate typeCadence or timingClosing behavior
Monthly estimateEach month during the workContinues until the final estimate/payment is generated
Acceptance-date progress estimateThrough the acceptance datePays mobilization, remaining barricades, and final quantity adjustment items (if applicable)
Combined sequence (author's reading)Monthly during work, one at the endClosing estimate has a fixed boundary at the named acceptance event
Job finishing in two visits (illustration)Monthly interval may not applyAn acceptance-date estimate may close the job
Job running across a seasonMonthly interval fitsSeries ends at the final estimate/payment
Estimate typeWhen it is generatedWhat the source says it covers
Monthly estimateEach month, continuing until the final estimate/payment is generatedA recurring cadence; the quote does not list line items
Acceptance-date progress estimateGenerated through the acceptance dateMobilization, any remaining barricades, and any final quantity adjustment items (if applicable)

Pick one for each stage of the job. If the work proceeds in visits with no fixed finish, the monthly cadence fits, because it keeps billing tied to progress. If the work ends with a defined acceptance point, the acceptance-date estimate fits the closing bill.

One reading of the two quotes is monthly estimates during the work followed by one acceptance-date estimate at the end. That sequence is a reasonable reading of both quotes, though the sources do not present it as a single procedure. Fill each table row with the lines from your own schedule of values, so every estimate can be traced to agreed wording.

Final quantity adjustments on the closing bill

The closing estimate in the TxDOT quote includes "any final quantity adjustment items (if applicable)." A quantity adjustment matches the billed amount to the quantity actually used or installed, rather than the quantity assumed when the schedule was written. Estimates made in advance rest on assumptions about material runs, fittings, or hours, and the final figure may differ.

Closing item named in the quotePlain meaning for a multi-visit jobCondition in the quote
MobilizationCost of bringing crew and equipment to site and setting upPaid through the acceptance date
Remaining barricadesProtective or site-control items still in place at the endPaid through the acceptance date, if any remain
Final quantity adjustmentsTrue-up of billed quantities to what was actually usedMarked "if applicable"

The plain meanings above are general descriptions, not definitions from the source. Write each adjustment as its own line so the reviewer can see it is a correction, not new scope. Reference the original schedule line each adjustment corrects, so the change can be traced. If adjustments are consistently large, the schedule's assumptions probably need review before the next job.

Using the rules on a real bill

Start with the schedule before the first visit. Write each major activity as a line with a value, and confirm the values add up to the price the client agreed to. The GSA clause treats the schedule as something submitted for approval, so the lines should be in front of the client before billing begins. Any later change to a line should be recorded in writing rather than made quietly on an invoice.

Next, check each line against the cost test. Ask whether the value carries the labor, materials, and equipment for that activity, plus its share of indirect costs such as office time, insurance, and vehicle upkeep. If a bond cost is shown as its own value, confirm it is there. If it is not shown separately, confirm it is still captured somewhere in the totals. A schedule that passes the detail test but leaves out indirect costs will still lose money on the job.

Then test the wording. Before a monthly estimate goes out, read each line and ask whether someone who never visited the site could match it to finished work. Lines that name the completed step, such as the connection of supply and return lines or the pressure test on the new system, are easier to approve. Lines that name only a phase or a vague stage are not.

For durations, compare what the schedule assumed against what happened. If a visit ran long, check whether the delay came from a condition the duration basis already recorded, such as site access, shutdown timing, or a part delivery. A foreseeable delay is easier to explain than one that was not. Because the GSA clause ties durations to the resources and constraints of the job, an unexplained overrun is also a signal that the duration basis needs updating for the next job.

Finally, close the job with one clearly named acceptance event. Write the acceptance date into the agreement and into the schedule, so the closing estimate has a fixed boundary. Then list any closing items that apply: mobilization, remaining barricades, and final quantity adjustments. Mark the items that do not apply as not applicable, so the closing bill stays short and checkable, and the client can see that nothing was left out.

Related guides: Backing 5% VAT out of a £483 price before a job is billed · Job-cost comparisons: 3 checks across periods · Credit sale dates: 2 dates to record for each job.

Sources

More field guides