Problem guide
Priorities change by whoever shouts loudest
Priorities change by shouting when the real order of work lives in one person's head, so the latest call or the loudest salesperson, partner or customer sets it. Software does not rank work by itself: in GTP's STRATUS, a new module's priority defaults to Medium and its due date is optional, and ServiceTitan warns that when too many job types are High or Urgent, nothing urgent stands out. Keep one ranked list, give one person the right to change it, and write down what each change pushes back.

How it actually happens
Most businesses have an order of work written down somewhere: a whiteboard, a spreadsheet, a queue in the ERP or the practice system. The trouble is that it is not the order anyone follows. The real order is decided in conversations, and the list catches up later, if at all.
A common version from a fabrication shop, described here as an example: the laser is halfway through a nest for a steady customer due Friday. A salesperson walks up and tells the operator his customer needs twelve parts today, and that the owner already agreed. The operator stops the nest and loads the new job. An hour later a second salesperson asks for the same favor. By Thursday the steady customer's parts are a day behind, and the production manager learns about both changes only when he asks why. The customer who never calls to push is the one who ships late.
The same story plays out in a warehouse when a rep asks a picker to pull his order first, and in a firm when a partner tells a staff accountant to drop everything for one client. Look at who touched the order. The requester set a priority. The owner set one by agreeing in passing. The person doing the work set one by choosing which request to honor. The person whose job is the sequence was not in the loop. Nobody wrote down what moved back.
Software often makes this easier, not harder. In STRATUS a new module starts at Medium with no required date, so the system has nothing to sort by until someone fills it in. When one package's dates are pulled forward with the phase link off, every other package keeps its old dates, so the screen shows no conflict. In Acumatica a firmed order is left alone by rescheduling and hidden from the default planning view. Each of these is a reasonable design choice. Together they mean the list on screen can look calm while the work is being reshuffled by phone.
Structural steel has a written default that helps. AISC's Code of Standard Practice says the customer who wants to set the delivery sequence puts it in the contract documents. It treats revisions as changes confirmed by change order and calls holds and late revisions disruptive, with compensation to the fabricator. A steel shop can point to that when a general contractor phones in a resequence after fabrication has started.
Rushes usually start upstream
When you log the reshuffles for a few weeks, a pattern shows. Many of the rushes were not new demands. They were jobs that waited on an approval, a drawing, information from the customer or material, then arrived already late. The shouting is the last step of a delay that started somewhere else. Fixing the upstream wait removes more rushes than any rule about who may walk onto the floor.
Signs you have this problem
- Salespeople or managers go straight to the people doing the work and ask them to move their job up
- Work in progress gets set aside halfway to run someone's rush
- Leads get different answers about what is next from different managers
- Quiet customers with firm dates get their work late while loud ones jump the line
- Every job, order or file in the system shows the same priority, so the list on screen means nothing
- Every morning meeting reopens the same argument about what comes first
What usually causes it
- There is no single ranked list that everyone accepts as the real order, so the screen and the floor disagreeThe invisible queue
- Anyone can move a job, and nobody has to approve it or say what it pushes backApproval drag
- Rush requests arrive by phone, text and hallway conversation with no single place to landThe exception swamp
Find your cause
Ask these in order. The first yes is usually where yours starts.
- Do salespeople, partners or managers ask the people doing the work directly to move theirs up?If yes: the work has several bosses for sequence. Route every request through one person with the list.
- Does every job or order in your software show the same priority or no due date?If yes: the system cannot rank anything. Set real priorities and need-by dates before trusting its order.
- When one job moves up, does the work it displaces keep its old dates?If yes: the cost of the jump is invisible. Move the displaced dates and tell their owners.
- Are most rushes caused by something late earlier, like approvals, information or material?If yes: the shouting is a symptom. Fix the upstream delay and the rushes drop.
How it breaks in each industry
- Structural steel fabrication
- The erector and the general contractor want pieces in erection order, and the shop wants to fabricate efficiently. AISC 303 lets the customer control the delivery sequence by writing it into the contract. A phone call to resequence after detailing or fabrication has started is a change, and the Code treats late changes and holds as disruptive.
- Mechanical and plumbing prefab
- Several project managers share one prefab shop, and each one's package is the most urgent. In STRATUS every new module starts at Medium priority with no required due date, so the ranking is whatever someone last typed, or nothing.
- Distribution and wholesale
- Sales reps walk to the warehouse to get their customer's order picked first. The pick list on screen runs in one order and the floor runs in another, and the orders from customers who never call ship last.
- Accounting and professional services firms
- Each partner treats their client as the priority and pulls staff onto it directly. The staff member juggles three urgent requests from three bosses, and the deadline that slips belongs to the client who did not call to push.
Where it breaks between systems
- Acumatica Manufacturing advanced planning and scheduling
- Production orders carry a dispatch priority from 1, the highest, to 10, the lowest, and finite scheduling loads them in that order, then by constraint date, then by order number. The rule works only if someone sets the number and reruns scheduling. Firmed orders are not rescheduled and are hidden from Rough Cut Planning by default.[2]
- GTP STRATUS modules
- When a module is created, the Priority dropdown defaults to Medium and the Due Date field is optional. Until someone changes them, every module sits at the same priority with no date to sort by.[4]
- GTP STRATUS package phase dates
- With the Link Phase Calculation toggle off, changing one start date, end date or duration does not move any other date. Pulling one package forward leaves every other package's dates where they were, as if nothing had been displaced.[5]
- Tekla PowerFab project schedule
- Only one user at a time can have the project schedule in edit mode, and time and progress come into the schedule when someone clicks Update Status. PowerFab does take a snapshot each time the project schedule changes, so the history is there if someone looks.[6]
- ServiceTitan job types and Dispatch Pro
- For shops that also dispatch service work, ServiceTitan advises setting most job types to Normal and warns that if too many are High or Urgent, genuinely urgent jobs will not stand out. In its Dispatch Pro automated dispatch, tags can raise or lower an individual job's priority, and unranked job types are the ones pushed to the end of the window or left unassigned when the board is overbooked.[9]
By the numbers
No industry association or government survey publishes a figure for this. The measurement below gives you your own.
Rules that apply
- AISC 303-22, section 6.6.1, delivery sequence[1]
- Fabricated structural steel is delivered in a sequence that permits efficient fabrication and erection and is consistent with the contract documents. An owner or owner's construction representative who wants to control the sequence must specify it in the contract documents. Structural steel only, and the contract can override it.
- AISC 303-22, sections 9.3 and 9.4.1, revisions and price adjustments[1]
- Revisions are confirmed by change order or extra work order. A price adjustment considers how much work changed and how late the change came relative to material ordering, detailing, fabrication and erection. The commentary calls items revised or put on hold very disruptive and says the fabricator should be compensated for those inefficiencies. It covers customer-driven changes, not the shop's own reshuffling.
Measure it in your own shop
From: Your schedule, work queue or pick list at the start of each day, the delivery or shipping log with promised and actual dates, and overtime by job or client.
- Save or photograph the order of work at the start of each day for four weeks.
- Compare each day's list to the day before and count the items that moved up and the items that moved back.
- For the items that moved back, check whether they were delivered late against the promised date.
- Count interrupted work and overtime hours on the days with the most moves.
Reading it: The number of moves per week tells you how unstable the order is. Late deliveries on displaced work are what the rushes really cost. If one requester or one customer accounts for most of the moves, that is the conversation to have first.
What does not fix it
- Marking more work urgent
- When everything is urgent nothing is. ServiceTitan's own setup advice says the same about job types set to High or Urgent.
- Buying a scheduling module
- Scheduling software ranks by the priority and dates people type in. With every job at the default priority and no due date, it ranks nothing, and a locked order can sit outside the plan.
- Banning rush jobs
- Some rushes are the right call. The fix is one person deciding, and everyone seeing what each one pushes back.
What to try this week
- Write down every reshuffle for two weeksEach time the order of work changes, note the job or order moved up, who asked, the reason given, and which ones slipped. After two weeks you will know who drives the changes and how often.
- Post one ranked list per team or work areaPut the order of work for each area where everyone can see it. Work that is not on the list is not next, whoever says so.
- Give one person the penName the production manager, scheduler, warehouse lead or practice manager as the only person who reorders the list. Everyone else brings requests to that person, never straight to the people doing the work.
- Make each jump show what it costsWhen something moves up, write next to it what moved back and by how many days, and tell the person who asked. If your software keeps other dates fixed when one moves, adjust the displaced work by hand.
- Review the change log weekly with salesOnce a week, go through the reshuffles with sales or account owners and the lead. Many rushes turn out to be dates that were missed earlier, at order entry or in approvals.
Where do-it-yourself stops
These steps cut the shouting and put a cost on each jump. The list is still held together by one person, by hand, and it does not show real capacity, material on hand or setup time, so each change is still a judgment call made without the numbers. The lasting fix is a tool built around your own work, steps and due dates that shows what a change does to everything else before it is made. That is what a Workflow Spec designs.
Questions people ask
Why do our priorities keep changing?
Because nothing makes the current order of work visible and binding, so the newest or loudest request wins. In many systems every job starts at the same default priority, so the screen cannot settle the argument either.
Who should own the priority list?
One person who sees the whole operation, such as the production manager, scheduler or operations lead. Others bring requests to that person; they do not walk them to the people doing the work.
Can a steel customer dictate the order we fabricate in?
Under AISC 303-22 section 6.6.1, the customer who wants to control the delivery sequence specifies it in the contract documents. Without that, steel is delivered in a sequence that permits efficient fabrication and erection. A later change in sequence is a revision, confirmed by change order or extra work order under section 9.3.
What if the owner of the company overrides the list?
That is fine if it goes through the list and its cost is written down like any other change. The record matters more than who made the call.
Is there published data on what reprioritizing costs?
We found no trustworthy figure. Several vendor pages quote numbers with no linked source, and we leave them out. Count the moves, the late displaced work and the interrupted setups in your own business instead.
Next step
How we fix this
This guide is how to find it and work around it. If it keeps coming back, it is rarely the only thing costing you. We come on site, find the issues costing you the most, and fix them, starting with the most pressing.
Fox & Santiago, Genesee, Idaho. We work nationwide, for clients across the United States, from our headquarters in Genesee, Idaho.
