When to use it
A defect appears near a notice or warranty boundary.
Connect installed assets, warranty documents, maintenance conditions, defect notices and repair acceptance after a property project closes.
Create a register by component, location and supplier. Link the executed contract, manufacturer document, installer warranty, commissioning or acceptance record and equipment identifier. Distinguish different warrantors and coverage types instead of recording one project-wide date.
Read the actual start event, duration, exclusions, notice method and maintenance conditions with the appropriate contract or technical reviewer. Delivery, installation, commissioning, acceptance and registration can be different events. An assumed anniversary date can leave the property monitoring the wrong window.
Identify registration evidence, maintenance obligations, operating limits and records requested by the warranty terms. Assign those activities to the maintenance plan. A warranty register is useful only if the property can produce the supporting evidence when a defect appears.
Keep the notice route and approved recipient current. Staff turnover at a supplier should trigger contact verification. Record relevant notice dates and evidence of transmission; do not infer that a conversation at the site constitutes the required contractual notice.
Record when the issue was first observed, component, location, symptoms, photographs, operating conditions and immediate protective action directed by the responsible professional. Preserve original files and the chronology. Describe the observed condition rather than labeling every failure a covered defect.
Track the contractor's response, requested inspection, proposed repair, exclusions asserted and outstanding technical questions. Keep the property response and specialist conclusion linked. Operational urgency and a warranty dispute may need separate decisions, especially where continued service or protective work is required.
Define who can accept the remedial work and what test, inspection or documentation is required. Record the work performed, replaced parts, dates, remaining conditions and any written change to the warranty. A closed vendor ticket is not necessarily proof that the original defect was resolved.
Update asset history and maintenance instructions after replacement or repair. Maintain a short exception report for unresolved defects, approaching review dates and missing records. Avoid closing an entire project warranty solely because the contractor's final invoice has been processed.
Hypothetical example: a newly installed door operator fails intermittently. The property logs the location, fault time, symptoms and operating conditions, then follows the agreed safety and service escalation. The notice record links the installed unit, acceptance date, warranty terms and maintenance history.
After repair, the designated reviewer checks the required operating evidence and documents remaining issues. The example does not determine coverage or instruct staff to service equipment beyond their competence.
A fictional tracker begins a warranty from a generic project completion date without the applicable agreement or product terms. The governing start and notice basis needs confirmation.
Original fictional example · no completed client assignment or property inspection is represented.
| Record to obtain | Review question or calculation |
|---|---|
| Executed warranty terms | Trace each term to its source |
| Acceptance and product records | Record the proper notice route and supporting evidence |
| Defect observations and notices | Keep unresolved applicability with the responsible adviser |
Useful working output: A source-linked warranty record and an owned defect follow-up.
Open each challenge to test the reasoning against a different finding.
Check: Compare discovery, documentation, notice, delivery and response dates to the actual warranty terms with the appropriate reviewer.
Decision effect: Preserve the chronology and obtain timely contractual guidance. Discovery and compliant notice are different events.
Check: Reconcile required tasks, dates, service evidence and exceptions using original records. Ask the warranty contact what documentation it requires.
Decision effect: Record the gap and next action. Do not manufacture retrospective service evidence to make the file appear complete.
Adapt the record request to authorized access, governing documents and the actual property. The example does not verify any unknown input or replace a professional conclusion.
Capital Project Payment Evidence and Milestone Review · More capital projects and building safety examples
A defect appears near a notice or warranty boundary.
Do not close a claim merely because a provider attended.
Link the asset, acceptance date, applicable document, reported defect and verified corrective result; preserve unresolved rights for adviser review.
Original proposed coordination checks · adapt to authorized access, the actual obligation and the appropriate professional review. These are not findings about your property.
Follow the related handoff workflow · Read the review definitions
A reusable control-definition worksheet. Add property-specific owners, dates, evidence links and status before using it as an action record.
These rows define suggested controls, not completed property findings. Interpret each check against your actual property records, responsible role and acceptance evidence. See the review instructions and reuse terms.
12 checks shown
No check matches those filters. Try a different term or area.
| Review area | Check | Evidence to request | Decision question |
|---|---|---|---|
| Register | Identify installed components | Asset and location schedule | Which component has which warranty? |
| Register | Separate manufacturer and installer terms | Warranty documents | Who provides each coverage? |
| Terms | Confirm actual start event | Acceptance or registration evidence | What event starts the period? |
| Terms | Confirm notice requirements | Reviewed warranty terms | How and to whom must notice be sent? |
| Conditions | Link maintenance obligations | Maintenance plan | What records must the property preserve? |
| Conditions | Verify registration status | Registration acknowledgement | Is required registration documented? |
| Defect | Record observed symptoms and dates | Defect log and original photographs | What was observed and when? |
| Defect | Preserve protective instructions | Professional direction | What immediate action was authorized? |
| Notice | Retain notice and delivery evidence | Notice record | Can transmission be demonstrated? |
| Notice | Track response and dispute status | Supplier correspondence | What remains unresolved? |
| Acceptance | Verify remedial work | Inspection or test record | Did the repair address the issue? |
| Acceptance | Update asset history and terms | Closeout and revised documents | What changed after repair? |
Use the event stated in the actual warranty or contract and retain proof of that event. Do not substitute the invoice date without confirming the terms.
The terms and circumstances matter. Have the appropriate reviewer confirm authorized repair arrangements and preserve instructions before making assumptions about continuing coverage.
Show the component, observed issue, notice status, responsible supplier, next action and decision required. Link sensitive or detailed technical records through the controlled file.