Case study / Analytics and Design · 2024

ANO “UK NOC RB” Agreement 777-888

EURASIAN NOC
Not a website — 87 pages of analytics.

We developed the technical specifications and designed the system for the Participatory Budgeting Portal of the Republic of Bashkortostan. This is not or development—it is an in-depth audit, a series of interviews with stakeholders, an analysis of the legislative framework, and 87 pages of detailed documentation, based on which the development contractor can build a turnkey product.

This project was created by the team at Halikov Studio · 2024

What's in the technical specifications → Read the case study

Appendix No. 4 · 2024

Technical Specifications
for the Development of a Web Project

pursuant to Contract No. 777-888

Client: Autonomous Non-Profit Organization “Management Company of the Scientific and Educational Center of the Republic of Bashkortostan”

pages of the final technical specifications

information security practices are described in detail

user roles with an access matrix

key objectives of the portal at launch

About the project

A portal where residents of RB decide for themselves what to build.

The nocrb.ru portal is a Participatory Budgeting (PB) tool for the Republic of Bashkortostan. Residents submit ideas—what to repair, what to build, which school project to fund—and and competition commissions review these applications. Six distinct PB practices, five user roles, multi-step application forms, scoring based on dozens of criteria, and integration with municipal reporting.

01 Informing residents about information security programs and success stories
02 Building an information security image through branding and educational materials
03 Convenient idea submission and online tracking of application status
04 Dashboards for curators, moderators, and administrators
05 Transparent contest results with infographics
06 Analytics: submitted / implemented / engagement / finances
07 Compliance with Federal Law No. 152-FZ and information security standards

"So that the development contractor doesn't have to ask ‘What exactly is meant here?’— the answer is already in the technical specifications. For every question. On each of the 87 pages.”

— Halikov Studio, an analytical team

Our steps

Five steps
from questions to a document.

We didn’t just cobble together a technical specification in two days using a template. We immersed ourselves in six separate IT programs , their regulatory framework, the logic of the competitive selection process, and how curators actually work in municipalities.

Phase 1 · Castdev In-depth interviews with stakeholders.

We spoke with the NOC team, ministry representatives, municipal coordinators, and competition committee moderators. We identified real-world scenarios and their bottlenecks—things that cannot be gleaned from the regulations.

Phase 2 · Audit Audit of the existing portal and regulatory framework.

We took a close look at the current nocrb.ru—what works and what’s missing. On top of that — we reviewed Federal Law No. 131-FZ, regional information security programs, methodological guidelines for each practice, standard application forms, and reporting templates.

Phase 3 · Mapping Mapping 6 information security practices and user roles.

We created a map of six initiatives (PPMI, SHIB, Pre-University, Real Deeds, Bashkir Courtyards, Our Village) along with their differences in data flows and participants. We described 5 roles— Guest, User, Curator, Moderator, Administrator—with a permissions matrix.

Phase 4 · Design Scenarios, application forms, and scoring rules.

We designed multi-step application submission workflows specifically for PPMI, SHIB, and Pre-University— including validation, input masks, Dadata integration, and PDF uploads of up to 50 MB. We developed scoring formulas based on dozens of competitive selection criteria.

Stage 5 · Final Final Terms of Reference as an appendix to the contract.

We compiled 87 pages covering topics ranging from the portal structure and roles to notification templates and acceptance criteria. The document was included in the contract as Appendix No. 4— and became the basis for the subsequent stages of development.

Case

Problem → Solution → Result.

The client didn’t know what language to use when communicating with the prospective contractor so that the contractor wouldn’t just put together “something like that portal.” They needed a document they could point to whenever a point of contention arose.

Task

Describe a complex government portal in such a way that any contractor understands the task in the same way.

The National Center of Excellence (NCE) had an existing portal, six separate information security practices each with their own set of regulations, and a request for a major upgrade: new scenarios, role-based dashboards, redesigned , infographics, and competitive analytics. But it’s impossible to describe such a scope in a 5-page text specification—the contractor will get bogged down in interpretations, and the budget will go overboard.

Solution

In-depth analysis and 87 pages of project documentation.

We interviewed all parties involved—the NOC team, curators, and moderators. We thoroughly reviewed the regulatory framework. We designed workflows down to the level of form fields, field validations, application statuses, and scoring formulas. We defined roles with a permissions matrix, integrations (Dadata, VK Auth, news from Telegram/VK/RSS), and notification rules. Each module — with acceptance criteria.

Result

An annex to the contract, ready for tender and development.

