Schedule deliveries backwards from the date the material is installed, not forwards from when the supplier can ship — then check that date against site access, storage and any permit you need to occupy the road. AI is good at the reconciliation: it compares purchase order promise dates against the schedule dates and flags every item that has drifted.
Key takeaways
Two failures cost the same amount of money and look nothing alike. The first is material that arrives late and stops a crew. The second is material that arrives three weeks early and has to be moved twice, gets rained on, blocks the only route into the building, and eventually turns up damaged on the day it is needed.
The fix is a habit rather than a tool: plan each delivery backwards from the installation date, subtracting the time to unload, stage, and inspect, and then check that the resulting date is physically and legally possible. AI helps by doing the reconciliation nobody has time for — comparing what the supplier promised to what the schedule now needs, every week, across every open purchase order.
For each material item, four dates matter: when it is needed at the workface, when it must be on site to be staged and checked, when it must ship to arrive by then, and when the order must be placed to hit that ship date. Only the first comes from the schedule; the other three come from the supplier and from your own site.
This is why the procurement horizon is longer than the field horizon. A three-week window is right for crews; materials need a longer look. Procore, for instance, generates lookaheads from the master schedule with a selectable window of one to six weeks, and the six-week end of that range is the one procurement should be watching. Whatever tool you use, run two horizons.
Access and standing time. Where does the truck stop, for how long, and who unloads. A delivery that needs a picker for forty minutes on a residential street is a different event from one dropped in a compound.
Storage. Interior storage before the envelope is closed is usually the binding constraint on small sites and is what pushes finishing material deliveries later than everyone would like.
Permits. This is the one most often missed on small jobs. The City of Toronto requires a Street Occupation Permit before starting a demolition, renovation or construction project where you plan to temporarily occupy any portion of the public right of way, alongside a construction permit for work within the right of way itself and a municipal road damage deposit. Other municipalities run equivalent regimes under different names. If your delivery plan involves the curb lane or the sidewalk, the permit lead time is part of the delivery lead time.
Inspection dependencies. Material that closes something up should not arrive before the inspection that has to happen first — and inspections have booking windows of their own, with Toronto taking requests from the next business day up to four weeks in advance.
The weekly delivery reconciliation
One row per open purchase order: item, supplier, quantity, promised date, required-on-site date derived from the schedule, variance in days, storage location, and who receives it.
Three flags worth automating: late (promised after required), early by more than the storage window, and silent (no confirmation from the supplier this week). The third one catches more problems than the first two combined.
A model can draft the chase email for every flagged row, referencing the PO number, the item and the date you need. A person reviews the batch and sends it.
Delivery records matter twice: once when you are arguing about a short shipment, and again when someone asks six months later when the material was on site. Construction management platforms build this in — Procore’s daily log includes “Delivery Entries”, alongside delay, manpower, equipment, quantity and observed weather entries, with photographs attachable to entries so they populate the photos tool. If you are not running a platform, the same three fields in a shared sheet will do: what arrived, what was short or damaged, and a photograph.
Dictating that record at the gate and letting a model turn it into structured entries is a reasonable use of the technology, because the failure mode of delivery records is that they are never written, not that they are written badly.
Materials create payment exposure that outlives the delivery. In Ontario a supplier or subcontractor with no direct contract with the owner can still have lien rights against the property — our sister firm addresses whether a lien claim is possible with no privity of contract. On the other side of the same relationship, an owner has statutory obligations about what must be withheld as holdback under the Construction Act. Neither of those is a scheduling matter, but both are reasons to keep delivery and payment records that agree with each other.
The Construction Act goes further than giving suppliers lien rights: every amount a contractor or subcontractor receives on account of an improvement, including any holdback owed to them, is by law held in trust for the subcontractors and suppliers who are owed money for that improvement, and a contractor who spends it on something else before those suppliers are paid has broken a statutory trust, not just missed a payment.
A builder in Surrey is framing three townhouse blocks. Windows are the long-lead item and the supplier quoted a date in week 14.
The weekly reconciliation flags the window order as silent in week 9 — no confirmation for eleven days. A drafted chase produces the real answer: the promise has slipped to week 17. Because the flag came in week 9 rather than week 14, the builder re-sequences the envelope work, moves the interior partition framing forward, and books temporary weather protection instead of losing three weeks of interior progress.
None of that required a prediction. It required someone to notice a silence, which is precisely the sort of noticing software is better at than people.
Keep the commitment with a person. Drafting a purchase order, checking it against the take-off and flagging a price or quantity that does not match the quote are all reasonable automations. Issuing a binding order is a commercial commitment and should be signed.
It is the right instinct where storage is tight, but it moves all the risk onto the supplier’s reliability. The honest version of just-in-time is a short buffer on the items that stop a crew and a longer one on anything with a single supplier.
Write the delivery protocol into the purchase order: notice period, permitted hours, contact on site, and what happens if it arrives without notice. Then log every breach. A pattern is a conversation with the supplier; an isolated complaint is not.
It usually does, in the general conditions covering delivery, storage, title and risk of loss. Standard-form Canadian contracts and their guides are published by the Canadian Construction Documents Committee, including CCDC 20, a guide to construction contract administration. Read what your contract says about who carries the risk in stored material before you accept an early delivery.
A 30-minute call is enough to tell you whether AI pays for itself here.