Common Property Handover in Israel: A Buyer's Operational Guide

Common property handover is the controlled transfer of a new building's shared spaces, systems, records and operating authority from the development team to the body acting for the owners. It is not simply a clean lobby, a working lift and a signature. A credible handover identifies who may receive what, tests the building under defined conditions, transfers drawings and operating knowledge, records every open defect, moves physical and digital control, and leaves the building ready for its first night of occupation. Buyers comparing new projects in Israel can use this guide before signing, not only at completion, because the contract and technical schedules determine much of what will later be available.

In Israeli documents you may see רכוש משותף, rechush meshutaf, for common property; נציגות, nezigut, or ועד בית, vaad bayit, for the owners' representation; פרוטוקול מסירה, protokol mesira, for a handover record; תוכניות עדות, tochniot edut, for as-built drawings; and ספר מתקן, sefer mitkan, for the facility or operation and maintenance manual. These terms should stay beside any English translation. An HOA turnover, strata handover, practical completion, completion certificate or condominium registration from another country is a useful comparison, but none is an automatic legal substitute for the Israeli event or document.

The short answer: four tracks must meet

Track	What must be established	What does not establish it alone
Authority	The receiving body's mandate and each signatory's capacity	Attendance by a developer-appointed manager
Engineering	Condition, performance, interfaces and open defects	An occupancy approval or isolated certificate
Information	Searchable as-builts, O&M manuals, asset data and warranties	An unindexed cloud folder or expiring download link
Operations	Accounts, keys, credentials, training, contracts and emergency cover	Possession of a plant-room key without system control

Handover is a process rather than one ceremony. Preparation begins before the inspection, functional testing may occupy several visits, the protocol freezes a factual position, defect closure continues afterwards, and seasonal tests expose conditions that were absent on a dry, lightly occupied day. The word "accepted" should never be allowed to conceal what was not tested or what remains outstanding.

Seven events that international buyers often confuse

Occupancy authorization

An authorization connected with occupation is an important regulatory milestone. It is not a purchaser's full quality inspection, an O&M package, a warranty register or proof that every promised shared amenity is complete. Ask which exact document has been issued, for which parts, subject to which conditions, and whether temporary arrangements remain.

Handover of the private apartment

Apartment key delivery concerns the unit, its attachments and its interfaces. It does not provide the owners collectively with operating control of the generator, water boosters, fire panel, roof drainage, lifts or access-control server. A defect in a private apartment may originate in a shared system, but the two records should not be collapsed into one list.

Common-area condition inspection

This is the engineering survey of shared zones and equipment. It produces evidence, measurements and a defect register. Inspection is not itself proof that the recipients have authority to bind every owner.

Operational custody

Operational custody means the building can actually be run: meters and utility relationships are identified, service providers can enter, emergencies can be managed, administrator accounts are held by the right body, and the operator knows shutdown and restart procedures.

First owners' meeting and representation

The owners need a documented mechanism for appointing the representation, defining routine powers, reserving material decisions and reporting to all owners. A temporary group formed in a messaging app may be useful, but its legal and contractual authority should not be assumed.

Management-company transition

A company installed during development may continue temporarily or be replaced. Its contract, loyalty, records, bank access, data and termination rules require separate review. Management transition is not the same event as engineering acceptance.

Condominium registration

The Israeli condominium order, plan and takanon deal with the registered structure of rights and common property. Registration can occur on a different timetable. It does not prove that a pump changed over correctly or that a roof leak was repaired. Conversely, an operating building may still have registration work pending. Treat title status and operational handover as linked but separate workstreams.

A practical timeline from 90 days before handover

90 to 60 days before the proposed date

Owners document who can organize the process and commission independent advice. The project lawyer reviews sale agreements and schedules; the owners' engineer defines scope, exclusions and required specialists. A formal data-room request asks for a system inventory, drawing register, authority approvals, test plan, warranty list and named delivery date for every missing item.

