Managing residential construction in Uzbekistan — what we see go wrong
Residential projects in Tashkent, Samarkand, and the regions have a predictable set of operational failure modes. Here's what they are and how to prevent them.
A 9-story residential building in Uzbekistan looks like a simple project on paper — the structural system is standardized, the unit layouts repeat, the finishing packages are well understood. In practice, the same seven problems show up on almost every site we look at. None of them are technical. All of them are operational.
Problem 1 — The SMETA is an optimistic fiction
The SMETA was produced during the tender to win the project. It was not built to be executed from. Quantities are rounded down, prices are last year's, and half the finishing lines say "standard" without specifying what standard. By month two, the SMETA is a reference document no one actually tracks against.
The fix is a two-week reconciliation at project start — the prorab and the finance lead go through every line, adjust quantities to real execution, update prices to current market, and produce a "working SMETA" that is what gets tracked. The tender SMETA becomes historical reference.
Problem 2 — Material deliveries arrive without warning
The delivery calendar exists in the procurement manager's head. The warehouse manager finds out when the truck arrives. The prorab finds out when the warehouse manager calls. This is how 3-hour unloading operations become 7-hour operations because nothing was staged.
The fix is a 48-hour rolling delivery schedule — every delivery confirmed and communicated to warehouse + site 48 hours before arrival. One Telegram message. Thirty seconds to send. Saves hours on both ends.
Problem 3 — Subcontractors work without a scope sheet
Uzbek residential construction leans heavily on subcontractors for electrical, plumbing, HVAC, finishing. The standard engagement is "we agreed on X million for the whole job." What "the whole job" actually includes is in everyone's heads and differs by person.
The fix is a one-page scope sheet per subcontractor: what is included, what is excluded, what triggers change orders, what the acceptance criteria are. Signed before the first day of work. The 30 minutes this takes prevents three weeks of end-of-project arguments.
Problem 4 — Cash flow is project-wide, not phase-based
Money flows in big chunks from the client when milestones are hit. Money flows out constantly — to suppliers, brigades, subcontractors — regardless of milestones. The mismatch is the number one reason solid projects produce bad months.
The fix is phase-based cash planning — each construction phase has its own expected inflow and outflow, and the director approves any outflow that crosses the phase boundary. This is not bureaucracy; it is the only way to catch a phase that is going to run out of cash before it actually runs out.
Problem 5 — Quality issues are caught at acceptance, not during work
The client inspector arrives at acceptance. They find 47 issues. Now the subcontractor is off site, the materials are used up, and every fix is expensive. The director absorbs the cost because the alternative is a 3-month dispute.
The fix is a weekly quality walk during the work, not just at acceptance. Prorab, director or deputy, subcontractor lead — 30 minutes per floor, items written down and numbered, closed the same week. The cost of a weekly walk is a rounding error compared to the cost of end-of-project rework.
Problem 6 — Late-stage scope creep from the owner
Every residential project we have seen has had at least one conversation three months in where the owner wants "a small change" that is not small. An additional elevator. A different facade cladding. A basement gym. Each of these is a project in itself, pretending to be a change request.
The fix is a scope-change register from day one. Every change, written down, priced, signed by both parties before work starts. Three-minute discipline per change. The register becomes evidence when the final payment is negotiated.
Problem 7 — Handover drags because documentation was last-minute
Acceptance documentation — technical passports, warranty docs, as-built drawings — is almost always produced in a panic in the final two weeks. Half of it is missing, half of it is wrong, and the state inspector takes weeks to review. The client blames the director.
The fix is "documentation at the phase" — every phase produces its own completion dossier at the end of that phase, while the people who did the work are still on site and the materials receipts are still fresh. By handover, the documentation is already done. The final two weeks are for formatting and signing, not for archaeological reconstruction.
The pattern
Six of the seven problems are communication problems disguised as technical problems. The SMETA is fine if it is tracked against. Deliveries are fine if they are scheduled. Subcontractors are fine if their scope is written. Quality is fine if it is inspected weekly. Scope is fine if changes are logged. Documentation is fine if it is produced as you go.
None of this requires software, though software makes each one faster. What it requires is the director deciding that the operational loop matters as much as the construction itself — which is the decision that separates residential projects that finish on time from the ones that finish six months late with 15% loss.