Platform Workflow
COMMUNX uniquely brings users, creators, and officials together on a single transparent platform. Citizens report issues, officials resolve them, and creators amplify impact through storytelling and reels.
Report Lifecycle
The report lifecycle on COMMUNX is designed to ensure transparency, accountability, and community engagement at every step. Citizens can easily report issues, track their progress, and see the impact of their contributions. Officials are empowered to address concerns efficiently, while creators help amplify important stories to drive awareness and action. This collaborative approach ensures that problems are not only reported but also resolved in a way that benefits the entire community.
Public community ( Report Generation )
From discovery to active member
User Submits Report
Citizen posts a formal or informal issue within a public community.
System Checks for Officials
Platform detects whether an authorized official is linked to that community.
If Official Present
Report routes to the official dashboard → assigned → resolved → proof uploaded.
If No Official Present
Issue auto-escalates to the creator dashboard → awareness via reels, auto emails, and X tagging.
Informal Posts
Go directly to creators for open discussion, community input, or later escalation into formal reports.
Resolution Lifecycle (Public Community)
Issue Identified
A user reports a verified civic problem within a public community.
Assignment
If officials are present, they assign an officer or worker responsible for resolution.
Proof of Work
The assigned worker uploads photo evidence after completing the task.
Community-Driven Resolution
In some cases, community members themselves solve the issue and submit proof for verification.
Verified Closure
Only the assigned worker or the person who resolved it can mark the issue as resolved, ensuring authenticity and transparency.
Intelligence Mapping
Smartly handle the auto assignment of issues to required authority responsible for that in the entire ecosystem
Platform Oversight Workflow
1. Issue Submission: User submits a formal report with location and category details.
2. Geo-Tagging & Classification: Platform automatically detects the data and classifies the area as rural or urban.
3. Administrative Layer Detection: Rural issues are mapped to the Block and routed to the BDO ( & other present officials); urban issues are matched to Municipal Corporation, Municipality, or Town Panchayat using LGD records.
4. Authority Mapping: System identifies the right department and responsible official based on the issue type and region.
5. Smart Routing: The issue is automatically forwarded to the correct official’s dashboard with all supporting data.
6. Fallback & Escalation: If no official is found, the issue is stored securely and escalated to the creator dashboard with automated emails and social tagging for awareness.
Open & Private community
How private and open communities handle reports — balancing formal escalation with open discussions.
Community-Level Routing & Review
1. Private Community Reports: When a formal report is submitted in a private community, it’s securely sent to the ADMIN dashboard for validation before further routing.
2. Admin Validation: The Admin verifies authenticity, ensures compliance, and assigns the issue to the appropriate official or creator for escalation.
3. Open Community Posts: Discussion-oriented communities act like civic forums (Reddit-style) — ideal for awareness, feedback, and brainstorming.
4. Informal Engagement: Posts in open communities don’t enter the formal routing chain but promote transparency and collective participation.
5. Ecosystem Linkage: Private, public, and open communities are all interconnected, ensuring both structured action and open dialogue coexist harmoniously.
