Organising a joint tender in Estonia's procurement register

A joint tender in Estonia needs a single commercial account of who will deliver the contract, even when several companies prepare different parts of the response. The procurement register can represent those companies and their users, but the business must first agree what their participation means. A partner named in a sales presentation is not yet a fully organised tender participant.

The useful starting point is a work allocation rather than a list of account names. Identify the proposed contracting participants, the resources supporting qualification and any subcontracted work. Then connect that structure to the evidence and people required in the electronic response. This prevents the portal configuration from becoming an accidental substitute for the actual consortium arrangement.

Give each company a definite role

The Ministry of Finance's Estonian supplier manual for RHR 5.3 distinguishes joint tenderers from subcontractors. Within subcontractors, it distinguishes entities whose capacity is relied upon from those whose capacity is not relied upon. The former may require their own ESPD or responses to the relevant exclusion and qualification questions, according to the procurement's requirements.

For a hypothetical facilities-information project, an Estonian surveying business might prepare property records while a Finnish software company provides the information-management service. The companies should decide whether they are submitting jointly or whether one is contracting with the other for a defined contribution. That decision should precede the distribution of portal tasks.

The distinction affects the commercial conversation. In a joint response, the companies need to reconcile their shared offer and respective obligations. In a subcontracting arrangement, the lead bidder needs an enforceable understanding of the supporting service and its price. Simply calling every contributor a consortium member can conceal who actually accepts the customer's requirements.

Prepare one short participant map naming each legal entity, its proposed work and the evidence attributed to it. If a qualification response cites a partner's project experience, the map should explain how that partner contributes to this contract. The purpose is to make the proposed delivery model intelligible, not to collect the maximum possible number of impressive company names.

Separate workspace permissions from company authority

The same RHR manual describes a responsible person and authorised users associated with a tender. It expressly distinguishes the portal's authorised-user role from a company's representation rights in the business register. A team can therefore have permission to edit a response without that permission itself proving authority to bind the business.

For the surveying and software companies, this calls for two parallel decisions. The companies establish who may approve their commercial commitments. They also assign the people who will prepare, review and submit information in the register. Sometimes one person performs both functions; the underlying authority and the electronic permission still come from different places.

A proposal coordinator may be well placed to assemble the complete response while a director approves the service commitments. The technical lead can check the scope of the software service without controlling the final price. Making those responsibilities explicit allows each person to review the part they understand and gives the coordinator a clear basis for the final submission.

This arrangement also makes substitution manageable. If the main coordinator becomes unavailable, the replacement needs suitable system access and a clear record of what the companies have approved. Handing over a password or forwarding a folder does not explain which figures remain provisional or which partner has accepted a revised delivery period.

Build the shared offer from traceable contributions

The State Shared Service Centre's procurement-register explanation presents the register as the place where purchasing intentions, procedure information and concluded contracts can be found. That continuity is commercially useful: the response should describe an arrangement the participants could actually carry into delivery, rather than a temporary collection of documents assembled only to pass the tender stage.

The hypothetical partners should agree a common description of the proposed service. The surveying company might own the initial collection and correction of property records, while the software company maintains the hosted service and user support. Their schedules must meet at a clear handover point. A promise of rapid software deployment is unhelpful if the required records will not be ready.

The price should reflect the same allocation. Establish which company has included onboarding, travel, data correction and recurring support. If each assumes the other has priced user training, the combined offer may omit a real delivery cost. If both include the same work, the proposal may become unnecessarily expensive or leave an unclear invoicing arrangement.

Evidence should follow those responsibilities. A reference for surveying work supports the surveying contribution; a software service record supports the relevant service claim. Where the response relies on a combined capability, explain the connection between the contributions rather than presenting the partners' experience as though it belongs to one undifferentiated company.

Use registration and communication deliberately

The official February 2023 getting-started guide explains that registering interest in a procurement enables notifications, questions and electronic submission. It also distinguishes the tender's suitability questions from the award-criteria fields. Those are different parts of the response and should receive deliberate ownership within the team.

The coordinator should route a clarification to the partner whose commitment it affects. A question about a required delivery period may need both companies' input, whereas a question about a particular reference document may belong to one. Preserve the published answer with the affected response material so that a late reviewer can understand why the offer changed.

Agree a common working interpretation of deadlines, especially across borders. The getting-started guide notes that the system view can display time according to the user's computer setting while notices and notifications use local time. Put the actual procurement deadline and the team's earlier approval deadline in one shared record, with the time zone stated explicitly.

Companies assessing Estonian defence-investment opportunities by purchasing category can use this organisation to move from broad market interest to a specific deliverable offer. Category knowledge helps identify suitable work; the joint tender still needs evidence and responsibilities matched to the particular procurement.

Review the completed response as a joint commitment

Before submission, the partners should review the assembled offer rather than approving their original attachments in isolation. Check that the final company names, work allocation, qualification claims and price still agree. A late edit to the service schedule may alter a commitment that another participant approved several days earlier.

Use a practical reconciliation: compare the participant map, the delivery description and the commercial totals with the material actually included in the response. Ask each partner to approve the commitments attributed to it. Record unresolved dependencies as decisions to settle before submission, rather than hiding them behind broad language about future cooperation.

The same discipline helps distinguish tender preparation from a wider investment relationship. An Estonian industrial-park opportunity can shape a company's future local presence, but it should not be represented as an existing facility or resource in a tender unless the claimed position is supported. The offer needs to describe what the participants can commit for this contract.

The result should be one response whose portal structure, supporting evidence and commercial arrangement tell the same story. That gives the partners a stronger basis for answering buyer questions and, if selected, for beginning delivery without renegotiating the fundamentals they should already have settled together.