Contract Management for Blade Supply: Delivery, Acceptance and Remedies

Two decisions are taken at every delivery under a blade supply contract: whether the lot conforms, and what happens if it does not. A contract is enforced by those two decisions being taken consistently, and most of the difficulty in managing one comes from deliveries accepted without either decision being recorded.

This decision path follows the sequence a contract administrator actually faces: calling off against the award, inspecting on receipt, handling non-conformance, controlling substitutions, applying remedies, and keeping the records a later audit or claim will need.

Delivery schedules and call-offs

Call-offs are where a contract’s commercial terms meet the fleet’s season, and the two questions at each call-off are how much and when. The quantity should be drawn against the awarded total, with the running balance recorded, so that the position is known without reconstructing it from delivery notes.

Two practices keep call-offs simple. Placing them in writing against the contract reference, even where the relationship is informal, so the audit trail exists. And placing them early enough to respect the lead time the award assumes, since a call-off issued late converts a scheduled delivery into an expedited one and moves the risk of the schedule onto the supplier in a way the contract may not support.

Inspection on receipt

Receipt inspection is the point at which the specification becomes enforceable, and it needs three things: a stated set of dimensions or properties to check, a stated method, and a recorded result. Without the third, the first two produce no evidence.

The dimensions worth checking on every lot are the ones that decide fitment, with the rest sampled. The method should be the one named in the contract, so that a later dispute is settled by re-measuring rather than by argument. The record should tie the result to the lot’s batch reference, which is what allows a template to be reused for every delivery without ambiguity.

Non-conformance handling

Non-conformance has a defined sequence, and following it is what protects both the fleet and the supplier.

Quarantine the lot and mark it so it cannot be drawn into a build. Record the measurement, the method and the requirement it failed, quoting the clause. Notify the supplier in writing with those facts rather than with a description. Then apply the route the contract provides — concession, replacement or rejection — and record which was used and why. The step most often skipped is the first, and using a quarantined lot during a busy week is the single event that turns a resolvable delivery question into a failed blade and a weakened claim.

Short shipment and substitution

Treat a substitute as a different problem from a shortfall.

The table below sets out how each is assessed, which clause applies, and what the usual response is when a delivery does not match the call-off.

The third row is worth understanding rather than resisting. A part inside its stated tolerance is conforming however much it differs from the previous lot, and a fleet dissatisfied with that outcome should change the tolerance in the next specification rather than reject a compliant delivery.

Remedies and escalation

Remedies work when they are applied in the order the contract sets out and when the earlier steps are recorded. The sequence is usually a written notification, a request for corrective action, a defined period for the supplier to respond, and then the contractual remedy if the response does not resolve the issue.

The value of the sequence is that each step produces a record. A fleet that escalates directly to a remedy without the earlier notifications is relying on goodwill rather than on the contract, and a fleet that never escalates has a contract that is not being managed at all.

Performance reviews

A review at a fixed point in the season gives the fleet a chance to raise patterns rather than incidents. The items worth reviewing are the lots delivered against the call-offs, the non-conformances with their causes, the lead times actually achieved against those quoted, and any substitution that was requested or supplied.

Raising a pattern is more productive than raising an incident, because it gives the supplier something it can act on. A review that says four of nine lots arrived late is more useful than one that lists nine delayed deliveries without a common cause.

Records and audit trail

The records that make a contract auditable are the ones generated by the process rather than assembled afterwards: the call-offs, the receipt inspections with their results, the non-conformance notifications and outcomes, and the substitution assessments.

Two further items belong with them. The batch reference of each lot, which links the delivered material to its production record. And the specification revision the lot was produced to, so that a later comparison knows which document applied. How those records support a claim is described on the warranty documentation page.

• Call-offs, recorded against the contract reference and the running balance.
• Receipt inspection results, with the method used and the dimensions checked.
• Non-conformance notifications, with the clause cited and the outcome recorded.
• Substitution assessments, where an alternative was offered or supplied.

What a managed contract produces

A contract managed this way produces two things beyond compliance. A supplier who knows the deliveries will be measured tends to deliver to the stated tolerances, which is the practical effect of a fleet that records its inspections. And a season’s worth of records that show the specification’s actual performance, which is the evidence the next tender is built on.

That second output is the one fleets most often forgo. Without it, the following award is made on the same assumptions as the last, and no amount of contract administration changes the specification that produced the outcome. The way those records feed an evaluation is described on the weighted scoring page, and the receiving routine that produces them is set out on the delivery inspection page.

Handling a delivery problem under time pressure

Most contract management failures happen in a week when material is needed urgently. The two responses that preserve the position are to accept the delivery with a recorded reservation rather than silently, and to keep the quarantine separate from the material in use.

A recorded reservation gives the fleet the option to pursue the question later without having stopped the route. Accepting without a record loses that option, and the fleet discovers at the end of the season that it has no evidence of what it accepted. Material and test standards that support the measurements involved are published by ASTM International and ISO, and public sector contract practice by the National Association of Counties and the American Association of State Highway and Transportation Officials.

SENTHAI manufactures plow edges, wear plates and carbide inserts in Rayong, Thailand, and issues each lot with the batch reference and dimensional record that receipt inspection and contract administration depend on. Deliveries that need their documentation or acceptance criteria confirmed can be raised through the contact page.