Straight into the service manual page
WrenchQuarry
More

3 duration requirements to set before a job enters the queue

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

Before a job enters the queue, set three duration requirements: each activity's length must rest on a realistic allocation of the resources it needs, each activity must be detailed enough to monitor, and, where the owner's payment process sets a calendar rule such as the Texas FIN progress estimate, the payment period must line up with that calendar. The first requirement comes from the General Services Administration's construction schedule clause, which says activity durations must be based on a reasonable and realistic allocation of resources, given physical and logistical constraints on the work (GSA).

Net takeaways

  • Build every activity's duration from the resources it needs and the physical and logistical limits on the work, not from the date you want to promise.
  • Check the payment calendar before you set dates, because a state payment process can require a progress estimate's period end date to fall in the previous month (Texas Department of Transportation).
  • Expect payment to follow approved estimates of completed work, as Minnesota's statute provides (Minnesota Revisor of Statutes).
  • Make each activity detailed enough to track progress, because a vague duration hides slippage until the promised time is already at risk.

The critical path schedule you must set

The first requirement starts with the scheduling method itself. The General Services Administration's construction clause states that "the Contractor shall use a critical path method project schedule to plan, coordinate, and perform the construction phase work" (GSA). In plain terms, a critical path method schedule links activities so that each one waits on the ones before it. The chain of linked activities that sets the earliest finish date is the critical path.

For a dispatcher, this changes what a promised time means. The time is the end of a chain, not a standalone number. If one activity on that chain is given too short a duration, every later activity inherits the error, and the promise moves with it. A job that looks comfortable as a single line on the day's queue can run late because a predecessor was underestimated several steps earlier.

That is why durations have to be set before the job is queued, not corrected afterward. The clause treats the schedule as the tool used to plan, coordinate, and perform the work. The same document that tells the crew what comes next should also show when the last link finishes. If the schedule is only a list of tasks with no links between them, it cannot tell you which delay matters, and you will learn about the problem only when the crew reaches it.

Once the chain is linked, the critical path tells you where a change in duration will move the finish. Activities off that path have some slack, while activities on it do not. A dispatcher who knows which links are critical knows which durations deserve the most careful estimates before the time goes into the queue.

Comparing the three rules side by side

The three requirements meet at the point where a schedule becomes payment. Texas and Minnesota show what the payment side looks like, and the table below sets their rules next to each other on the same measures.

MeasureTxDOT progress supplemental estimate (FIN)TxDOT semi-final estimateMinnesota payment basis
What it governsProcessing payments through FINEstimate tied to project acceptancePayments
Timing conditionPeriod end date falls in the previous monthNot generated when acceptance is close to the regular cut-off dateWork completed, as approved
What it is measured againstThe progress supplemental estimate's period end date falling in the previous monthThe regular month's estimate cut-off dateEstimates of work completed

The Texas progress rule sets a specific calendar condition on the period end date. For payments to be processed by FIN, the period end date of the progress supplemental estimate must be in the previous month (Texas Department of Transportation). A dispatcher who sets a completion date without checking this calendar can finish work in one month while its estimate lands in the wrong period.

The Texas semi-final rule works differently. It is a warning against generating an estimate too close to the end of a cycle. If the acceptance date is close to the end of the regular month's estimate cut-off date, the semi-final estimate should not be generated (Texas Department of Transportation). The duration question here is whether acceptance can be scheduled comfortably away from the cut-off.

The Minnesota rule sets the basis rather than the calendar. Payments shall be based upon estimates of work completed as approved by the public contracting agency (Minnesota Revisor of Statutes). Read side by side, the Texas and Minnesota rules show that a payment date depends on two things at once: when the work is actually done and approved, and which period the estimate falls in. Both must be planned in the same duration.

What the construction schedule must include

Durations cover more than the work crews do in the field. The construction phase schedule must depict all activities necessary to complete the work, including, as applicable, all submittal and submittal review activities, all procurement activities, and all field activities, including mobilization, construction, start-up, testing, balancing, commissioning, and punchlist (GSA). The table below groups the items the clause names by category.

Activity categoryItems named in the clause
Submittal activitiesSubmittal and submittal review activities
Procurement activitiesProcurement activities
Field activitiesMobilization, construction, start-up, testing, balancing, commissioning, punchlist

Most of the named items are field activities, which is the category dispatchers usually see. The other categories sit upstream and downstream of the crew. Submittals and their reviews must happen before the materials can be ordered, and procurement must happen before the field work that uses those materials. A promised time that counts only the field activities leaves out much of the scheduled work.

The clause also covers the end of the job. Startup, testing, balancing, commissioning, and punchlist all appear in the list. These tend to be the activities that stretch a finish date, because they depend on inspections, equipment readiness, and corrections. Giving them a realistic duration, rather than a single bare day at the end, keeps the queue promise honest.

