Straight into the service manual page
WrenchQuarry
More

A closure cut 225 units to 175 and caused a $4,000 loss

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

A flood closed Hicks for several days, cutting shipped units from 225 to 175 and leaving $17,500 in sales against fixed expenses they could not cover, for a $4,000 loss. The first day back is about deciding which jobs in the queue can still ship at a profit and which should not be taken at all.

  • Break-even was 225 units; at 175 units and $17,500 in sales, the shortfall showed up as a $4,000 loss.
  • Fixed expenses like rent, insurance, and loans do not pause during a closure, so the loss is simply the gap between what remaining work earns and what fixed costs demand.
  • Profit begins only at the unit past break-even — in the example, the 226th unit.
  • Reset the queue by counting what can actually ship, valuing that count against what each job bills, and comparing it against fixed expenses.
  • Dispatch in order: jobs that can ship this week with parts on hand first, then jobs waiting on parts, unconfirmed jobs, and jobs past their expected date.

What happened when the shop closed

A flood closed a manufacturer called Hicks for several days. The number of units they could ship and sell dropped from 225 to 175. At 175 units, or $17,500 in sales, they could not cover their fixed expenses, so they took a loss of $4,000. That is the whole story in one sentence, and it is the number your own queue reset has to answer for.

You have just lived the same shape of event. Storm or flood, shop closed, jobs on hold. The queue you come back to is not the queue you left. Some jobs are past their date. Some customers have moved on. Some work still needs doing but cannot start until a part arrives. The job of the first day back is to decide which jobs you can still do at a profit, and which ones you should not take at all.

This post walks through that decision the way the example does it: start from the number of units you can ship, work out what that number earns, and compare it against the fixed costs you still carry. The break-even calculation here follows the OpenStax managerial accounting text, which you can read at Principles of Accounting, Volume 2: Managerial Accounting | OpenStax. The queue-sorting, dispatch, and customer-call advice that follows is ours, not the source's.

Why fixed expenses do not shrink when you close

The closed days do not pause your rent, your insurance, your loan payments, or your tool leases. Those costs keep running. OpenStax states that at 175 units, Hicks did not generate enough sales revenue to cover their fixed expenses, and the shortfall showed up as a loss of $4,000.

So the loss is not a mystery. It is the gap between what your remaining work earns and what your fixed costs still demand. When you come back to the queue, the first question is not "how fast can we clear it." The first question is "what does each job in it actually contribute."

Here is what that gap looked like in the example.

Shop stateUnits shipped and soldSalesFixed expenses coveredResult
Normal month225$22,500YesNo profit, no loss
After the closure175$17,500Not fully$4,000 loss

Read that table against your own numbers. Your unit is a job, a ticket, or a repair. Your sales figure is what the job bills. Your fixed expenses are the costs that did not close with the shop. The row you are in now depends on how many of those jobs you can still run and bill.

How the break-even point works in your queue

OpenStax shows that Hicks had to sell 225 units to cover their fixed expenses. That is the break-even point: the volume at which sales cover fixed costs plus variable costs, so the shop makes no profit and suffers no loss.

The same source makes the next step plain. Profit begins only at the unit past break-even. As they put it, they will not begin to show a profit until they sell the 226th unit.

What this means for your reset is direct. A job you take below break-even volume reduces the loss if it covers its own variable cost, and adds to the loss only if it does not. Any job you take at break-even volume only covers costs. Work you book past break-even volume is where profit lives.

Three steps to reset the queue

  • Count what you can ship. Walk the queue and mark the jobs that can actually run this week: parts on hand, bay space open, tech available. That count is your 175 or your 225. That is your $17,500 or your $22,500.
  • Compare contribution against fixed expenses. Subtract the variable costs of the jobs you can ship from what they bill, then compare that figure with your fixed expenses, or compare total sales against fixed plus variable costs. Gross billing alone overstates how close you are to break-even. If it clears, you are at or past break-even.

Do the same math for the week ahead, not just the week behind. The queue you are looking at was built for a shop that was open. It does not match the shop you have now.

Which jobs to work first

Not every job in the queue earns the same margin, and not every job can run on the day you reopen. OpenStax's example treats every unit the same, since its figures imply a constant sales amount for each unit. Your queue does not work that way.

Sort the queue before you dispatch anything:

  • Jobs that can ship this week with parts on hand
  • Jobs waiting on a backordered part
  • Jobs the customer has not confirmed
  • Jobs past the date the customer expected

Start with the first group. Those are the jobs that turn into shipped units and sales revenue this week.

