- Industry
- Hospitality · Italian hotel compliance
- Type
- Guest reporting & reservation desk
- Roles
- Hotel manager · front desk staff
- Stack
- PHP · MySQL (invioUserDB) · Morris charts
- Proof
- 5 screens · 2:27 product demo
The problem
Italian hotel operators must file guest data to ISTAT and police systems — manual forms and spreadsheets break under seasonal volume.
Constraints
Delivery stayed inside the client's stack, tenancy, compliance and media-ownership boundaries. Where a choice was forced (suite vs owned plane, BYOC vs CPaaS, local vs cloud models), the architecture section below records the trade-off rather than a marketing rewrite.
Business requirements
Reservations desk, Italian guest compliance forms, export and reporting on PHP MVC.
Architecture
Classic MVC admin with reservation entities feeding compliance export jobs.
Engineering challenges
- Compliance fields — ISTAT/police shapes validated before export.
- Legacy UX — operators need fast reservation entry.
The solution
Italian hotel guest compliance-style platform with admin screens and export path documented locally.
My role
Full-stack PHP delivery for hospitality compliance workflow.
Technology stack
Production considerations
- Export audit trail for submitted guest filings.
- Role separation for front-desk vs back-office.
Screenshots
Hotel login

Dashboard

Attendance trends, subscription status and support shortcuts — the daily operational view for property managers.
New reservation

Italian guest compliance

Multi-guest wizard captures birth place, document type and ID numbers required for domestic guests.
Non-Italian guest compliance

Working-system video
Watch on YouTube → · 2:27 · Dedicated watch page →
Architecture diagram
flowchart LR HOTEL[Hotel desk] RES[Reservations] IT[Italian guest flow] NIT[Non-IT guest flow] DB[(MySQL invioUserDB)] OUT[ISTAT / Questura export] HOTEL --> RES --> DB RES --> IT --> OUT RES --> NIT --> OUT
Outcomes
Restored or delivered system documented with screenshots and local demo — portfolio write-up only.
FAQ — buyer & architecture questions
Ten common questions about this case study, fit, and engagement.