Warranty Documentation for General Contracting
Warranty Documentation defines how all product, system, and workmanship warranties are collected, checked, organized, and handed over at the end of the project. It covers requirements from the contract, documents from subcontractors and suppliers, and the way this information is packaged so that facility staff can actually use it. The process also establishes how warranty start dates, durations, and claim procedures are recorded for future reference. When followed, the project leaves behind a clear, usable warranty record instead of a pile of loose paperwork.
Define warranty documentation requirements and standards
Step 1: Review contract and specifications for warranty requirements
Read the contract, general conditions, and specification sections that describe warranties. Note durations (for example, one-year workmanship, five-year roof), special coverage (for example, weatherproofing, equipment), and any format requirements for documentation.
Step 2: Identify client-specific warranty expectations
Ask the client or their representative whether they have a standard format or list of required warranty documents. Some clients have their own templates, online portals, or minimum requirements for what must be included.
Step 3: List all systems and components requiring warranties
Create a list of systems and components that typically have warranties: roofing, waterproofing, windows, doors, flooring, mechanical equipment, electrical gear, fire alarm systems, specialty finishes, etc. Use the specs to confirm which items are actually warrantied.
Step 4: Define minimum documentation for each warranty
For each warranty type, write down the minimum documentation you expect: warranty certificate, terms and conditions, registration confirmation if applicable, coverage period, and contact information for service.
Step 5: Document warranty standards in a short guideline
Summarize what you found in a 2–3 page guideline that explains which warranties are required, what documents must be collected, and in what format (PDF, original paper, or both).
Step 6: Review standards with project manager and key subcontractors
Walk through the guideline with the project manager and major subcontractors so they understand what will be required at closeout. Adjust any unrealistic requirements in coordination with the design team and client.
Set up warranty document tracking log
Step 1: Choose log format (spreadsheet or software field)
Decide whether you will track warranties in a spreadsheet, in your project management platform, or both. Pick a format that you can update easily and that the project manager can also view.
Step 2: Define columns for key information
Include columns such as system/component, location, subcontractor, supplier/manufacturer, warranty duration, required document type, received date, reviewed status, and notes. Add a column for “included in client package” so you can mark when it is fully processed.
Step 3: Pre-populate log with known warranty items
Using your warranty standards list, enter all major systems and components that require warranties. Leave received and status fields blank for now; this becomes your checklist.
Step 4: Store the log in a shared project folder
Save the log in a common project directory where the superintendent, project engineer, and project manager can access it. Control editing rights so only a few people can change the data to avoid accidental deletions.
Step 5: Explain the log to project team
Show the log to the team in a short meeting and explain how it will be used. Make it clear that any time a warranty document is received, it should be recorded in this log.
Step 6: Update the log regularly
Set a recurring reminder (for example, weekly during closeout) to review and update the log. Mark new warranties received, note which ones need follow-up, and share status in closeout meetings.
Collect warranties from subcontractors and suppliers
Step 1: Send formal warranty request letters
Prepare and send a written request (email or letter) to each subcontractor and key supplier listing the specific warranties you require from them, the format, and the due date. Reference contractual obligations and your warranty guideline.
Step 2: Tie warranty requests to pay applications or retainage
Coordinate with the project manager or accounting so that final payment or retainage release is contingent on receipt of required warranties where allowed by contract. Clearly communicate this linkage to subcontractors.
Step 3: Follow up with regular reminders
A week or two before the due date, remind subcontractors of outstanding warranties. After the due date passes, follow up more frequently with a clear list of exactly what is missing.
Step 4: Receive and log incoming warranty documents
As warranties arrive (by email or paper), record each document in the warranty log with the received date. Save digital copies into the appropriate folder and note any missing pages or signatures.
Step 5: Request missing details or corrections
If a warranty is incomplete, missing signatures, missing coverage dates, or obviously boilerplate that does not match the project, respond back with specific corrections needed. Avoid accepting vague or generic paperwork that will not help later.
Step 6: Maintain a “missing warranties” list
Keep a filtered view or separate list of systems/components that still do not have warranties on file. Use this list in closeout meetings so everyone knows which items are holding up full completion.
Collect operations and maintenance (O&M) manuals and maintenance requirements
Step 1: List all equipment and systems needing O&M manuals
From the equipment schedules, submittals, and specifications, list all equipment that should have an operations and maintenance manual: HVAC units, boilers, chillers, pumps, panels, fire alarm systems, specialty equipment, etc.
Step 2: Request O&M manuals from subcontractors
Send a request to each relevant subcontractor asking for digital O&M manuals for the equipment they furnished and installed. Specify preferred format (searchable PDF where possible) and due dates.
Step 3: Verify manuals cover installed models
When manuals arrive, skim them to confirm they match the actual equipment make and model used on the project. If they cover a product “family,” ensure the specific installed model is clearly included.
Step 4: Identify maintenance tasks and intervals
For each major piece of equipment, note recommended maintenance tasks and intervals (for example, “change filters every 3 months,” “inspect belts annually”). This information will be important for the client’s operations team.
Step 5: Organize O&M manuals by system and location
Save manuals in a folder structure that mirrors how the building is organized (for example, Mechanical Room 1, Roof Equipment, Level 2 Electrical). This makes it easier for maintenance staff to find the right manual later.
Step 6: Link O&M manuals to related warranties in the log
In your warranty log, add references or links to where the related O&M manual is stored. This ties maintenance instructions and warranty coverage together for future use.
Review warranties for coverage, terms, and start dates
Step 1: Open each warranty and read key sections
For every warranty in your log, read at least the coverage description, duration, start date, exclusions, and claim procedure sections. Focus on the practical details rather than legal language you cannot change.
Step 2: Confirm coverage matches contract expectations
Compare warranty duration and scope to what is specified in the contract and specs. If coverage is shorter or narrower than required, flag the discrepancy and discuss it with the project manager and subcontractor.
Step 3: Check that start dates are correct and clear
Identify how the warranty start date is defined (for example, date of substantial completion, date of startup, date of invoice). If no start date is shown, plan to document one yourself in your log at project completion.
Step 4: Note any maintenance conditions
Pay attention to any maintenance requirements that are explicitly tied to keeping the warranty valid. Make a note of these so they can be highlighted to the client later.
Step 5: Record key details in warranty log
For each warranty, enter the confirmed coverage period, start date (or rule for start date), and any special conditions in the log. This turns individual documents into a usable summary.
Step 6: Address any obvious gaps with trades or suppliers
If a warranty is clearly non-compliant or missing essential information, contact the subcontractor or supplier and request a corrected document. Escalate to the project manager if they resist providing the required coverage.
Organize warranty documents by system, location, and vendor
Step 1: Decide on primary organization method
Choose whether the main structure of the warranty package will be by system (HVAC, electrical, roofing), by building area (Building A, Building B, floors), or a combination. Consider how the client’s maintenance team thinks about their building.
Step 2: Create digital folder structure and binder layout
Build corresponding folders for each system or area in your electronic files. If preparing physical binders, plan sections and tab labels that match the digital structure so both sets align.
Step 3: Assign each warranty to a primary category
Using your log, assign each warranty to one primary system or area folder, even if it could fit in multiple places. Aim to reduce duplication while keeping things logical for end users.
Step 4: File digital warranties into appropriate folders
Save each reviewed warranty PDF into its designated folder, using clear file names that include the system and vendor (for example, “RTU-1 – ABC Manufacturer Warranty.pdf”).
Step 5: Prepare physical copies if required
If the client requires hard-copy binders, print key warranty documents and file them behind the correct tabs. Use good-quality paper and avoid tiny, unreadable print.
Step 6: Update warranty log with folder references
Note in the log where each warranty is stored (folder path and binder section). This creates a map between the tracking tool and the final filing system.
Create client-facing warranty summary and quick reference
Step 1: Decide on summary format (table or booklet)
Choose a format that matches the client’s preferences and project size. A concise table may work for smaller jobs; a short booklet or section within the closeout manual may be better for larger projects.
Step 2: Select key fields to show
For each warranty, include fields such as system/component, location, warranty duration, coverage start date, service contact name/phone/email, and notes about special conditions.
Step 3: Populate the summary from the warranty log
Use your warranty log to fill in the summary document. Double-check that dates and contact details match the underlying documents before finalizing.
Step 4: Group information by system or building area
Arrange the summary so the client can quickly find information when a problem arises—for example, group all mechanical equipment together or group by floor or building wing.
Step 5: Write a short “how to use this document” section
At the front of the summary, include simple instructions explaining how to look up warranty information and what to do before calling for warranty service (for example, gather model and serial number, describe the issue).
Step 6: Format the summary clearly
Make sure the summary is easy to read: use clear headings, enough spacing, and simple fonts. Avoid squeezing too much text onto a single page at the cost of readability.
Create internal warranty response and claims procedure
Step 1: Identify internal contacts for warranty issues
Decide who will be the primary and backup contacts for warranty calls (for example, service coordinator, warranty manager, or project manager). Note their phone and email in the procedure.
Step 2: Define how warranty requests are logged
Specify how incoming issues will be recorded: in a service ticket system, spreadsheet, or dedicated warranty log. Include fields for date, client contact, location, description of problem, and urgency.
Step 3: Describe initial response steps
Outline how quickly clients should receive a response (for example, within one business day) and what the first responder should do: acknowledge receipt, ask clarifying questions, and check the warranty summary for coverage.
Step 4: Define how subcontractors will be notified
Explain how your team will contact responsible subcontractors when a warranty issue relates to their work. Include expectations for response time and who will coordinate access to the site.
Step 5: Include guidance for non-warranty issues
Describe what happens if an issue is not covered by warranty (for example, out-of-scope damage, expired coverage). Outline how the client will be informed and, if appropriate, how a service quote will be prepared.
Step 6: Document and store the procedure with closeout materials
Write the procedure in clear, step-by-step language and store it with internal project records. Provide a brief version or contact info section to the client so they know whom to call.
Review warranty package with client and obtain acknowledgment
Step 1: Schedule a closeout meeting focused on warranties
Arrange a meeting with the client’s facilities or operations staff specifically to review warranties and maintenance information. Avoid trying to squeeze this into the last five minutes of a general meeting.
Step 2: Prepare sample pages and key highlights
Bring the warranty summary, a sample of detailed warranties, and key O&M manuals to show the structure. Highlight critical systems and any unusual warranty conditions.
Step 3: Explain where documents are stored
Show the client how to access the full warranty set: shared drive, physical binders, online portal, or USB drive. Confirm that at least two people on their side know how to reach the information.
Step 4: Walk through a sample warranty scenario
Describe a typical situation (for example, rooftop unit failure) and walk them through how they would use the summary to identify coverage and who to call. This makes the process more concrete.
Step 5: Clarify any special procedures or limitations
Discuss any warranties that have unusual conditions, such as required annual inspections by the manufacturer or limitations on who can perform repairs. Make sure the client understands these clearly.
Step 6: Obtain written acknowledgment of receipt
Ask the client to sign a simple acknowledgment that they received the warranty documentation and summary and that you reviewed how to use it. File this acknowledgment in your closeout records.
Archive warranty documentation in company systems
Step 1: Create a final “Warranty – FINAL” folder
Within the project’s file structure, create a clearly named folder for final warranty documents and related logs. Keep this separate from working drafts and correspondence.
Step 2: Save all warranty-related files into the final folder
Move the final warranty summary, individual warranty PDFs, O&M manuals, logs, and client acknowledgment into this folder. Make sure file names are clear and match what the documents actually contain.
Step 3: Confirm backup coverage
Check that this folder is included in your company’s regular backup process (cloud, server, or both). Coordinate with IT if necessary to ensure long-term retention.
Step 4: Note warranty key facts in project closeout report
In your internal project closeout or handoff report, summarize where warranties are stored and list any critical warranty details (for example, extended roof warranty, long-lead equipment coverage).
Step 5: Restrict editing of final warranty files
Change permissions on the final warranty folder so that most users have read-only access. This prevents accidental changes to official documents after closeout.
Step 6: Use warranty archive in future claims or reference
If a warranty claim or question arises in the future, use this archive as the starting point. Encourage staff to reference the stored warranties before promising free work or making commitments.
👈 Use this SOP template inside Subtrak
Edit with AI. Customize in seconds. Store and share all your SOPs and checklists in one place.