SIGN IN
Create a sample account or log in
Use the demo accounts or create a sample student account in four quick steps.
Parul University · CSE Department
Apply for leave without standing in a queue.
Students apply online, the HOD reviews and records a decision, and students can track the result — all in one clear record.
Simulated demo — sample data only. Do not enter real student or parent information.
—
Student record
Sample student
Demo data from this browser
0Total
0Pending
0Approved
Submitted
HOD review
Decision
Next: HOD review
Parent contact on file
Demo data from this browser
How it works
Four steps from request to record.
No paper. No queue. One record that both sides can see.
APPLY
Fill out and submit a leave request
Pick dates, category, and a reason. Your profile details auto-fill the form.
REVIEW
The HOD reviews and decides
The HOD approves, rejects with a comment, or asks for more information.
TRACK
Check the status and history
Students follow the recorded status and can review previous requests.
For students
Apply, confirm, and track — from your phone.
The student side is built around a short form and a dashboard that keeps every request visible.
Create a sample account
Student workflow
What the demo supports
- Profile details pre-fill parts of the leave form.
- Enter leave dates, category, and reason.
- Parent contact details are shown for confirmation on the form.
- Track request status and review past requests from the dashboard.
- Cancel a request while it is still pending.
For HODs
One review screen. A clear decision record.
The HOD dashboard requires a login. It is a review tool, not a public page.
Open the HOD demo login
HOD workflow
What the demo supports
- View requests awaiting review.
- Review student details, dates, category, reason, and attendance context.
- Approve, reject with a comment, or ask for more information.
- Record parent contact and a short decision note.
- Approved and rejected requests remain listed for review.
No automatic notifications are sent in this demo.
Request statuses
What each status means.
Status is always written in text — never conveyed by colour alone.
Pending
Awaiting review
The request has been submitted and is waiting for the HOD. A pending request can be cancelled by the student.
Approved
Approved by the HOD
The HOD accepted the request and the decision is recorded. The request stays in the student’s history.
Rejected
Rejected by the HOD
The HOD rejected the request and added a comment explaining why. The record remains visible in the history.
Needs Info
More information required
The HOD needs additional details before making a decision. The request stays on record while it is reviewed.
Cancelling a pending request moves it to Cancelled. No response-time guarantee is implied.
Demo vs production
What works now, and what is planned.
The demo is honest about its limits. Production capabilities are labelled as planned.
| Area | Current demo | Planned production |
|---|---|---|
| Application | HTML, CSS, and JavaScript | Same product, production build |
| Accounts | Simulated demo accounts | Real server-side authentication |
| Data | Browser demo storage | Real database with protected data |
| Access control | Client-side role checks | Server-side authorization on every request |
| Attendance | Sample values only | Officially authorized integration |
| Notifications | Not available | Planned, subject to approval |
The “Planned production” column describes intended work, not features that are available today.
Try the demo
Ready to see the full flow?
Create a sample account in four quick steps, or log in with a demo account. No real student data needed.
Privacy notice
This is a simulated demo. Protect real information.
The current build uses simulated accounts and sample data stored in this browser. Do not enter real student, parent, or college information.
Not yet implemented: production security, live attendance integration, and real notifications.
Read the full privacy policy
- Real deployment requires college approval and proper security controls.
- Student and parent contact information must be protected with role-based access and secure transport.
- Live attendance must use an officially authorized data source — not scraping or shared student credentials.