AMC and warranty tracking: renew, claim or replace before the date passes

Every admin head has a story about a warranty that ran out two weeks before the server's disk failed, or an AMC that auto-renewed for a printer that had already been scrapped. Both are avoidable. AMC and warranty tracking is not complicated, but it needs dates in one place, reminders that reach the right person early enough, and a repair log that tells you whether the contract was worth it.

What to record for AMC and warranty tracking

For each asset, and for each service contract, keep a small set of facts:

The link between the two matters most. A contract that says "AMC for 4 split ACs, 2nd floor" is useless when one of them has moved. List the covered assets by code, so a contract and the machines it covers can be found from either side.

Comprehensive vs non-comprehensive AMC

The two main kinds behave very differently when something breaks.

• Comprehensive AMC: labour and spare parts are covered, usually with exclusions for consumables (toner, drums, filters), physical damage and power surges. Higher fee, predictable spend.
• Non-comprehensive AMC: labour and scheduled preventive visits only. Parts are quoted and billed separately. Lower fee, but a compressor or motherboard failure becomes a surprise bill.

A practical rule: go comprehensive for equipment where a single part can cost a large share of the machine (UPS batteries aside, think compressors, controller boards, print heads), and non-comprehensive for simple, cheap-to-fix items. Read the exclusions list either way; it is usually longer than the inclusions.

Reminders that arrive in time

The most common failure is not a missing date but a reminder that reaches the wrong person, or reaches the right person three days before the end.

A sensible default:

Send the AMC renewal reminder to the asset or facilities team first, and copy the department head who owns the budget. Sixty days is not too early: getting two quotes, a purchase approval and a PO through a mid-sized company often takes a month.

A warranty expiry alert is a different kind of reminder. It is a prompt to act while repairs are still free:

1. Run a health check on the items whose warranty ends next month (battery health on laptops, SMART status on disks, a test print on printers).
2. Log every fault found and raise it with the maker before the end date.
3. Decide whether an extended warranty is worth buying for this batch.

A worked example from a Gurugram office

A 300-person office in Gurugram has 280 laptops, 6 multifunction printers, 2 servers, a 40 kVA UPS and 24 split ACs.

• Laptops: 3-year onsite warranty. 90 laptops bought in October 2023 reach the end of warranty in October 2026. IT runs battery and disk checks in September, logs 11 faults and gets them fixed free. They decide not to extend: these laptops will be replaced within a year anyway.
• Printers: non-comprehensive AMC at ₹18,000 a year for all six. The repair log shows ₹46,000 in parts last year, mostly fusers and rollers. A comprehensive quote of ₹52,000 now looks cheap, and they switch.
• UPS: comprehensive AMC excluding batteries. Batteries are tracked as a separate item with their own replacement date.
• ACs: non-comprehensive AMC with four preventive visits a year. The vendor's visit reports are attached to the contract, so a missed visit shows up before renewal.

None of these decisions needed a consultant. They needed the dates, the costs and the repair history in the same place.

The repair log is your evidence

Every repair, service visit and part replaced should be logged against the asset: date, fault, vendor, cost, whether it was under warranty or AMC, and how long the item was down. Most teams log repairs through the IT or facilities helpdesk, where the ticket is linked to the asset, so the history builds up without extra effort.

After a year, the log answers questions that otherwise turn into arguments:

• Did the AMC vendor meet the promised response time?
• How much did we spend on parts outside the contract?
• Which model fails most often?

The repair or replace decision

When a contract comes up for renewal, look at four numbers per asset or model:

1. Age against its expected life. A laptop at 4 years is past the 3-year useful life most companies use in their fixed asset register.
2. Last 12 months' cost: AMC fee plus parts plus vendor visits.
3. Downtime: days out of use, and what that cost the team.
4. Support status: whether the maker still supplies parts and updates.

If the yearly cost is heading towards a third of a new unit's price, or the model is near the end of the maker's support, replacing usually wins. Plan the purchase before the AMC end date, not after.

Do not forget the end of the story

When an asset is retired, end its warranty and contract records too, and remove it from the AMC schedule before the next renewal. Otherwise you will pay to maintain a machine that is sitting in the scrap yard.

Electronic items should go to an authorised recycler or back through the producer's take-back channel. The E-Waste (Management) Rules, 2022 place duties on bulk consumers, and the Central Pollution Control Board publishes the lists of registered recyclers. Keep the handover receipt against the disposed asset.

Small items need the same care at exit as at purchase; our note on tracking bulk IT accessories covers the stock side.

A short checklist

• Every asset has a warranty end date; every contract lists the assets it covers.
• Reminders at 60, 30 and 7 days for contracts, and 30, 7 and 1 for warranties.
• A health check before each batch of warranties ends.
• Every repair logged against the asset, with cost and downtime.
• A renew-or-replace review before each renewal.
• Retired assets removed from contracts before they renew.

In the Asset Manager, warranty and AMC end dates sit on a calendar with reminders, contracts carry their covered assets and a Renew button for the next term, and repairs are logged against each item. A spreadsheet with the same columns and a disciplined owner will get you most of the way too.