Horizon research dossier · Georgia · Transport and logistics · reviewed 2026-10-11

Georgia logistics and Trans-Caspian connectivity: a full decision dossier for a defined shipment, service or infrastructure proposition

Decision question: Under what evidence conditions should a shipper, operator, technology firm, terminal supplier, engineering company or investor advance a Georgia logistics proposition to a controlled route test or authorised project pursuit?

Verified facts

World Bank, Georgian and international sources document corridor investment, procurement and trade-data context; none establishes an available shipment, service level, terminal slot, project eligibility, customer mandate or supplier appointment.

Horizon view

Georgia should be approached through named route nodes or an authorised project package, with separate evidence files for freight, digital workflow and procurement.

Commercial implication

Require current responsibility, capacity, documentation, counterparty, data, risk-allocation and commercial evidence before quoting, bidding or committing resources.

Dossier sequence

1. Decision scope and non-claim boundary

This dossier is for a defined Georgia logistics proposition: a freight movement, forwarding/terminal service, route-visibility workflow, storage or handling offer, corridor technology, rail/road/port equipment, engineering assignment or project-package hypothesis. It does not establish that a corridor is operationally suitable for any cargo, that an infrastructure programme is open to a supplier, or that a local party is an authorised partner. The initiating brief must state origin, destination, commodity/service, volume, frequency, handling condition, customer, required delivery outcome, commercial role, budget holder and decision date. It must also identify the evidence source expected to validate each critical assumption, and the owner who will obtain it. Without those elements, a corridor description remains geographic context rather than a viable logistics decision.

2. Evidence hierarchy and dated facts

The World Bank TC-GATE approval, its project and procurement documents, Georgian Roads Department notices, Geostat data, EBRD strategy and European Commission connectivity material have different evidentiary roles. Finance approval shows a programme; a procurement notice applies to a specific package and period; trade statistics describe historic aggregates; strategy documents frame needs; operator or contractor evidence may speak to a defined service. Record the source, date, publisher, geography, route segment, asset/package, decision relevance and expiry trigger. Do not convert an investment figure into capacity, a trade statistic into customer demand, a tender notice into general eligibility or a policy statement into a commercial promise. Evidence must remain traceable, current and proportionate.

3. Split shipment, service and project decisions

A shipment requires a current operator chain, commodity-specific acceptance, equipment, bookings, documents, tariff basis, insurance, liability and contingency handling. A digital/logistics service requires a named workflow, system/data owner, authorised user, interface, support model and commercial route. A project pursuit requires an authorised package, implementing entity, notice, qualifications, technical scope, funds source and contract authority. These are not interchangeable decisions. TC-GATE and related connectivity evidence can frame all three research paths, but it cannot establish any one of them. Maintain separate files and stop conditions so a freight enquiry does not become an unsupported procurement pursuit, or a project notice a claim of route capacity. The commercial team should label every record accordingly before it enters a dashboard, avoiding a combined pipeline of incomparable activities.

4. Route and node architecture

Map the actual movement rather than a regional line on a map. Identify pickup, origin warehouse, exporter, rail/road acceptance, border point, terminal, port or sea interface where relevant, onward transport, customs/transit role, destination terminal, importer/consignee and final delivery. At each hand-off, name the party that contracts, possesses cargo, owns or transmits data, bears risk, handles claims and informs the customer. Record operating hours, booking and cut-off rules, equipment and cargo restrictions, dwell-time evidence, storage exposure, disruption alternative and escalation contact. A route has no commercial meaning until the chain is complete for the proposed cargo and time window. The route map should show the evidence source and last verification date next to every node, then flag gaps that require operator confirmation. It should also state whether the plan is door-to-door, terminal-to-terminal or only a conceptual corridor leg. This prevents a partial service estimate from being presented as an end-to-end solution.

5. Capacity, performance and service evidence

Capacity is a condition at a bottleneck and date, not a general property of a country or corridor. Request written, current information for commodity acceptance, equipment type, volume limits, booking lead time, train/vessel or road schedule, terminal handling, cut-offs, border/inspection process, seasonal constraint, dangerous-goods or temperature-control conditions, claims procedure and re-routing. Distinguish a published schedule, an estimate and completed-performance evidence. Define whether a transit measure is port-to-port, terminal-to-terminal or door-to-door, and when its clock begins. A national programme or macro figure cannot support a transit-time promise, customer penalty commitment or inventory model. For each variable state the relevant cargo and season, the source/owner, the measurement period and the circumstances in which it would no longer be valid. A good service file preserves adverse or failed-movement evidence; only collecting favourable performance creates a false reliability assumption.

6. Tariff, landed cost and risk allocation

Build a route-specific cost model: pickup, export handling, carrier charges, rail/road/sea legs, terminal and port charges, documentation, broker fees, inspection, storage, demurrage/detention exposure, insurance, destination handling, last mile, tax/currency and exceptional-cargo charges. Identify whether each figure is a binding quote, tariff, customer assumption or internal estimate. Model disruption as well as base case. Confirm the delivery term, title and risk transfer, liability caps, declared-value requirements, exclusions, damage notice, claim handler and insurer. A low headline rate does not establish competitive landed cost if it omits waiting, handover, claims or working-capital exposure. The model needs payment timing and cash exposure as well as price: deposits, prepayment, credits, claim recovery, currency conversion, invoice disputes and delayed release can change route viability. Do not compare routes until the assumptions and inclusion/exclusion boundary are identical.

