Van cost example: $200 until 8 riders, then $400

• List each fixed monthly cost and mark the headcount where it would step up.
• Find the last headcount your current vehicles cover before you add a technician.
• Test the one to eight passenger band against your own crew, not against a textbook price.
• Keep the shirt example out of any price you give a customer.
• Ask whether each cost stays owed in a slow month before you count it against a single job.

Fixed cost stays flat inside a relevant range, according to OpenStax, and steps up when you pass it. Treat the textbook figures as a worked example for testing your own numbers. They are not a vehicle price you can buy, and they should not set what your customers pay. Replace each figure with your own before you use the example.

Fixed costs are easiest to understand as costs that stay put across a range of activity. OpenStax uses a van to show where that range ends. Your task is to find the edge of that range for your own vehicles and crew before you add the next technician. Start with the vehicle you use most often and write its seat count on the page.

Some fixed costs are owed even when no work is sold. In the lease example, the owner is obligated to pay $1,000 per month whether or not he produces and sells any shirts, according to OpenStax. Your own rent and other monthly bills may work the same way, so list each one and note whether it is owed in a slow month.

Start with the trigger, not the dollar amount. The example's reason for its jump is a vehicle limit, according to OpenStax. Your steps need a reason too, such as a seat count, a second vehicle, or a second dispatch slot. Write the trigger beside each cost so you can check it against your own equipment. If a cost has no trigger, ask whoever set its price what makes it change.

Relevant range is the phrase to search for when a cost example mentions headcount. It names the span where the fixed amount holds, and it is easy to lose when someone copies only the numbers. Write its limits beside the figures on your own sheet.

If you dispatch jobs, the step may show up first as a full board, before it shows up as a cost. Record each step in one shared place so both views check the same headcount edge. For a handoff checklist, see the dispatch handoff checklist.

Begin with the single vehicle, since the later figures in the example build on it. Keep the example's structure, one vehicle, one price, and one seat limit, and change only the figures.

The next figure sets the headcount that the single van covers: if they send one to eight participants, the fixed cost for the van would be $200, according to OpenStax. Participants is the textbook's word, and riders are the closest match on your job board. For your crew, count riders for each vehicle rather than technicians on the roster, because seats are the limit in this example. Write the count beside the vehicle that carries those riders.

The example then changes at the next headcount. OpenStax says that if they send nine to sixteen students, the fixed cost would be $400, and the reason given is that they will need two vans, according to OpenStax. The jump from $200 to $400 is the step to watch in your own numbers. Mark the booking size that would cross your current range before you accept it.

Here is the reference table.

Read the figures in order: the vehicle price, the headcount it covers, and the next headcount that changes the price. None of them is a job price, so copy the order rather than the numbers.

Assume a crew of 10 riders needs a ride to a job. That count exceeds the example van's capacity, so another van is needed. The fixed cost rises from $200 to $400: a $200 increase. Compare the added fixed cost with the margin from the job before accepting the booking.

OpenStax places the top of the range at eight passengers in its van example, according to OpenStax. The first headcount outside that span is nine. A crew that reaches nine riders has crossed the edge in this example. Your own edge may sit at a different headcount, so the same test applies to your vehicles and your schedule.

Pull the busiest day from your last month of schedules and count the riders on each vehicle. Compare that count with the seat limit of each vehicle you already own. The edge is the seat limit or headcount threshold of each vehicle. Write the highest count you have seen beside the edge as your current peak load.

Plan for the whole band rather than for the first extra rider alone. Ask what each extra seat would trigger on your vehicles, and write that answer beside the edge.

If you are about to hire, ask which headcount the next hire would reach. If that headcount is the first one outside your current vehicles, the hire carries the step with it. Put the hire date beside the step so the cost shows up before the invoice does.

Dispatchers can use the same edge on the board. Mark the largest group your vehicles can take on each route, and flag any booking that fills the last seat. That is a planning habit, not a rule from any source.

Start by listing every cost you pay in a month regardless of the jobs you run. Write each one on its own line with the amount you pay and the day it is due. Use last month's bills as your starting point, and confirm each amount against the statement. Leave out the costs that change with each job for now, since they belong in the margin check later.

If your list includes a vehicle payment, check whether the contract changes when riders are added. Write the answer beside the payment, even if the answer is that it does not change. Repeat the check whenever you sign a new agreement for a vehicle, a lease, or a service plan.

Keep fixed items that stay flat within your current range on a separate line from fixed items that step. Mark each stepping line with the headcount that triggers it.

Review the list once a month. Add any new cost, remove any cost that has ended, and update the headcount edge when a vehicle changes. Bring the list to the owner and the dispatcher together, so both roles agree on the current edge.

The textbook uses a single shirt as its contribution margin example, according to OpenStax. Read that example for the order of the steps, not for the figures. Write down the revenue first, then the variable cost, and then the margin that remains.

Keep this example for the mechanics only. It describes a shirt, so its figures do not carry over to service job prices. Replace each number with the figures from one of your jobs, and label the job as a test so nobody confuses it with a customer quote.

Begin with one job you ran last week. Write the price the customer paid, then write the costs that changed because that job happened. Materials used on that job are one example of a cost that changes with the job, so list them separately from your fixed costs.

Compare several results before drawing any conclusion, since a single job is a weak basis for a hiring decision. For settings to check, see Job costing setup for field service: 5 key settings.

Compare that margin against the fixed cost each new vehicle adds, and write both numbers on the same line. A job that barely covers its variable cost leaves less room to carry a step.

Your number moves when a vehicle, a seat count, or a contract changes. Update the list when any of those change, because the old edge no longer applies. Write the date of each change beside the number so the history stays clear.

Recurring bookings can change the count without any new technician. Check how often the same group rides together before you assume the edge is safe. If a recurring booking grows, the load may reach the edge before the calendar shows it. Review the recurring list at the start of each month, so growth shows up early. For repeat visits, see Technician scheduling: 4 tools for repeat visits.

Keep the exact band on the page, not a rounded average, so the edge stays visible. A rounded figure can hide the point where the next band begins.

Track the largest group you actually run each week, and keep the expected count beside it. Compare both counts with the vehicle's seat limit to see how close you are to an edge. If either count approaches that limit, bring the next hire into the planning discussion early.

Your next step is to list your fixed monthly costs and mark the headcount where each one would step up. Start with the costs you can name today, and add the rest as you find them. For each line, write the trigger, the amount, and the date you last checked it. Then sort the lines into flat costs and stepping costs, and keep both groups on one page for the next hiring decision.

How many passengers does the example van hold?

Eight passengers is the capacity the textbook gives for its van, according to OpenStax.

What does the cost become at nine riders?

At nine passengers the fixed cost would be $400 for two vans, according to OpenStax. Compare the ninth seat with the seats you already own before you assume the same jump.

What is a relevant range?

A relevant range is the span of activity where a fixed cost stays the same, as the van example shows, according to OpenStax. Find the edge for your own vehicles and write it on your plan.

How is contribution margin found?

Contribution margin is sales revenue minus variable cost: the shirt example uses $15 minus $10 to get $5, according to OpenStax. Use the same order on one job.

Is rent a fixed cost in the example?

Whether your own rent belongs in the fixed column depends on the lease terms you have. Check those terms before you sort the cost into the list.