Rental Property Listing Portal with Owner Verification and Visit Scheduling

Renting a home in a new city usually starts with a listings site full of stale posts, fake owners and phone numbers that go unanswered. Tenants waste days visiting flats that were already rented or were never the poster's property, and owners waste time on visitors who never show up. This project answers that problem with a rental property portal that puts owner verification before contact: an owner uploads a government ID and a property document, an admin matches the names, and only then does the listing carry a verified-owner badge and accept visit requests. Tenants filter by city, budget, BHK and furnishing, open a listing to see its owner status, and book a visit in a real date and time slot instead of chasing phone calls. The result is a smaller, trustworthy set of listings where every visit request reaches a checked owner, and every confirmed visit has a reference the tenant can quote.

The demo portal built for this project lists 12 homes across 5 cities, with 9 verified owners and 3 owners still pending verification, so the badge states and the visit-scheduling gate can be seen working rather than described. Filtering the demo by the city Pune returns 4 listings, and filtering by a budget of up to ₹15,000 per month also returns 4 listings — both counts measured from the demo's own data during the build. In the demo, the visit scheduler renders only for verified owners; for the 3 pending listings it stays hidden until approval, which is how the verification gate is enforced in the interface.

A tenant opens the portal and searches by city, budget, BHK and furnishing, then scans the results for the green verified-owner badge. Opening a listing shows the home's photos, rent, deposit and amenities alongside the owner's name and verification state, so trust is judged before any contact happens. If the owner is verified, the tenant picks a visit date and time slot and submits the request; the owner then confirms it, and the tenant keeps a reference number for the visit. Pending owners stay visible but cannot receive visit requests, so no tenant ever books a visit with an owner whose documents are still unchecked. The whole journey runs inside the portal — no phone numbers are exposed before a visit is confirmed. Listings from pending owners stay visible for browsing but cannot take a visit request, so trust is enforced by the workflow itself rather than by a warning label.

1. The tenant searches with 4 filters — city, budget, BHK and furnishing — and the portal returns matching listings with a live count of verified owners among them.
2. Each listing card shows rent per month, BHK, area in sq ft, city, furnishing and the owner's verification badge.
3. Opening a listing shows its photos, amenities, deposit (2 months' rent by design) and the owner's verification state, including which documents were matched.
4. The owner onboards by uploading a government ID and a property document; an admin compares the names and approves or rejects the application with a reason.
5. Only approved owners display the verified badge and receive visit requests; pending owners' listings show "Verification pending" and hide the scheduler.
6. The tenant picks a visit date from the next 4 days and one of 4 daily time slots, enters a name and mobile number, and submits the request.
7. The owner confirms the visit within a 24-hour design window, and the tenant receives a confirmation state with a reference number such as RV-2026-08413.

Tech stack:

• HTML5 · CSS · JavaScript (single-file demo front end)
• Node.js · Express (REST API)
• MySQL database
• JWT authentication
• Multer file uploads for owner documents
• Nodemailer visit alerts
• Responsive CSS grid layout
• Git version control

Searching, verifying and booking are the three capabilities this portal is built around. Tenants get a filterable listing search with a verified-owner badge on every genuine home, owners get a document-upload registration that ends in an admin check rather than instant self-approval, and both sides get a visit scheduler that replaces phone-tag with dated slots and a confirmation reference. Around that core sit an admin verification queue, listing management for owners, and a responsive interface that works on a phone — the device most tenants actually search on. Online rent payment and deposit escrow are deliberately left out of the core build and listed as future scope, so the project stays honest about what it does and does not handle. A tenant never sees a phone number before a visit is confirmed, which is what keeps unverified contact out of the process entirely.

• [Verified-owner badges] Every listing shows its owner's verification state: a green badge once an admin has matched the owner's ID against a property document, or a "Verification pending" label until then. Implemented in the demo.
• [Search and filters] Filter the 12 demo listings by city, budget, BHK and furnishing, with a live count of matching homes and how many come from verified owners. Implemented in the demo.
• [Visit scheduler with confirmation] Pick a date from the next 4 days and one of 4 daily time slots, then receive a confirmation state with a visit reference number. Implemented in the demo.
• [Owner registration and document upload] Owners submit a government ID plus a property document (sale deed, tax receipt or society letter) as the first step of verification. Implemented as a workflow in the full build; the demo models the resulting states.
• [Admin verification queue] Admins review submitted documents, approve or reject with a reason, and only approved owners can receive visit requests. Implemented as a workflow in the full build.
• [Listing management] Owners create, edit and deactivate their own listings, with rent, deposit (2 months' rent by design), furnishing and amenities fields. Implemented in the full build.
• [Responsive portal interface] The listing grid, detail view and scheduler adapt from desktop to mobile widths without a separate app. Implemented in the demo.
• [Online rent payment] Tenants paying rent or deposits through the portal, with receipts and reminders. Future scope — not built into this project.

• Working demo portal (single-file HTML/CSS/JS) with 12 listings, verification states and visit scheduler
• Full-stack portal source code (Node.js · Express · MySQL) with owner registration, admin queue and visit booking
• Database schema for listings, owners, verification applications and visit requests
• Project report PDF (problem, methodology, verification workflow, screenshots, limitations)
• PPT presentation for final review
• Viva Q&A preparation document (web architecture, authentication, verification design, scheduling logic)
• Setup guide for running the demo and the full-stack build locally