Why a fixed crew runs out
Add output beyond a fixed crew's limit by paying for extra hours or adding a second crew or machine. Each option has a different cost pattern, so each needs its own price. This guide shows how to find the limit, then how to price both options for a specific job.
Every estimator who prices labor-heavy work hits this wall sooner or later. A single press can run only so many parts in a shift. When the job asks for more than that, the schedule will not stretch by itself, and the budget will not cover the gap unless you plan for it.
The managerial accounting text from OpenStax helps here because it sorts costs by how they behave when activity changes. It includes a table of fixed costs for merchandising, service, and manufacturing organizations ( OpenStax, section 2.2). A fixed cost stays the same in total while activity moves within a certain band. A crew's fixed wages are an example. They are owed in a slow week and in a full one.
The catch is that a fixed cost is fixed only inside a band. Once the work passes what the crew can do, the wages still do not change, but the output does not grow either. You then have to decide how to get more output, and each way changes the cost pattern.
The relevant range is your cap
OpenStax uses a quality inspector to make the point. The inspector can check a maximum of 80 units in a regular 8-hour shift, and the inspector's salary is a fixed cost ( the OpenStax text). The relevant range for QA inspection is therefore 0–80 units each shift.
Textbooks call this the relevant range: the span of activity over which a cost pattern is valid. For your work, it is the output your crew or machine can reach in normal working hours. Everything inside it is priced with the fixed cost spread across the job. Everything above it needs a separate decision.
Most estimates skip this step. Estimators often write "the crew is fast" or "the machine is quick" and move on. That phrase will not price a job that runs past the limit. Write the cap as a rate and a period instead: how many units the crew completes each shift, how long a shift runs, and how many shifts a week the crew works. Once the cap is on paper, you can see the exact point where the job goes over it, and price what lies beyond.
Write the assumptions next to the cap. If the crew works shorter days in winter, the cap changes. If a machine needs a changeover between runs, the cap for mixed jobs drops below the cap for a single product. Those details decide where the relevant range ends, so they belong in the estimate.
The OpenStax examples give three limits that can be written as rates:
A worked example: the screen-printing shop
OpenStax follows the inspector with a second case, a screen-printing business. The owner's one machine can produce 2,000 T-shirts a month. The current employee produces 20 shirts an hour, which is 160 in an 8-hour work day ( OpenStax). The case shows two limits at once: the pace of each person and the ceiling on the machine.
Use those figures to test a rush order. Divide the rush quantity by 20 shirts an hour to get the employee hours it needs. A rush order larger than 160 shirts cannot be finished in one 8-hour day at that rate, so the hours beyond the regular day are the extra hours to price. If the crew can finish within the regular day, there are no extra hours to price. Once the cap is a rate, a rush order becomes a question of hours.
The monthly ceiling matters too. If existing orders already use most of the 2,000-shirt limit, a rush order is not free even when labor is available. The machine is the constraint, and overtime for the employee does not fix that. Check both limits, people and machine, before you promise a date.
The same text notes that the leased space is large enough for an additional screen-printing machine and one additional employee ( OpenStax, section 2.2). That sentence points to the second option. Before you choose between overtime and added capacity, check whether the added capacity can physically fit. Space is a real limit that many estimates overlook.
Option 1: add hours
The first option is overtime. OpenStax lists it as one choice when a quality inspector cannot keep up with volume: "(1) Pay the quality inspector overtime in order to have the additional units inspected" ( OpenStax). The same logic applies to a framing crew, a paint crew, or an operator running a press. The crew stays the same size, and you pay for more hours so the extra output gets done.
Overtime changes the cost pattern. The regular wage was fixed inside the band. Extra hours rise and fall with the work you run through them, so the cost becomes partly variable. The text covers this mixed-cost pattern with a graph: "Graphically, mixed costs can be explained as shown in Figure 2.20." ( section 2.2). For a crew, the picture is simple: a fixed base for the regular shift, plus a variable charge for each extra hour.
Pricing extra output has a close cousin in valuation. Odoo's accounting documentation defines the idea this way: "Inventory valuation is a method of calculating how much each in-stock product is worth internally" ( Odoo documentation). The same discipline applies to output your crew produces but has not yet delivered. Track each unit's real labor cost separately from the price the client will eventually pay.
To price it, take the cost of an extra hour, including whatever load you add on top of wages, and divide it by the output that hour produces. In the screen-printing case, an hour at 20 shirts an hour yields 20 shirts, so the labor cost for each shirt is the hourly overtime cost divided by 20. Compare that unit cost with the cost of the alternative. Use your own overtime rate, not a figure from a textbook. For related rate inputs, see construction overtime cost.
Machines carry running costs too. If a machine runs extra hours, add power, consumables, wear, and extra maintenance. A machine past its regular shift is not free just because the operator is already on the payroll.
Overtime also has limits beyond cost. Check any overtime and maximum-hours rules that apply where you work before you assume the option exists. Hours affect quality too. In the inspector case, the extra work is inspection, so every extra unit still needs its check. A tired crew makes more mistakes, and rework costs money. Compare the costs before choosing overtime for a short peak. For a long run, a crew that stays on overtime is a sign that the cap sits in the wrong place.
Option 2: add a second unit
The second option is added capacity. The OpenStax inspector example describes it directly. A second inspector would raise the maximum to 160 inspections each shift, assuming the second QA inspector can inspect an additional 80 units each shift ( the OpenStax example). Adding a second unit of the same capacity moves the cap up, and the fixed cost pattern holds across the larger band.
The cost changes shape. The second salary is also fixed, and so is a second machine's lease, depreciation, or purchase cost. You spread that fixed cost across the units the job produces. The unit looks cheap when the work fills it and expensive when it does not. Idle capacity is still a cost. When the job ends and the second person has nothing to do, the wages keep coming.
Adding capacity takes time. You need to hire, train, and onboard a person, or order, install, test, and set up a machine. A new crew is usually slower than its steady pace in the first days. Plan a second unit early rather than adding it in the last week of a backlog. A late addition often arrives as the work is ending, which leaves you paying for a unit that barely contributes.
Space and tooling are the next constraints. The screen-printing owner's leased space fits an added machine and an added employee, but your site may not. Check the floor, the power supply, access, and the tools each unit needs. A second unit that cannot fit or cannot be supplied adds cost and no output.
Coordination has a cost too. Two crews on one job need schedules, handoffs, and clear quality checks. Doubling headcount rarely doubles output on day one. Build a ramp into the schedule and state it in the estimate, so no one expects full output from a crew still learning the work.
Overtime or a second unit
Put the two options side by side and the trade-off is clear.
Overtime adds hours to the existing crew, and those extra hours stop when the work stops. A second unit gives steady capacity and lifts the cap for the whole operation, not just one job.
The useful test is to compare total cost at the volume you expect. Add the overtime cost for the extra units across the whole job. Then add the fixed cost of the second unit for the period it will run, including setup and ramp time. Choose the lower total, and weigh the risks: quality under overtime, idle time with a second unit, and schedule risk for each.
The answer changes with volume. A small, one-off excess usually favors overtime. A large backlog that will continue for months usually favors added capacity. A middle case, where the excess is real but uncertain, may favor overtime now with a plan to add capacity if the work keeps coming. Write that plan down with the trigger that starts it, so the client and your team both know when the decision changes.
Measure real output
Estimates often start from the best day the crew ever had. That is a mistake. Use records from past jobs instead: units completed each shift, including breaks, setup, rework, and waiting for materials. If you can run a trial batch before you bid, time it. A cap built on ideal output will be too high, and in practice the relevant range will end sooner than it looks on paper.
The OpenStax figure of 80 units in an 8-hour shift is a maximum. Compare that maximum with sustained output before using it in an estimate. Compare planned and actual results on finished jobs, and revise the cap when the numbers drift. A cap you check every quarter is worth more than one you set once and forget.
When the mix of work changes
A cap is rarely one number once the work varies. A crew that handles three product types may run one of them faster than the others. A machine that switches between sizes or colors loses time at each changeover. The effective cap for a mixed run sits below the cap for a single repeated product, and that gap is easy to miss when you price from one good example.
Price each product type against its own cap, then add the results. Count a changeover as part of the cost of the run, not as a footnote. When a mixed job also runs past the cap, compare overtime and a second unit using the mixed rate, not the best-case rate.
Explain the choice to the client
Clients rarely mind a price change when they understand the reason. Tell them what the crew can do in a normal shift, what the job asks for, and how you plan to close the gap. If you choose overtime, say what it costs and what it does to quality. If you choose a second unit, say when it starts, how long it runs, and what the ramp time means for the schedule.
Keep the explanation short and tied to the cap. A sentence such as "our crew completes this many units each shift, so this job needs extra hours to finish on the date" is clearer than a long argument about labor. Clients who see the cap usually accept the logic, even when they dislike the number.
Putting it into your estimate
Work through these steps for each job:
- Write down the cap. Record the output of the crew or machine as a rate and a period, such as units each shift and hours each shift.
- Compare the quantity to the cap. Find the excess the job creates and how often it repeats.
- Price overtime for the excess. Use the extra hours, your overtime rate, the machine's running costs, and the output each hour.
- Price a second unit for the excess. Use its fixed cost for the period it will run, plus setup and ramp time.
- Choose the lower total at the expected volume, and write down why.
- Check space, equipment, and crew availability before you commit to the second option.
- State the assumption in the proposal, so the client understands why the schedule or price moved.
Each step is short, but the discipline matters. The mistakes below are the ones that cost estimators the most.
Common mistakes
Treating fixed wages as free extra capacity comes first. Those wages cover the crew only inside the relevant range. Beyond it, you are paying for something new.
Assuming output doubles when headcount doubles is second. Coordination, training, and space all cut what a second unit delivers on its first day.
Forgetting machine running costs is third. Overtime on a machine is more than labor. Power, consumables, and wear add up.
Failing to write the cap down is fourth. If nobody can say what the crew does each shift, nobody can say when a job goes over it.
Ignoring local rules is fifth. Check the overtime and hour rules that apply where you work before you price the option.
Keep the decision visible
The two ways to add output are simple to describe and harder to price well. Both options work. Each suits a different kind of excess.
Write the cap, compare the excess to it, price each option at the expected volume, and state your choice. That habit catches most problems before the job starts, and it gives you a clear answer when the client asks why the schedule or price changed.