Request managment

Project Summary: Request Management System Objective: Develop a simple, user-friendly online request management system to handle different types of requests, such as maintenance and purchase requests. The system should include role-based access control, approval workflows, and basic analytics. Key Functionalities: User Management & Authentication: Users can register and log in with roles: Requester (can submit requests) Department Manager (can approve/reject requests) Engineering Manager (final approval and assignment) Passwords should be securely stored (hashed). Session-based authentication to restrict access. Request Submission: Dynamic form with the following fields: Auto-filled: Requester Name, Department, Date & Time, Sequential Request Number (per department). User Inputs: Area (dropdown, multi-selection) Line (dropdown, multi-selection, filtered by Area) Room (dropdown, multi-selection, filtered by Line) Equipment (dropdown, multi-selection, filtered by Room) Priority Level (dropdown, single selection) Description (text field) Attachment (optional file upload) All fields (except attachment) are mandatory. Approval Workflow: Requests are submitted by any user but require approvals as follows: Department Manager: Approve, Reject, or Comment (send back to requester) Editable approval Engineering Manager: Approve, Reject, or Assign to Section Head (with auto-tracking of assignment date/time) Notifications for approvals/rejections (email + platform notifications). Request Tracking & Status Updates: Requests should have statuses: Pending Under Process (after Engineering Manager approval) Completed Status changes should trigger notifications. Dashboards & Reporting: Basic dashboard with the following insights: Request counts (by status, department, and priority) Average lead time (from submission to completion) Filter requests by department, category, status. Export reports to Excel/PDF. Access Control: Only authorized roles can approve/reject requests. Unauthorized users should see appropriate error messages. Custom request forms based on department/role. Technology Preferences: Web-based (accessible via PC & mobile). Simple UI with minimal complexity. Hosted online for real-time access. Suggested stack: Node.js ([login to view URL]), MongoDB (or simple JSON storage), HTML/CSS/JS for frontend. Expected Deliverables: Fully functional web application with all mentioned features. A user-friendly dashboard for tracking and approvals. Secure authentication and authorization system. Documentation on how to use and maintain the system