Route a post-handover defect
A practical reference for building operators
Start with the asset and handover context, then ask Project and Property Operations to verify the applicable source records before contractor routing. This page uses the fictional Northbank Works mixed-use property as a coordination example. It covers post-handover defect reports, not routine maintenance; applicable contract terms and approved local procedures take precedence.
Identify the asset and handover context
Use identifiers to find the right source record; they do not establish coverage.
Capture the property or project, building and area, asset or system, relevant handover date or package reference, and a concise description of what was reported or observed. These details help distinguish similar equipment, locations, and handover packages.
If the asset or package is uncertain, record what is known and ask Project and Property Operations to help resolve the record match. Do not infer warranty applicability from a location, date, or asset label alone.
Illustrative Northbank Works reference
Fictional coordination examples only—not a live record, contract extract, or coverage decision.
| Example asset or system | Handover context | Sample document reference | Routing role to verify |
|---|---|---|---|
| East Tower, Level 1 plant-room door; reported leak nearby | East Tower package ET-04; sample handover date 14 March 2025 | ET-04 closeout index, section 6.2 (fictional reference) | Project and Property Operations owner verifies the source contract and identifies the appropriate door-installation contractor role, if applicable |
| West Pavilion, lobby lighting control | West Pavilion package WP-02; sample handover date 30 April 2025 | WP-02 closeout index, section 4.1 (fictional reference) | Project and Property Operations owner verifies the source contract and identifies the appropriate controls-contractor role, if applicable |
Worked example: report near the plant-room door
An operator receives a report of a leak near the East Tower Level 1 plant-room door. The operator records the location and describes the report without assuming its source, then matches the area to the fictional ET-04 handover package. They note when the issue was reported or observed and gather available relevant photographs or handover context without carrying out an inspection or repair.
The operator sends that context through the established Project and Property Operations route. The owner checks the source contract and handover record, then verifies whether the door-installation contractor role is the appropriate route. A separate report about a worn floor finish in the same corridor would be assessed through the routine maintenance route; being nearby does not make it a defect-liability case.
Evidence to assemble
Share available facts; do not wait for a perfect record to raise an ownership question.
Location and asset
Name the property, building, level, room or area, and asset or system identifier where known.
- Use identifiers that distinguish this location from similar areas.
Observation
Record when the issue was reported or observed and describe what was seen or reported in neutral terms.
- Separate observed facts from suspected cause or responsibility.
Handover context
Include the package name, reference, or date that may help locate the source record.
- Mark uncertain identifiers as unconfirmed rather than guessing.
Available supporting material
Share relevant photographs or records with enough context to identify what they show.
- Do not describe a sample reference as proof of coverage.
Common routing questions
Use the responsible owner to resolve record and contract questions.
What if I cannot identify the asset or handover package?
Send the known property, building, area, and reported issue through the established Project and Property Operations route. Ask the owner to help identify the asset and source handover record; do not guess a package or contractor.
What if no warranty reference is listed?
A missing reference does not confirm that coverage exists or does not exist. Share the available asset and handover context with Project and Property Operations so the owner can check authoritative contract and closeout records.
How do I distinguish this from routine maintenance?
Use the applicable local process and source records. A post-handover report may require contract and handover verification; an ordinary upkeep issue follows the established routine maintenance route. Location alone does not decide the route.
Who confirms contractual applicability and contractor routing?
The accountable Project and Property Operations owner verifies the applicable contract and handover records and coordinates the appropriate contractor handoff. This page does not make a coverage decision or promise a response time.
Hand off the context
The responsible owner verifies the source records before contractor routing.
This reference does not submit a case, grant approval, determine coverage, or promise a response time.
-
1
Send the available context
Use your organization's established Project and Property Operations route to share the asset, location, observation, handover details, and available evidence.
-
2
Owner checks the source records
Project and Property Operations verifies the authoritative contract and handover records and resolves uncertain ownership or applicability.
-
3
Coordinate the appropriate route
Where applicable, the responsible owner coordinates the handoff to the contractor identified by the verified records.