This is also the moment to compare sales promises with binding material. If the brochure says residents' club, pool, gym, smart building or concierge, identify the contractual specification, operating concept, capacity, access rules and equipment schedule. A photograph or render is not a commissioning criterion.

60 to 30 days before handover

The technical team reviews documents before walking the site. It builds an initial asset register and document-gap log. Visits are separated by discipline because a single general tour cannot properly cover envelope, drainage, electrical supply, generator, water, sewage, fire, smoke control, lifts, security and digital systems. Relevant installers and authorized inspectors are booked for functional demonstrations.

30 to 7 days before handover

Baseline inspections and pre-tests take place. Each issue receives a unique ID, precise location, evidence, consequence, temporary control and owner. The developer has an opportunity to repair and provide missing evidence. Test scripts are agreed for normal operation, alarms, loss of mains, backup, high demand and safe controlled faults where appropriate.

The handover day

Start with the attendance and authority sheet, not the signature page. Confirm the document revision, record meter readings, count keys and tokens, review each system's status and attach the current defect register. If something was not tested, it is recorded as "not tested", not presumed operational. A missing document is named exactly, with its required revision, responsible party and delivery date.

The first 24 hours

Confirm insurance, emergency numbers, lift rescue, essential maintenance coverage, utility accounts, access to plant rooms, consumables and secure backups. No critical service should depend on the personal card, telephone or email address of an employee who may leave the developer or contractor.

The first 30 days

Occupancy increases and the building starts revealing patterns. Monitor water pressure, lift waiting, gate failures, smells, pump alarms, car-park ventilation, refuse operation and repeat complaints. Keep one controlled defect database. Multiple spreadsheets held by the developer, manager and committee create disputed identities and lost closure evidence.

First season and first year

Schedule the first rain inspection, hot-weather review, planned power-loss test and full-occupancy review. Reinspect open items and review all contractual and statutory notification dates with counsel. Update the asset register whenever equipment is replaced, firmware changes or a warranty provider changes.

Who may receive the building, and whose interests are involved

Participant	Legitimate role	Control question
Developer or seller	Coordinates delivery and remains responsible under applicable documents and law	Who can commit the company to a remedy and deadline?
Main contractor	Explains construction and performs repairs	Is it contractually responsible to owners, or acting through the developer?
Developer-appointed manager	Runs the property during a transition	Who appointed and pays it, who receives its reports, and when can it be changed?
Temporary owners' group	Organizes early decisions	What resolution or authorization defines its scope and duration?
Elected nezigut or vaad bayit	Acts within applicable law and owners' decisions	Does its authority cover this exact protocol and any waiver language?
Owners' engineer	Verifies scope, condition, performance and evidence	Is the appointment independent and sufficiently specialized?
Owners' lawyer	Reviews mandate, contract, reservations and legal effect	Whom does the lawyer represent, and has every annex been provided?

A conflict of interest is not proof of poor work. It is a reason for disclosure, allocation of roles and independent verification. A developer-appointed manager may be highly competent and still hesitate to classify its appointor's failure as a critical defect. An engineer routinely retained by the contractor is not the same as the owners' independent verifier. A committee member who sells services to the building should disclose that interest and step away from the relevant decision.

Good authority minutes answer five questions: who appointed the recipient, when, for how long, for which acts, and which decisions remain with the owners. They also require reporting, access to records and preservation of dissent. Israeli government guidance on resident representation in urban renewal emphasizes transparency, conflict disclosure and the limits of a representation's role in material decisions. That guidance is not automatically the governing rule for every newly built condominium, but it is a valuable governance benchmark.

Build a data room, not a document dump

A useful data room has an index. Every file is tagged by building, zone, discipline, system, document type, date, revision, author, status and related asset. The index should show whether a file is approved, as-built, superseded, draft or missing. A separate gap register records the requested item, reason, responsible supplier, promised date, actual date and acceptance review.

The eight document families

