Sindh IT Portal — Facilitation DeskSpecification documents
Englishاردوسنڌي
← All documents

Vision & Scope

The executive overview for the Sindh IT Portal — Facilitation Desk: what it is, why it exists, who it serves, and what it will (and will not) deliver in Version 1.

Field Value
Doc ID 00
Status Draft
Owner S&ITD / MAAHIR
Languages EN (master) · UR · SD

1. Executive Summary

The Sindh IT Portal — Facilitation Desk (abbrev. SITP) is a standalone, AI-enabled, multilingual facilitation and grievance platform built by the Science & Information Technology Department (S&ITD), Government of Sindh, for IT companies and investors operating in Sindh. Its purpose is to give the IT industry a single, trusted window through which problems involving any Government of Sindh department can be logged, tracked, coordinated, and resolved — quickly, transparently, and with accountability at every rung.

The platform is delivered as a Public-Private Partnership (PPP): owned and politically directed by S&ITD, operated by MAAHIR, and hosted on Server4Sale infrastructure at the canonical URL https://sindhitportal.maahir.io. The footer of every page reads "Operated by MAAHIR · Powered by Server4Sale."

The Portal serves three languages out of the box — English (master), Urdu, and Sindhi — with full right-to-left (RTL) rendering for Urdu and Sindhi, WCAG 2.1 AA accessibility, and a dual Gregorian and Hijri (Islamic) calendar consistent with government convention. The visual identity is Ajrak-inspired, paired with the Government of Sindh seal and the S&ITD logo.

SITP is not a general-purpose complaints box. It is a specialized facilitation instrument for the IT industry — built to absorb the full lifecycle of an IT company's interaction with government: from information and self-service, through formal ticketing and inter-departmental escalation, to tripartite hearings, signed resolution letters, and public transparency reporting. It is S&ITD's deliberate evolution toward a SIFC-style "single window" for the IT industry at the provincial level: one door, every department behind it, the IT company in front of it.

This document is the executive frame for the entire documentation set. It defines the product identity, the problem it solves, the vision and mission, the goals, the success metrics, the stakeholders, the scope boundary, and the assumptions, dependencies, and risks. Detailed requirements, workflows, and technical specifications live in subsequent documents and are cross-referenced where relevant.


2. Problem Statement

2.1 The friction IT companies face

An IT company in Sindh — whether a SECP-registered firm, a sole proprietor, a freelancer, a foreign branch, or an early-stage startup — must routinely transact with many different Government of Sindh departments and provincial/federal bodies. A short, illustrative list:

Each of these operates its own processes, counters, forms, and response norms. There is no single coordinated channel that lets an IT company raise a problem once and have it routed, tracked, escalated, and closed across the relevant departments. As a result:

2.2 Why the existing channel is not enough

The Government of Sindh already operates the CM Complaint Cell at istd.sindh.gov.pk/complains, which handles general public complaints routed to departments. This is a valued public service and remains untouched by this project. However, it is not engineered for IT-industry facilitation: it does not offer specialized company registration, multiple authorized representatives, SLA-bound escalation ladders, tripartite hearings, AI-assisted triage and drafting, multilingual content in Sindhi, signed resolution letters with QR verification, knowledge bases of IT-relevant SOPs, or a public transparency dashboard tailored to industry. The Sindh IT Portal — Facilitation Desk is built specifically to fill that gap, and to act as the coordinating layer across the 40+ departments of the Government of Sindh.


3. Vision & Mission

3.1 Vision

A knowledge-based, investor-friendly Sindh in which IT companies — from solo freelancers to multinational branches — experience government as a single, responsive, transparent partner, and in which every industry problem with any department is heard, coordinated, and resolved on time, with the outcome visible to the company, to leadership, and to the public.

3.2 Mission

To build and operate one trusted, multilingual, AI-enabled facilitation desk that:

  1. Gives IT companies a single window to raise and resolve problems with any Government of Sindh department.
  2. Coordinates those problems across departments through binding SLAs, structured escalation, and tripartite hearings.
  3. Uses AI to simplify, summarize, translate, route, and draft — never to replace human accountability.
  4. Provides leadership with real-time oversight and the public with transparency reporting.
  5. Becomes the provincial template for a SIFC-style single window — first for IT, then for other priority sectors.

