Long-lead item tracker

Job register

The things whose delivery date drives the job, and the last thing the supplier actually told you.

The four items that decide the job

On most jobs there are three or four items whose delivery date sets the finish, and everybody knows what they are until somebody leaves. This is the list, with the order number, the supplier and the last thing they said, so chasing it is a two-minute job rather than an archaeology exercise.

It predicts nothing

No lead-time data, no forecast, no schedule impact and no escalation. The tool holds the dates you were given and the updates you received. Everything else is a conversation with a supplier, which is where it belongs.

Around it

Approvals before the order go on the submittal log. What arrives is the material delivery log, and if a late item stops work, the schedule delay log is where that gets recorded.

A register of orders and the dates suppliers gave you. It holds no lead-time data, predicts no date, calculates no schedule impact and makes no claim against any supplier. Everything runs on your device.

Questions people ask

Does it know how long anything takes to make?
No. There is no lead-time database in this product, nothing is looked up, and no date is predicted. Every date here is one a supplier gave you, typed as they gave it — which is the only date worth writing down, because it is the one you can hold them to.
Does it work out what a late delivery does to my program?
It does not. No impact is calculated, no float is consumed and nothing on this list touches a schedule. If a slipped date matters, that is a conversation and, if you decide it held work up, a row on the schedule delay log.
Why record the last thing the supplier said?
Because “they said the middle of March” three weeks ago is a different fact from the same sentence today, and by the time it matters nobody remembers which. The response field is dated by the row's own history, so the story of a slipping item is readable rather than remembered.
Is this the same as a submittal log?
No. A submittal is the approval process before an order is placed — shop drawings going out and coming back. This is the order itself and the wait afterwards. Most long-lead items pass through both, and the submittal number is a sensible thing to note here.