Planning and authorization material: permits, relevant approved plans, conditions, completion documents and applicable authority approvals.
As-built records: architecture, relevant structure, electrical, water, sewage, drainage, fire, ventilation, communications, controls, external works and landscape.
O&M and sefer mitkan: operating sequences, safe shutdown, restart, preventive maintenance, troubleshooting, spares and contacts.
Equipment schedules: manufacturer, model, serial, capacity, location, installer and commissioning date.
Test evidence: laboratory results, authorized inspections, pressure tests, balancing, functional tests, load tests and corrective retests.
Warranties and service: warranties, service agreements, response times, exclusions and maintenance conditions.
Emergency information: isolation points, valve maps, evacuation interfaces, escalation tree and specialist callouts.
Physical and digital assets: keys, remotes, licences, admin users, cloud subscriptions, SIMs, domains and configuration backups.

As-built means built, not merely approved

An approved design shows what was authorized or intended. An as-built drawing should show what was installed. Real projects contain rerouted pipes, moved sensors, revised cable pathways and relocated access panels. During a leak or fire-system fault, a beautifully stamped but inaccurate drawing can waste critical time.

Require a viewable PDF and, where useful for future professional work, the relevant native file. Each sheet should carry a revision and date and identify building, floor, zone, dimensions, levels, pipe sizes, circuit references, flow direction, valves and isolation points as relevant. The engineer should sample the record against reality. A valve drawn inside an accessible riser but installed above a sealed ceiling is a handover defect even if the line itself works.

What makes an O&M manual usable

A sefer mitkan should describe this building, not present generic product catalogues. It should map each product manual to an asset and location, explain the system logic, list set points, identify normal and alarm states, show safe shutdown and reset sequences, define planned maintenance and state warranty-preservation conditions.

Use the night-shift test: can a competent facility technician who never met the construction team determine which booster supplies which zone, isolate a leak safely, understand the alarm and order the correct part? If not, the manual is not complete. Video training can help, but searchable written procedures remain necessary when the trainer is unavailable.

The asset register and warranty calendar

The asset register is the operational memory of the property. Give every maintainable asset a unique ID and, where appropriate, a durable label or QR code. A public-facing tag must not disclose passwords or security-sensitive network information.

Field	Required level of detail
Identity and location	Building, floor, room, grid, panel or service zone
Function	Duty, standby, life-safety, domestic service or amenity
Make, model and serial	Transcribed and photographed from the nameplate
Design data	Flow, head, power, capacity, set point or relevant parameter
Dates	Installation, test, commissioning, claimed handover and first use
Warranty	Provider, scope, conditions, claimed start date and source document
Maintenance	Task, interval, qualification and completion record
Spares	Part number, recommended stock and storage location
Linked records	As-built, manual, test report, defect and service agreement

Do not reduce the warranty calendar to one date column. Preserve the contract date, installation, commissioning, first apartment delivery, first use of the shared asset, operational handover, protocol signature, notification and any alternative date asserted by either side. Statutory liability, contractual remedies and manufacturer warranties may operate differently. The owners' lawyer should make an asset or defect-category matrix and avoid surrendering a disputed date merely for administrative tidiness.

Inspect by zone, including the unphotogenic places

Site, paths, external drainage and landscape

Check falls, settlement, paving joints, trip hazards, accessibility, lighting, irrigation and landscape interfaces. A controlled water test can show whether runoff reaches gullies or approaches entrances, lift pits and the car park. Chambers, valves and isolation points must remain locatable after planting matures. Compare access routes and claimed common zones against the applicable plans and legal schedules.

Facade and envelope

Survey cracks, staining, fixings, sill details, copings, joints, sealants and penetrations. Lawful professional drone imagery can improve coverage but does not replace close assessment where access is required. Evidence of a cladding inspection does not prove every sealant joint is sound or that safe future maintenance access exists.

Roofs and shared terraces

Inspect falls, outlets, emergency overflows, thresholds, upstands, protection layers, equipment plinths and safe service routes. Map every waterproofing penetration. Confirm that a condenser, solar installation or decorative screen does not block drain cleaning. Flood or spray testing must follow the design and professional direction so the test itself does not cause damage.