The 87 pages of the final technical specifications were included in Contract 777-888 as Appendix No. 4. The client received a document that can be used to conduct a tender, evaluate contractors, and accept completed phases. No “well, we had a different idea” at acceptance—the answer is in the technical specifications. The nocrb.ru portal itself is being developed separately; we only prepared the design portion.

Goals and Objectives ✦

Portal Structure ✦

User Roles ✦

Information Security Practices ✦

Application scenarios ✦

Competition scores ✦

Personal Account ✦

Admin Panel ✦

Integrations ✦

Document Management ✦

Goals and Objectives ✦

Portal Structure ✦

User Roles ✦

Information Security Practices ✦

Application scenarios ✦

Competition scores ✦

Personal Account ✦

Admin Panel ✦

Integrations ✦

Document Management ✦

What's Inside the Technical Specifications

Ten sections,
87 pages of details.

Each section includes examples of user interfaces, field descriptions, validation rules, and acceptance criteria. Below is a table of contents for the key sections.

01 ~5 pages

Goals and Objectives of the Portal

Seven Key Objectives: From Informing Residents to Compliance with Federal Law No. 152-FZ and Information Security.

Visitor Information
Building the IB's Image
User-Friendly and Clear Interface
Collecting and Tracking Requests

02 ~8 pages

Portal Structure and Pages

Header, “About Us,” “Projects,” “News,” “Documents,” “IB Best Practices,” and “Contacts” pages— with sections, filters, and an implementation map.

Menu and navigation
Filters by year, status, and MO
Map of projects in the Republic of Belarus
4 infographic blocks

03 ~6 pages

User Roles

Five roles with a functionality access matrix—ranging from an unauthorized guest to an administrator with full access.

Guest
User (initiator)
Municipal Curator
Moderator and Administrator

04 ~14 pages

6 Information Security Practices

PPMI, SHIB, Pre-University — with sections on “Mission,” “Goal,” “Algorithm,” “Calendar Plan,” “Partners,” “Documents,” “Completed Projects,” and “Analytics.”

PPMI — Local Initiatives
SIB — School IB
PU — Pre-University Program
Real Deeds / Courtyards / Our Village

05 ~22 pages

Application Submission Scenarios

Multi-step forms for PPMI (GO and GP/SP), SHIB, and PU — with validation of full name via Dadata, phone number field, various statuses, and email notifications.

5+ steps to complete
Save draft
Upload PDF up to 50 MB
Document archive “Download all”

06 ~12 pages

Competitive Selection and Scoring

Dozens of criteria with formulas for calculating base and final scores—based on media type, number of publications, initiative group, voting, etc.

Application evaluation criteria
Formulas for calculating scores
Management of application windows

07 ~6 pages

Personal Account

Registration, login (including VK auth for initiators), password recovery, tracking the status of submitted ideas and requests.

Registration and VK OAuth
Password requirements
Application history and statuses

08 ~7 pages

Admin Panel

Management of content, news, best practices, documents, application submission windows, score calculation, and user roles

Content CRUD
Application window management
Assigning curators
Modifying scoring formulas

09 ~4 pages

Integrations and Notifications

Dadata, VK Auth, news feeds from nocrb.ru, Telegram, and VK, email notifications regarding request statuses, input fields, and validation.

Dadata: Full name and addresses
VKontakte OAuth
News feed from social networks
Email and statuses

From the process

Photos from the meetings
and working sessions.

In-depth interviews, audits, mapping. The slots below are for live photos from the NOC and municipalities: these can be uploaded later via the website’s admin panel.

Stage 1 · Castdev Ufa · 2024

Working session / practice review · Ufa, 2024

Stage 3 · Mapping Ufa · 2024

Interview with a municipal coordinator · Bashkortostan, 2024

Stage 1 · Castdev Bashkortostan · 2024

Final specification review / acceptance · Ufa, 2024

Stage 5 · Final Ufa · 2024

Final artifact

Technical Specifications
as an attachment to the contract.

The document was included in the contract as Appendix No. 4 and served as the basis for the subsequent tender and development. The nocrb.ru portal itself is no longer our responsibility.

DocumentTechnical Specifications
TypeAppendix No. 4
ClientANO “UK NOC RB”
ContractorIndividual Entrepreneur L.D. Khalikov
Volume87 pages

Would you like the same technical specifications?

Before we get started —
let’s conduct a thorough analysis.

We approach the product from a design perspective: interviews, audits, scenarios, forms, and acceptance criteria. The end result is a document that leaves nothing to the contractor’s imagination.

Go to nocrb.ru All of the studio's case studies

EURASIAN NOC Not a website — 87 pages of analytics.