The phrase "as applicable" matters. Not every job has every category, and the schedule should reflect the ones that do. A dispatcher should not add submittal or procurement activities out of habit, but should confirm which categories the job actually requires before setting its duration.

How detailed each activity must be

The clause does not stop at listing activities. It also says how they must be written. Activities shall be sufficiently detailed and limited in duration to enable proper planning and coordination of the work, effective evaluation of the reasonableness and realism of the project schedule, accurate monitoring of progress, and reliable analysis of schedule impacts (GSA). That sentence sets two limits at once. An activity must be detailed enough to be meaningful, and it must be short enough to be checked.

The table below lists the four purposes the clause names.

Purpose named in the clauseWhy it matters for the queue
Planning and coordination of the work (1 of 4)Crews and suppliers can only be scheduled against activities they can recognize
Evaluating reasonableness and realism of the schedule (2 of 4)A reviewer can judge whether a duration is believable
Accurate monitoring of progress (3 of 4)A long, vague activity shows no progress until it ends
Reliable analysis of schedule impacts (4 of 4)A delay can be traced to a specific activity only if the activity is specific

The limit on duration is the part dispatchers often miss. A single activity that runs for weeks tells you little about where you stand. If the crew is halfway through it, the schedule still reads as one unchanged block. Breaking long work into shorter activities gives you checkpoints, and checkpoints are what let you see a slip before the promised time arrives.

Detail also works in the other direction. An activity that is too fine-grained adds administrative weight without helping the decision. The clause asks for detail sufficient for planning and coordination, evaluation of reasonableness and realism, accurate monitoring of progress, and reliable analysis of schedule impacts. The right level is the one at which a late finish can be traced to a single named activity.

Setting durations from real resources

The clause gives the rule for the number itself. 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 (GSA). A duration is therefore a result of resources and constraints, not a figure chosen to fit a date already promised.

The table below breaks that sentence into the inputs it names.

Input named in the clauseNumber of inputs namedHow it shapes the duration
Resources required to complete each activity1The crew, equipment, and materials the activity actually needs
Physical constraints on the performance of the work1Conditions at the site that limit how quickly the work can proceed
Logistical constraints on the performance of the work1Access, delivery, sequencing, and scheduling limits that affect timing
Total inputs3All three must be considered together

Reading the rule this way prevents a common error. A dispatcher can set a duration by asking how long the work should take in an ideal case. The clause asks a different question: what resources will this specific activity have, and what physical and logistical limits will it face? A duration built from the second question is harder to shorten on paper, because each reduction must be matched by a resource or a constraint that changes.

As a practice rule, apply the same thinking to the whole queue. If several jobs draw on the same crew or equipment, each job's durations must reflect the share of those resources it can actually receive. A duration that assumes full access to a crew already committed elsewhere is not a realistic allocation, even if it looks reasonable on one job's schedule. Setting durations this way is what makes the promised time something the crew can keep.

Expecting the schedule to be revised

The General Services Administration's construction clause includes a sentence that is easy to skim past: "The Contractor should anticipate that the project schedule will be subject to review and may require revision" (GSA). For a dispatcher, the practical point is that the schedule you hand over is a working document, not a final verdict.

This matters for durations because a duration set before a job enters the queue is an estimate built from the resources and constraints you knew at the time. Some of those inputs will change. A crew may be pulled to another job, a delivery may arrive late, or a site condition may slow the work. The clause expects the schedule to be examined and, where needed, changed.

Planning for revision does not mean padding every activity. It means treating the first queue time as provisional. Keep the version of the schedule that produced the original promise, so you can see what changed later and why. When you revise a duration, record the input that moved it, whether that was a resource, a physical condition, or a logistical limit. A revision with a stated cause is much easier to explain to an owner than a time that simply moved without explanation.

Expecting review also argues for checking the schedule against actual progress regularly. If you know the plan will be examined, you should examine it yourself before problems grow. Waiting until the promised time is close leaves little room to adjust.

Matching the payment period to the calendar

Some payment rules depend on dates as well as on the work itself. The Texas Department of Transportation's measurement and payment manual sets a clear requirement for progress supplemental estimates: "For payments to be processed by FIN, the period end date of the progress supplemental estimate must be in the previous month" (Texas Department of Transportation).

For scheduling, this means the calendar belongs in the duration decision. A completion date can look correct on the crew's plan and still produce an estimate that falls in the wrong period. Before you promise a time, identify which month the estimate's period end date will land in, and if the payment runs through FIN, confirm that the period end date satisfies the previous-month requirement.

The rule is stated for payments processed by FIN. If your owner's payments do not run through that process, this quote does not set your dates, and you should check the rules that apply to your own agency. Do not assume a Texas calendar requirement applies to every job you queue.

In practice, build the calendar check into the queue entry itself. Record the period end date on the job record and treat it as a fixed constraint when you set the durations of the final activities. The field work may be ready to finish on a particular day, but, for FIN-processed payments, the period the estimate falls in governs when payment is processed. Making that link visible keeps the owner's expectations about payment aligned with the schedule's dates.

