Phoenix

RCLootCouncil Export String -- click Generate to build an encoded string from the current priority order and roster. Copy it and paste it into RCLootCouncil in-game to sync loot priorities to your council.
Priority List -- read-only view of every item's ranked priority order as set in the Priority Order sheet. The Heroic/Mythic toggle above the list shows one difficulty at a time (Heroic by default) instead of stacking both under every item. Each ranked player shows their current wishlist tag for that item (or "No wishlist tag" if they never tagged it), so you don't have to leave the tab to check what they actually set. Use the search box to jump to a specific item. Above the list sit three collapsible summary sections, each starting collapsed with a one-line overview -- click a section's header to expand it for the full detail: "Priority List Conflicts" (stale-after-Heroic #1s and same-boss #1 stacking), "Drift" (see below), and "#1 Priorities Held" (every player currently holding at least one #1, with their count and a flag if any of those #1s share a boss -- two items both locked behind the same kill; counts of 4+ are highlighted in red as worth a look). The badge count on this sub-tab covers just the Conflicts and Drift sections, not the full #1 table, since holding several #1s is expected once the raid has 30+ managed items.
Drift -- a saved item/track priority order (the one committed via the Priority Edit modal) whose top 3 no longer matches what the scoring generator would suggest today. This can mean scores shifted enough since the save to reorder or bump a player in/out of the top 3, but it's just as often a saved order that was intentionally hand-adjusted away from the generator's suggestion in the first place -- the check has no way to tell those two apart, since it only compares the saved order against today's generator output, not against what the generator suggested at save time. "Check for Drift" recomputes and compares live; it also runs automatically right after committing Scoring tab performance updates. A drift flag isn't automatically wrong -- it's worth an officer's eyes to confirm the saved order is still the intended one, not a signal that something needs fixing.
Unmanaged Items -- items that appear in players' BiS lists but have no priority order assigned yet in the sheet. The badge count shows how many need attention.
Contested Items -- items wanted by 6+ players (officer BiS picks and raider wishlists combined), collapsed by default -- click an item to see who wants it and their current priority rank.
Notes -- every item with a raider-written wishlist note, and who wrote it (e.g. a pure-DPS raider explaining an off-spec BiS want). The gold badge is just a "something's here" flag, not a problem to fix. Read-only context for sequencing calls -- doesn't affect the generated priority order itself.
Incomplete Wishlists -- raiders who haven't tagged a status for every gear slot yet. Worth checking before generating a suggested priority order; see the BiS Manager > BiS Lists sub-tab for which slots each raider is missing.

Refresh from WCL -- fetches the last raid reports from WCL and calculates Recent/Trend/Best scores for each DPS player, using whichever metric is selected: Ilvl Bracket % (percentile within same-gear players -- consistent across gear levels, but the comparison pool grows as the tier goes on, which can push scores down over time even with steady play) or Overall % (percentile across everyone who logged the fight -- a stabler pool over the tier, but rewards being ahead on gear). Tanks and healers are skipped and marked Manual. Scores are held in a session draft until committed.
Commit Performance Scores -- saves the Recent score from the draft above into Scoring (performance_score), which is what the Priority Generator uses. Safe to run multiple times; it always recalculates from scratch.

Raid Nights Since Last Item -- how many raid nights have passed since each player's last loot award, grouped by role.
BiS Demand vs Awards -- ranks items by how many active players want them on their BiS list, next to how many times each has actually been awarded in the selected season. High demand + low awards is what to prioritize.
Priority Order Health -- flags stale priority order entries for players no longer on the active roster, active non-bench players missing from priority order entirely for a season, and saved Mythic #1s where the player already received the Heroic version of that same item.
Season Loot Pace -- items awarded per week of the season, compared to the same week last season. "Week 1" is measured from the first tracked loot award of the season, not the raid-lockout calendar, since Supabase doesn't store a season start date yet.
Tier Sets -- each active roster player's tier-set piece count (out of 5), so you can see who's behind without opening every profile card. Synced from Raider.IO via the "Sync Roster Tier Counts" button here (same sync as the Priority tab's).

These recurring nights drive the raid calendar raiders see (Home widget and the Calendar page) -- add one row per weekly raid night, edit and click Save per row. Raiders are auto-marked Present unless benched; an Optional night has no automatic Present and everyone must respond instead (#895).
Use One-Off Changes below to cancel a single occurrence of a weekly night, or add an extra night that isn't part of the regular schedule.
Cancelling or removing a night does not touch any RSVPs raiders already submitted for it -- those rows are left in place but become harmless.