7. Documentary, customs and compliance gate

This dossier does not determine customs or trade-compliance treatment. For a named movement, establish commodity classification, origin, exporter/importer authority, commercial/transport documents, transit declarations, permits or controls, packing/labelling, inspection, insurance, sanctions/restricted-party screening, broker role and document-language/legalisation needs. Assign an owner, issuing authority, validity date, review point and escalation path to each item. Route investment, a country trade portal or a forwarder introduction cannot complete this gate. Do not release a shipment, make a compliance claim or accept a customer delivery obligation until the document chain and accountable parties have been verified for the specific product and counterparties. The gate should show which documents are required before booking, loading, border arrival and release, and whether a correction can be made without cargo loss, storage cost or contractual breach. Keep local specialist confirmation distinct from Horizon’s research synthesis.

8. Project and procurement route

TC-GATE procurement material and Georgian Roads Department notices are valuable because they identify a formal evidence route, but only for their stated package and validity period. Before pursuing any infrastructure, consulting, equipment or technology opportunity, confirm the exact component, client, financing, procurement method, notice status, eligibility, required credentials, technical terms, timetable, language, submission process, local-delivery expectation, decision authority and conflict conditions. Keep a package-level record of positive and negative results: a project may be funded yet closed, outside scope, already contracted or mismatched to the company. A project page, investor forum or general connectivity policy is not an invitation to bid. The bid/no-bid record should assess legal entity and local-registration needs, reference thresholds, financial/security requirements, permitted partner structure, conflict checks, preparation cost and realistic delivery responsibility. If an authoritative requirement is missing, monitoring; not early supplier positioning; is the proper result.

9. Digital logistics and data boundary

A visibility, document, tracking or optimisation proposition must begin with one workflow: booking, terminal appointment, milestone update, exception handling, trade document exchange, invoice/reconciliation or inventory hand-off. Identify system owner, authorised users, data fields, source of truth, interface, hosting, retention, identity/access control, security review, support responsibility and change authority. National digitalisation or corridor programmes do not grant a private supplier access to production systems or commercially sensitive data. Use approved non-production data where possible. A dashboard demonstration may show product capability, but it is not evidence of data quality, interoperability, legal access, customer acceptance or operating performance. The evidence plan should define refresh frequency, accuracy threshold, exception ownership, audit trail, user training, backup path and shutdown procedure. If a route’s commercial value depends on live data but the data owner cannot authorise it, treat the value hypothesis as unproven.

10. Counterparty and local-delivery diligence

Assess each forwarder, carrier, terminal, broker, integrator, engineering firm, adviser or customer as an accountable entity. Verify legal identity, ownership, authority, operating role, licences where relevant, geographic coverage, physical assets, staff, subcontractors, insurance, claims handling, customer references, integrity/sanctions exposure, data practices, financial resilience and exit/transition plan. A trade-body profile, event meeting or public listing cannot prove capability. The delivery design should specify who sells, books, moves or configures, supports, communicates delay, owns each escalation and reports performance. Require current proof that the entity can carry the allocated responsibility rather than a similar but unrelated reference. If responsibility is diffuse, hold the proposition rather than relying on assumed coordination. The diligence file must also identify contractual liability limits, any use of subcontractors and the customer’s remedy if performance or communication fails.

11. Commercial model and customer system

Define the customer problem and buying system before offering a route or capability. A cargo owner may value resilience, cost predictability, visibility, handling, storage, customs coordination, project-cargo control or emissions reporting; an operator may value equipment, workflow automation, maintenance, energy efficiency or safety. Map economic buyer, logistics/technical owner, procurement, finance, compliance, end user and contract owner. Then connect the value hypothesis to price, implementation/service cost, payment timing, currency, performance obligations, customer data/reporting and termination. Corridor investment does not identify a buyer. A relationship becomes a pipeline only when a named party accepts a bounded problem and next evidence step. The account plan should preserve the decision sequence and declined assumptions so a sector narrative cannot substitute for the customer’s actual economics, authority or operational constraints.

12. Controlled pilot or route test

The first operational action should resolve one defined uncertainty. For freight it may be a low-volume or sample movement with written bookings, documents, insurance, milestones, contingency and after-action review. For technology it may be an authorised workflow test with a data boundary, user group, security control, measure and stop condition. For a project it may be procurement-readiness analysis only where the official route allows it. The charter must state participants, cost allocation, evidence method, success measure, delay/damage or incident protocol, confidentiality, decision owner and exit. It should also specify whether the movement or test has a commercial customer, who owns the cargo/data at closure, how deviations are approved, and what happens to residual stock, documents and access rights. A meeting, memorandum, generic rate sheet or route map is not a pilot.

13. Contracting and governance

