Back to all projects

Boarding house management system

Room, tenant, and payment management for a thirty-room boarding house.

Role
Full-stack developer
Year
2025
Links
Repository

Problem

The owner tracked room availability and rent payments across a notebook and a separate spreadsheet. Whenever a new tenant arrived the data drifted: a room listed as occupied was actually free, or last month’s payment could not be found.

Approach

  • A single source of truth. Rooms, tenants, and payments live in SQLite with explicit relations, so there is no duplicated status to disagree with itself.
  • A light public page. The room catalogue is server rendered, so it opens quickly on a slow phone network with no client JavaScript at all.
  • A separate admin panel. Data management uses a Preact SPA loaded only after login, keeping the public bundle small.
  • Errors surfaced early. Validation runs on the server and its messages are shown verbatim, so the operator knows exactly what to fix.

Outcome

  • Monthly payment bookkeeping dropped from roughly 15 minutes to under 3.
  • No more rooms silently missed, because status is recorded in one place.
  • Catalogue page loads in under one second on a 3G connection.

Lessons

The real need was smaller than my first plan: one “mark as paid” button and a printable monthly recap. The analytics report I designed first was never used.