Cases / Handover & lifecycle
Handover & lifecycle

Keep jotallas apart from szavatossag and release the retention

Write the two guarantees into the contract as two things, take the works over with the outstanding items listed, run both clocks separately, and release the retention against the right one instead of against whichever ends first.

7 steps12 minGeneral contractorSpecialist subcontractorDeveloper / clientCost consultancy / QS practice

How it works, step by step

7 steps across the platform - what you do at each one, and why it matters.

1

Write the two guarantees as two clauses

Contracts

Record in the contract, separately, the jotallas the contractor undertakes and its period, and the szavatossag that follows from the Ptk. whether anybody writes it down or not. Alongside them record how the obligation is secured: retention held from each payment, a bank guarantee, or both, and on what event each is released.

Why: Under jotallas the obligor escapes only by proving that the cause of the defect arose after performance; under szavatossag the party claiming carries the proof. A clause that says only garancia leaves that question to be argued at the worst possible moment, which is when a defect has appeared and neither side has a technical answer yet. Two clauses cost one paragraph and settle it in advance.

InContract draftScope and building typeOutTwo guarantees written separatelyRetention and security terms
2

Check whether a mandatory jotallas applies

Validation

Before the terms are agreed, check whether the work falls under a jotallas imposed by law rather than chosen by the parties. Government Decree 181/2003 (XI. 5.) is the one that matters in housing, and where it applies the parties cannot contract below it.

Why: A negotiated guarantee shorter than the mandatory floor is not a negotiated guarantee, it is an unenforceable clause that both sides believed until the day it was tested. The contractor priced a risk it did not shed and the client relied on a period that was never in danger, and both find out at the same moment.

InBuilding type and clientDrafted guarantee termsOutMandatory floor identifiedCompliance report
3

Take the works over with the list attached

Punch List

Walk the works at the atadas-atvetel and record what is outstanding as a list of items with owners and dates, separating what is genuinely incomplete from what is defective. Fix the takeover date on the record, because both guarantee periods are measured from performance.

Why: Everything after this is dated from here, so a takeover that happened in stages and was never written down leaves two parties with two different opinions about when the clocks started. The distinction between incomplete and defective matters as much: incomplete work is finishing under the contract, and defective work is the guarantee, and only one of them should be holding up the payment.

InCompleted worksTakeover inspectionOutList of outstanding itemsTakeover date fixed
4

Put the retention on a schedule, not in a memory

Finance

Total what has been retained across the payments, split it into the portion released at takeover and the portion released at the end of the guarantee, and record each release as a dated event with the condition that triggers it.

Why: Retention is the most commonly forgotten money in construction, in both directions. A contractor who does not track it asks for it late, sometimes years late and sometimes never. A client who does not track it releases it early against a defect it had every right to hold, and cannot get it back.

InRetention held to dateRelease termsOutRelease scheduleBalance still held
5

Run the two clocks as two clocks

Deadlines

Open a deadline for each period from the takeover date: the jotallas as the contract or the decree sets it, and the kellekszavatossagi igeny separately. Where the thing supplied is real property, that second one lapses five years from performance under the Ptk. rather than in the one year that applies generally.

Why: Both parties tend to file the job when the shorter clock stops, and that is the error the five-year rule punishes. A client who lets the szavatossagi period run out on a real defect loses a claim it had; a contractor who thinks the file closed with the jotallas has stopped keeping the record that would answer the claim. Two dated deadlines cost nothing and prevent both.

InTakeover dateBoth guarantee periodsOutJotallas end dateSzavatossag end date
6

Classify each defect before you argue about it

Warranties & Defects Liability

When a defect is notified, record which period it falls in, what the site record says about that work, and which guarantee is being relied on. Then track the remedy to closure with the date it was fixed, because a repaired part restarts the limitation on that part.

Why: Which guarantee applies decides who has to prove what, and that decides the outcome far more often than the technical merits do. Making the classification an explicit step, with the site record next to it, is what turns a defect notice into a question with an answer rather than into an exchange of letters that runs until somebody gives up.

InDefect notified after handoverSite record for that workOutDefect classified under one guaranteeRemedy tracked to closure
7

Close the guarantee without closing the file

Close-out

At the end of the jotallas period, walk the outstanding items, release the final retention against a clean list, and keep the project record open until the longer szavatossagi period has run rather than archiving it with the money.

Why: The record is the asset that outlives the retention. A claim arriving in year four is answered from the naplo, the inspections and the takeover list, and a firm that filed all of it when the money was released is answering from memory instead. Releasing the retention and keeping the file are two decisions, and only one of them should be made at this point.

InExpired jotallas periodOpen defect itemsOutFinal retention releasedRecord kept for the longer period
Modules

Modules in this playbook

7 / 190 platform modules

The market this case is written for

Hungary

Everything in this case follows how construction work is measured, priced and paid for in this market. The forms, the cost breakdown and the payment rules are the ones used there, not a generic version of them.

Standards it follows

  • Kbt.
  • TSZSZ

You do not have to set any of that up by hand. The first time you open the platform it asks which market you work in. Choose this one and it sets the interface language, loads the matching cost database and records the cost classification, and it adds an example project you can open straight away.

The rule checks for this market come with the platform too. Switch them on once and an estimate that misses something the market expects is flagged while you are still working on it, not after the tender has gone out.

More in Handover & lifecycle

Handover & lifecycle

Hand over and close out

Finish the job cleanly: work the punch list to zero, confirm every inspection passed and no…

5 steps14 minOpen
Handover & lifecycle

As-built and O and M handover

Pull the as-built record together, prove the quality file has no gaps, then issue an operat…

3 steps12 minOpen