A completion photo of one balcony cannot represent a building with dozens of different openings. Units may use different panel sizes, balcony shapes, substrates, access restrictions, or approved exceptions. A handover pack should let a property manager locate an opening, identify the installed product and boundary, find its photos, understand any unresolved item, and know who is responsible for inspection or follow-up. The record is a management tool, not a guarantee that conditions will never change.
Build a Hierarchical Project Register
Use project, building, floor, unit, opening, and panel IDs that remain stable across drawings, labels, photos, packing, installation, and service. Avoid using resident names as the primary identifier because occupancy can change. Define orientation consistently, such as looking outward from inside the unit.
The master register should show status: surveyed, approved, manufactured, delivered, installed, exception open, rework required, handed over, or excluded. Dates and responsible parties make the status meaningful.
Record the Product at Each Opening
Identify transparent nylon or wire-reinforced net, mesh size, strand or product specification, color, panel dimensions or drawing reference, edge finish, accessory set, and batch or order reference where available. Keep the two MaxCatNet product types distinct rather than using the generic word 'mesh.'
If several products or colors appear in the project, add a legend. Any field substitution should point to its approved change record. The installed record must reflect what is present, not only what the original quotation listed.
Describe the Boundary and Fixing Context
For each opening, list top, bottom, left, right, corners, panel joints, access details, and major obstructions. Record visible substrate or assembly, fixing method as installed, and the installer-confirmed detail reference. Never reduce the boundary to 'four sides fixed' when posts, pipes, glass railings, open tops, or stepped ceilings are involved.
The handover should flag concealed or uncertain substrate information rather than turning it into a claim. Building permission, drilling restrictions, and installer responsibilities belong with the project record.
Use a Standard Photo Sequence
Take an overall view, each edge, corners, panel connections, access features, obstructions, labels, and any exception. Use the opening ID in the photo log without placing misleading permanent labels on the residence. Photographs should be dated and oriented.
Capture door and window movement where the net interacts with usable openings. Close-ups need context; pair each detail with a wider view. Protect resident privacy by excluding faces, personal documents, and unnecessary interior details.
| Handover Layer | Core Record | User |
|---|---|---|
| Master project register | Units, openings, status, exceptions | Project manager |
| Opening sheet | Geometry, product, boundary, installer detail | Installer and service team |
| Photo log | Overall, edges, corners, access, exceptions | Handover reviewer |
| Resident or operator note | Inspection, access, reporting route | Occupant or manager |
| Exception register | Owner, due date, evidence, closure | All responsible parties |
Keep Exceptions Visible Until Closure
An exception may involve access, substrate, unfinished building work, missing panel, damage, changed geometry, resident restriction, or a boundary that cannot be completed under the approved method. Give each issue an ID, description, location, temporary status, responsible owner, due date, and required closure evidence.
Never mark an opening complete because the majority of its perimeter is installed. If use is restricted pending closure, state that clearly through the responsible site process. Closed exceptions should remain in history with before and after evidence.
Hand Over Inspection and Change Responsibilities
Explain who performs routine visual checks, how residents report damage, who may alter or repair the system, and what events trigger reassessment: window replacement, facade work, railing changes, impact, loose fittings, cut mesh, or access modification. The maintenance guide can support the recurring check.
Provide supplier and installer contact routes, but distinguish product questions from site-fixing responsibility. Handover should also state that the net is intended for cats and is not a child fall-protection system.
Design the Record for Future Service, Not Only Project Closeout
A handover pack may look complete on the day the installer leaves and still fail the first service request. Test the record by asking whether a new property manager can locate Unit B-1204, identify the living-room balcony opening, find its panel and material, see the original perimeter, understand an exception, and contact the responsible installer without relying on the original project team. Missing links should be fixed before archive.
Use file naming that survives transfer between systems. Include stable IDs, date, and revision rather than resident names or camera filenames. A photo index can connect one overall view and each boundary detail to the opening sheet. Keep high-resolution originals in an access-controlled project archive and provide a practical handover copy. Define retention and privacy responsibility under the project and local requirements.
Service history should append to the original opening record. Window replacement, facade access, damage, material repair, panel replacement, or a changed fixing line receives a dated event with before/after photos and approval. Never overwrite the first installed state; it provides the comparison that later work needs. If a unit is excluded or access was unavailable, retain that status visibly in the master register.
The building manager also needs a dashboard of open exceptions and upcoming actions, not just hundreds of individual sheets. Summarize counts by status, responsible owner, due date, and restriction. The summary must always link back to exact openings. This combination of overview and traceability keeps a large project manageable while preventing a whole-building completion statement from hiding one unresolved balcony.
Verify a Sample of Units Before Final Acceptance
Select a documented sample across balcony types, floors, installers, materials, and exception histories. Compare register, panel ID, installed material, boundary photos, access operation, and resident handover. Sampling never proves every unit is identical, so high-risk or exception openings may require full review under the project plan. Record findings and expand the check when a systematic mismatch appears. Correct both the physical work and the master data; a repaired edge with an incorrect panel record leaves future service exposed. Final acceptance should show what was checked, what remained open, and who owns the next action.
Buyer Checklist
- Use stable project, unit, opening, and panel IDs.
- Record actual installed material, mesh, color, edge, and change approvals.
- Describe every boundary, corner, panel joint, obstruction, and access feature.
- Use a consistent overall-to-detail photo sequence.
- Track exceptions with owner, due date, restriction, and closure evidence.
- Give residents or managers a clear damage-reporting and inspection route.
- Require reassessment after building or opening changes.
Frequently Asked Questions
Is one completion certificate enough for a multi-unit project?
A project-level certificate may form part of handover, but opening-level records are needed to trace products, boundaries, photos, and exceptions.
Should resident names appear in panel IDs?
Stable unit and opening identifiers are usually better because occupancy and personal data can change.
Who approves a repair after handover?
The handover should identify the responsible installer, supplier, property manager, and approval route for the actual system.
Related Product or Reading
Use cut-panel identification for multi-opening projects earlier in the workflow so manufacturing and handover share the same panel IDs.
Discuss the Exact Project
Ask MaxCatNet to review the product and panel fields for your handover register, while the project installer confirms site boundaries, fixing details, exceptions, and release.