Worklog
Maintenance work log, Revelstoke Mountain Resort
The maintenance team's work log. Everyone logs jobs from their phone, parts orders go through approval, and admins get reports and CSV exports. Runs on the resort network, with no internet needed.
- Role
- Built for the maintenance team at Revelstoke Mountain Resort
- Year
- 2026
- Runs on
- Runs as a Windows service on a PC on the resort network. Not on the internet.
Problem
The maintenance team kept its work log, parts orders and supplier list in spreadsheets.
What I built
- A Python web app with no outside packages and one SQLite database. One computer on the resort network runs it, and staff open it in a browser on a phone, tablet or PC.
- Everyone signs in with their own username and PIN, logs each job with a category, room, details and start and end times, and sees their own day, week, month and history.
- Parts orders: anyone can request one, an admin approves it, then it is marked ordered and received. Each step is stamped with the person and the date, and the CSV export keeps the old sheet's layout.
- A shared vendor directory with tap-to-call phone numbers, account numbers and notes.
- Reports by month or any custom date range, CSV exports for Excel, backups, and imports of the old logs, vendors and orders.
- A phone layout that works one-handed: a bottom tab bar, one card per job instead of wide tables, light and dark mode, and it can be added to the home screen like an app.
- Packaged as a single Windows program that runs as a service, with an automated test suite.
Stack
Python, SQLite, Vanilla JavaScript, PWA, PyInstaller, Windows service
Outcome
The team's work log, parts orders and vendor list now live in one app on the resort network instead of separate spreadsheets.
Proof
Runs as a Windows service on a PC on the resort network. Not on the internet.