Problem guide
Jobs and orders wait for missing information
Work stalls when it is released with questions still open, and nobody owns the answers or watches the clock on them. It happens to a fabrication job on the shop floor, a custom order in fulfillment and a tax return waiting on client documents. For structural steel, AISC's Code of Standard Practice sets a default yardstick: approval drawings go back to the fabricator within 14 calendar days unless the contract says otherwise. Review each job or order before release, date every open question, and name the person who answers it.

How it actually happens
Most work starts with an order taken by someone who will not do the work: a salesperson, an estimator, an account manager, an intake coordinator. That person captures what the customer said and what the quote assumed. The people doing the work need more than that. A shop needs the current drawing revision, the material grade, the finish, the quantity per release and the ship date. A tax preparer needs every client document. A fulfillment team needs the artwork for a custom order. When any of those is missing, the work still gets released, because nobody wants it sitting in the office looking late.
Here is a typical version, offered as an example. An order for twenty guard panels reaches the floor with a drawing but no finish called out. Cutting and forming go fine. At the paint line the lead stops, because this customer has used two colors before. He texts the salesperson, who is on the road. The answer comes back three days later to the office manager, who means to walk it out and does not. The lead asks again on Monday.
Every handoff in that chain is a person carrying a question in their head or their phone. The question has no date, no owner on paper and no place where anyone else can see it. The lead knows the work is stuck. The office does not know it is stuck on them.
In structural steel the wait has a published shape. Shop drawings go out for approval and nothing is fabricated until they come back. AISC's Code of Standard Practice sets 14 calendar days as the default return time, and it asks the fabricator to flag discrepancies promptly while asking the owner's side to resolve them in time. A steel shop that writes down when each question went out and came back can show exactly where the days went.
Prefab shops working from a model have a different version. A package flagged on hold in STRATUS shows a warning color, and the package rolls up to the status of its lowest part. The floor sees that something is wrong. The screen does not say what the question is or who is answering it. In Tekla PowerFab, whether a held drawing actually stops the shop depends on a company setting that can allow, prompt or prevent.
ERP-driven manufacturers can stall in a quieter way. If the scheduler will not load an order until every material is on hand, one late item moves the whole order, and the floor sees only that the order is not on the list.
Why the hold list keeps going stale
A held list breaks down the same way every time. People add work when it stops and forget to clear it when the answer comes, or the answer comes and the work restarts without anyone writing the date. After a month the list has jobs on it that shipped and misses jobs that are stuck. The fix is not a better list. It is making the answer itself the thing that clears the hold, so the record and the work move together.
Signs you have this problem
- Work sits staged or parked with a note that says waiting on info
- Leads walk to the office or message sales several times a day to ask the same question
- Nobody can list every job or order currently on hold without asking around
- Questions go to salespeople or account managers by text and the answers never come back to the people doing the work
- Work is flagged on hold in the software and people keep working on it anyway
- Work gets started on a guess and then has to be redone when the answer arrives
What usually causes it
- Work is released before anyone checks the order against what production needs, so the people doing the work find the gapsThe handoff gap
- Open questions sit in one person's inbox or phone, and a hold flag in the software shows a color but no reason or ownerThe invisible queue
- Approvals and answers sit with the engineer, the client or the customer, and nobody tracks how many days they have been outApproval drag
Find your cause
Ask these in order. The first yes is usually where yours starts.
- Do most stalls trace to something the customer or salesperson could have told you when the order was taken?If yes: the gap is at order entry. Add those items to the release review so the work waits in the office instead of on the floor.
- Is work waiting on approvals, documents or answers from the engineer, the client or the customer?If yes: the wait is outside your walls. Date every request out and back, and raise the oldest ones with the customer's contact each week.
- Does work marked on hold in your software keep getting worked on?If yes: the hold is a color, not a stop. Check whether your system is set to allow, prompt or prevent, and make the setting match what you want.
- Do answers arrive but never reach the people doing the work?If yes: the reply lands with whoever asked by phone or text. Route every answer to the job or order record and the held list, not to a person.
How it breaks in each industry
- Structural steel fabrication
- Shop and erection drawings go out for approval and the job cannot be released to fabricate until they come back. AISC 303-22 sets 14 calendar days as the default return period, and the commentary treats that as the fabricator's portal-to-portal time. Discrepancies found while detailing turn into RFIs that hold the pieces they touch.
- Build-to-order manufacturers on an ERP
- Where the ERP schedules by material availability, one missing input can hold everything. In Acumatica's advanced planning and scheduling, a production order is scheduled only when all of its material is available in full, so a single short item moves the entire order.
- Accounting and tax firms
- A return or a year-end engagement is started before the client has sent every document. The preparer works around the gaps, the open items live in emails to the client, and the file sits half done while nobody tracks how long each request has been out.
- E-commerce and consumer brands
- Custom and personalized orders need something only the customer can give: artwork, a size, an engraving line, a color choice. The order is paid and sits in fulfillment until someone emails the customer, and the reply lands in a support inbox the packing team never sees.
Where it breaks between systems
- Tekla PowerFab drawings on hold
- A drawing is put on hold by setting its approval status to H, and it shows highlighted in red. What the hold does to production and purchasing is a company setting with three choices: allow work to continue as usual, prompt the user, or prevent the drawing from moving forward. On Allow, a held drawing keeps moving.[3]
- Tekla PowerFab revised drawing imports
- When a revised drawing or bill of materials is imported and a change cannot be applied automatically, the only choices are to save it for later, which puts the items on hold in Pending Changes, or to prevent it. A held drawing cannot be worked until a person reviews and processes the change. The help page describes no alert to that reviewer.[5]
- GTP STRATUS tracking statuses
- An ON HOLD status is set up as a Warning tracking status, which changes page colors to show work has stopped. GTP notes that the status's other permissions, such as Can Assemble and Can Package, still apply, so the warning alone does not lock the item. An assembly or package displays the status of its lowest-ordered child.[6]
- Acumatica Manufacturing advanced planning and scheduling
- If one material for one operation is not available, the whole production order is rescheduled, not just that operation. Partial quantities on hand are ignored during scheduling. This applies only with the APS feature turned on, and material validation can be excluded.[7]
By the numbers
| Figure | What it measures |
|---|---|
| 14 calendar days[1] | Default time for approval documents to come back to a structural steel fabricator under AISC 303-22, section 4.4, unless the contract documents set a different period. A trade-practice default, not a statute. |
| 5.5 hours a week[8] | Time construction professionals said they spent each week looking for project data, in a 2018 survey of 599 respondents (500 in the US) by FMI for PlanGrid, a software vendor. Self-reported, not observed. |
Rules that apply
- AISC 303-22, section 4.4, return of approval documents[1]
- Approval documents go to the owner's design and construction representatives and are returned to the fabricator within 14 calendar days. Their release is what lets the fabricator begin fabrication, under 4.4.1(c). Structural steel only, and the contract can change the period.
- AISC 303-22, section 3.4, discrepancies in the contract documents[1]
- When the fabricator finds a discrepancy during its work, it must promptly notify the owner's construction representative, and the resolution must be timely so as not to delay the fabricator. The Code applies where the contract documents do not say otherwise.
- AISC 207-20 (2020 edition, since superseded), section 1.6, contract and specification review[2]
- AISC-certified fabricators need a documented procedure for reviewing the contract and project specifications on every project, starting no later than acceptance of the work, with records kept. The commentary says the review should ideally begin at estimating or bid. It binds certified shops only; check whether a newer edition has replaced 207-20.
Measure it in your own shop
From: Your job or order release dates, hold notes or whiteboard photos, RFI, submittal or document-request logs, and the email or text threads where questions were asked.
- Pull every job or order released in the last two months and mark each one that stopped for missing information.
- For each stall, find the date the question was asked and the date it was answered, and note who held it.
- Sort the stalls into three groups: answerable at order entry, waiting on the customer, client or engineer, and answered but not passed on.
- Total the days in each group and count work started on a guess that was later redone.
Reading it: The biggest group of days tells you where to work first. Order-entry stalls are fixed by the release review. Customer and engineer stalls need dated tracking and weekly follow-up. Answered-but-lost stalls mean the reply has no path back to the people doing the work.
What does not fix it
- Starting the work on a best guess
- It keeps people busy and hides the stall. When the answer differs from the guess, you pay for the work twice and the wait still happened.
- Flagging the job on hold in the software
- In some systems a hold is a color and a status, and work can still move. A flag with no reason, owner or date does not tell anyone what to chase.
- A daily meeting to chase open questions
- It finds the questions once a day and depends on memory. Without a dated list, the same item is discussed for a week and nobody can say how long it has been open.
What to try this week
- Log every stall for two weeksEach time work stops for an answer, write the job or order number, the missing item, who was asked, the date asked and the date answered. Two weeks of entries show which questions repeat and who holds them.
- Date each question in both directionsRecord when the question went out and when the reply came back. In structural steel, AISC 303 puts the duty to flag a discrepancy promptly on the fabricator and the duty to resolve it in time on the owner's side, so both dates matter. The same two dates show whether a client or your own team held the work.
- Review the order before it is releasedBefore work is released, one person checks it against a short list: current drawing or spec revision, material, finish, quantity, due date, and any customer document the work depends on. Anything missing keeps the job in the office. AISC-certified steel shops already owe a documented contract review on every project.
- Decide what a hold does in your softwareFind out whether a hold in your system stops work or only changes a color. In Tekla PowerFab that is a company setting; in STRATUS a warning status does not lock the item by itself.
- Post one list of held workKeep a board or shared sheet of every held job or order with what it waits for, who owns the question and how many days it has been open. Read it at the start of each shift or each day.
Where do-it-yourself stops
These steps cut the number of stalls and make the rest visible. Questions and answers still travel by text and email between production, sales, the engineer and the customer, and the held list is only as current as the last person who touched it. The lasting fix is a tool built around your own order entry and production system that stops an incomplete job at release and carries each open question to its answer with a date on both ends. That is what a Workflow Spec designs.
Questions people ask
How long should approval drawings take to come back to a steel fabricator?
AISC 303-22, section 4.4, sets 14 calendar days as the default unless the contract documents say otherwise. The commentary describes it as the fabricator's portal-to-portal time, so it counts from when the documents leave the shop until they come back.
Whose job is it to raise a missing detail on the drawings?
Under AISC's Code of Standard Practice, the fabricator must promptly notify the owner's construction representative of a discrepancy, and the owner's side must resolve it in time not to delay the fabricator. Writing down both dates is how you show which side held the job.
Does putting a drawing on hold in Tekla PowerFab stop the shop?
Only if the company is set up that way. Trimble's help describes three company settings for drawings on hold: allow work to go on as usual, prompt the user, or prevent the drawing from moving forward.
Should every job be held until it is complete?
Hold only for what stops the work: the current drawing or spec revision, material, finish, quantity and any customer document it depends on. A short release review gets used every time; a long one gets skipped.
Is there published data on how long jobs wait for answers?
We found none. The closest published figure is self-reported: in the 2018 FMI survey for PlanGrid, construction respondents said they spent 5.5 hours a week looking for project data. Your own stall log is the only reliable measure for your business.
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.
