Track long-lead materials against the work that needs them

Illustrative example: a process-plant pump is required for an installation activity on 24 June. Assume the approved project procedure requires receipt inspection and document acceptance before release for that activity.

The readiness gap is four calendar days, from 24 to 28 June. Arrival alone appeared four days early. The relevant package owner can now see the real issue: document acceptance, rather than transport.

This does not establish a four-day delay to project completion. The planner must assess calendars, available float, work sequencing, resource constraints and any authorised recovery option. The commercial team separately assesses contractual implications from the actual facts.

Begin with the work package or activity that needs the material. Confirm what “ready” means for that use. A pump may need different evidence for unloading, installation, testing and commissioning. Avoid one readiness date that implies all four stages are authorised.

Then map the required steps: technical approval, vendor drawings, manufacturing release, production, inspection, dispatch release, transport, receipt and acceptance. Some can run in parallel; others depend on an earlier decision. Record the dependencies that matter rather than copying a generic milestone list into every package.

For the pump example, assume transport takes five elapsed calendar days and receipt inspection takes another two, starting immediately on arrival. To be ready on 24 June, dispatch must occur by 17 June and arrival by 22 June. Documents reviewed in parallel must also be accepted by 24 June. Adding their review duration to transport would overstate the chain if the work can genuinely overlap; ignoring them would understate it. Recalculate using the project's working calendars, review availability and agreed allowances before treating those dates as a plan.

The engineering owner validates technical prerequisites. Procurement owns the commercial order and supplier follow-up. The inspector or quality owner confirms the relevant checks. Logistics owns transport evidence, and the planner owns the relationship to the programme. Each milestone should have one person responsible for the next update.

Keep the supplier’s committed date, the project’s current forecast and the actual completion date. Also retain the baseline or approved need date. If every update replaces the previous promise, the team loses the history needed to understand repeated slippage.

A supplier email saying “dispatch next week” is a commitment or forecast input. A release note and transport evidence support a different level of confidence. Record the evidence date and the next verification action, especially for a forecast that has not changed for several reporting cycles.

If a critical prerequisite has no credible forecast, show readiness as unknown or conditional. Do not fill the gap with the need date and display the package as on time. The next action is to obtain a supported forecast from its owner.

Use a short reason for each forecast movement: drawing review, material procurement, manufacturing capacity, inspection, transport or project-side prerequisite. Free text can explain the detail, while consistent reason categories help the team identify recurring causes.

A useful long-lead register includes package ID, related activity, need date, forecast readiness, current constraint, accountable owner, supporting reference and next action date. Display the age of the last verified update.

“Pump P-204 at risk” is less useful than “P-204 documents returned for correction; vendor response due 18 June; engineering review owner assigned; readiness forecast 28 June against 24 June need”. The second version tells the meeting what can be acted on.

For multiple delivery lots, split the quantities or equipment identities that support different work fronts. A package can be partly usable. Conversely, delivery of most components may not help if one missing component blocks the whole assembly. The package engineer should define that dependency.

A procurement register can provide evidence for schedule updates, but it should not silently move the approved baseline. The planner reviews actuals and forecast dates in the scheduling system, records the reason for changes and assesses downstream effects.

A package reported as 95% complete can still miss its need date if the last prerequisite blocks release. Keep progress percentages alongside the dated dependency chain; they answer different questions.

An ERP purchase-order record helps maintain ordered quantities and supplier commitments; ERPNext’s purchase-order documentation describes that purchasing record. The readiness register may need engineering and inspection inputs held elsewhere. Link those sources by stable package and document IDs rather than manually copying a single status into every system.

When a gap appears, ask which prerequisite can change and who has authority to change it. The team might accelerate a document response, arrange a required inspection, adjust an approved delivery sequence or ask the planner to evaluate alternative work. Any technical substitution or changed acceptance requirement remains with the qualified owner and applicable approval process.

Avoid asking the software to declare a substitute equivalent or to bypass an inspection to recover time. Its useful role is to make the constraint, evidence and consequences easier to review.

Measure forecast reliability at a fixed look-ahead, the age of unverified dates and the number of unresolved readiness gaps. Track causes as well as lateness. If most gaps arise before order placement, expediting transport will not address the main problem.

Long-lead tracking improves decisions when it joins a material package to a particular use at a particular date. The register should make a late prerequisite visible early enough for its owner to act.

1. Select the packages most relevant to upcoming constrained activities.
2. Define readiness for each activity with engineering and quality owners.
3. Map the prerequisites, evidence and accountable owners.
4. Compare verified readiness forecasts with the planner’s need dates.
5. Review gaps and document the authorised action without overwriting the baseline history.