Lobby, corridors and stairs

Inspect doors, closers, ironmongery, glazing, stone, ceilings, lighting, emergency lighting, signage, handrails, treads and landings. Measure suspicious clearances and slopes. Confirm that fire doors complete their intended closing action and that furniture or decoration does not narrow an escape route.

Accessibility as a continuous journey

Do not inspect an accessible parking space, lift and entrance separately. Follow the whole route from street or parking through the gate, intercom, threshold, lobby, lift, corridor and shared service. Review turning spaces, gradients, controls, signage, lighting and obstructions against the project requirements. A planter installed after an approval may still make a maneuvering area unusable.

Parking, stores and back-of-house areas

Check bay markings, circulation, columns, corner guards, headroom, drainage, lighting, ventilation, pedestrian routes and signs. Stores must not obstruct equipment or service access. Inspect walls and slabs for water marks. For vehicle charging, distinguish a working charger, cable pathway, electrical capacity, load-management provision and a marketing statement. The new-project EV charging guide covers capacity and billing in depth.

Shafts and plant rooms

Each room needs a name and number matching the drawings. Check safe access, lighting, ventilation, drainage, labels, penetration seals and orderly supports. Remove contractor materials and unrelated storage. Every isolation point should be labeled, and keys should be held through a controlled register.

Commissioning shared systems

Commissioning is the planned verification that installed systems perform their required sequences and interfaces. The project may use another contractual term, and the required process depends on the design and applicable obligations. The owners should still demand a test plan, competent participants, expected results, measured outcomes and corrective retests.

System	Functional evidence to seek	Record to retain
Electrical distribution	Circuit identification, protection, loads, isolation and labeling	Single-line drawing, test report and panel schedule
Generator	Start, transfer, intended supported loads and stable return	Load-test data, response times and fuel arrangement
Water boosters	Pressure at critical points, duty changeover, alarms and leaks	Pump curves, set points and commissioning sheet
Sewage and drainage	Flow, sump pumps, floats, alarms, access and overflow path	Schematic, test record and access photographs
Fire detection and suppression	Zones, devices, pumps, voice alarm and interfaces	Cause-and-effect matrix, reports and bypass register
Smoke control and car-park ventilation	Trigger sequence, airflow direction, sensors and alarms	Test scripts, measurements and balancing data if applicable
Lifts	Travel, communication, rescue interface, accessibility and recovery	Certificates, service contract, log and training record
Gates and barriers	Safety sensors, manual release, power loss and credentials	Manual, remotes list and controller configuration
Access and intercom	Enrolment, revocation, roles, backup and apartment calls	Administrator register, privacy process and backup
CCTV	Coverage, time accuracy, retention, permissions and export	Camera map, access policy and settings record
Networks and controls	Connectivity, alarm routing, backup, clock and data export	Network map, licences, users and configuration backup
Refuse systems	Operation, cleaning, drainage, odor control and safety	Training, maintenance plan and service details
Pool and wellness	Plant, water treatment, ventilation, safety and maintenance	Relevant approvals, logs, manuals and training

Life-safety and technical systems must be handled by appropriate qualified people. Owners' representatives should not open live electrical panels, bypass interlocks or stage unsafe failures. Their job is to require competent testing, observe defined evidence, record exclusions and track remediation.

Test five operating modes

Normal mode: everyday sequence, capacity, noise, vibration and usability.
Alarm mode: whether a fault reaches the correct active recipient, with useful location and wording.
Mains or communications failure: what continues, what stops safely and how recovery occurs.
High demand: water pressure, power, ventilation and lift service at a representative design condition.
Controlled fault: duty and standby changeover, failed sensor or fire sequence only when safe, planned and professionally supervised.

A strong test record states the initial condition, action, expected result, actual result, measurement, participants, time and software revision. A short video may supplement the record but cannot show invisible set points, trend data or the authority of the tester.

Transfer physical and digital custody

