Sports Facilities Management Platform
A platform that centralizes facilities, equipment, bookings, maintenance and users, with workflows for field agents, administrators and other user groups.
Surf Web Development · French local authority
This case study does not expose any internal data.
- 01WebReact 19, TanStack Query and Zod-validated forms
- 02APINestJS, REST, JWT, Passport and Swagger
- 03DomainBookings, recurrence, conflicts and maintenance
- 04ServicesPostgreSQL, Prisma, email, PDF and mapping
Business problem
Bookings, associations, equipment and maintenance work were spread across several processes. The platform had to prevent schedule conflicts, improve availability data and make status changes traceable.
My role and contribution
Backend-focused full-stack developer. I contributed to API and data model design, booking and maintenance rules, React interfaces, tests and the delivery lifecycle.
- Designed domain-oriented NestJS APIs
- Modelled facilities, slots, equipment and maintenance with Prisma
- Implemented recurring booking and conflict rules
- Added notifications, PDF documents and Swagger API contracts
- Wrote Jest tests for bookings, maintenance, equipment and users
Core features
- 01Bookings and availability
- 02Schedule conflict detection
- 03Facility and equipment management
- 04Reports and maintenance workflows
- 05Notifications and documents
- 06Role-based dashboards
Simplified architecture
- 01WebReact 19, TanStack Query and Zod-validated forms
- 02APINestJS, REST, JWT, Passport and Swagger
- 03DomainBookings, recurrence, conflicts and maintenance
- 04ServicesPostgreSQL, Prisma, email, PDF and mapping
Main technical challenge
Keeping recurring bookings and maintenance consistent: a series may overlap a slot, make a facility unavailable or require a partial update without breaking history.
Qualitative outcomes
- Several operational processes centralized in one platform
- Lower double-booking risk through explicit rules
- Clearer equipment and maintenance tracking
- Automated coverage of sensitive business scenarios
Limits, confidentiality and lessons
The end client is intentionally anonymized as a French local authority. No name, logo, URL, internal screen or user data is published. The diagram was created specifically to explain the architecture.
Technologies used
Frontend
- React 19
- TypeScript
- Vite
- TanStack Query
- Zod
- Radix UI
Backend
- NestJS
- Prisma
- PostgreSQL
- JWT
- Swagger
Services
- Nodemailer
- PDFKit
- MapTiler
- Recharts
Quality
- Jest
- CI/CD
- Postman
- ESLint
- Prettier