Nach dem Kbt. auf einen öffentlichen Bauauftrag bieten

Open the tender as a procedure of its own and record the becsult ertek of the whole work, the procedure type the contracting authority chose and whether it sits above or below the national threshold. Read the value across the whole work rather than per lot, because that is how the threshold is measured.

Warum: The national thresholds are set in the central budget act for the year and republished by the Kozbeszerzesi Hatosag each January, so last year's figure is the wrong figure and nobody is going to warn you. Kbt. 19. governs how the estimated value is worked out, and choosing a method that keeps a work under a threshold is the finding that undoes a whole procedure, so the number you record here is the number the file has to defend.

Save the kozbeszerzesi dokumentumok exactly as they came out of the EKR, with the date each item arrived. Record the deadline for offers and the ajanlati kotottseg, the period your price is bound for, next to them.

Warum: Documents are corrected and reissued during the bidding period, and every clarification the authority answers goes to all bidders. Keeping the version you actually priced is what lets you show weeks later which set your offer answers, and the bound period is what tells you how long a win can still cost you if your suppliers move.

Read the unpriced itemised bill in as the bill you price, keeping the tetel numbering, the unit and the quantity the authority issued. Put a unit price on every line, including the ones you would normally carry inside another rate, and read each tetel description before you price it.

Warum: Government Decree 322/2015 (X. 30.) is what puts the itemised bill at the centre of a Hungarian construction procurement, and the priced version you return is read line against line rather than as a total. One tetel left at zero, one renumbered line or one unit quietly changed is enough to make the offer unreadable against the others, and an unreadable offer is not a cheap offer.

Record the basis under the offer while you still remember it: which norm set the labour hours, which rezsioradij the dij is built on, which quotes carry the anyag, what the preliminaries assume and which risks are priced rather than excluded.

Warum: Kbt. 72. lets the contracting authority demand a justification where a price or a cost element looks disproportionately low, and it may reject an offer whose justification does not stand up. That request arrives with a short deadline, weeks after you priced, and the difference between keeping the job and losing it is whether the calculation behind the number already exists in writing or has to be rebuilt from memory in three days.

Build the non-price half of the bid as its own package: the egyseges europai kozbeszerzesi dokumentum, the declarations on the kizaro okok, the references and the professionals the alkalmassag criteria ask for, and the ajanlati biztositek where the notice requires one. Name any capacity provider and any subcontractor the notice makes you name.

Warum: In an EU-threshold procedure the EEKD is a preliminary declaration and the underlying certificates are called in later, which tempts a bidder to treat the form as a formality. It is not one: a declaration that does not match the certificates that follow it is worse than a missing reference, because it reads as a false statement rather than as a gap, and the consequence is exclusion rather than a request to complete the file.

Run validation over the whole submission before it goes anywhere: every tetel priced, quantities and units unchanged from the kiiras, the totals adding up, and every document the notice lists actually present in the package.

Warum: Everything an evaluator can reject an offer for is mechanical, and every one of those things is cheaper to find here than in an answer to a hianypotlas under a three-day clock. This is also the last moment at which a decimal place in the total is still an internal problem.

Send the offer up through the EKR before the deadline and keep the transmittal record of what went, when, and under which procedure identifier. Communication in the procedure runs through the same system, so the record and the correspondence stay in one place.

Warum: The EKR timestamps the submission, and a bid that lands after the deadline is not a late bid, it is not a bid. Bidders lose work every year to an upload begun twenty minutes before the hour on a file that turned out to be larger than the connection, which is a scheduling failure rather than a commercial one.

When the authority asks for the file to be completed, put the request on the correspondence thread with the deadline attached, answer exactly what was asked and nothing else, and record what went back and when.

Warum: Kbt. 71. is the second chance the procedure gives you, and it is the only one. The deadlines are short, they run in working days, and they are usually set while the person who assembled the bid is on another job. An answer that arrives a day late is treated the same as no answer, and an answer that changes something nobody asked about invites a different problem.