Procurement is the quietest part of an office fitout and usually the one that decides the handover date. Nothing on site moves fast if the right items have not been ordered in the right sequence weeks earlier. Yet procurement is rarely discussed as a decision process in its own right. Tenants tend to treat it as a long list of things that will be bought at some point, when it is actually a series of decisions that each depend on the previous one and each carry a cost if they are made in the wrong order.
The useful way to think about procurement is as a decision framework, not a shopping list. Each item belongs somewhere in the sequence, and the right question is not “when will we buy this” but “which decision unlocks the order for this”. Answering that for each element of the scope is what keeps the programme honest. The questions below are the ones we walk through internally before committing orders on a fitout.
Question one: is the design stage actually finished for this item?
The first filter on any procurement decision is whether the underlying design is complete enough to commit to. A joinery order placed while the concept is still in flux will come back as a variation when the design is finalised, and the rework usually erases any time savings. A flooring order placed before the layout is locked will end up short or long once the walls settle.
Design completeness is not a single gate for the whole project. Different items reach design completeness at different stages. The concrete test is whether the drawing for a specific item would survive the next round of client review unchanged. If yes, the item is ready to price and order. If no, the order is premature regardless of how long the lead time looks.
Tenants who push orders ahead of design resolution are usually trying to save calendar days, but the programme saving rarely materialises. The pattern around where programmes slip almost always includes at least one premature order that had to be changed mid-build.
A useful second test on design readiness is whether the drawing for the item has passed services coordination. An item that looks ready on an architectural drawing but has not been reconciled against the ceiling grid, the mechanical ducts, or the electrical circuits is still at risk. A joinery wall that clashes with a sprinkler head or a light fitting on the engineer’s drawing will need to be changed, and the change rarely gets back to procurement before the order has already gone out.
Question two: what is the honest lead time, including delivery and install prep?
Published lead times are rarely the full story. A quoted six-week joinery lead usually excludes final shop drawing sign-off, factory scheduling realities, freight windows, and the few days it takes to stage delivery on site. The effective lead time from order to “installed and commissioned” is usually a week or two longer than the quote suggests, and the gap matters more at the tail of a programme than the middle.
The decision framework question here is not “can we hit the quoted lead time” but “can we hit the full cycle including the steps the quote does not cover”. Items that pass this test can be held until later. Items that fail it need to be committed earlier than the quoted lead time implies. Long-lead procurement discipline is usually a function of the cycle, not the quote.
Question three: does this item unlock other trades?
Some items only affect themselves. A run of acoustic wall panels can land late without disrupting anything else. Other items hold up whole trades. A joinery delivery that slips by a week can push flooring, electrical fit-off, and commissioning into the same compressed window. Glazing that arrives late can prevent the ceiling from being closed. Specialty lighting that is delayed can freeze the electrical handover.
The framework question is: if this item arrives two weeks late, what else stops. Items that stop other trades belong at the front of the order queue regardless of their own lead time. Items that only affect themselves can wait. This is the single most useful filter in procurement sequencing, and it is also the one most commonly skipped because it requires thinking about dependencies rather than lists.
Question four: what is the cost of a wrong order versus the cost of a late order?
Procurement carries two distinct risks that need to be priced separately. A wrong order is the cost of an item that arrives and does not fit the final design. A late order is the cost of an item that fits but arrives too late to install without pushing the programme. The two risks push in opposite directions: the first says wait, the second says commit early.
The answer is item-by-item, not blanket. For high-customisation items, the cost of a wrong order is high and the cost of a late order is usually absorbable, so waiting for design resolution is the right answer. For commodity items with long shipping windows, the cost of a late order is high and the cost of a wrong order is low, so committing early is the right answer. Collapsing these into a single rule is how procurement decisions drift into variations. The framework around why variations happen and how to prevent them usually includes a procurement decision that did not sit on the right side of this question.
Question five: who is responsible for the order and the interface?
Procurement is rarely a single person’s job on a large fitout. The builder places orders for trade-specific items. The designer or fitout manager places orders for joinery, finishes, and specialty items. The tenant sometimes places orders for IT, AV, and furniture. Each handoff between these parties is a place where an order can stall or slip.
The decision framework question is whether each item has a clear owner, a clear decision deadline, and a clear interface point. Items with ambiguous ownership are the ones that end up late because everyone assumes someone else is handling them. The discipline is to put a name against every order at the end of design development, not at the start of construction. Where tenants underestimate the coordination load around procurement, they often also underestimate the cost of having too many people involved in the same decision chain.
Question six: does the order survive a single round of design review?
The last filter before committing an order is to test it against the most recent round of design review. If the review introduced any change that touches the item, directly or indirectly, the order is not ready. If the review left the item untouched, the order is ready even if the review raised questions about adjacent items.
This is the moment where procurement either moves cleanly or leaks time into the build. A disciplined team will walk through the open orders after every design review and mark which ones are cleared and which ones need to wait. A loose team will rely on memory, and something will slip. The small habit of running this check is what separates a procurement cycle that holds from one that gets patched during construction.
Question seven: what does the programme look like if this item is the one that slips?
The final framework question is a stress test: for each item on the procurement list, imagine it is the one that arrives late and ask what the programme does. If the answer is that the programme absorbs it without trouble, the item is low risk. If the answer is that the programme loses a week, the item is medium risk. If the answer is that the programme loses the handover date, the item is high risk and belongs under active tracking regardless of how simple it looks.
This question is worth asking explicitly rather than leaving it implicit in the programme. Every project has three or four items where the answer is “everything stops”, and those are the items that deserve weekly attention from the fitout manager rather than being buried in a procurement schedule. Following the correct build order is only possible when these critical items are ordered against the build sequence rather than against a generic procurement calendar.
The discipline of naming these items early also changes how the project team talks about risk. Instead of a vague sense that “procurement might be tight”, there is a short list of three or four specific items whose status drives the programme. Weekly meetings can then focus on those items rather than cycling through the full schedule. Tenants who see this list often realise for the first time how much of the programme is sitting on the status of a handful of specific orders rather than the overall trade schedule.
If you are planning a fitout and want help deciding which items belong on which week of your procurement schedule, we can help you walk through a complete office fitouts procurement framework against your specific scope and lead times.
📞 Call us on 1300 60 93 93