When a semi-final estimate is wrong

The same Texas section warns against a specific mistake near the end of a job. It says: "If the acceptance date of the project is close to the end of your regular month's estimate cut-off date, do not generate a 'Semi-Final' estimate" (Texas Department of Transportation).

The mistake is generating a semi-final estimate when the acceptance date sits close to the regular cut-off. The quote does not define how close is close enough to trigger the warning, so a dispatcher should not guess. Compare the planned acceptance date with the regular month's cut-off, and if the two are near each other, treat the semi-final estimate as unavailable for that cycle.

This affects the duration decision directly. If acceptance is scheduled for the final days before a cut-off, the completion chain may need to move, or the promised time must account for the next cycle. A dispatcher who sets an acceptance date without checking the cut-off has not finished the job's schedule, even if every field activity is complete.

Acceptance is the event that anchors the final stretch. Activities such as testing, commissioning, and punchlist, which the GSA clause lists in the construction phase, usually come before acceptance. Their durations therefore decide whether acceptance lands near a cut-off. Setting those activities with realistic lengths gives you room to choose an acceptance date that does not collide with the estimate cycle.

How payments follow completed work

Minnesota's statute approaches payment from a different angle. Its rule is that "payments shall be based upon estimates of work completed as approved by the public contracting agency" (Minnesota Revisor of Statutes). The trigger is the completed work and the approval of an estimate of that work, not the date on the queue.

This changes what a finish date means for the owner. A job can be physically done on the planned day and still depend on an estimate of that completed work being approved before payment follows. The schedule should show when work is complete, and the plan should leave room for the time needed to prepare and approve the estimate. Keep these two things distinct on the job record, so that a finished crew is never mistaken for a paid job.

The quote also shows a sequence. Work is completed first, an estimate is built from it, and the public contracting agency approves that estimate. Each step depends on the one before. A duration set without room for preparing and approving the estimate assumes payment arrives the same day the work ends, and the statute does not describe that arrangement.

The practical habit is to record completed work in terms an estimate can reflect. When a crew finishes a phase, note what was done, so the estimate later describes the same work the schedule shows. Clear records make the estimate easier to check and approve.

Which one should you pick?

These three rules are not really competing options. Each answers a different question, and a single job can face more than one of them. Still, when a dispatcher must decide which requirement to check first before entering a job in the queue, the answer depends on how the owner pays.

OptionRule it draws onQuestion to answer before queueing
Check the payment calendarTexas progress supplemental estimate ruleWill the estimate's period end date fall in the previous month?
Check acceptance against the cut-offTexas semi-final estimate ruleIs the planned acceptance date close to the regular cut-off?
Plan for approved completed workMinnesota payment basisWill the estimate of completed work be ready for agency approval?

If payments run through FIN, check the calendar first, because the Texas manual makes the previous-month period end date a condition for processing (Texas Department of Transportation). If the agency pays on approved estimates of completed work, as Minnesota's statute provides (Minnesota Revisor of Statutes), plan the completed-work record and the approval window first. Where both kinds of rule apply, check both, starting with whichever constraint lands earliest in the schedule. Choosing by convenience is the wrong basis, because a missed calendar or approval date is what turns a finished job into a late payment.

Related guides: Set a job priority before dispatch: 3 fields · Job site dispatch: 3 checks before crews leave · Backing 5% VAT out of a £483 price before a job is billed.

Reader questions

Does every progress estimate in Texas have to end in the previous month? Not according to the quote. The requirement applies to payments processed by FIN. For those payments, the period end date of the progress supplemental estimate must be in the previous month (Texas Department of Transportation).

Should I generate a semi-final estimate if acceptance is near the cut-off? The Texas manual says not to when the acceptance date is close to the end of the regular month's estimate cut-off date (Texas Department of Transportation). The quote does not define "close," so compare the dates on your own job.

What decides payment under the Minnesota rule? Payments are based upon estimates of work completed as approved by the public contracting agency (Minnesota Revisor of Statutes). The queue date does not appear in that rule.

If the work finishes on schedule, will I be paid that day? The Minnesota basis does not say so. Payment follows an estimate of completed work that the agency approves, so the approval step needs time in your plan.

Do the Texas rules apply to every project I queue? No. The period end date requirement is stated for payments processed by FIN. Confirm whether your owner's payments use that process before you apply it.

Can one schedule cover both calendar and approval needs? Yes, if it shows when the work finishes, when the estimate of that work will be prepared, and which period the estimate falls in. Both the Texas calendar requirement and the Minnesota completed-work basis depend on dates tied to the work.

Do I need to revise a schedule after it enters the queue? Possibly. The GSA clause says the Contractor should anticipate that the project schedule will be subject to review and may require revision (GSA). Record the cause of each change so the revisions can be explained later.

Sources

More field guides