4. Goals & Objectives

The goals below are SMART (Specific, Measurable, Achievable, Relevant, Time-bound) and are the basis for the KPIs in §5 and the detailed metrics in /specs/en/17-analytics-kpis/.

# Goal SMART objective (V1 target, indicative) MoSCoW
G1 Reduce average resolution time Reduce mean ticket turnaround time (TAT) for IT-industry problems to ≤15 working days within 12 months of launch. [Must]
G2 Increase transparency Provide 100% of tickets with real-time status, SLA clock, and a public transparency dashboard (volume, TAT, SLA compliance by department). [Must]
G3 Enable inter-department coordination Onboard ≥40 Government of Sindh departments/sections with at least one trained, certified officer each within 9 months of launch. [Must]
G4 Provide leadership oversight Deliver 7 role-scoped dashboards (incl. CM/SACM, Secretary, DG, Officer, Company, Public, Operator) updated in near real time. [Must]
G5 Multilingual accessibility Deliver full functionality in EN, UR, and SD, RTL-correct, WCAG 2.1 AA compliant, with a maintained trilingual glossary. [Must]
G6 Self-service deflection Deflect ≥30% of would-be tickets to knowledge base / SOPs / AI chatbot within 12 months, measured via deflection tracking. [Should]
G7 AI-enabled productivity Deploy all 11 AI capabilities (OCR, summary, routing, urgency/sentiment, draft replies, translation, duplicate detection, public chatbot, PII redaction, trends, MoM extraction) behind a pluggable engine. [Must]
G8 Trust & accountability Enforce a proof-of-resolution gate (no Resolved without evidence + note) on 100% of tickets; QR-verifiable resolution letters on letterhead. [Must]
G9 PP readiness & sustainability Operate under a binding PPP with SLAs, source-code escrow, and an exit/handover plan so the Government of Sindh retains continuity regardless of operator. [Must]
G10 Adoption Register ≥1,500 verified IT entities (companies, proprietors, freelancers, foreign branches, startups) within 12 months of launch. [Should]

5. Success Metrics / KPIs (High-Level)

Detailed definitions, formulas, thresholds, and reporting cadences are owned by /specs/en/17-analytics-kpis/. The headline KPIs for this program are:

KPI family Headline metric Direction
Resolution speed Average resolution TAT (working days); median TAT; % within SLA. ↓ TAT, ↑ % in-SLA
SLA compliance % of tickets meeting category SLA (default 2/5/10 days); % escalated. ↑ compliance
Customer experience CSAT score (post-resolution); % reopened; % appealed. ↑ CSAT
Self-service Deflection rate (KB/SOP/chatbot resolution vs ticket creation). ↑ deflection
Participation Number of departments with active, certified officers; % of tickets acknowledged on time.
Volume & reach Ticket volume by category/department/district; registered entities by type. healthy growth
Transparency Public dashboard uptime; reports published on schedule; export usage.
AI value Draft-reply acceptance rate; OCR accuracy; auto-routing precision.
Trust & safety Abuse/moderation actions; false-complaint penalties; identity appeals. controlled

6. Stakeholders

The Sindh IT Portal — Facilitation Desk is a multi-actor system. The actor map below is described in words and rendered as a Mermaid diagram.

Written description. The CM Sindh and the SACM sit at the political apex, with the Secretary S&ITD as the administrative owner. S&ITD staff (Super Admin, facilitators) operate the day-to-day. 40+ Government of Sindh departments each contribute Secretaries, Director-Generals (DGs), and officers who act on tickets and join tripartite hearings. IT companies and their authorized representatives are the primary external users; citizens and the general public use the read-only surfaces. MAAHIR operates the platform; Server4Sale hosts it. The ecosystem — PSEB, P@SHA, SECP, NADRA, FBR, SRB — is integrated for verification and routing. A public dashboard serves media, researchers, and investors.

