Kasaba-loyiha

At a design firm, work on a single object is split across five departments (architecture, structures, HVAC, water supply, electrical) and dozens of specialists, while the client side follows the process with its own engineers and accountants. Drawings and expert review comments scattered across e-mail and messengers, and it was easy to lose track of which version was current and who had approved what. They needed one system for the 14 roles on both sides, with strict versioning and a history of every action.

We built one system on a Go (Gin) backend with a Next.js interface. Every object gets an automatic code (PRJ-YYYY-NNN) and is broken down into buildings and departmental sections; tasks move through six stages on a Kanban board (issued → in progress → in review → awaiting chief engineer → returned → approved) and are assigned along the director → chief engineer → head of department → engineer chain. Documents are versioned and commented on, the client side gets an 18-item checklist, and document types are kept distinct (planning permits, architectural/structural/water sets, expert review comments); review comments close in their own flow. The finance and accounting module runs contracts, acts, materials and the address programme, with 8 printable A4 reports and Excel export. An AI assistant was added that works strictly inside each user's own permissions — it never surfaces data the role cannot see. Notifications go out over Telegram and Firebase.

The design process moved into the system completely: object, task, document version, review comment and payment stage are visible in one place, and every action stays in the history. The system covers 14 roles and 5 departments. The whole platform was later moved onto the client's own server (on-premise) — file storage was switched to MinIO and the dependency on external cloud storage was removed, so project documentation stays inside the company.