Client case study · Rajshahi City Corporation

Shohor · RCC

Every municipal service, on one governed record.

Rajshahi City Corporation uses Shohor, the Tiger One module for citizen services, to connect revenue and taxation, licensing and permits, civil registration, property and markets, public health and welfare, back-office workflow, finance and platform services in one governed enterprise environment.

ClientRajshahi City Corporation (RCC)
SolutionShohor, the Tiger One citizen-services module
FocusConnected city-corporation operations
Share

A city corporation’s responsibility spans services, revenue, assets and public space.

Rajshahi City Corporation administers a wide range of municipal responsibilities, from citizen-facing services such as trade licensing, holding-tax assessment and civil registration to market management, public health, environment and welfare, and the back-office, finance and platform functions that support them. Each of these responsibilities generates its own records and decisions. Shohor provides an enterprise layer through which these service domains can be viewed as parts of the same institutional record.

30wards described by RCC’s official portal
6municipal departments listed in RCC’s public institutional profile
One portalfor bilingual, citizen-facing access to multiple municipal services

Challenge

See a wide municipal mandate as one operating system.

01

Many service domains

Citizen requests, complaints, licensing, holdings, assets and field work each create their own records and decisions.

02

Citizen expectations

Residents expect requests and complaints to be tracked and answered, not lost between departments and counters.

03

Exceptions hidden in volume

Overdue requests, ageing complaints and administrative gaps need to be visible before they become routine.

Solution

Shohor becomes a shared enterprise record across every service category.

The module organizes the corporation’s work into the same service categories used in Shohor’s own module inventory, while presenting management with a shared enterprise view. It does not reduce every function to a single screen; it gives each function a place in the same governed system.

01

Revenue & Taxation

Holding tax assessment, amendment, appeal and review, with merger and name-separation workflows for the underlying holding record.

02

Licensing & Permits

Trade and advertisement licences, contractor enlistment, and premises, medical, educational and pet registrations, each with its own renewal cycle.

03

Civil Registration & Certificates

Birth, death, citizenship, inheritance (waris) and divorce registration, plus configurable certificate types beyond the standard set.

04

Property, Markets & Rentals

Market shop allotment, sublet and transfer, road, sidewalk and vehicle rental, and legacy allotment records kept searchable.

05

Public Health, Environment & Welfare

Waste management, pollution complaints, water and gas connections, immunisation records, dispute resolution and citizen welfare support.

06

Back Office & Workflow

Staff workspace, department and role-based routing, ward and address registry, e-Nothi integration, reporting and citizen messaging.

07

Finance & Payments

Invoicing and ledger control, online payment gateway integration, and bank and challan reconciliation.

08

Platform

A bilingual citizen portal, OTP login, push notifications, a documented API and per-deployment configuration.

Representative management view

Turn many service counters into one management conversation.

A leadership view can summarize demand, workflow movement, ward-level patterns and the exceptions that need attention while keeping citizen records and sensitive operational figures inside the governed system.

01

Service demand

Compare applications and requests by service domain and ward.

02

Workflow movement

See where applications are waiting between review, payment, approval and issue.

03

Revenue control

Connect assessment, collection, receipts and reconciliation without publishing sensitive figures.

04

Management attention

Bring ageing requests, renewal deadlines and field follow-up into one review queue.

SHOHORMunicipal operations
Representative visual · no live data
Citizen servicesDemand by domainApplications · requests · renewals
WorkflowStage and ageingReview · payment · approval · issue
GeographyWard-level viewDemand · complaints · field follow-up
ManagementAttention queueExceptions · deadlines · reconciliation
Service demand by domainIllustrative relative pattern
Revenue & taxation
Licensing & permits
Certificates
Engineering & rentals
Health & welfare
Ward-level service pattern30 public administrative wards
123456789101112131415161718192021222324252627282930
Management attentionGoverned exception view
01
Ageing service requestsReview by department and stage
Review
02
Renewal deadlinesLicences, permits and registrations
Plan
03
Payment reconciliationAssessment, receipt and bank record
Match
04
Field follow-upComplaints, assets and assigned action
Assign
Conceptual Shohor management view created for this public case study. It illustrates the management questions the connected record can support; it is not an RCC system screenshot and contains no operational data.

Connected service cycle

From citizen application to a closed, verifiable record.

01Apply

A citizen applies online, in Bangla or English.

02Assess

The fee is assessed against the relevant service and ward.

03Pay

Payment is collected online and a receipt issues instantly.

04Approve

An officer approves through the routed department workflow.

05Issue

A certificate or approval issues, verifiable and on file.

Operational value

A clearer institutional line of sight across connected municipal operations.

One municipal vocabulary

Citizen requests, complaints, holdings, licensing and assets are organized within a shared environment rather than isolated department views.

Exceptions become visible

Overdue requests and unresolved complaints can be surfaced for focused review within governed workflows.

Reusable civic data

The same structured records can support management reporting and deeper service and asset analysis over time.

Next opportunity

Turn connected municipal records into service intelligence.

As completeness and history grow, this deployment can move beyond consolidated reporting toward governed analysis that helps the corporation prioritize maintenance, improve service response and coordinate departments more effectively.

01

Service-level intelligence

Combine request type, routing and resolution history to see where citizen response could improve.

02

Maintenance prioritization

Connect asset condition, complaint patterns and field history to plan upkeep with better evidence.

03

Revenue and compliance patterns

Compare holdings, licensing and assessment records to support fair, consistent administration.

04

Area-level performance view

Relate requests, complaints and field activity by zone and ward to guide local attention.

05

Field-team coordination

Use assignment, location and workload patterns to improve coverage and response time.

06

Cross-department coordination

Connect assets, services and complaints across departments to reduce fragmented handling.

Grounded in RCC’s public service mandate.

This case study presents the platform at a high level without publishing internal screens or operational figures. Institutional framing is supported by Rajshahi City Corporation’s official portals, which describe its 30 wards, six municipal departments and the citizen services administered across those departments.

Hero photograph of Rajshahi City Corporation’s Nagar Bhaban headquarters by Nahid.rajbd, Wikimedia Commons, licensed under CC BY-SA 4.0. No confidential operational data is reproduced.

One institution. One governed view.

This deployment shows how Shohor can reflect the operating reality of a city corporation.

Discuss an enterprise municipal platform