flowchart TD CM["CM Sindh<br/>(Syed Murad Ali Shah)"] SACM["SACM — Political Head<br/>(Muhammad Ali Rashid)"] SEC["Secretary S&ITD<br/>(Administrative Owner)"] subgraph SITD["S&ITD (Owner)"] SA["Super Admin / Facilitators"] end subgraph DEPTS["Government of Sindh — 40+ Departments"] D1["Labour & HR"] D2["Industries & Commerce"] D3["Excise / Taxation"] D4["Energy"] D5["Board of Revenue"] D6["Investment"] DN["… others"] OFF["Secretaries · DGs · Officers"] end subgraph INDUSTRY["IT Industry"] CO["IT Companies (5 entity types)"] REP["Authorized Representatives"] PUB_C["Citizens / Public"] end subgraph OPS["Operator & Host"] MAAHIR["MAAHIR (Operator)"] S4S["Server4Sale (Host)"] end subgraph ECO["Ecosystem / Integrations"] NADRA["NADRA"] SECP["SECP"] FBR["FBR / NTN"] SRB["SRB"] PSEB["PSEB"] PASHA["P@SHA"] NITB["NITB e-Office"] end CM --> SACM SACM --> SEC SEC --> SITD SEC --> DEPTS SITD -->|coordinates via| DEPTS CO --> REP REP -->|file & track| SITD SITD -->|routes & escalates| DEPTS DEPTS -->|resolve & report| SITD SITD -->|public dashboard| PUB_C OPS -.->|operates & hosts| SITD ECO -.->|verify & integrate| SITD

6.1 Stakeholder register

Stakeholder Interest / Role
CM Sindh (Syed Murad Ali Shah) Political authority; ultimate accountability for provincial IT industry outcomes; oversight dashboard consumer.
SACM (Mr. Muhammad Ali Rashid) Political head of the Portal; chairs sensitive/VIP closures; sets direction; ministerial dashboard consumer.
Secretary S&ITD Administrative owner; owns the legal mandate and department MoUs; the apex of the in-house escalation ladder.
S&ITD Super Admin & staff Day-to-day operators on the government side: configuration, RBAC, feature flags, sensitive-ticket approvals, facilitation.
Department Secretaries / DGs / Officers (40+ Sindh departments) Receive routed tickets, act on them, join tripartite hearings, sign resolutions, feed SOPs and KB content; primary "resolver" actors.
IT companies (SECP, proprietor/partnership, freelancer, foreign branch, early startup) Primary external users; raise problems, supply evidence, participate in hearings, receive signed resolutions.
Authorized representatives (Primary / Admin / Filer / Viewer / Notify) Act on behalf of companies; file and track tickets; exactly one Primary Authorized Rep per company.
Citizens / general public Consume read-only public surfaces: transparency dashboard, KB, SOPs, circulars, official records.
MAAHIR (operator) Builds, operates, and maintains the platform under PPP; SLA-bound to S&ITD.
Server4Sale (host) Provides and operates the underlying infrastructure; "Powered by Server4Sale."
PSEB / P@SHA / SECP / NADRA / FBR / SRB Ecosystem and integration partners: verification data, routing context, industry bodies for outreach and adoption.
Media, researchers, investors Consumers of the public transparency dashboard and reporting.

7. Scope

This section states what Version 1 (V1) of the Sindh IT Portal — Facilitation Desk does and does not include. V1 is delivered in phases per /specs/en/14-roadmap-release/, but the entire scope below is in-scope for V1 and prioritized with MoSCoW.

7.1 In scope (V1)

V1 includes all seventeen modules of the platform (codes A–Q) summarized below. Full functional detail lives in /specs/en/02-functional-reqs/ and each module's dedicated document.