The loss in the example came from jobs that could not ship. When the shop reopens, the jobs that did not ship while it was closed have already passed their best chance. Some customers will have found another shop. Some will still be waiting. You will not know until you call.

Planning from the $4,000 loss

OpenStax states the loss directly: at 175 units and $17,500 in sales, Hicks suffered a $4,000 loss. That number is what you carry into the next month's planning.

You cannot claw the $4,000 back by working harder in the same week. The week is over. What you can do is keep the next week out of the same row. That means the queue you dispatch on the first day back has to be built to clear break-even, not just to clear the board.

The temptation on the first day back is to take every job waiting, to make up for lost time. That works only if the volume you take clears break-even at the margin those jobs carry. If the jobs you are taking are low-margin work, you can ship a full board and still sit under the line.

Resetting the queue after a closure

Work through the queue in this order, and do it before you send a single tech out:

  • Pull every open ticket. Print or export the full list. You want the whole queue in front of you, not what the screen shows first.
  • Mark what can ship. Parts, bay, tech. If any one is missing, the job does not ship this week.
  • Revalue what is left. Reprice anything quoted before the closure. Material costs and supplier lead times may have moved while you were closed.
  • Call the customers expecting dates. A customer who has been waiting through a closure needs to hear from you before they call you.
  • Hold what cannot run. Do not let jobs that cannot ship sit in the active dispatch list and eat a tech's morning.

OpenStax's example does not tell you what to do about the jobs that will never ship. It only shows what happens when they do not. Your job as the owner or dispatcher is to move the queue into the group that can.

The conversation with customers waiting on a date

You will make calls on the first day back. Keep them short and factual. Tell the customer the shop was closed, tell them the new date, and tell them what you need from them to hold that date.

A customer who has been waiting will ask about price. If you repriced the job, say so and say why in plain words. Do not bury the change. A surprise on the invoice costs you more than a higher number on the phone.

If a customer cannot wait, release the job. It frees a bay and a tech, and it keeps your queue honest. A job that will never ship is taking up space a job that will ship could use.

What to tell your techs on day one

Your techs will want to know what to run first. Give them the sorted queue from above, not the raw list. Tell them which jobs can ship and which ones are waiting on something.

If a tech starts a job that cannot finish, the day's output drops and you lose the same ground twice. The first day back is not the day for exploratory work. It is the day for jobs that will bill.

If a tech asks why the queue is shorter than usual, you have an honest answer. The shop was closed. The queue reflects what can ship, not what was promised.

The week after: watching the line

Once the first week is dispatched, keep watching the line. OpenStax frames break-even as a volume and a dollar figure.

If you find you are shipping jobs but still landing short, the mix could be the problem — or you may have too few units, or fixed costs that are too high. Look at which jobs are carrying the least contribution per hour of bay time. Those are the jobs that fill the board without filling the gap.

You do not need a new system for this. You need the same three numbers each week: what you can ship, what it bills, and what your fixed costs run.

What the sources do not cover

The OpenStax example uses one product at one price, so it does not tell you how to split your queue when jobs carry different margins. Ask your accountant how to weight the queue when your jobs do not all earn the same amount per hour of shop time.

That is the one open question here, and it matters on your first day back more than any other detail in this post.

Related guides: Bulk order sales tax: 3 checks before billing · Bundled maintenance plan sales tax: 8 steps to check · Job-cost comparisons: 3 checks across periods.

Questions owners and dispatchers ask

Do fixed expenses stop during a closure? No. OpenStax's example shows that after the closure, the remaining sales revenue still had to cover fixed expenses, and when it did not, the shortfall appeared as a $4,000 loss. Your rent, insurance, and loans do not pause because the bay doors are shut.

How do I know when I am back above break-even? You are at break-even when the units you can ship cover your fixed expenses, and you are above it at the unit past that point, where profit begins. In the example, break-even was 225 units and profit began at the 226th unit. For your shop, the equivalent is the job past the one that clears your fixed costs for the week.

What if the customer will not wait for a new date? Release the job and tell the customer plainly that you cannot hold the date. A job sitting in the queue with a date you will miss costs you the relationship and the bay space.

Should I take extra work to catch up? Take work that clears break-even at your current margin. Extra volume below the line reduces the loss only if each job covers its own variable cost. Check what each job contributes before you commit the bay.

Who should set the new dates with customers? The person who will actually dispatch the job. In most shops that is the dispatcher, because they know which jobs can ship and which are waiting on parts. The owner sets the pricing and the policy on repriced work.

Sources

More field guides