Facility Booking
Manages booking for all municipal recreation facilities — arenas, pools, community centres, sports fields, park pavilions — including ice allocation, sports field scheduling, seasonal/recurring bookings, pricing, and conflict prevention.
Double-Booking
Booking Confirm
Calendar Load
Concurrent Bookings
Purpose-Built for Canadian Municipalities
Purpose & Scope
What this module owns
Clear ownership boundaries prevent duplication and ensure every capability has exactly one authoritative home.
Owns
8Delegated to
4Core booking engine, calendar
Facility locations, map display
Deposits, rental fees, refunds
Confirmations, reminders, weather cancellations
These capabilities are handled by dedicated modules and consumed via stable API contracts — keeping boundaries clean and ownership unambiguous.
Core Capabilities
What it does
4 capability groups comprising 8 discrete capabilities — each with API surface, business rules, and data ownership.
Define facilities with type, amenities, capacity, accessibility, and subdivide into bookable spaces.
Facilities
Define facilities: name, address, type (arena, pool, community centre, sports field, park), amenities, capacity, accessibility, photos, operating hours.
Spaces
Subdivide into bookable spaces (Arena A, Meeting Room 1, Diamond 1). Space attributes: capacity, floor surface, equipment, setup options.
Online search, visual availability calendar, booking requests with instant or approval-based confirmation.
Search
Search by type/date/time/capacity. Visual availability calendar.
Request
Booking request with event type, attendance, setup, special requests. Instant confirmation (low-risk) or approval workflow (alcohol, large, commercial).
Every module owns a single bounded context, exposes stable APIs, and can be composed into any Civic product — that's the architecture that scales.
Krutik Parikh
Creator of Civic
Data Model
Entity Architecture
5 entities with 4 relationships — the authoritative schema for this bounded context.
Entities
Select an entity to explore its fields and relationships
API Surface
Integration Endpoints
9 RESTful endpoints across 4 resource groups — plus 3 domain events for async integration.
/api/v1/facilities
List facilities
/api/v1/facilities/{id}/spaces
Bookable spaces
/api/v1/facilities/{id}/availability
Availability calendar
Ecosystem
Products that depend on this module
1 Civic products consume Facility Booking — making it one of the most critical platform services in the ecosystem.
Technical Specifications
Performance, Compliance & Configuration
Double-Booking Incidents
Booking Confirmation
Calendar Load
Concurrent Bookings
Availability
FAQ
Frequently Asked Questions
Ready to Integrate
Build on Facility Booking
Request an architecture brief, integration guide, or live demo environment for your team.