Mod Code In-scope capability MoSCoW
A PUB Public site: multilingual info, FAQ, AI chatbot, SEO, hreflang, help center, onboarding wizard. [Must]
B TKT Ticketing core: full lifecycle; SLA (2/5/10 default, configurable); auto-escalation; proof-of-resolution gate (evidence + note → auto-close); appeal + CSAT; sub-tasks, merge/split, link, watchers/CC, bulk; draft & save-later; smart filing assistant. [Must]
C ORG Nested departments (Dept → Section → Staff) with DG/Secretary oversight; company reps (Primary/Admin/Filer/Viewer/Notify); roles + granular overrides; account-lifecycle automation. [Must]
D FILE Files: two-sided upload; ClamAV AV scan; encrypted storage; preview; versioned; secure download links. [Must]
E AI 11 AI capabilities: OCR, summary, auto-routing/classification, urgency/sentiment, draft replies, translation (EN/UR/SD), duplicate/similarity detection, public chatbot, PII redaction, trends/analytics, MoM action-item extraction. Pluggable engines. [Must]
F COM Internal comms (3 tiers): ticket-scoped private threads; org-wide inbox (DMs/groups); full channel-based chat (threads, pins, presence, typing, read receipts, full-text search). [Should]
G NOT Notifications: Email (Mailjet) / SMS / WhatsApp / in-app; templated; multilingual; two-way inbound replies; preference center (digests, quiet hours). [Must]
H INT Integrations: NADRA (CNIC), SECP, FBR/NTN, SRB, PSEB, NITB e-Office, OIDC SSO, webhooks/REST API. [Must]
I ANL Comprehensive analytics: 9 metric families; 7 role dashboards incl. public transparency dashboard; GIS/district heatmap; scheduled digests; exports (PDF/Excel/CSV); Metabase + custom charts. [Must]
J KB Knowledge base + SOPs: articles, downloadable forms, versioned SOPs, AI semantic search, "was this helpful", deflection tracking, service catalog. [Must]
K MCI Multi-channel intake: email/SMS/WhatsApp-to-ticket, toll-free IVR/voice, walk-in/offline entry. [Should]
L DOC Document generation + e-sign: trilingual official letters/resolution certs on letterhead; PKI digital signing; QR verification (anti-forgery). [Must]
M MTG Hearings + TRI + MoM: tripartite meeting (Company + S&ITD + Dept); physical + virtual (hybrid); calendar; Zoom/Meet/Teams; MoM upload-first → AI extracts action items; Chair/DG approval for sensitive tickets; auto-share; action items → sub-tasks. [Must]
N SUG Suggestion & content portal: suggestion box, circulars/announcements, versioned document repository. [Should]
O TRN Training & certification: LMS-lite staff courses + exam-gated certification (must pass before handling live tickets). [Must]
P OFC Brand & officials CMS: dynamic Minister/Secretary/DG records → propagate to site, letters, dashboards; historical accuracy (date-aware letters). [Must]
Q FFG Feature flags: every capability toggleable by Super Admin (per dept/env). [Must]

Cross-cutting in scope (governance, trust, infrastructure):

7.2 Out of scope / future (V1)

Item Disposition Rationale
Native mobile apps (Android/iOS) Won't (this phase) PWA first; native via React Native (Expo) is a later phase once core flows stabilize.
E-payments / online fee collection Won't (this phase) Defer until fee schedules and payment-gateway integration are mandated; not on the critical facilitation path.
Auto-assignment / load-balancing of tickets Won't (this phase) Manual and rule-based routing first; intelligent auto-balancing is a later phase.
Detailed DR runbooks Won't (this phase) Baseline NFR (backups, failover, RPO/RTO, availability) is in scope; full operational runbooks deferred.
Replacement of the CM Complaint Cell Won't (any phase) The CM Complaint Cell at istd.sindh.gov.pk/complains remains the public channel and is untouched.
Non-IT industry sectors Won't (this phase) IT first; the architecture is extensible to other priority sectors later.

8. Relationship to Existing Systems

8.1 Standalone by design

The Sindh IT Portal — Facilitation Desk is a brand-new, standalone product. It does not extend, fork, or replace the existing CM Complaint Cell, and it makes no changes to any department's internal file-management or case-tracking systems. It is purpose-built for IT-industry facilitation and inter-department coordination, which no existing provincial system provides.

