Fingerprint-based Student Attendance System for Transport


The application should aim to automate the student attendance process using fingerprint authentication and geolocation. The app will have different user roles (Driver, Parent, Accountant, Admin), each with specific functionalities. Data will be integrated with Google Sheets and Firebase for real-time access and storage.

User Roles and Functionalities:

  1. Driver Login:
  • Primary Role: Data Gatherer
  • Functions:
    • Authenticate using fingerprint and registered mobile number.
    • Mark student attendance at four critical points:
      1. Boarding the bus (morning)
      2. Dropping at school (morning)
      3. Boarding the bus (afternoon)
      4. Dropping at bus stop (afternoon)
    • Capture geolocation and timestamp for each attendance event.
    • Use mobile’s fingerprint sensor for student attendance.
    • Real-time bus tracking for parents.
  1. Parent Login:
  • Primary Role: Viewer
  • Functions:
    • Authenticate using OTP sent to registered mobile number.
    • View attendance logs with geolocation and timestamps for each event.
    • Real-time bus location tracking.
    • View fee status (paid/unpaid) and pay fees through the app.
    • Restricted access if previous month’s fee is unpaid.
    • Receive notifications for fee payment reminders.
  1. Accountant Login:
  • Primary Role: Attendance and Fee Manager
  • Functions:
    • View attendance logs class-wise and bus-wise.
    • Update fee payment status.
    • Allow exceptions for unpaid fees (with admin approval).
    • Manage sign-ups for students using admission number and mobile number.
  1. Admin Login:
  • Primary Role: Overall Manager
  • Functions:
    • View comprehensive logs of attendance and bus-wise details.
    • Assign roles and manage users (except parents).
    • Approve exceptions for unpaid fees.
    • Oversee all activities within the app.

Data Integration:

  1. Google Sheets:
  • Used for validating student data during sign-up.
  • Fields: Admission Number, Student Name, Class/Section, Father’s Name, Mother’s Name, Registered Mobile Number, Address.
  1. Firebase Database:
  • Used for real-time data storage and retrieval.
  • Manages user authentication and attendance logs.
  • Stores fee payment status and exceptions.
  • Backup and synchronize data with Google Sheets.


  1. Sign-Up Process:
  • Accountant/Admin enters the admission number and mobile number.
  • System fetches data from Google Sheets for validation.
  • If valid, proceed to fingerprint registration.
  • If already registered, display “Already Registered” message.
  • Store registration details in Firebase.
  1. Attendance Marking:
  • Driver authenticates using fingerprint and registered mobile number.
  • Driver captures student’s fingerprint at each of the four critical points.
  • System records geolocation and timestamp for each event.
  • Data is stored in Firebase and synchronized with Google Sheets.
  1. Parent Access:
  • Parent logs in using OTP sent to registered mobile number.
  • If fees are unpaid, redirect to fee payment window.
  • Parent can view attendance logs and real-time bus tracking.
  • Notifications are sent for upcoming fee payments.
  1. Fee Management:
  • Accountant updates fee payment status in the app.
  • Parents can pay fees through the integrated payment portal.
  • System restricts app access if previous month’s fee is unpaid.

Database Schema:

  1. Google Sheets:
  • Fields: AdmNo, StudName, ClassSection, fName, mName, Smsno, Add.
  1. Firebase Database:
  • Users Collection:
    • user_id (AdmNo): Unique identifier
    • name: Student’s Name
    • class_section: Class and Section
    • father_name: Father’s Name
    • mother_name: Mother’s Name
    • registered_mobile: Mobile Number
    • address: Address
    • role: (Driver/Parent/Accountant/Admin)
  • Attendance Collection:
    • attendance_id: Unique identifier
    • user_id: Student’s AdmNo
    • timestamp: Time of attendance marking
    • location: Geolocation coordinates
    • event_type: (Board Morning, Drop School, Board Afternoon, Drop Bus Stop)
  • Fee Collection:
    • fee_id: Unique identifier
    • user_id: Student’s AdmNo
    • status: (Paid/Unpaid)
    • amount: Fee amount
    • due_date: Fee due date
    • exception: (If any, with admin approval)

User Interface:

  1. Login Screen:
  • Options: Driver Login, Parent Login, Accountant Login, Admin Login
  • Fingerprint authentication for drivers.
  • OTP-based authentication for parents.
  1. Sign-Up Screen (Accountant/Admin):
  • Fields: Admission Number, Mobile Number
  • Button: Fetch Data
  • Display student details if valid.
  • Fingerprint registration if not already registered.
  1. Attendance Screen (Driver):
  • Display list of students.
  • Fingerprint capture for attendance.
  • Display geolocation and timestamp for each event.
  1. Parent Dashboard:
  • View attendance logs.
  • Real-time bus tracking.
  • Fee status and payment portal.
  • Notifications for fee payment.
  1. Accountant/Admin Dashboard:
  • Comprehensive attendance logs.
  • Fee management and exceptions.
  • User management (assign roles, approve exceptions).


  • Firebase Authentication
  • Firebase Firestore for database
  • Google Maps API for geolocation
  • Payment Gateway API for fee transactions

Data Integration:

  • Google Sheets API for student data validation

Security Measures:

  1. Authentication:
  • Fingerprint authentication for drivers and sign-up process.
  • OTP-based authentication for parents.
  • Role-based access control.
  1. Data Privacy:
  • Encrypt sensitive data stored in Firebase.
  • Regular backups to Google Sheets.
  1. Access Control:
  • Restrict access based on fee payment status.
  • Admin-controlled role assignments and exceptions.


This detailed blueprint outlines the development of an Android application for student attendance using fingerprint authentication and geolocation. The app will cater to different user roles (Driver, Parent, Accountant, Admin) with specific functionalities. Integration with Google Sheets and Firebase ensures real-time data access and storage. The project is structured to ensure a secure, user-friendly, and efficient attendance management system for schools.

Budget: INR 50,000


What is the purpose of your publication, project request, sale, or just exposing the work?

If it is a sale you should at least put some screens, have a demo or video of the functional product. If it is a work request, indicate what the available budget is.

Available budget is INR 50000.

1 Like

For this much app process Budget just INR 50,000 INR is too low,
It should be atleast 125,000 INR,
If ok contact me

1 Like

For data security reasons you need to leave out the fingerprint option if you want to store it in an online database.
Also look here:


PM Me I am ready to make the application with above specifications.

1 Like

Good idea! And don‘t forget to include the info that you are storing fingerprints into an online database in the apps policy. This will make it easier and faster for google to reject his app and suspend his account.


As I am a Law Student so I know what is allowed & what is not ?So don’t worry I will tackle it …

1 Like