Warranty register builder
A warranty register that dates every item from its own taking over rather than the project’s, and works out the expiry dates itself.
The seamThe contractor’s defects period and the supplier’s warranty on the same item: two obligations, two clocks, two expiry dates, and one owner left holding both.
A warranty register with one end date on it is wrong, and it is wrong the same way under both regimes this site has sourced. FIDIC 2017 defines a defects period for the Works, for a Section and for a Part, and a Part gets one year even where the Works it sits in was agreed to be longer. The Saudi GTPL Executive Regulations start a separate warranty period from the date each shortcoming is received. Two regimes drafted independently both run the clock per item, so the unit of this register is the item.
The second point is the one that costs money. Remedying a defect does not restart the contract period: Sub-Clause 11.3 extends it, caps the extension at two years beyond the stated expiry, and in 2017 allows one only where the defect results from an act listed in Sub-Clause 11.2(a) to (d). A supplier’s warranty on a replaced component may restart, because a new component carries new terms. A register that restarts both records an end date later than the real one, so the owner believes it holds cover it does not hold.
Only the regimes that give a per item anchor date and a stated period. For the rest, work the periods out in the handover calendar first.
Each period here is cited to its clause and linked to free published commentary on that clause. Check your Contract Data and any Particular Conditions: every one of these periods can be amended, and on most Gulf contracts at least one has been.
The register sheet holds the header row and one row below it, and that row carries the formulas whether or not you asked for the example values: the computed columns are part of the template. Copy it down. Dates arrive as real dates rather than as text, so the sheet can do arithmetic on them, and every formula tests for an empty cell first so an unfilled file opens clean. The mark and the reasoning are on the sources tab and in the file properties, and neither touches the grid.
How this is built, if you want it
The workbook is assembled in this browser without a third-party library, which is why nothing you type reaches a server: there is no upload step to reach one through.
Warranty register
2026-10-01. projects-advisors.com/tools/warranties
One row per warranted item, dated from that item’s own taking over. Four columns are computed by the workbook from the columns beside them; the rest are recorded, and each says what requires it.
| Column | What it holds, and what requires it |
|---|---|
| Asset tagRequired | The shared key. The same string identifies this item in the technical and financial registers, which is what lets somebody holding a failed asset find out whether it is still under warranty.This publication. The asset tag is what lets a warranty log be joined to the asset registers of the same organisation. ISO 55001:2024 treats data and information in Clause 7.6; the tag is not attributed to it. What this proposal rests on, and what would show it wrong. |
| DescriptionRequired | What the warranted thing is.What the thing is, in words the maintenance team would also use. |
| Location | Where it is, at the resolution somebody could walk to.This publication. A warranty claim needs the item found and inspected inside the notice period, and an item nobody can locate is one nobody claims on. What this proposal rests on, and what would show it wrong. |
| Part or Section it belongs to | Which Part or Section was taken over, because that is what fixes this item’s dates.FIDIC Conditions of Contract, 2017 edition, Sub-Clause 11.1: the obligation to remedy runs to the end of the DNP for the Works, for a Section or for a Part. Which one this item sits in determines which period applies to it. |
| Taking over or initial receipt dateRequired | The date THIS item was taken over, not the date the project was.FIDIC 2017, Sub-Clause 1.1.27 and 11.1, and Saudi GTPL Executive Regulations Article 128(1), which starts a separate period of the contractor’s warranty from the date each shortcoming is received. Both regimes date the period from the item, and a register that dates every row from one project handover is wrong under both. |
| Contract defects period, monthsRequired | The period the Contract Data actually states for this item. Twelve is the fallback where none is stated, not the norm.FIDIC 2017, Sub-Clause 1.1.27: the DNP is the period stated in the Contract Data, or one year if none is stated. Tyson notes that a Part does not exist when the Contract Data is written, so a Part gets one year even where the Works or Section it sits in was agreed to be longer. |
| Contract defects period expiresComputed | Taking over date plus the contract defects period in months.Computed. FIDIC 2017 Sub-Clause 11.1 runs the contractor’s obligation to remedy to this date, and every retention release, bond release and performance certificate on the project hangs off it. |
| Furthest an extension can carry itComputed | Contract defects period expiry plus two years.FIDIC 2017, Sub-Clause 11.3: an extension may not carry the DNP more than two years beyond the expiry of the period stated in the Contract Data, and in the 2017 edition an extension is available only where the defect results from an act listed in Sub-Clause 11.2(a) to (d). The 1999 edition allowed one wherever the defect affected the Works. |
| Is it Plant | Yes or no. The two-year tail in the next column is for Plant only, so the sheet has to be told which items are.FIDIC 2017, Sub-Clause 11.10 limits liability for unfulfilled obligations "in respect of Plant". Whether an item is Plant is a contract question with a two-year consequence, and a register that leaves it implicit computes that tail for the car park barriers and the landscaping too. |
| Liability for Plant endsComputed | Where the item is Plant, the contract defects period expiry plus two years. Otherwise blank.FIDIC 2017, Sub-Clause 11.10: liability for unfulfilled obligations in respect of Plant is limited to two years after the end of the DNP for that Plant, unless the law provides otherwise or in cases of fraud, gross negligence, deliberate default or reckless misconduct. The clause says "for that Plant", which is the standard assuming a period per item. |
| Manufacturer or supplier | Who gave the second warranty, which is a different party.The supplier’s or manufacturer’s warranty is a separate obligation from the contractor’s defects liability under FIDIC 2017 Clause 11, so it needs its own party on the row. |
| Supplier warranty starts on | The event the supplier’s or manufacturer’s own warranty terms name as the start of cover, in their words: delivery, installation, start-up, energisation, taking over, or something else. Blank until the terms have been read.This publication. The start of a supplier’s or manufacturer’s cover is whatever its own warranty document names. It is not set by the construction contract, and this register does not assume it is taking over or any other event. Recording the named event beside the date lets anyone check the date against the document. What this proposal rests on, and what would show it wrong. |
| Supplier warranty start date | The date the named event actually happened for this item. Not the taking over date unless the warranty names taking over.This publication. A supplier’s warranty runs from the event its own terms name, which need not be taking over. A chiller whose warranty runs from delivery in August, and which is taken over in November, is out of supplier cover three months before a register dated from handover would say. What this proposal rests on, and what would show it wrong. |
| Supplier warranty, months | Whatever the supplier’s own terms say, which is not 12 by default.The supplier’s warranty document. There is no standard period; the number comes from the certificate referenced two columns along. |
| Supplier warranty expiresComputed | Supplier warranty start plus the supplier period in months.Computed. The two expiry dates on this row are different dates and the gap between them is the owner’s exposure: after the earlier one lapses, whatever it covered is the owner’s cost. |
| Warranty certificate reference | The document. A warranty nobody can produce is not a warranty.The Saudi national turnover procedure requires a warranty log to be available at turnover, and a log pointing at no documents does not satisfy it. |
| What voids it | Servicing intervals, approved parts, operating limits, commissioning by the maker. Anything the cover is conditional on.This publication. Neither FIDIC 2017 Clause 11 nor the national turnover procedure requires the conditions to be recorded, and they are a way an owner can lose cover it is still paying for: the condition sits in a document filed at handover while the maintenance contract that has to satisfy it may be written by somebody who never saw it. What this proposal rests on, and what would show it wrong. |
| Who to notify to claim | The named route and the notice period, if the warranty sets one.This publication. The Saudi turnover procedure requires the entity to designate a warranty administrator; it does not require the route recorded per item, and a warranty administrator with no route on the row is a title rather than a control. What this proposal rests on, and what would show it wrong. |
| Defect notified | When the defect on this item was notified, if one has been.FIDIC 2017, Sub-Clause 11.1: the Employer notifies, and the notice is what starts the remedying obligation. It is also the evidence that the defect appeared inside the period. |
| Remedied | When it was put right.FIDIC 2017, Sub-Clause 11.4: what happens next depends on whether the contractor unduly delayed, and that is measured from these two dates. |
| What the repair did to each period | The contractor’s period and the supplier’s period do not behave the same way after a repair. Record which changed and on what authority.This publication. Sub-Clause 11.3 extends the DNP and does not reset it, and caps any extension at two years beyond the stated expiry; a supplier’s warranty on a replaced component may genuinely restart, because a new component carries new terms. A register that restarts both records an end date later than the real one, so the owner believes it holds cover it does not hold. What this proposal rests on, and what would show it wrong. |
| Status | In force, Remedied, Expired, or Claimed and refused, exactly as written; the workbook accepts only these four.This publication. Refused is the value worth having, because a refusal names the condition the warrantor relies on. The ground itself goes in the next column. What this proposal rests on, and what would show it wrong. |
| Ground of refusal | Required where the status is claimed and refused: the ground the warrantor gave, in its own terms, with the date and reference of the refusal. Leave blank otherwise. The workbook accepts Claimed and refused as a status only once this cell is filled; it cannot notice the cell being cleared afterwards, and a pasted value bypasses the rule.This publication. A refusal states which condition the warrantor relies on. Recorded on the row, it is what lets the maintenance arrangements be checked against the condition, and a register with nowhere to put it loses it. What this proposal rests on, and what would show it wrong. |
Computed from
- Tyson, FIDIC 2017: Clause 11, Defects After Taking Over, Howard Kennedy (FIDIC 2017 second edition, clause commentary; read 2026-09-25)https://internationalconstructionknowledgehub.com/wp-content/uploads/VT-FIDIC-2017-Clause-11-Defects-After-Taking-Over.pdf
- Saudi Government Tenders and Procurement Law and its Executive Regulations, consolidated Arabic text, third edition (third edition, the law in force until the new law takes effect; amendments to the regulations after this edition are not consolidated in it; read 2026-09-25)https://www.mof.gov.sa/Knowledgecenter/newGovTendandProcLow/Documents/%D8%B1%D8%A8%D8%B7%20%D9%86%D8%B8%D8%A7%D9%85%20%D8%A7%D9%84%D9%85%D9%86%D8%A7%D9%81%D8%B3%D8%A7%D8%AA%20%D9%88%D8%A7%D9%84%D9%85%D8%B4%D8%AA%D8%B1%D9%8A%D8%A7%D8%AA%20%D8%A7%D9%84%D9%84%D8%A7%D8%A6%D8%AD%D8%A9%20%D8%A7%D9%84%D8%AA%D9%86%D9%81%D9%8A%D8%B0%D9%8A%D8%A9%20-%20%D8%A7%D9%84%D8%A5%D8%B5%D8%AF%D8%A7%D8%B1%20%D8%A7%D9%84%D8%AB%D8%A7%D9%84%D8%AB.pdf
- Executive Regulations of the Government Tenders and Procurement Law (2019 Executive Regulations, amended 1 September 2026; to be re-issued with the new law; read 2026-09-03)https://www.mof.gov.sa/en/Knowledgecenter/newGovTendandProcLow/Documents/Executive%20Regulations.pdf
- Government Tenders and Procurement Law, new law published in Umm Al-Qura 22/3/1448 (4 September 2026), Arabic (gazetted 4 September 2026; in force 120 days after publication; read 2026-09-05)https://www.uqn.gov.sa/decisions-and-regulations/4001762
- ISO 55001:2024, asset management system requirements (2024 edition; read 2026-09-26)https://www.iso.org/standard/83054.html