Building control today is distributed across metal keys and cloud accounts. Use a custody register for:

Standard, master, restricted and emergency keys, including quantity and holder.
Remotes, access cards, proximity tags and service codes, including revocation method.
Administrator accounts for access control, intercom, CCTV, building controls, charging and gates.
Email addresses and telephone numbers used for password recovery and multi-factor authentication.
Software licences, user limits, renewal dates and data ownership.
Cloud subscriptions, SIM cards, communications contracts, domains and certificates.
Tested configuration backups, restore instructions and version history.
Vendor remote access, approval, logging and termination method.

Do not put passwords in a protocol circulated to every resident. Store them in a controlled password vault owned by the authorized building body, with at least two continuity holders, multi-factor authentication and access logs. Default passwords and temporary contractor accounts should be addressed after transfer, in coordination with the vendor so that support and warranty are not unintentionally impaired.

Use a defect register that can close a defect

"Water in basement" is not manageable. One defect record should contain:

Field	Purpose
Unique ID	Keeps discussion, evidence and retest tied together
Exact location	Building, floor, grid, room, surface or asset ID
Condition and requirement	Says what is observed and what was expected
Evidence	Original photograph, video, measurement, report or drawing
Severity	Safety, service outage, progressive damage, use or finish
Temporary control	Barrier, isolation, monitoring or other risk reduction
Owner	Named company and contact, not "contractor"
Target	Repair and retest date
Status	Open, in work, ready for test, closed or reopened
Closure proof	After evidence, repeat test and verifier acceptance

Paint over a stain is not proof that water ingress is closed. Resetting an alarm is not a repair if it returns. Replacing a pump is not complete until the new serial, warranty, test and as-built record are incorporated. Closure must address cause, consequence and the information baseline.

Draft a protocol that distinguishes fact from waiver

The protocol should identify project, date, time, participants, capacity, drawing revision, inspected zones and systems. Number every attachment. Use separate status categories:

Received and tested, with a named test and evidence.
Received with reservations, where custody transfers but a defined gap remains.
Not tested, because access, conditions, competence or time were unavailable.
Missing document, naming the document and required revision.
Temporary arrangement, naming operator, cost, responsibility and end date.
Developer access retained, naming purpose, area, controls and expiry.
Open defect, linked to the defect register ID.

There is no responsible universal instruction to sign every protocol or refuse every protocol. A carefully reserved signature can sometimes make safe operational transfer possible. In another case, the draft may contain broad releases, inaccurate confirmations or unauthorized commitments and require amendment before signature. The owners' lawyer evaluates wording and authority. The engineer confirms only technical matters actually verified. Preserve every signed version and annex.

When does liability or warranty start for common property

Do not state that one protocol or one date universally starts every legal, contractual and manufacturer period for every shared component. The Sale Apartments framework, purchase agreement, facts of making an asset available, different delivery events, identity of the recipient, nature of the defect and supplier terms may matter differently. A statutory remedy, contractual warranty and manufacturer's warranty are not necessarily coextensive.

The Standards Institution of Israel publishes a general explanation that frames the apartment inspection period from the date the apartment is made available to the buyer, with duration varying by defect category and a later responsibility period. That is useful background, but an apartment-oriented summary does not by itself resolve every common-system date dispute. Project counsel should prepare a dated matrix by asset and claim category, preserve alternative asserted dates and issue notices promptly.

Asset	Installed	Commissioned	First use	Claimed delivery	Operational custody	Defect notice	Developer position	Owners' position
Water booster	Evidence	Evidence	Evidence	Date and source	Date and protocol	Date and receipt	Reasoned	Reasoned

Maintenance cannot wait for the legal debate. A manufacturer may require filter cleaning, a first service after operating hours, periodic exercise or work by an authorized contractor. Schedule those steps from day one while expressly preserving legal positions.

The first operating day

Before the development team leaves, confirm:

