Handover day arrives with champagne energy and contract-law consequences. The developer's representative has keys, a folder and a document called the zapisnik o primopredaji — the handover protocol — and everyone in the room wants it signed in twenty minutes. This page is about why those twenty minutes matter more than most buyers realise: the protocol is the evidentiary hinge on which your defect rights turn, the statutory notice windows that follow are short, and the sequence completes the off-plan arc we have built across this series — from the reservation and pre-contract, through instalments and escrow, the use permit and the insolvency ranking — at the last moment when your money is still leverage.
Why a clean signature costs rights
Montenegrin law rewards the party who inspects and objects, and it does so in two places at once.
Under the sale rules of the Law on Obligations, the buyer must examine the thing received as soon as the ordinary course allows and notify the seller of visible defects within eight days, on pain of losing the rights those defects would carry — and where the inspection happens in the presence of both parties, which is exactly what a handover appointment is, objections to visible defects must be raised immediately (Article 489). The works-contract rules say the same thing from the contractor's side: after inspection and acceptance of the work, the contractor no longer answers for defects that an ordinary inspection would have revealed, unless he knew of them and concealed them (Article 683).
Put plainly: a clean, unqualified signature on the protocol is not a formality. It is the legal event that converts every scratch, every misaligned door, every unfinished balcony rail from "the developer's problem" into "something you accepted". The document was designed to record the property's condition at the moment of transfer; used under time pressure, it records instead that there was nothing to record.
One materially important softening exists for individuals: in consumer contracts, the buyer is not obliged to inspect at all, and must notify visible defects promptly on learning of them, at the latest within six months of discovery (Article 489(4)). That helps — but it is a shield for the unwary, not a plan. Relying on consumer status means relying on characterisation arguments after the fact, against a counterparty holding your signed protocol. The plan is to inspect.
The clocks, laid end to end
What buyers underestimate most is not the standards — it is the calendar. The windows are short, they start on events rather than on convenience, and they stack.
| Track | What it covers | Notice window | Long-stop | Enforcement |
|---|---|---|---|---|
| Sale — visible defects | What an ordinary inspection reveals at handover | Immediately at a joint inspection; otherwise 8 days (consumer: on discovery, up to 6 months) | The handover itself | Rights extinguish one year from the notice (Article 508) |
| Sale — hidden defects | Defects not discoverable by ordinary inspection | 8 days from discovery | Seller not liable for defects appearing more than 6 months after delivery, unless a longer period is agreed (Article 490) | One year from the notice |
| Works — hidden defects | Defects in executed works | As soon as possible, at most one month from discovery (Article 684) | Two years from acceptance of the work | One year from the notice (Article 685) |
| Structural soundness | Stability and soundness of the building, and of the ground it stands on | 6 months from establishing the defect (Article 713) | Ten years from handover (Article 712) | One year from the notice |
A word on why four tracks exist for one apartment. Your own contract with the developer is a sale, so the sale rows govern what you can demand from the developer directly. The works and soundness rows belong to the construction relationship behind your purchase — employer against contractor and designer — and they reach you not through your contract but through the statute: the employer's defect rights pass to later acquirers of the building by law, and the soundness liability runs to every acquirer in its own right. The tracks are parallel, not alternatives, and a well-run file keeps all of them alive.
Three features of that table deserve emphasis. First, the six-month cut-off in the sale track is default law, not mandatory law — "unless a longer period is agreed" is an invitation your contract can accept, and a negotiated defect-liability period is one of the cheapest protections available at signing stage. Second, every notice window feeds a one-year enforcement window: notifying is not the end of diligence but the start of a countdown to proceedings. Third, none of the seller-side comfort is available to a counterparty who knew: a seller who knew of the defect, or could not have been unaware of it, cannot rely on your late inspection, your late notice or the six-month cut-off (Article 493), and the contractor is in the same position for facts known to him (Article 686).
The ten-year rule, and why it travels with the building
The strongest right in the stack is the one buyers hear about least. For defects concerning the soundness of the building — its structural integrity, and defects of the ground it was built on — the contractor is liable for defects that appear within ten years of handover of the works, and the designer is liable alongside where the defect originates in the design (Article 712). Two features make this regime remarkable.
It cannot be excluded or limited by contract — the statute says so in terms, and it runs in favour of the original employer and every later acquirer of the building. And separately, the ordinary defect rights of the employer against the contractor pass to all subsequent acquirers of the building by law (Article 711) — with the predecessor's clock, not a fresh one.
For the apartment buyer, that means your rights against the developer under your sale contract are not the whole arsenal: for soundness-class defects, you hold a statutory, non-excludable claim against the contractor and the designer, whoever they are, for a decade from handover of the works. The discipline it demands is documentary — knowing who built and who designed, which is exactly the kind of information the permit file contains and a buyer's counsel collects while it is easy.
What you can actually demand
The remedies ladder, for a defect properly notified, is set by Article 496: demand that the defect be removed or the thing replaced; or a price reduction; or declare the contract terminated — and damages on top of any of the three, including for harm the defect caused to your other property. Termination has its own discipline: as a rule you must first give the seller an appropriate further period to perform (Article 498), after which the contract dissolves by law if nothing happens (Article 499).
And the small print can do less than developers hope. Contractual limitation or exclusion of defect liability is permitted in principle — but void where the defect was known to the seller and not disclosed, and void where the clause was imposed through a position of monopoly (Article 494); a buyer who waived only termination keeps every other remedy. Read together with the non-excludable soundness regime, the space for drafting your rights away is much narrower than the standard contract's confidence suggests.
The Boka pattern: keys before the use permit
A recurring coastal scenario deserves its own paragraph: the developer offers handover — sometimes with a discount for cooperation — while the upotrebna dozvola does not yet exist. Everything we set out in the use-permit guide applies at full force: use of a structure before the permit is prohibited by law, the completed building cannot yet be registered, and the inspector's powers include stopping use of an unpermitted structure. A "handover" of a unit you cannot lawfully occupy or register is not a completion; it is a transfer of possession dressed as one, and payment schedules that release the final tranche against it convert your leverage into hope. The final instalment belongs behind the permit and the registration sequence — which is a clause, not a wish, and it is negotiated at contract stage, not at the door.
The handover-day script
None of the above requires confrontation. It requires a sequence, agreed in advance and followed calmly.
Inspect properly. Take a snagging engineer or architect through the unit; measure, test, open, run water. The cost is trivial against what a clean signature waives. Where the project warrants it, that inspection sits inside broader construction advisory work — permit file, as-built conformity, systems.
Record everything in the protocol itself. Every visible defect, listed, with photographs referenced. The protocol is your evidence; make it evidence of the truth.
Sign with reservations, not refusals. An unqualified signature waives; an unreasonable refusal to attend acceptance has its own consequences under the works rules. The professional middle is a signed protocol that accepts possession and records defects and expressly reserves all rights — in writing, on the document.
Notify in writing, immediately. The joint-inspection rule makes "we mentioned it verbally" a dangerous file. Confirm the defect list to the developer in writing the same day, by a channel that proves receipt.
Calendar the clocks. Eight days, one month, six months, one year, ten years — each from its own trigger. A defect diarised is a claim; a defect remembered is an anecdote.
Send us the draft handover protocol and the payment schedule before the appointment — ideally before the contract that fixes them is signed. We will tell you plainly what the protocol as drafted would waive, which clocks start on signature day, and how to hold the final tranche where it still does its work.
