TicketDesk

Running IT, A/V, and maintenance across six hospitality venues means requests arrive everywhere at once — texts, calls, hallway conversations — and disappear just as fast. Nothing gets tracked, the same issues recur, and there's no record of what was fixed or who handled it. At scale, that's lost time and repeated failures.

A single ticketing platform scoped to the realities of a multi-venue operation: each venue sees only its own work, staff are onboarded through a controlled invite flow, and every request is routed, tracked, and closed with a full history. Built as a PWA so it works on a phone behind the bar or a desktop in the office without installing anything.

• Venue-scoped access control, so a manager at one location can't see or touch another's tickets
• Staff onboarding through an invite flow rather than open signup
• Per-ticket messaging thread, so the back-and-forth on a problem lives with the problem instead of in someone's texts
• Photo capture from camera or gallery, so issues are documented visually at the source
• Separate active and closed views, so the open queue stays focused

This is a production system handling real work across six venues, designed, built, secured, and shipped by one person. The access-control model alone — every query scoped to the right venue, verified and corrected when an edge case slipped through — is the kind of thing that separates a working product from a demo.