<!-- generated by php artisan docs:split-brd from brd/BRD-Morvia-Project-Guide-en.md — edit the BRD, not this file -->

#### TRR-031 | Hall search and booking request (trainer)
**Source:** p.76–78; A-p.6, A-p.18 · **Actor:** independent trainer, affiliated trainer
- **Built as (D8):** the hall's `availability` shows only what is free — time held by an accepted or booked request is hidden and returns if the booking is withdrawn or cancelled.
- **Who can request:** the independent trainer and the center-affiliated trainer. A **trainee cannot**
  create a hall booking request; trainees only browse halls (TRN-027).
- **Request:** one request can hold **one or several slots** for the **same hall**; all slots are one
  booking unit with **one status**.
- **Request data:** hall · expected attendees · requested extra features · list of slots, each with
  date, start time, end time. The trainer adds several slots manually.
- **The system automatically:** computes the hours of each slot and of the whole request · checks
  capacity · checks availability for each slot · checks conflicts for each slot · computes the total
  price of the whole request (HPV-005).
- **Rules:** all slots in a request belong to the same hall and the same selected features; no automatic
  recurrence ("every Sunday and Tuesday for a month") — slots are entered manually.
- **Validation before sending:**
  - *Capacity:* expected attendees must not exceed the hall's maximum capacity.
  - *Availability:* every slot must fall inside an availability period of the hall on that date.
  - *Conflict:* no slot may conflict with an existing booking of the same hall in the same period.
  - *Result:* if any slot is unavailable or conflicting, the request cannot be sent until that slot is
    edited or deleted. No partial booking or partial acceptance.
- **Changed by additional requirements:** booking is done independently of course creation; the trainer
  copies the booked hall's details into the course (D1, TRR-010). For a threshold-start in-person
  course the booking happens after the minimum is reached and the date is set (TRR-015).
- **Built as (TD-24):** only accepted and booked requests hold a slot; a pending request does not block another trainer, and the same trainer cannot send the same pending times twice.

**Acceptance, rules and screen notes citing TRR-031:**

- WF-07 — Hall booking — Trainer / center builds request (slots, attendees, features) → validation (capacity, availability, conflict) → Pending → provider accepts (contacts revealed, price fixed, commission Pending) or rejects → external payment → provider confirms Booked (commission Due = income) → Completed after last slot. Booker withdraws before Booked; a Booked booking is cancelled by the provider on the booker's request or offline with a reason; any cancellation cancels the commission (D8, DEC-33); admin settles commission — TRR-031, TRR-032, HPV-007, HPV-008, HPV-009, HPV-010, HPV-011, ADM-018, ADM-019, ADM-020
- BR-HALL-07 — The price is computed from the total hours of all slots in the request plus the selected feature prices charged per slot. — HPV-005, TRR-031
- BR-HALL-09 — The number of attendees cannot exceed the hall's maximum capacity. — TRR-031
- BR-HALL-10 — One booking request can hold one or several slots for the same hall; each slot has a date, start time and end time. — TRR-031
- BR-HALL-24 — Booking slots are entered manually in the request; the current scope has no recurring booking engine. — TRR-031
- BR-HALL-25 — If any slot in the request is unavailable or conflicting, it must be edited or deleted before the request is sent. — TRR-031
- BR-ADMIN-HALL-05 — A multi-slot booking stays one booking with one status. — ADM-018, TRR-031
