# Reservation Requests Every pending request from an official who wants to work a **By request** game, across all your games in one place. Approve a requester to assign them. When a game fills, the rest stay in your queue as **backups** under **All Games** until a slot frees up. If you decline instead (**Organization Settings → Reservation Requests**), they’re declined and shown similar open games. ## Tip Click a `Requests` badge on the Games page to jump straight here, filtered to that game. ## Workflow ### Review See who requested each open slot, and any schedule conflicts or prior history with you. ### Approve Click `Approve` on the requester you want. They're assigned immediately. ### When a game fills Its other requesters become backups under **All Games**, and each is told once and shown similar open games — no action needed. If you decline losing requests, they’re declined instead. ## Sections ### The Summary Bar Pending requests and Games with requests use the current filters. Open slots and Oldest request use the current page: #### Pending requests Total requests waiting for a decision across every game shown. #### Games with requests How many distinct games have at least one pending requester. #### Open slots Total unfilled official slots across games on the current page — a rough sense of how much staffing is still needed. #### Oldest request When the longest-waiting request on the current page came in, so nothing sits unattended too long. ### Filtering Narrow the queue before you review it: #### Event Show only requests for games linked to one event. #### Date range From / To — limit to games in a specific window. #### Officials Show only requests from specific officials. #### Show `Needs Officials` (the default) lists only games with an open slot. `All Games` adds full games, including any backups they still hold. #### Search Click `Search` to apply. `Reset` clears every filter, including one arrived via a game link (see the Tip above). ### Group by Game or Official Toggle how the queue is organized: #### Game One card per game, its requesters listed by who requested first. Shows `N in queue` (and the queue limit, if the event sets one). A full game shows `Full · N backups` instead, with Approve locked until a slot frees up. A requester the game filled over is tagged `Backup`. #### Official One card per official, showing every game they've requested — useful for spotting an official requesting more games than they can realistically work. ### What each requester row shows Context to help you decide who to approve: #### Prior games How many times this official has worked with you before — `No prior games with you` for a first-timer. #### Schedule conflict Flags when this official already has another assignment (or another pending request you approved) at an overlapping time. Approving anyway is allowed, but the conflict is your call. #### Requested When they submitted the request — oldest first within a game. #### Distance Shows `—` today; officials don't have stored locations yet, so this isn't populated. ## FAQ ### What happens when I click Approve? The official is assigned to that slot immediately — the same assignment path as the Games page assign flow. For an event-linked game they're added to the event's official pool first; for a standalone game they're assigned directly. ### Why did a request disappear without me approving it? The official withdrew it, it overlapped a game you assigned them to, or the game filled while you decline losing requests (**Organization Settings → Reservation Requests**) — then each official is told they weren’t selected and shown similar open games. By default a filled game keeps them as backups under **All Games** instead. ### Where are my backups? Under **All Games**. The default **Needs Officials** view lists only games with an open slot, so a full game and its backups appear once you switch to **All Games**. Each backup is tagged `Backup`; the game says `Full · N backups`, and Approve opens if a slot frees up. Requests on full games aren’t counted in any request badge (the nav, the Games page, or an event schedule), since there’s nothing to approve yet — once a slot reopens, its pending backups count again. Turning on **Decline losing requests** doesn’t decline backups you already hold — they stay in your queue. ### Why can't I click Approve? You don’t have **editor** access to assignments — you can see the queue but not act on it. Ask whoever manages delegations for editor access to assignments if you need to approve. Or the game is already full — its card says `Full` — and Approve opens if a slot frees up. ### A game shows "N in queue · limit X" — what does the limit mean? The event this game belongs to caps how many officials can queue for a slot at once. Once the limit is reached, officials can no longer submit new requests for that game until the queue shrinks — by approval, a withdrawal, or, if you decline losing requests, when a game fills. Backups you keep on a full game still count toward the limit. ### Why do I only see By request games here? Self-assign games never generate requests — an official claims an open slot instantly, with nothing for you to approve. This page only ever shows games set to require approval. ### What does the "Back to Games" button do? It appears only when you arrived here via a `Requests` badge on the Games page — click it to return to the Games page you came from. If you got here another way (e.g. the nav sidebar), there's no back button, since we don't know where to send you.