Warranty Claim Deadline Example
A full worked example for procurement teams. Replace the sample numbers with your own project, supplier, contract, or approval data before using the wording in a live file.
Visual example: file-note structure
The practical claim deadline is earlier than the expiry date when notice and response time matter.
Situation
A pump was commissioned on 15 January 2026 with a 12-month supplier warranty. Operations reports abnormal vibration in December 2026. The purchase terms require warranty issues to be notified at least 30 days before expiry where possible.
Procurement must calculate the last practical claim date and start supplier follow-up before the warranty becomes disputed.
Inputs
| Input | Example entry |
|---|---|
| Warranty start basis | Commissioning date |
| Commissioning date | 15 January 2026 |
| Warranty duration | 12 months |
| Warranty expiry | 15 January 2027 |
| Notice period | 30 days |
| Last practical claim date | 16 December 2026 |
| Evidence needed | Photos, vibration report, PO, warranty certificate |
Decision
Procurement should notify the supplier before 16 December 2026 and log the claim. Waiting until the expiry date leaves too little time for inspection, replacement, or dispute resolution.
Supplier email wording
Suggested wording: We are notifying a warranty issue for the pump commissioned on 15 January 2026. Abnormal vibration was observed and supporting evidence is attached. Please confirm inspection date, warranty coverage position, and proposed corrective action before the warranty period expires.
What to watch before using this
Warranty dates are often disputed because teams use different start points. Delivery date, installation date, commissioning date, handover date, and practical completion date may all create different answers. Confirm the contract basis before writing to the supplier. Keep defect evidence, photos, operating logs, warranty certificate, and first notification email together so the supplier cannot reject the claim because the file is incomplete.
How this would sit in an approval file
In a warranty file, procurement should show the warranty start basis, expiry date, last practical claim date, defect discovery date, supplier notification date, and evidence collected. The file should make it clear whether the warranty started from delivery, installation, commissioning, handover, or another contract event. This matters because a supplier may reject a claim if the buyer relies on the wrong start date.
The buyer should keep defect photographs, inspection notes, maintenance records, delivery documents, warranty certificates, commissioning records, and supplier email acknowledgements together. A warranty issue often fails because the team waited too long or could not prove when the defect was reported.
Common mistakes in this situation
- Waiting until the final warranty expiry date before notifying the supplier.
- Using delivery date when the contract starts warranty from commissioning or handover.
- Sending a claim without defect evidence or maintenance records.
- Failing to track supplier response and replacement commitment.
Manager review wording: Procurement should issue the warranty notice before the last practical claim date and keep the claim open until supplier responsibility, action, and closure evidence are recorded.
Buyer review checklist
Before sending the warranty notice, procurement should check whether the defect evidence is strong enough for the supplier to act. Attach photographs, serial numbers, delivery notes, commissioning records, maintenance logs, and a short description of when the defect was first observed. If the issue may be caused by installation, misuse, or poor maintenance, the technical team should review the file before the supplier is blamed.
The follow-up owner should also be named. Warranty claims often fail after the first email because nobody tracks supplier response, inspection date, replacement promise, or closure evidence. The file should remain open until the defect is repaired, replaced, credited, or formally rejected with reasons.
Evidence to attach
- Supplier quotation, technical request, or project instruction.
- Calculation output from the matching I Love Procurement tool.
- Emails, approvals, dates, or supplier evidence supporting the assumptions.
- The matching template download completed with your real values.