Why standalone (and not a feature bolted onto the CM Complaint Cell):

  1. Specialized for the IT industry. SITP carries company registration for 5 entity types, multiple authorized representatives per company, IT-specific SOPs and service catalogues, and a brand identity (Ajrak-inspired) aimed at investors.
  2. AI-enabled by design. Eleven AI capabilities — OCR, summarization, drafting, translation, urgency/sentiment, routing, duplicate detection, PII redaction, MoM extraction — are core, not optional.
  3. Inter-department coordination layer. SITP's escalation ladder (Staff → DG → Secretary → SACM), tripartite hearings (Company + S&ITD + Department), and proof-of-resolution gate exist because the IT company's problem typically spans more than one department.
  4. Leadership- and public-facing by design. Seven role dashboards, including a public transparency dashboard, are first-class.
  5. PPP-operated. Built and run by MAAHIR on Server4Sale under binding SLAs, with escrow and exit plan — a delivery model that the CM Complaint Cell does not have.

8.2 Benchmarks and reference systems

SITP's design is informed by, and benchmarked against, the following:

Reference system What we learn from it
India CPGRAMS (pgportal.gov.in) Gold standard: appeal, feedback, status tracking by ID, role-based department access, mobile apps, AI chatbot, already supports Urdu and Sindhi. Primary model for ticket flows.
Pakistan Citizens Portal (PCP) Familiar mobile-first UX; ministerial dashboards; routing to departments.
SIFC "One Window" The investor single-window model that S&ITD is provincializing for the IT industry.
India state investor desks (Karnataka Udyog Mitra, Invest India) Investor-facing facilitation patterns and concierge triage.
PSEB / P@SHA / SECP IT-industry bodies whose membership and verification data may be integrated (Module H).

9. Product Identity

Item Value
Full name Sindh IT Portal — Facilitation Desk
Short name Sindh IT Portal (abbrev SITP)
Tagline (EN) A single window for IT companies to resolve problems with Government of Sindh departments.
Canonical URL https://sindhitportal.maahir.io
Docs site https://sindhitportal.maahir.io/docs/ (Docusaurus)
Owning department Science & Information Technology Department (S&ITD), Government of Sindh
Political head SACM — Mr. Muhammad Ali Rashid
Administrative head Secretary S&ITD
CM Sindh Syed Murad Ali Shah
Operator (PPP partner) MAAHIR
Hosting / infrastructure Server4Sale ("Powered by Server4Sale")
Footer "Operated by MAAHIR · Powered by Server4Sale"
Branding direction Ajrak-inspired palette (indigo / maroon / black) with Ajrak motif accents and Sindhi cap iconography; co-primary marks = Government of Sindh seal + S&ITD logo.
Languages English (master) · Urdu (RTL) · Sindhi (RTL).
Accessibility WCAG 2.1 AA across all three languages.
Calendar Dual Gregorian + Islamic (Hijri) in the UI (government convention).
Typography EN: Inter/Poppins · UR: Noto Nastaliq Urdu · SD: Noto Naskh Arabic.
Ticket IDs Meaningful: SITP-YYYY-<DEPT>-<NNNNNN> (e.g., SITP-2026-LBR-000123).

See /specs/en/16-branding-design-system/ for full brand specification.


10. Guiding Principles

These principles shape every design and engineering decision and recur across the documentation set.

  1. Progressive disclosure. Show the user only what they need at each step. Complexity is revealed as the task demands it — never upfront.
  2. Role-scoped UX. A freelancer, a company filer, a department officer, a DG, the Secretary, and the SACM each see a different product. The same data, presented for each role.
  3. Three-click rule for the company journey. From landing on the site to filing a ticket — or from a notification to seeing the latest status — should take no more than three clicks.
  4. AI as simplifier, not decision-maker. AI drafts, summarizes, translates, routes, and detects — but a human approves every consequential action. AI never closes a ticket or signs a letter.
  5. Sensible defaults. SLA clocks (2/5/10 days), escalation thresholds, and notification preferences ship with safe defaults so the platform is useful on day one and tunable thereafter.
  6. Transparency and accountability. What the platform does, it does visibly — status, SLA clock, assignee, escalation history, resolution evidence, and a public transparency dashboard. Aligned with the Sindh Transparency & RTI Act 2016.
  7. Data sensitivity drives architecture. AI and OCR engines are pluggable: cloud (Azure OpenAI / Google / AWS / Document AI / Textract) for quality by default, with a self-hosted toggle (Llama / Qwen / Tesseract) for residency, sovereignty, or sensitivity needs.
  8. One source of truth, three languages. English is the master; Urdu and Sindhi are parallel translations kept structurally identical via a maintained glossary.
  9. Build for trust. Every official artifact (resolution letter, certificate) is QR-verifiable and date-accurate against the Officials CMS; every ticket carries an immutable audit trail.
  10. Government-formal, plain-language. The product speaks like a competent civil servant, not a marketer: clear, imperative, respectful, jargon-free where possible.

