Replace optimistic expediting percentages with evidence

Start with the order, approved technical scope, required site date and agreed delivery terms. Identify the actual sequence of design approvals, material availability, manufacturing, inspection, documentation, packing, dispatch and receipt relevant to the package. Do not impose a generic manufacturing sequence on equipment whose process differs.

For each milestone, identify what evidence establishes completion and who can accept it. A supplier's statement may support a forecast; a required inspection release may need a different authority. Keep these evidence types distinct.

ERPNext's Purchase Order documentation provides an example of recording item requirements and dates. The useful expediting model goes further by connecting the order to the package-specific milestones and the project's need. The order date alone does not explain delivery readiness.

In this fictional example, the supplier's 90 percent refers to its internal estimate of manufacturing effort completed. It does not include the required test appointment, release documentation or transport. Record that definition rather than converting it into 90 percent delivery readiness.

The expediter asks for the remaining manufacturing activities, evidence of completed milestones, the proposed test date and confirmation from the relevant parties. If the appointment is unconfirmed, show it as a forecast with an unresolved dependency. The buyer's assessed delivery position should reflect that uncertainty.

Avoid replacing one unsupported percentage with another calculated from equally weighted milestones. Completing nine of ten milestones does not necessarily mean 90 percent of the time, cost or delivery risk has passed. Show the milestones and the critical unresolved dependency directly.

A dated production record may support a manufacturing milestone. A photograph may show a particular assembly, provided its identity and date are clear. An inspection report may establish the result of a defined inspection. None automatically proves that the entire package is ready for dispatch.

Ask for evidence that answers the specific question rather than demanding a large weekly document dump. If the concern is an unconfirmed test appointment, another photograph of completed fabrication is unlikely to resolve it. Record the source, date and limitations of each update.

Keep the supplier's original statement and the buyer's assessment separately. If the assessment differs, explain why. This gives commercial and project managers a transparent basis for escalation without presenting an internal judgement as though it were a supplier commitment.

A package may depend on a subvendor component or a buyer approval. Identify those dependencies and their owners. A supplier delay report that ignores an outstanding buyer response will misstate the position; a buyer report that accepts every supplier explanation without evidence is equally weak.

For each dependency, record the required input, promised date, latest evidence and effect on the next milestone. If the impact is uncertain, ask the responsible planner or technical owner to assess it. The expediter should not invent a schedule consequence from a late email alone.

Preserve changes to forecast dates. A current date without the previous commitment hides slippage. Review the reason for movement and whether the proposed recovery depends on additional approvals, resources or risks that the project has not accepted.

A supplier may offer to dispatch part of the package while the balance remains unfinished. Assess whether the partial shipment supports usable work at site, meets the agreed release conditions and can be received, stored and identified properly. Shipping something is not automatically a useful recovery measure.

Keep item-level quantities and package completeness visible. Record what remains, its dependencies and the evidence needed before the next dispatch. Commercial and logistics owners should assess the contractual, cost and handling implications of the proposed split.

At receipt, reconcile what arrived against the dispatched scope and site acceptance records. A dispatch milestone should not be used as proof of site receipt or quality acceptance. The invoice and receipt matching guide shows why those states must remain distinct downstream.

For each package, show the site need date, latest supplier forecast, assessed forecast, unresolved dependency and next owner. Focus the meeting on changes since the last review and decisions needed. Keep stable background detail available without reading it aloud every week.

Escalate the specific issue: confirm a test appointment, resolve a technical query, obtain release evidence or approve a logistics option. Record the response and the revised forecast basis. An escalation labelled expedite urgently does not tell the recipient what would unblock the package.

A controlled register may be enough for a small number of critical packages. A procurement platform helps when many suppliers, documents and milestones interact. Compare tools using the unconfirmed-test example and a partial-dispatch case, including exports and history retrieval.

The test is whether a new project manager can understand what is complete, what remains uncertain and what must happen before the package reaches site. A lower-confidence forecast with visible evidence is more useful than a precise date unsupported by the remaining work.

1. Select a critical package and define its real delivery milestones and acceptance evidence.
2. Ask the supplier to explain the basis of its percentage and forecast.
3. Assign unresolved appointments, approvals and subvendor dependencies to owners.
4. Review forecast changes against site need dates and retain the evidence behind each movement.