Unified Survey-Based Selection + Verification System

Inspiration

In real-world systems like college selections, internships, hackathons, and government schemes, the process is often fragmented and unfair.

Users bypass steps Verification is manual and slow Selections lack transparency Multiple tools are used for one workflow

What it does

✅ Selection (Pick-N, priority ranking) ✅ Eligibility enforcement ✅ Document verification ✅ Multi-level approvals ✅ OTP / authentication validation ✅ Slot booking & scheduling ✅ Long-term action planning

1. Rule Engine (DSL-based)

We designed a custom Eligibility Rules DSL that controls:

Who can access a survey When they can access it What conditions must be satisfied

Example:

eligibility: all: - survey("SURVEY_1").approved == true - user.category in ["students"] 🔹 2. Hard & Soft Gating 🔒 Hard gating → Cannot proceed without approval 🔓 Soft gating → Can proceed after attempt

This prevents bypassing and enforces structured progression.

🔹 3. Quota + Fair Allocation System Category-based quotas (e.g., boys/girls) Waitlist system Allocation policies (FCFS, Rank-based, Hybrid)

Ensures fair and transparent selection.

🔹 4. Workflow / Relay System

Multi-level decision flow:

Group 1 → Group 2 → Admin → Final Selection

Used for:

Project approvals Hiring pipelines Committee decisions 🔹 5. Document & Verification Engine File uploads (PDF, images, etc.) Multi-level verification Conditional access based on approval 🔹 6. Unified Lifecycle Tracking

Every action is traceable:

Selection → Verification → Approval → Allocation

Ensuring auditability and trust.

How we built it

Frontend: React / Flutter (UI for surveys & dashboards) Backend: Node.js + Express Database: PostgreSQL / MySQL Rule Engine: Custom DSL parser + evaluator Authentication: OTP-based validation Storage: Secure file handling for document uploads

Challenges we ran into

1. Designing a Flexible Rule System

Creating a DSL that is:

Human-readable Machine-executable Scalable

…was one of the hardest parts.

1. Preventing Race Conditions

Handling:

Seat allocation Quotas Concurrent users

required careful transaction handling and state control.

1. Balancing Power vs Simplicity

We needed:

Enterprise-level features But still easy for admins

So we designed a guided UI + advanced DSL mode.

What we learned

System design matters more than just UI Real-world problems need structured workflows Rule engines can simplify complex systems Fairness + transparency = strong product value

What's next for Unified Survey-Based Selection + Verification System

AI-based recommendation system for selections Predictive allocation optimization Government & institutional integration Mobile-first deployment

Built With

• apis
• authentication
• custom
• dsl
• engine
• express.js
• jwt
• mysql
• node.js
• react
• rest