11. Assumptions & Dependencies

# Assumption / Dependency Notes
A1 Legal mandate + department MoUs will be issued by S&ITD binding departments to SLA response. Without this, inter-department compliance is voluntary. See /specs/en/22-governance-legal/.
A2 API access to NADRA (CNIC), SECP, FBR/NTN, SRB, and PSEB for verification will be granted by the respective bodies. Drives file-first, verify-in-parallel registration. See /specs/en/08-integrations-spec/.
A3 Server4Sale hosting is available to the required availability, capacity, and security standard. Server environment verified: Ubuntu 24.04, Node 22, MariaDB 10.11, 3.4 TB disk, 243 GB RAM.
A4 MAAHIR PPP contract is in force with binding SLAs, escrow, IP ownership, and an exit plan. See /specs/en/23-ppp-vendor-exit/.
A5 Source-code escrow is established so the Government of Sindh retains continuity regardless of operator. Critical PPP safeguard.
A6 Sindh public holiday calendar is provided/maintained for SLA pausing. Drives SLA-clock behaviour.
A7 PSEB / P@SHA will partner on outreach and adoption to drive company registrations. De-risks adoption.
A8 NITB e-Office integration is technically available for official file movement. Module H scope.
A9 Trilingual reviewers (native Urdu and Sindhi) are available for translation QA. Required for language quality.
A10 Keycloak (OIDC + 2FA) is acceptable as the identity provider for staff and company users. Drives auth architecture.

12. Risks & Mitigations

# Risk Likelihood / Impact Mitigation
R1 Low adoption by IT companies and departments. Medium / High Change management; PSEB/P@SHA partnerships; onboarding wizard; multilingual marketing; public dashboard to demonstrate responsiveness.
R2 Inter-department non-compliance with SLAs. High / High Legal mandate + per-department MoUs; escalation ladder to DG → Secretary → SACM; published department scorecards on the public dashboard.
R3 Data sensitivity / sovereignty concerns (cloud AI on government/citizen data). Medium / High Pluggable AI and OCR engines; self-hosted toggle (Llama/Qwen + Tesseract); PII redaction as a core AI capability; encryption at rest and in transit.
R4 Scope creep. High / Medium MoSCoW prioritization on every requirement; phased delivery; feature flags (Module Q) to toggle capabilities per dept/env.
R5 Trilingual quality (especially Sindhi) drifts from the English master. Medium / Medium Maintained _glossary.md; native-speaker review; structural parity enforced by conventions; CPGRAMS already proves Urdu+Sindhi is achievable.
R6 PPP vendor lock-in. Medium / High Source-code escrow; documented IP ownership; binding exit/handover plan; standards-based stack (NestJS, MariaDB, Keycloak).
R7 Cybersecurity threats (defacement, data breach, DDoS). Medium / High Penetration testing; CERT-PK coordination; CII registration; ClamAV on all uploads; rate-limiting; 2FA; observability (Sentry + Grafana/Loki).
R8 Abuse / false complaints. Medium / Medium Moderation tools; false-complaint penalties; CAPTCHA; rate-limiting; anonymous/whistleblower intake; identity-verification appeals.
R9 Political or leadership change affects sponsorship. Medium / Medium Officials CMS (Module P) makes the product leadership-agnostic and historically accurate; standalone architecture survives turnover.
R10 AI quality / hallucination erodes trust. Medium / High Human-in-the-loop on every consequential action; AI never closes or signs; PII redaction; draft acceptance metrics tracked.

13. References

13.1 Benchmark and reference systems

13.2 Government of Sindh structure

13.3 Internal documentation references


End of document. Urdu and Sindhi parallel translations (ur.md, sd.md) follow this master structure exactly.