Before scale, confirm legal parties, authority, scope, service levels, acceptance, price/currency, payment security, insurance, liability, cargo/data access, confidentiality, IP, subcontracting, performance reporting, change control, compliance, termination and handover. The contract type must suit the route: shipment booking, service agreement, pilot letter, technology statement of work or authorised procurement contract. A local partner cannot solve a contract that does not allocate claims, customer communication, data responsibilities, storage/return, delay or transition. Maintain a governance calendar with operating contacts, escalation levels, evidence repository, performance-review cadence and the rule that no public claim may outrun the current documented evidence. The contract file should state which operational evidence is incorporated, what reports are binding, how a dispute is notified, who approves deviations and what happens to cargo, data, tooling, system access or customer communication at exit.

14. Risk register and stopping conditions

Risks include missed capacity, border or terminal delay, document failure, cargo loss/damage, insurance exclusion, storage/demurrage, subcontractor failure, payment or currency exposure, sanctions/integrity issue, data/cyber incident, site/safety concern, procurement ineligibility, performance dispute and reputational overclaim. Each requires source, owner, mitigation, residual exposure and an explicit stop trigger. Stop before exclusivity, volume or delivery commitments, production-data transfer, binding quote, bid submission, sensitive site access or public customer/project statements when authority, document route, operational condition, commercial allocation or compliance control is unresolved. A documented hold is more valuable than a corridor claim that cannot be delivered. The record should distinguish controllable operational risk from unverified external conditions, then set a date at which unresolved evidence forces a stop rather than a further extension of assumptions. Owners must confirm closure in writing.

15. Final decision gate

Advance only when a defined shipment, service workflow or authorised project connects to current primary evidence; named accountable counterparties; an executable commercial or procurement route; complete document, data and operating boundaries; viable local delivery; a documented financial/risk model; and a bounded next action. The decision record must separate facts, Horizon inference and commercial implication; list open items; name the approver; limit permitted spend/activity; set evidence expiry; and identify prohibited actions. A go permits only the stated test, bid or negotiation. It does not approve a carrier, terminal, customer, authority, project, tender, contract, route performance or transaction. Reopen the dossier after any material change to route, cargo, project, counterparty, conditions or regulation. Before decision, the owner must check that current written evidence; not a prior discussion, map or macro statistic; supports every material operating claim. A positive decision should state the maximum commitment, the evidence expiry date, the customer/project owner and the immediate stop condition. Where any material element is unverified, hold and request it from the accountable party rather than filling the gap with corridor narrative. No exception is implied.

What to verify before acting

This completed research dossier is not Georgian transport, rail, road, port, terminal, maritime, customs, procurement, data-protection, cybersecurity, sanctions, export-control, insurance, tax or legal advice. It does not approve a carrier, forwarder, broker, terminal, operator, authority, platform, project, tender, supplier, customer, contract, shipment or transaction.

Current market intelligence

Signals connected to this dossier

28 October 2026

Georgia’s September banking data show broad credit and deposit growth

Companies evaluating Georgian financing should monitor three next checks: the National Bank’s next lending and asset-quality release; policy-rate, inflation and exchange-rate developments; and changes in foreign-currency exposure and sector lending. A bankability file should record borrower and sponsor, project or working-capital purpose, facility type, currency, tenor, collateral, covenants, equity contribution, sensitivity, fees, insurance, approvals, disbursement, repayment and default terms before treating aggregate credit growth as commercially relevant.

13 October 2026

Uzbekistan and Georgia advance a Poti logistics-centre route for Black Sea market access

Create a Poti route file with separate workstreams for product groups, forecast volumes and seasonality; Uzbek collection and packaging; rail, road and Caspian interfaces; Poti free-zone, terminal, warehouse and cold-chain counterparties; maritime service and destination-port hand-off; customs, origin, transit, sanitary or phytosanitary documentation; cargo insurance and claims; data and tracking; service-level measures; pricing, currency, tax, invoicing and payment terms. Obtain current written evidence on asset status and specific service availability before offering a route, reserving capacity or representing access to a customer.

18 October 2026

Georgia broadens the road-infrastructure delivery conversation ahead of a stated new-project pipeline

Create a Georgia infrastructure account map around a defined proposition such as design, engineering, construction management, specialist materials, road safety, bridges, tunnelling, geotechnics, drainage, digital monitoring, quality assurance, equipment, maintenance or training. For each target authority or project, verify the published procurement notice and package; legal bidder and consortium structure; qualification and reference criteria; local labour, plant, safety and environmental requirements; design and technical standards; financing and performance-security conditions; programme, acceptance and defects-liability terms; insurance, tax, currency, invoicing and payment mechanics. Use the State Procurement Agency record and the accountable authority documents as the controlling evidence before allocating bid resources or making any market-access claim.

Relationship platforms

Autumn 2026; online masterclasses, October–November incubation and late-November Demo Day described by GITA; exact participant schedule requires recheck · Kakheti Regional Tech Parks, Georgia

Wine Incubator 2026

27–28 October 2026 · Tbilisi

Tbilisi Finance Summit 2026

6 November 2026 · Tbilisi

eCommerce Georgia 2026: Conference and Expo