Appropriate insurance is active based on professional advice and authorized decisions.
Residents have one emergency contact and a defined escalation chain.
Essential lift, fire, generator, pump, gate and other service contracts are active.
Common electricity, water, gas and communications accounts sit with the appropriate party.
Cleaning staff know which chemicals are permitted on stone, metal, glass and timber.
Critical consumables and spares are available and labeled.
Vendor access protects residents and is logged.
One event log records time, alarm, action, vendor and outcome.
Emergency procedures remain available during internet failure.
Residents receive a clear operating notice covering temporary restrictions and contacts.

A property manager can perform these tasks, but the owners' body needs visibility and exportable records. Contracts, invoices, alarm history and service evidence should not remain in one manager's private mailbox. The Hebrew property-management guide covers ongoing governance; handover must first create a complete operational baseline.

Seasonal and occupied-building verification

First rain

Clean outlets beforehand, then observe roofs, planters, terraces, ramps, basement joints, pits and shafts during and immediately after rain. Record the water path, not only the final stain. Link evidence to the exact drawing and defect ID so maintenance blockage can be distinguished from construction failure.

Heat wave

Trend plant-room temperatures, electrical equipment, lifts, pumps, shared cooling or ventilation and energy use. Equipment that operated in spring may alarm in August. Compare measurements to design and manufacturer parameters.

Planned power failure

Under qualified supervision, verify generator start, supported loads, emergency lighting, gates, lift communication, fire systems, pumps and stable return to mains. Record transfer times and alarms. Never create an improvised outage in an occupied building.

Full occupancy

Review peak water pressure, lift waiting, refuse volume, odors, machine noise, parking circulation, access control and complaint frequency. If the tower was handed over with ten percent occupancy, actual demand performance remains unproven.

The remote or overseas owner

An overseas buyer can require a strong evidence process:

A legally reviewed power of attorney or representation mandate with defined limits.
A bilingual data room with controlled versions and a readable document index.
A route-based video inspection showing locations and nameplates, not a marketing montage.
A protocol that preserves all untested items and missing evidence.
Original photographs and time-stamped defect history, including reopened issues.
A separate systems training session, recorded where lawful and agreed.
Remote voting and reporting that lets absent owners understand material decisions.
Secure storage owned by the building body, not the current manager alone.

Do not let familiar foreign vocabulary create false certainty. HOA board, managing agent, syndic, strata manager and condominium association describe different systems in different jurisdictions. Ask which Israeli person or body holds the mandate, which document grants it, and whether the planned action falls within that mandate. A foreign lawyer can help with the buyer's home-country issues, but Israeli counsel should review the Israeli purchase and handover documents. Our Israeli real-estate lawyer guide explains the purchasing role in more detail.

Printable 100-point common property handover checklist

Mark each item: received, received with reservation, not tested, missing document, or not applicable. Link observations to defect IDs.

Authority, contract and baseline

The receiving body's appointment or election record is available.
The representation's signing authority is defined in writing.
Material decisions reserved to owners are listed.
Conflicts of committee, manager and consultants are disclosed.
Owners' counsel reviewed the proposed protocol wording.
Owners' engineer issued a scope and exclusion statement.
Developer, seller, contractor and responsible signatories are identified.
A named person can commit each responsible company to dates.
Common-property specifications and contract schedules are indexed.
Marketing promises are mapped to binding documents or flagged.
Occupancy, apartment delivery and operational custody dates are separated.
Condominium registration status is checked separately.
Tzav, takanon and condominium plan status are recorded.
Common areas and attachments are compared with legal plans.
All protocol annexes are listed before signature.

Data room and as-built information

A searchable file index records date, revision and status.
A document-gap register names owner and due date.
Architectural as-built drawings have been received and sampled.
Electrical and panel as-builts reflect the installed layout.
Water, booster and valve drawings are available.
Sewage, drainage, sump and chamber drawings are available.
Fire detection and suppression drawings are available.
Smoke-control and car-park ventilation drawings are available.
Communications, intercom, CCTV and controls drawings are available.
External works, irrigation and lighting drawings are available.
Every drawing identifies building, floor, zone and revision.
Viewable PDFs and useful native files are securely retained.
Isolation points match both drawing and field labels.
Construction changes have been incorporated into final records.
Expiring links have been copied into owner-controlled storage.

