Lead Time and Order Tracking Preparation Checklist

Walk through the project room by room and write down everything that has to be bought rather than built, however small it seems at this stage.

Small items with long lead times cause as much disruption as large ones and are far less likely to be on anybody's list.

Mark against each item who is ordering it, and separate the ones you are buying from the ones somebody else is buying.

Two parties buying into the same project on different assumptions is the usual source of a gap in the list.

Ask whoever is running the works what else will need ordering that you have not listed, and add whatever they name without editing it.

Trades know the ordinary long-lead items in their own area, and the answer is usually specific and short.

Mark any item whose availability you have been told is uncertain, and treat those differently from items simply described as taking a while.

Uncertainty and duration are different problems requiring different responses, and mixing them hides the more dangerous one.

Note which items have to arrive before other work can proceed, since those are the ones whose delay reaches beyond themselves.

An item that blocks following work has a different weight from one that can be fitted whenever it arrives.

Keep everything in one list rather than a separate note for each supplier, because the point of the list is seeing the items together.

Separate notes per supplier reproduce exactly the fragmentation the tracker exists to fix.

Ask the supplier or the person ordering what information they need before an order can be placed, and record their answer item by item.

Ordering information often includes details an owner would never think of, and the gap is usually discovered at the worst moment.

Write the decision that sits behind each item next to it, in the same row, so the two are never looked at separately.

An owner asked for a decision out of context cannot see what it is holding up, which is why decisions drift.

Mark where one decision cannot be made until another is settled, and note which of the two has the earlier order behind it.

Chained decisions are how a single late choice reaches several orders at once.

Note any item that cannot be ordered until something physically exists on site, such as an opening that has to be measured.

These items cannot be brought forward by deciding earlier, which makes them a sequence problem rather than a decision problem.

Ask the supplier what has to be complete before they can measure; that condition is theirs and is not negotiable by you.

Record who is waiting for each decision, so you know who to tell when you make it rather than announcing it generally.

A decision made and not passed on has the same effect as a decision not made.

Mark any choice you have made provisionally, since a provisional choice cannot be ordered against and is easily mistaken for a settled one.

Provisional choices harden into settled ones simply by sitting in a list, which is worth guarding against explicitly.

Decide a small fixed set of fields for every row, such as the item, who orders it, the decision behind it, and where things stand.

A fixed handful of fields is far easier to complete consistently than a free-form note, and gaps become obvious at a glance.

Include a field for what has to happen next and who does it, rather than only a field describing the current state.

Without a next-action field, a tracker becomes a description of the past and stops prompting anybody.

Order the list by which item needs deciding soonest rather than by room or by supplier, and re-sort it when the picture changes.

Ordering by urgency is what makes the top of the list the thing to deal with today.

Keep each row short and factual, with the correspondence filed elsewhere and referenced rather than copied into the tracker.

Trackers that accumulate narrative stop being readable and are abandoned within a few weeks.

Decide whether the tracker is shared with anyone else, and if so, be clear that it is your own record rather than an instruction.

A shared owner list can be read as a direction to a supplier, which is not what it is for.

Never treat an entry in your own tracker as placing or confirming an order; only the party ordering can do that.

Fill in a handful of rows for items already settled and see whether the fields hold them before the pace picks up.

Reworking the structure is easy while there are a few rows and painful once there are many.

Decide what you will treat as confirmation that an order exists, and apply the same test to every item rather than to some of them.

A consistent test is what makes a gap visible; an inconsistent one hides exactly the items you would most want to catch.

Ask for written confirmation of each order, including what was ordered and when it is expected, and file it against the row.

Verbal reassurance about an order is the commonest form of information in this area and the least useful.

Read what was actually ordered against what you chose, particularly any reference or variant, rather than assuming they match.

References transcribed loosely point at a different item, and the error usually surfaces only on delivery.

Where what was ordered differs from what you chose, raise it with whoever placed the order before anything is delivered or installed, rather than deciding yourself whether the difference matters.

For items ordered by somebody else, ask them to confirm the order exists rather than inferring it from a conversation about the item.

Discussing an item and ordering it are separate events that sound very similar in a project conversation.

Keep the not-yet-ordered rows visible at the top rather than filed with the completed ones, since those are the live risk.

A tracker that sorts completed and outstanding items together hides the only part that still needs attention.

Ask each supplier when it would be sensible to check back on an order, and put that date in the tracker as a next action.

Suppliers usually give a straightforward answer, and it converts waiting into something with a date attached.

Set a regular point at which you read the whole tracker rather than only the rows somebody has asked you about.

Rows nobody has mentioned recently are exactly where a quiet slip is sitting.

At each conversation about the works, ask specifically about the items that block following work rather than about deliveries in general.

A general question gets a general answer; a named item gets a specific one.

Record each expected date you are given and keep the earlier ones visible, so a pattern of movement is apparent rather than only the latest position.

A date that has moved repeatedly is telling you something a single current date cannot.

Treat a supplier who has gone quiet as a signal in its own right, and follow up rather than reading silence as everything proceeding.

Silence is the most common form an emerging delay takes before anybody describes it as one.

Tell whoever is affected as soon as a date moves, rather than waiting until you know what will be done about it.

Early notice gives the people arranging the work options that late notice removes.

Ask what the new date affects beyond the item itself, including any work that was waiting for it and anybody already booked.

The reach of a delay is what matters, and it is rarely described in the message announcing it.

Ask what alternatives exist, what each of them would involve elsewhere on the project, and whether any of them would need an earlier decision revisited.

Alternatives usually exist and usually carry a consequence somewhere else, which is worth surfacing together.

Whether an alternative item is suitable is a matter for a suitably qualified professional and for the people installing it, not a decision to take on availability alone.

Ask whether part of the order can arrive earlier, and whether receiving part of it helps or creates a storage problem instead.

Partial delivery is sometimes offered and is not always an improvement once storage and protection are considered.

Record what you were told about the delay, by whom and on what date, in the row for that item rather than in your messages.

Keeping the history in the row means the whole story of an item is in one place when it matters.

Decide what you are doing, tell everybody affected, and update the row, rather than leaving the item in an undecided state.

Undecided rows accumulate and are the ones that later look like nobody was paying attention.

Record what actually arrived against each row, including any variant or substitution, rather than assuming the order description is what came.

What was ordered and what arrived can differ, and the row is the natural place to note it.

Extract the supplier, the reference and the specification of each installed item into one short list to keep with the papers after completion.

This list is what makes a later repair or replacement a short enquiry rather than an investigation.

Note where any spare material is stored and what it belongs to, since spares are lost by being unlabelled rather than by being thrown away.

Spare material is only useful if the next person can tell what it matches.

Read the tracker through for rows still open at the end of the works and ask what became of each one before everybody leaves.

Open rows at completion are the items most likely to become a question nobody can answer later.

Archive the working detail and keep the short list, rather than handing on a long record nobody will read.

A short, readable list survives a change of ownership; a long one does not.