Problem guide
The shop doesn't know what the field needs next
The shop builds in the wrong order because the field's real dates live in the project manager's schedule, while the shop works from due dates set when the order was written. The same split happens anywhere a central operation, such as a commissary kitchen or a main warehouse, supplies locations that run on their own calendar. Out of the box, Procore's Material Request template leaves both due date and quantity optional, so a request can reach the shop with neither. Put a need-by date on every order, line up the two lists weekly, and name who passes changes the same day.

How it actually happens
The field and the shop run on two different calendars. The project manager keeps the install schedule, adjusted every time the general contractor finishes early, a floor slips, or an inspection moves. The shop keeps a list of open orders with due dates set when each order was written. Nobody owns the job of keeping the two in step. A commissary kitchen and its restaurants, or a central warehouse and its branches, have the same two calendars.
Here is an example of the drift. A project manager moves an install up a week because the general contractor finished the slab early. He tells the crew lead on site and updates his own schedule. The shop still has the handrail sections for that job due the following Friday, and it is working on something with an earlier due date. On Monday the crew arrives with nothing to set. The project manager calls the shop, which stops what it is doing to rush the rail. Meanwhile a set of stair stringers, finished two weeks early, sits in the yard waiting on a job that slipped.
The request side breaks in its own way. A foreman who needs something tells the project manager by phone or text. Kojo, a procurement software vendor, describes the same pattern for material: requests from the field come to purchasing over phone, text or email. The project manager turns it into a shop order when he gets to it. The date the foreman needed it is in the foreman's head, and the request form often does not ask. Procore's default Material Request form leaves the due date optional.
This is not a new problem. A 2006 study of electrical contractors described a paper requisition that already had a box for the date needed, filled in by hand and passed from the project manager to purchasing. Twenty years on, many shops still carry that date on paper or not at all.
Prefab shops working from the model have it better for planned work. STRATUS will not create a package without a required date. The trouble comes with the unplanned request: it arrives as a sketch or a PDF, gets typed in by hand, and is cut manually. The most urgent work often has the least structure behind it.
Then there is the return trip. Items arrive on site and are counted, or not, by a foreman who logs them in the field system if he logs them anywhere. A shortage reported late becomes a rush. A shortage never reported becomes a second trip.
Early is a miss too
Shops tend to count late items and ignore early ones. An item finished three weeks before it is needed takes space, gets handled twice, can get damaged or spoil, and used labor that a late item needed. When you measure the mismatch, count both. They come from the same missing date.
Signs you have this problem
- Crews or locations are ready for an item and the shop-built material is not
- Finished items sit in the yard or the warehouse for weeks while the work that needs them is not ready
- Managers call the shop to ask when something will be done
- The shop learns about a schedule change after it has already built the item
- Requests arrive as a sketch, a photo or a text with no date on them
- Rush work comes from problems that were known days earlier
What usually causes it
- The field or location schedule and the shop's work list are kept in different places and never comparedThe field-to-office split
- Changes reach the shop by phone, if at all, and requests arrive without a need-by dateThe handoff gap
- Nobody can see which shop items are due for which need dates, so the shop sorts by order dateThe invisible queue
Find your cause
Ask these in order. The first yes is usually where yours starts.
- Do shop orders carry only an order date or a general due date, not a need-by date from the point of use?If yes: the shop is sorting by the wrong date. Add a need-by date to every order and sort by it.
- Do requests come by text, sketch or phone with no date or quantity?If yes: the request form is the gap. Require need-by date and quantity before a request is accepted.
- Does the shop hear about schedule changes only when someone calls?If yes: there is no path for changes. Name a contact on each side and log every change the day it happens.
- Do finished items wait in the yard or warehouse while other items are late?If yes: the shop is building in order-date sequence. Run the weekly lineup and resequence to the need dates.
How it breaks in each industry
- Structural steel fabrication
- Anchor rods and embeds have to be on site before the concrete pour, long before the steel they support. AISC 303-22 says they must ship so they are available when needed and that the owner's construction representative must give the fabricator enough time. The field side has to say when, early enough, for that to work.
- Mechanical and plumbing prefab
- A modeled package carries a required date in STRATUS. A field request that is not in the model comes in as a sketch or PDF, its bill of materials is typed in line by line, and its cuts are manual. The urgent field item is the one with the least structure.
- Restaurants and hospitality
- A commissary kitchen preps sauces, doughs and portioned proteins for several locations from a standing par list. A location that books a large party or adds a special tells its manager, not the commissary, so one store runs out on Friday night while another throws product away on Monday.
- Distribution and wholesale
- A central warehouse kits or assembles orders for branches and job-site deliveries in the order they were entered. The branch knows which customer needs material first, but that date lives in a phone call or an email, so the warehouse builds the easy order and the urgent one waits.
Where it breaks between systems
- Procore Material Request template
- In Procore's built-in Material Request correspondence type, Due Date and Quantity are visible but optional and Location is hidden. Only Assignees, Description, Number, Private, Status and Subject are required. An admin can change the fieldset, but out of the box a request can be submitted with no quantity and no need-by date.[3]
- Procore Daily Log for materials received and installed
- Procore's answer for tracking quantity delivered and installed is the Daily Log's Productivity Log, with a matching Delivery log recommended. The Daily Log cannot generate an invoice from those quantities. Receipt is a field entry separate from the purchasing record, and the shop sees it only if someone reports on it.[4]
- GTP STRATUS non-modeled field requests
- A field request with no model can be handled, but the project still needs a published model with at least one 3D object. GTP notes the request is often a paper sketch or an outside PDF, line items are added by hand, and all cuts are manual with no TigerStop cut list sent to the station.[5]
- GTP STRATUS package required date
- Required Date is mandatory on every new package, and admins cannot remove it from the New Package dialog, though it can be edited later. For modeled work, the prefab system forces the need-by date that the general field request form leaves optional.[6]
- GTP STRATUS notifications
- Status changes reach people mainly through an activity feed inside the STRATUS website. Email notification is limited, and for some events the checkbox is disabled. A foreman who rarely logs in can miss that a package moved. The page was last updated in April 2023.[7]
By the numbers
| Figure | What it measures |
|---|---|
| 11 days to about 6[2] | Average procurement lead time before and after one Iranian construction company moved purchase requests to a home-built cloud system, over seven months. Document and entry errors per 100 requests fell from 4.8% to 0.5%. A single case study, published 2025. |
Rules that apply
- AISC 303-22, section 6.6.2, anchor rods and embedded items[9]
- Anchor rods, washers, nuts and other anchorage or grillage materials built into concrete or masonry must be shipped so they are available when needed, and the owner's construction representative must allow the fabricator enough time to fabricate and ship them. The duty runs both ways. Structural steel only.
- AISC 303-22, section 6.6.1, delivery sequence[9]
- Steel is delivered in a sequence that permits efficient fabrication and erection unless the contract documents prescribe one. A field that needs a particular order has to put it in writing.
- AISC 303-22, section 6.6.3, and AISC 207-20 (2020 edition, since superseded), section 1.13.2, shortages and receiving[10]
- A shortage claimed against the shipping statement must be reported to the fabricator promptly so it can be investigated. Certified shops must compare materials they receive against the purchase order and receiving documents. Together they close the loop from site receipt back to the shop.
Measure it in your own shop
From: Your shop order list with due dates, the field's install schedule or three-week lookahead, delivery tickets, and the yard or staging inventory.
- For the last month, list every shop item delivered to site and the date it was actually installed.
- Mark items that arrived after the crew needed them, and items that sat more than a week before install.
- For each late item, find when the field's date changed and when the shop learned of it.
- Count crew hours lost waiting on shop items and the rush orders pushed through the shop.
Reading it: Late items show the field's cost of the gap; early items show the shop's cost in space, handling and damage. The days between a field change and the shop hearing about it is the number to shrink first.
What does not fix it
- Tracking only purchase orders and deliveries
- It tells you what was bought and when it arrived. It does not tell the shop which item the field needs first, which is a schedule date, not a purchase date.
- Building everything as early as possible
- Early items take yard space, get damaged and tie up material and labor that a late item needed. Early and late come from the same missing date.
- A field request form with optional dates
- If the date is optional, it is usually blank. The shop is left guessing from the order date again.
What to try this week
- Match two weeks of missesFor two weeks, write down each time the field or a location waited on the shop, or the shop built something early. Note the job or location, the item, and the date each side learned the real need.
- Make need-by date a required fieldEvery shop order and request carries the date the item must be on site or at the location. If your request form leaves the date optional, make it required, or reject requests without one.
- Hold a standing weekly lineupOnce a week, set the next three weeks of installs, events or location needs beside the shop's open work. Walk each item and confirm its need-by date. Fifteen minutes, same time every week.
- Name one contact on each sideOne person at the point of use and one in the shop pass schedule changes the same day they happen, and each change goes in a log so the next lineup starts from current dates.
- Close the loop on receiptWhen shop items arrive, the person receiving them confirms quantity and condition back to the shop. A shortage reported a week late turns into the next rush.
Where do-it-yourself stops
These steps line the shop up with the field once a week and catch many misses. Between lineups the two schedules still drift, and every change still depends on someone remembering to call. The lasting fix is a tool built around your own schedules and shop orders, so a date that moves at the point of use moves in the shop's work list the same day. That is what a Workflow Spec designs.
Questions people ask
Why does the shop build in the wrong order for the field?
Because the shop sees due dates that were set when the order was written, while the real dates live in the field schedule. When the field moves, nothing tells the shop.
What is the difference between a due date and a need-by date?
A due date is set when the order is written. A need-by date comes from the current install schedule and changes when the field changes. The shop should sort by the second.
Who is responsible for telling a steel fabricator when anchor rods are needed?
Under AISC 303-22 section 6.6.2, the fabricator ships anchorage materials so they are available when needed, and the owner's construction representative must allow enough time to fabricate and ship them. Both sides have a part.
Has anyone measured what a better request process saves?
One published case study, of a single Iranian construction company over seven months with a home-built system, reported procurement lead time falling from 11 days to about 6. It is one company, so treat it as an example, not a benchmark.
How did field requests work before software?
A 2006 study of electrical contractors, Automated Field Material Procurement using Pocket PCs, described a paper requisition listing the material, quantities, the dates needed and cost codes, filled in by the foreman or project manager and sent to purchasing. It called the process mostly paper-based with double entry.
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.