Manuals, assets and warranties

The O&M manual is building-specific, not only generic brochures.
Each system has a clear description and operating sequence.
Alarm meanings and safe responses are documented.
Shutdown, isolation, reset and restart procedures are documented.
Preventive maintenance states interval and required competence.
Manufacturer, installer and service contacts are complete.
Make, model and serial are photographed and transcribed.
Capacity, set point and design duty are recorded.
Each warranty is linked to the correct asset.
Warranty-preservation maintenance has been identified.
First service dates are entered into an active calendar.
Critical spare parts and storage location are recorded.
Maintainable equipment has a durable unique asset label.
QR labels expose no credentials or sensitive network data.
A multi-date warranty and claim matrix has been created.

Fabric, access and shared zones

External falls and drainage have been suitably tested.
Gullies, chambers and valves are clean, labeled and accessible.
Paths and ramps are free from settlement and trip risks.
The complete accessible journey has been inspected.
Facades were surveyed for cracks, fixings and sealant gaps.
Roof penetrations are mapped and sealed.
Roof outlets and emergency overflows are accessible.
Roof thresholds and drainage near doors were checked.
Lobby and corridors were checked for finishes and hardware.
Fire doors close without obstruction as intended.
Stairs, handrails, guards and landings were inspected.
Emergency lighting and escape signs were demonstrated.
Parking was checked for drainage, markings and headroom.
Stores do not block equipment or service routes.
Plant rooms contain no contractor debris or unrelated storage.
Plant-room names and numbers match the drawings.
Safe lighting and maintenance access exist around equipment.
Shafts and penetrations have the intended protection and sealing.
Landscape does not conceal chambers or emergency outlets.
A complete photographic condition baseline is securely stored.

Systems and commissioning

Electrical panels are labeled and match the single-line drawing.
Relevant electrical inspection records are in the data room.
The generator was tested for start and intended load transfer.
The actual backed-up load list was verified.
Water pumps were tested for duty, standby and alarm.
Pressure was measured at critical endpoints and suitable demand.
Sewage and drainage pumps were tested with floats and alarms.
Fire detection was demonstrated through defined scenarios.
Fire interfaces with lifts, doors and ventilation were tested.
Smoke extraction and car-park ventilation sequences were shown.
Lifts were checked for travel, communication and recovery.
Lift rescue procedure and callout contacts are available.
Gates were tested for sensors, manual release and power loss.
Access control was tested for user enrolment and revocation.
Intercom calls were sampled across entrances and apartments.
CCTV was checked for coverage, time, retention and export.
Building alarms reach a monitored and active recipient.
Refuse equipment was tested for operation, cleaning and safety.
Pool and wellness plant was reviewed by suitable specialists.
Every test records expected result, actual result and evidence.

Custody, protocol and day one

Keys, master keys, remotes and cards are counted and assigned.
Administrator accounts are owned by the authorized building body.
Default passwords and temporary users have been addressed.
Licences, cloud services, SIMs and domains have transferred.
Configuration backup and restore have been verified.
Vendor remote access is documented, logged and revocable.
Handover-day meter readings are photographed and recorded.
Common utility accounts sit with the appropriate party.
Each defect has an ID, severity, owner and target date.
Temporary arrangements state operator, cost and expiry.
Untested items are expressly marked, never presumed compliant.
Insurance, emergency cover and essential service contracts are active.
Residents received operating restrictions and reporting contacts.
Rain, heat, outage and full-occupancy tests are scheduled.
The signed protocol and all annexes are stored securely.

Frequently asked questions about common property handover in Israel

Who accepts common property from an Israeli developer?

