Availability, boss assignments, bench decisions and publish flow.
Open roster →Officer Scribe v8.7.0Closed beta
Guild operations without the spreadsheet sprawl.
Officer Scribe gives World of Warcraft leadership one place to plan raid nights, manage people, review progression evidence and keep decisions moving after Discord scrollback has gone.
Officer-controlled decisionsDiscord-first workflowEvidence kept with the raid
Guild OperationsTodayCOMMAND CENTREWhat needs attention next
Live workflowProgression evidence, avoidable mechanics and player trends.
Review logs →01
ReadinessWoWAudit Droptimizer checks linked to the published roster.
Ready02
PeopleRecruitment, trials, absences and player identity in one workflow.
Track03
Officer follow-throughMeeting decisions become owned actions and reminders.
Own itPlan the raidAvailability → roster → publish
Review the evidenceWarcraft Logs → Raid Intelligence
Run the teamRecruitment → meetings → actions
Keep raiders informedPersonal assignments → Raiders Zone
Built around the work officers already do every week.
No replacement spreadsheets disguised as a dashboard. Each area is connected to the next part of the guild workflow.
Raid planning
Boss-by-boss roster operations
Plan IN, BENCH and OUT assignments by encounter, enforce absences, use Roster Copilot as decision support and publish personal raid assignments.
Explore →Warcraft LogsRaid Intelligence
Review progression, avoidable mechanics, deaths, output changes and repeat patterns with evidence that stays attached to the raid night.
Explore →PeopleRecruitment and trials
Keep applicants, trial reviews, Raider.IO identity, Warcraft Logs evidence and officer feedback in one shared pipeline.
Explore →LeadershipMeetings, actions and reminders
Capture officer meetings transparently, turn decisions into owned actions and keep reminders and delivery history visible.
Explore →Guild eventsEvent Creator and Discord sign-ups
Create non-meeting guild events, collect Going / Maybe / Can’t attend responses in Discord and keep upcoming events plus history in the dashboard.
Explore →RaidersRaiders Zone
Give each raider a self-scoped view of rosters, attendance, performance history, Raid Intelligence and their linked character identity.
Explore →ReadinessWoWAudit and WoWUtils workflows
Verify Droptimizer readiness through WoWAudit and use explicit, reviewable WoWUtils roster/setup sync where the provider supports it.
Explore →OperationsRisk Radar and recruitment needs
Surface upcoming attendance pressure, utility gaps, draft-roster risk and role-depth concerns without making the decision for officers.
Explore →In gameOfficer Scribe addon
Bring raid-night operations and local RCLootCouncil history into WoW without turning the addon into a second source of truth.
Explore →Raid operations
One raid night, one operating view.
Officer Scribe keeps attendance, roster construction, readiness and post-raid evidence connected. Roster Copilot supports the decision with constraints and evidence; it never publishes a team for you.
Boss-specific compositionIN, BENCH and OUT / ABSENT per encounter with role targets and encounter rules.
Expected attendanceRaiders default to Present unless they explicitly mark Tentative or Absent.
Readiness checksWoWAudit Droptimizer status is matched back to the actual rostered character.
Risk RadarForward-looking attendance, role depth and unfinished-roster risk without automatic officer decisions.
1
Availability
Default-present attendance with explicit Tentative and Absent states.
2
Build the roster
Set the 20 per boss, apply encounter rules and review Copilot evidence.
3
Publish raid night
Lock the plan, send personal assignments and run readiness checks.
4
Review the raid
Analyse Warcraft Logs and keep the evidence beside the next roster decision.
ProgressionPull weighting and current execution wall
MechanicsAvoidable hits, repeat patterns and confidence
PlayersSelf-vs-self trends, deaths and output context
Officer queueShort list of causal actions worth review time
Raid Intelligence
Make the post-raid conversation more specific.
Raid Intelligence separates raid-level execution from player-level evidence, tracks progression over time and keeps uncertainty visible when the data is weak.
Mechanical Score remains avoidance-only: unsupported damage, required soaks and generic deaths do not become personal penalties.
Use the specialist tools. Connect the operational work between them.
Commands, roles, DMs, meetings, event sign-ups, reminders and guild access
Raid Intelligence, progression evidence and player review
Character-linked Droptimizer readiness and raid checks
Manual roster/setup reconciliation and supported absence flows
Canonical character identity for profiles and recruitment
Addon-side loot history and Officer Scribe bridge data
Team operations
Guild leadership does more than build a roster.
Recruitment, trial decisions, officer meetings, actions, reminders and broadcasts share the same guild context instead of living in disconnected channels and spreadsheets.
Recruitment pipelineFour-raid trial reviewMeeting captureAction ownershipDelivery historyGuild broadcasts
RecruitmentReview → Interview → Trial → Decision
MeetingsAgenda → Minutes → Decisions
ActionsOwner → Due date → Reminder → Complete
Raiders Zone
A useful player view without exposing the officer workspace.
Active raiders can see their own roster assignments, attendance, performance history, Raid Intelligence evidence and linked character details. Leadership data stays leadership-only.
My HubMy RosterMy PerformanceMy Raid IntelligenceMy Attendance
Officer ScribeGuild Operationsv8.7.0 · closed betaRun the guild from one operational workspace.
Install Officer Scribe, connect your leadership roles and keep the next raid, the last raid and the officer follow-through in the same place.
By installing or signing in, you confirm that you are at least 18 and agree to the Terms and Privacy Policy.