Download and print
Download the no-sign-up Markdown checklist or print this page. It is educational and does not certify a schema as secure or correct for a specific business.
Integrity and tenant boundaries
Review foreign keys, delete behavior, composite ownership constraints, tenant-aware uniqueness, cross-tenant access policies, and migration rollback. Ensure child rows cannot reference a parent in another business.
- Foreign keys and explicit cascade/restrict rules
- Tenant key or enforceable path for every private row
- Unique constraints scoped to the correct business and lifecycle
Time and lifecycle
Store instants consistently and retain the IANA zone used to interpret recurring local rules. Validate start < end, legal status transitions, capacity-consuming states, and rescheduling behavior. Decide whether historical records are retained or soft-deleted and who can restore them.
Operational safeguards
Include created_at/updated_at and only useful actor/audit fields. Protect overlapping reservations under concurrent requests. Add indexes based on customer, tenant, staff, status, and time-window queries; confirm with representative query plans. Keep privileged credentials server-side and review row-level security policies.