--- title: How do I build an equipment warranty register from closeout documents and catch claims before coverage ends with AI? | AEC Agents url: https://aecagents.si/use-cases/warranty-register-from-closeout-documents description: A new building hands over a stack of warranty letters, manufacturer certificates and O&M binders, and the start dates are all different: substantial completion for the contractor's warranty, startup for a chiller compressor, the date of a manufacturer's inspection for the roof. Coverage also often depends on conditions buried in the fine print, like a quarterly service by an approved provider. Have Claude or ChatGPT read each warranty document into one register, and have Copilot in Excel or Gemini in Google Sheets compute end dates from the start trigger you confirm, match open work orders against active coverage and flag maintenance conditions that are falling behind. Whether a failure is covered is decided with the manufacturer or installer, not by the spreadsheet. last_modified: 2026-11-11 source: AEC Agents (free, open workflows; not engineering advice) --- [AI assists](https://aecagents.si/use-cases/warranty-register-from-closeout-documents#honesty-labels)Workflow guide · not independently tested # How do I build an equipment warranty register from closeout documents and catch claims before coverage ends with AI? A new building hands over a stack of warranty letters, manufacturer certificates and O&M binders, and the start dates are all different: substantial completion for the contractor's warranty, startup for a chiller compressor, the date of a manufacturer's inspection for the roof. Coverage also often depends on conditions buried in the fine print, like a quarterly service by an approved provider. Have Claude or ChatGPT read each warranty document into one register, and have Copilot in Excel or Gemini in Google Sheets compute end dates from the start trigger you confirm, match open work orders against active coverage and flag maintenance conditions that are falling behind. Whether a failure is covered is decided with the manufacturer or installer, not by the spreadsheet. [Facilities Manager](https://aecagents.si/roles/facilities-manager) · Facilities & O&M · Claude · ChatGPT · Microsoft Excel · Microsoft Copilot · Google Sheets Content updated 11 November 2026 · Tool links listed below; vendor features and pricing change, so confirm with the vendor ## Short answer Use Claude or ChatGPT, then Copilot in Excel or Gemini in Google Sheets: Claude or ChatGPT reads warranty letters and certificates into one register with coverage, start trigger and conditions copied as written; Copilot or Gemini computes end dates from the start dates you enter, flags expiries, corrective work orders on covered assets and overdue service conditions, and Claude drafts claim notices. A new building hands over a stack of warranty letters, manufacturer certificates and O&M binders, and the start dates are all different: substantial completion for the contractor's warranty, startup for a chiller compressor, the date of a manufacturer's inspection for the roof. Coverage also often depends on conditions buried in the fine print, like a quarterly service by an approved provider. Have Claude or ChatGPT read each warranty document into one register, and have Copilot in Excel or Gemini in Google Sheets compute end dates from the start trigger you confirm, match open work orders against active coverage and flag maintenance conditions that are falling behind. Whether a failure is covered is decided with the manufacturer or installer, not by the spreadsheet. A person still checks: start dates against the completion certificate and startup reports, and every claim and coverage question with the warranty holder before work is done or paid. ## AI tie-in **Tool:** Claude or ChatGPT, then Copilot in Excel or Gemini in Google Sheets Claude or ChatGPT reads warranty letters and certificates into one register with coverage, start trigger and conditions copied as written; Copilot or Gemini computes end dates from the start dates you enter, flags expiries, corrective work orders on covered assets and overdue service conditions, and Claude drafts claim notices. ### Prompt 1 ``` Read these warranty documents [upload]. Build a table with one row per item: system, equipment tag, make, model, serial, warranty holder, coverage as written, start trigger as written, duration, conditions to keep coverage and claim contact. Copy terms exactly and write NOT STATED instead of guessing. Do not interpret coverage. ``` ### Prompt 2 ``` Here are the headers and a few sample rows of my Register tab and my work order export [paste]. Write Excel formulas (or a step-by-step Copilot plan) that compute end dates from the start dates I entered, flag items inside 180, 90 and 30 days, list corrective work orders on assets still under warranty and list conditions with no matching preventive work order in the required interval. Use only my data. ``` **Human check:** Start dates against the completion certificate and startup reports, and every claim and coverage question with the warranty holder before work is done or paid. ## The problem Build an equipment warranty register from closeout documents and catch claims before coverage ends with AI. This is a common, time-consuming task for a facilities manager. ## What this workflow does A new building hands over a stack of warranty letters, manufacturer certificates and O&M binders, and the start dates are all different: substantial completion for the contractor's warranty, startup for a chiller compressor, the date of a manufacturer's inspection for the roof. Coverage also often depends on conditions buried in the fine print, like a quarterly service by an approved provider. Have Claude or ChatGPT read each warranty document into one register, and have Copilot in Excel or Gemini in Google Sheets compute end dates from the start trigger you confirm, match open work orders against active coverage and flag maintenance conditions that are falling behind. Whether a failure is covered is decided with the manufacturer or installer, not by the spreadsheet. **How it works:** AI drafts or analyzes. A person operates the tools, checks the work, and takes action. **Your checkpoint:** The register reflects what the documents say and the start dates you entered. It does not interpret warranty terms or decide whether a failure is covered, and a document marked NOT STATED needs a call to the holder. Claims and disputes go through the warranty holder, and anything tied to a construction contract goes past your project manager or counsel. ## Before you start - Access to the named tool; confirm license, version and cost with the vendor. - A small, non-confidential sample to try the workflow on first. - A qualified person to review the output before it is used. ### Tools and access - [Claude (Anthropic)](https://www.anthropic.com/claude) - [ChatGPT](https://chatgpt.com/) - [Microsoft Excel](https://www.microsoft.com/microsoft-365/excel) - [Microsoft Copilot](https://www.microsoft.com/microsoft-365/copilot) - [Google Sheets](https://workspace.google.com/products/sheets/) ## Follow the steps 1. Collect the closeout warranty letters, manufacturer warranties, extended service agreements and the startup reports that set start dates. Use an AI account your organization allows for building records. 2. Have Claude or ChatGPT read each document into a Register tab: system, equipment tag as written, make, model, serial, warranty holder (installer or manufacturer), what is covered as written (parts, labor, refrigerant, workmanship), the start trigger stated, duration, conditions to keep coverage (service intervals, approved providers, registration) and the claim contact. It copies terms exactly and writes NOT STATED rather than guessing. 3. Enter the actual start dates yourself from the substantial completion certificate and startup reports, then have Copilot in Excel or Gemini in Google Sheets compute end dates and days left, with flags at 180, 90 and 30 days. 4. Match the equipment tags to your CMMS asset list and work order export. Flag corrective work orders on assets still under warranty, so the repair goes to the warranty holder instead of your own budget. 5. Flag warranty conditions against your preventive maintenance history: service visits overdue, registration never sent, and service done by someone other than an approved provider when the document requires one. 6. Before each 90-day flag, walk the equipment and log any defect so the claim is filed while coverage is active. Have Claude or ChatGPT draft a short factual claim notice from the register row and work order, and you send it. ## Try a small example Replace the bracketed fields with your own project details. No tested sample run is published for this workflow yet. ### Sample input ``` Fill in the bracketed [fields] in the text below with your project data. ``` ### Starter prompt ``` Here are the headers and a few sample rows of my Register tab [paste: tag, make, model, serial, holder, coverage as written, start trigger, start date I entered, duration months, conditions, claim contact] and my work order export [paste: work order, asset tag, date, type, description, status]. Write Excel formulas (or a step-by-step Copilot plan) that compute end dates and days left, flag items inside 180, 90 and 30 days, list corrective work orders on assets still under warranty, and list conditions with no matching preventive work order in the required interval. Use only my data and do not decide whether any failure is covered. ``` ### Expected output ``` Not published yet. Treat any output as a draft and check it against the source documents. ``` ## Check the result - Every value, citation or quantity traces back to a source document. - Missing information is marked as missing, not filled in. ## Limits and recovery - The register reflects what the documents say and the start dates you entered. It does not interpret warranty terms or decide whether a failure is covered, and a document marked NOT STATED needs a call to the holder. Claims and disputes go through the warranty holder, and anything tied to a construction contract goes past your project manager or counsel. - Check your organization’s data policy before sharing project files with third-party tools. **Stop or switch when:** The source cannot be verified, permissions are missing, or the result contains unsupported facts. ## Frequently asked questions How does AI help with this? Claude or ChatGPT, then Copilot in Excel or Gemini in Google Sheets: Claude or ChatGPT reads warranty letters and certificates into one register with coverage, start trigger and conditions copied as written; Copilot or Gemini computes end dates from the start dates you enter, flags expiries, corrective work orders on covered assets and overdue service conditions, and Claude drafts claim notices. A person still checks: Start dates against the completion certificate and startup reports, and every claim and coverage question with the warranty holder before work is done or paid. How do I how do I build an equipment warranty register from closeout documents and catch claims before coverage ends with AI?? Collect the closeout warranty letters, manufacturer warranties, extended service agreements and the startup reports that set start dates. Use an AI account your organization allows for building records. Have Claude or ChatGPT read each document into a Register tab: system, equipment tag as written, make, model, serial, warranty holder (installer or manufacturer), what is covered as written (parts, labor, refrigerant, workmanship), the start trigger stated, duration, conditions to keep coverage (service intervals, approved providers, registration) and the claim contact. It copies terms exactly and writes NOT STATED rather than guessing. Enter the actual start dates yourself from the substantial completion certificate and startup reports, then have Copilot in Excel or Gemini in Google Sheets compute end dates and days left, with flags at 180, 90 and 30 days. The full step list is above. Does this use an AI agent or regular software? It is labeled AI assists: AI drafts or analyzes. A person operates the tools, checks the work, and takes action. What tools do I need? Claude, ChatGPT, Microsoft Excel, Microsoft Copilot, Google Sheets. Confirm license, version and cost with the vendor, and try it on a small non-confidential sample first. Has this workflow been tested? Workflow guide · not independently tested. Written from vendor documentation and practitioner use. Labels apply to the steps described here, not every feature of a product. Links were checked when the page was written. ## Where to go next - [How do I turn O&M manuals into an asset register and PM plan with AI, every task cited?](https://aecagents.si/use-cases/om-manuals-asset-register-pm) - [How do I find repeat failures in my work order history by asset, problem and vendor with AI?](https://aecagents.si/use-cases/work-order-repeat-failures-by-asset) - [How do I flag risky contract and spec clauses with AI before legal review?](https://aecagents.si/use-cases/contract-risk-review) - [All Facilities Manager workflows](https://aecagents.si/roles/facilities-manager) - [All Schedules, submittals and project controls workflows](https://aecagents.si/tasks/project-controls) ## Evidence and maintenance Written from vendor documentation and practitioner use. Labels apply to the steps described here, not every feature of a product. Links were checked when the page was written. - [Claude (Anthropic) (vendor site)](https://www.anthropic.com/claude) - [ChatGPT (vendor site)](https://chatgpt.com/) - [Microsoft Excel (vendor site)](https://www.microsoft.com/microsoft-365/excel) - [Microsoft Copilot (vendor site)](https://www.microsoft.com/microsoft-365/copilot) - [Google Sheets (vendor site)](https://workspace.google.com/products/sheets/) ## Put it to work Start with a small sample and keep the original record open while you verify the result. ## Know what does the work. Agent executes : An AI agent calls connected tools to carry out bounded actions. You set permissions and review the result. AI assists : AI drafts or analyzes. A person operates the tools, checks the work, and takes action. Conventional automation : Rules or specialist software perform the task. No AI agent is required.