Handover is where a construction project becomes somebody's workplace. If the last week is spent chasing paint touch-ups while manuals, tests and asset information are missing, the client receives a room but not a usable operating system. Close-out should be designed at the start.
For a Pune or Mumbai project, the useful question is not whether a design looks current. It is whether the brief, building, services, procurement and operating rules agree. The following framework is written for decision-makers who need a workplace that can be priced, built, occupied and maintained.
Define practical completion
Agree what must be complete before the client occupies: life-safety approvals, access, power, cooling, lighting, toilets, clean surfaces, furniture, technology, signage and agreed testing. Define what can remain open under a controlled snag list and what prevents use.
Use a room or area readiness schedule. It makes partial handover visible and stops a general statement such as 'the site is ready' from hiding a meeting room that has no display or a floor whose services are not commissioned.
Build the as-built record
As-built drawings should reflect what is actually installed: partitions, doors, services, circuits, data, equipment, controls and access. Record revisions and locations. A drawing that shows the design intent but not the final route is a future maintenance trap.
Keep the record digital and searchable where the client can use it. Link assets to room names or numbers consistently. This is less glamorous than a final photograph and considerably more useful when a fault occurs.
Test building services
Document the agreed tests for electrical, HVAC, lighting controls, fire systems, plumbing, access, AV and network-related interfaces. The exact tests depend on the project and authorities. State who witnesses, who signs and what happens when a result is outside the agreed range.
Use professional references and the building's requirements carefully. BEE offers official energy-efficiency context and CIBSE provides engineering knowledge resources, but the project engineer remains responsible for the applicable test method and record.
Give facilities the keys to operation
Training should cover normal operation, resets, maintenance access, filter or consumable information, vendor contacts, warranties, cleaning, safety and escalation. Split sessions by role. A facilities manager does not need the same explanation as a room user.
Ask the operator to perform the routine tasks while the installer observes. This reveals missing labels, inaccessible panels and undocumented assumptions. A training attendance sheet is evidence of a session, not evidence that the system can be operated.
Close the snag list properly
Each snag needs a location, description, owner, due date, status and verification. Use photographs where they clarify the issue. Distinguish a cosmetic defect from a functional failure and prioritise anything that affects safety, access, water, comfort, technology or business use.
Reinspect after the fix. A contractor's message saying 'done' is not verification. The person who accepts the item should be able to point to the corrected condition and the record should retain that decision.
Carry the project into the DLP
The defects-liability period needs a contact route, response expectation, visit rhythm and escalation path. Record recurring faults rather than closing each call in isolation. Patterns can indicate a design, installation or operating problem.
Schedule a post-occupancy review after the workplace has been used. The Vektor process and contact route provide the start of the conversation. A good handover is not the end of accountability. It is the point where accountability becomes operational.
Before approval, ask three plain questions. What is known from the site or the client? What is still an assumption? What will prove the decision worked after installation? Put the answers beside the relevant drawing, schedule or source. This keeps the conversation honest when the project moves from strategy to design, from design to procurement and from procurement to handover.
A decision checklist for the project meeting
Use this checklist to turn the article into a controlled next step. It is intentionally practical: each item should have a named owner, a source or drawing, a decision date and a test that another person can verify. If an item is still an assumption, label it as one. That is not a weakness. It is a warning before the assumption reaches procurement or site work.
- Define practical completion: define the owner, evidence, decision date and acceptance test before the drawing or order is released.
- Build the as-built record: define the owner, evidence, decision date and acceptance test before the drawing or order is released.
- Test building services: define the owner, evidence, decision date and acceptance test before the drawing or order is released.
- Give facilities the keys to operation: define the owner, evidence, decision date and acceptance test before the drawing or order is released.
- Close the snag list properly: define the owner, evidence, decision date and acceptance test before the drawing or order is released.
- Carry the project into the DLP: define the owner, evidence, decision date and acceptance test before the drawing or order is released.
For a live project, carry the open questions into the brief, cost plan, programme and handover record. The team should be able to tell what is confirmed, what is provisional, what is excluded and what will be checked after installation. That discipline is more valuable than adding another adjective to the design description.
Decision matrix for this project
This guide is most useful when it becomes a project control. Use the table below to assign an owner, retain the evidence and define what will count as done. It keeps a design conversation connected to procurement, site work and handover.
| Decision area | Question to answer | Evidence to retain |
|---|---|---|
| Acceptance | What must be tested before the client takes over? | Agreed test schedule and sign-off |
| Records | Which as-builts, assets and warranties will be delivered? | Indexed close-out register |
| Operation | Can facilities run and maintain the installed systems? | Manuals, setpoints, training and contacts |
| Defects | How are remaining issues owned and closed? | Snag and defects-liability register |
Implementation checklist
Before releasing the next drawing, order or site instruction, check each of these items. A useful checklist does not replace judgement. It makes the judgement visible to the people who must approve, build and operate the workplace.
- Acceptance: record the decision owner, evidence source, decision date and acceptance test.
- Records: record the decision owner, evidence source, decision date and acceptance test.
- Operation: record the decision owner, evidence source, decision date and acceptance test.
- Defects: record the decision owner, evidence source, decision date and acceptance test.
Questions decision-makers ask
The central decision is turning handover into a usable operating package of tests, drawings, manuals, warranties, training and open-item ownership. Keep that decision visible in the brief so layout, procurement and delivery choices can be tested against it.
Confirm the evidence listed in the decision matrix: the scope, responsible owner, relevant drawings or records, and the date when the decision will be accepted. Mark assumptions instead of treating them as facts.
Coordinate it before procurement and before ceilings, partitions or services are closed. Late coordination usually turns a design question into a variation, rework or an operational compromise.
Define the handover index at the start of the project and update it as systems, finishes and approved substitutions change. The useful next step is a controlled review with a named owner, an agreed evidence source and a simple acceptance test.
Keep the handover index live during the build. When a fitting, control sequence or approved substitute changes, update the record before close-out. That small habit prevents the client from receiving a technically complete folder that no longer matches the rooms on site.
Sources and scope note
This article uses the official and professional reference pages below for the limited points they publish. Recommendations about layout, procurement and delivery are Vektor Spaces' practical project guidance, not a claim that a rating, code approval or performance outcome has been achieved. Confirm the current requirements with the appointed consultants, landlord and authorities for the actual project.
- Bureau of Energy Efficiency. Official BEE website. The article treats energy-code compliance as a project-specific design and approval question, not a universal promise.
- CIBSE Knowledge Portal. Professional engineering guidance portal used as a reference point for building-services design and operational questions.
- IGBC Green New Buildings rating system. Official IGBC page describing its Green New Buildings rating system and the wider family of green-building programmes.