Usually a body acting for the apartment owners is needed, but its identity and authority depend on the ownership stage, owners' decisions, project documents and applicable law. Do not assume that a developer-appointed management company can waive rights for owners. Record the mandate and conflicts, and have Israeli counsel review the specific signature.

Is apartment key delivery the same as building handover?

No. The apartment process covers the unit and certain attachments and interfaces. Shared systems such as pumps, generator, roof drainage, fire, lifts and access control require building-level inspection, records and custody. Keep separate registers, then cross-reference a private defect when its cause lies in a common system.

Does an occupancy approval prove that the building is defect-free?

No. It is an important authorization milestone, but not a complete purchaser quality review, specification comparison, commissioning record or O&M transfer. Ask for the exact approval and any conditions, then require system-specific evidence and an independent common-property inspection.

What are tochniot edut?

Tochniot edut are the Israeli project term commonly used for as-built drawings. They should reflect installed routes, valves, circuits and equipment, not merely the approved design. Require revision dates and verify a sample in the field. Retain viewable files and useful professional source formats under owners' control.

What should a sefer mitkan contain?

A useful sefer mitkan, or O&M manual, maps manuals to actual assets and locations. It explains system logic, set points, alarms, safe shutdown and restart, preventive maintenance, spare parts, warranties and contacts. Generic catalogues without asset mapping are not enough for a new technician to operate the building.

Must the representation sign if defects remain?

There is no universal answer. A reserved acceptance may support safe operational transfer in one project, while inaccurate statements, broad releases or dangerous conditions may require amendment before signing in another. Record untested items expressly. The owners' engineer verifies technical facts and counsel evaluates authority and legal effect.

Does signing start every warranty period?

It should not be assumed. Contract terms, making assets available, delivery facts, defect category, recipient identity and manufacturer conditions may produce different dates and arguments. Project counsel should maintain a dated matrix and preserve alternative positions. Notify defects and perform required maintenance without waiting for the date dispute to end.

What is commissioning in a residential building?

It is structured verification that systems perform defined sequences and interfaces, including normal, alarm, backup and safe failure behavior where relevant. The label and contractual scope differ by project. A commissioning record should state expected and actual results, measurements, participants, time, software version and corrective retest.

Who should pay for the common-area survey?

That depends on purchase agreements, project arrangements and owners' decisions. Some projects include funding for an owners' inspector, while others require a collective engagement. More important than the payment route is a clear client, independence, adequate insurance, specialist scope and direct delivery of evidence to owners.

What if the developer has not transferred passwords?

List each missing credential, licence and account as a separate protocol item with an owner and due date. Transfer recovery email, telephone, subscription and data ownership to the authorized building body. Credentials belong in a controlled vault, not a resident-wide message. Coordinate changes to preserve support and warranty.

Why is a first-rain inspection necessary?

Dry-day inspection cannot fully expose waterproofing and drainage performance. Rain can reveal flow toward entrances, blocked overflow paths, planter leakage, facade joints and basement ingress. Clean drains first, document water paths during the event and link each finding to the drawing and defect record.

How can an overseas owner participate?

Use a legally reviewed mandate, an independent technical representative, bilingual version-controlled records, route-based video, original evidence and remote reporting. Keep Hebrew document names beside translations. Video attendance alone cannot replace physical testing, authority checks or the signed record.

Sources, scope and disclosure

The factual framework draws on the Israeli Ministry of Justice condominium-file service, the Hebrew condominium registration service, the Ministry of Construction and Housing registration-status service, the Standards Institution of Israel explanation of contractor responsibility, the government guide for new-apartment buyers, the government resident-representation principles, and the government guide to its model urban-renewal agreement. The last two address urban renewal. They are used for relevant governance and handover practices, not as automatic rules for every developer sale.

This is general information, not legal or engineering advice for a specific building. Contracts, permit conditions, specifications, registration documents, system type and current law must be reviewed by Israeli counsel and appropriately qualified professionals acting for the owners. This guide does not claim that one event starts every inspection or warranty period and does not give a blanket instruction to sign or refuse a handover protocol.