Emergency and High-Severity Grievance Fast-Track System

[RohanExploit]

Description
Certain grievances like water leakage, road collapse, or power hazards require priority handling.
Technical Scope
Severity classification at creation
Priority queues in backend
Shortened SLA rules
Real-time notifications to authorities
Public “Urgent” tag visibility
On-Ground Impact
Critical problems get faster response
Lives and property risk reduced

[github-actions]

👋 Hello @RohanExploit!

Thank you for opening this issue on VishwaGuru.

Issue Details:

• Title: Emergency and High-Severity Grievance Fast-Track System
• Number: Emergency and High-Severity Grievance Fast-Track System #290

Next Steps:

1. A maintainer will review your issue
2. The issue may be labeled for categorization
3. Additional information might be requested
4. Once triaged, work can begin!

Tips for a great issue:

• Provide clear steps to reproduce (if it's a bug)
• Include expected vs actual behavior
• Add screenshots or logs if relevant
• Mention your environment details (OS, browser, versions, etc.)

We appreciate your contribution to making VishwaGuru better! 🚀

[Arman-op]

hey @RohanExploit can you assign this issue to me

[RohanExploit]

@Arman-op under which program you are enrolled Apertre or ECWoC

hey @RohanExploit can you assign this issue to me

[Arman-op]

@Arman-op under which program you are enrolled Apertre or ECWoC

hey @RohanExploit can you assign this issue to me

under Apertre 3.0

[RohanExploit]

@Arman-op You are assigned rhe issue , Once you deliver the task attach the screenshots/screen recording in comments of what impact you created .

hey @RohanExploit can you assign this issue to me

[ermansibhatia]

Hi, I would like to work on this issue as a contributor for ECWOC'26. Could you please assign it to me?

[RohanExploit]

How will you work ,Give Walkthrough ,how will be execution?

[Dhruvi2006-source]

Hi @RohanExploit, I would like to work on this issue.

I reviewed the Emergency and High-Severity Grievance Fast-Track System proposal and would be happy to take ownership of it.

My implementation approach would be:

• First, inspect the existing issue creation flow, grievance data model, API structure, and notification architecture.
• Add a clear severity classification system at grievance creation, with well-defined levels such as normal, high, and critical.
• Ensure urgent categories such as water leakage, road collapse, electrical hazards, and other potentially dangerous situations can be prioritized appropriately.
• Implement backend prioritization so high-severity grievances are processed ahead of normal grievances where applicable.
• Add configurable SLA handling for urgent grievances instead of hardcoding priority behavior throughout the codebase.
• Add the necessary notification flow for high-severity issues while preserving the existing notification behavior for regular grievances.
• Expose the urgent/high-severity status clearly in the UI with an accessible public “Urgent” indicator where appropriate.
• Keep the implementation compatible with the existing SQLite development setup and PostgreSQL production setup.
• Add or update tests for severity classification, priority handling, SLA behavior, and notification logic.

Before making changes, I will carefully review the current architecture and existing contribution conventions to avoid duplicating functionality and to ensure the implementation integrates cleanly with the existing React, FastAPI, database, and AI-powered grievance workflow.

I would be happy to take ownership of this issue and submit a focused PR for ECWoC26.