Evony Battlefield Signup Workflows That Actually Work

Apr 21, 2026 by evonytools 6 min read

TL;DR: Battlefield events like BoC and BoG only allow 20 members per team, so “signup” is really about team selection and availability tracking. SvS involves everyone but needs shift coordination. This guide covers how to build workflows for each event type that scale as your alliance grows.

The real problem: team selection, not open signups

Most Evony alliances approach battlefield events like open-registration sporting events — post a signup sheet and hope the right people respond. But that misses how battlefield events actually work.

BoC and BoG are 20v20 matches. R4/R5 registers the alliance, picks a timeslot from the 9 available options, and selects which 20 members will fight. This is not an open signup — it is a leadership decision about who plays.

SvS involves the entire server for 7 days. Here, the challenge is not limiting participation but coordinating shifts and roles across your full roster.

These are fundamentally different problems that need different workflows.

BoC and BoG: the 20-member team workflow

For weekly battlefield events, you need a system that answers three questions:

Who is available at the timeslot options we are considering?
Who should we pick from the available members?
Who are the alternates if someone drops?

Step 1: Availability check (48-24 hours before registration)

Before registration opens, post an availability poll covering the timeslot options:

List the 9 available timeslots (or the 3-4 most realistic ones for your alliance’s timezone spread)
Members react or respond with which slots they can make
R4/R5 reviews availability and picks the timeslot where the strongest combination of players can attend

Why this matters: If your best 20 players can all make Slot 3 but only 12 can make Slot 7, picking Slot 7 because it is convenient for the R5 costs your alliance the match before it starts.

Step 2: Team selection (when registration opens)

Once R4/R5 selects the timeslot and registers the alliance, it is time to pick the 20.

Selection criteria to consider:

Troop tier and count — a player with full T13 marches is more valuable than a higher-power player with depleted troops
General quality for the role — BoC needs building capturers, defenders, and kill team members. BoG needs all of that plus players who can handle the Phoenix and other boss monsters.
Reliability — a player who shows up on time every week is worth more than a stronger player who is a coin flip
Role balance — 20 attackers and zero defenders loses BoC. You need a balanced team.

The selection message in Discord should include:

The 20 selected members, tagged
Their assigned role (capture team, defense, kill team, carriage/boss duty)
3-5 named alternates in priority order
The timeslot in UTC plus local timezone conversions
A deadline to confirm (e.g., 6 hours before the match)

Step 3: Confirmation and alternates

Every selected member must confirm. A “selected but no-show” is worse than not selecting them at all because you could have given the slot to someone reliable.

Confirmation flow:

Selected member reacts or messages to confirm
If a member does not confirm by the deadline, R4 moves to the first alternate
Alternate gets a direct notification: “You’re now on the BoC team. Can you confirm?”
If the alternate also cannot make it, move to the next one

Set a hard cutoff for substitutions — no swaps within 1 hour of the match. If someone drops that late, you play with 19 rather than bringing in someone unprepared.

SvS: full-roster shift coordination

SvS is the opposite problem. Everyone participates, but you need to coordinate 7 days of sustained activity across timezones.

Shift signups

Divide the day into 3-4 shifts based on your alliance’s timezone spread:

Shift A: 00:00-06:00 UTC (Asia/Oceania prime time)
Shift B: 06:00-12:00 UTC (Europe morning, Asia evening)
Shift C: 12:00-18:00 UTC (Europe afternoon, Americas morning)
Shift D: 18:00-24:00 UTC (Americas prime time)

Members sign up for the shifts they can cover each day. Most members can cover 1-2 shifts per day.

What to track per shift:

Shift lead (R4 or trusted R3)
Number of rally-capable players online
Number of temple defenders available
Total active members

The goal: ensure every shift has at least one rally leader, enough fillers for a rally, and enough defenders to hold temples. If a shift consistently has gaps, adjust shift boundaries or recruit members in that timezone.

Role signups for SvS

Beyond shifts, SvS needs role assignments:

Rally leaders — who can lead PvP rallies? Boss rallies? Throne attempts?
Temple holders — who will sit on temples during their shift?
Scouts — who monitors enemy movement and reports in Discord?
Resource managers — who tracks healing reserves and distributes speedups?

These roles should be assigned before SvS starts, not improvised on day 1.

Tracking availability over time

The alliances that handle team selection best are the ones that maintain ongoing availability data, not just event-by-event polls.

What to maintain:

Each member’s typical online hours (in UTC)
Each member’s BoC/BoG participation history (selected, confirmed, showed up, performance)
Each member’s SvS shift coverage history
Preferred roles and strengths (rally leader, filler, defender, etc.)

Why this matters:

When registration opens for BoC, you already know which timeslots work for your strongest players without running a new poll
When selecting your team of 20, you can see who has been reliable vs. who tends to drop
When planning SvS shifts, you know where your coverage gaps are before the event starts

Alliance Studio’s roster system tracks member availability, participation history, and role assignments in one place. If you are managing this manually, a dedicated spreadsheet tab per member with their availability windows and event history is the minimum.

The no-show problem

No-shows are the single biggest source of frustration in battlefield events. A selected member who does not appear wastes a slot that could have gone to someone else.

Preventing no-shows:

Require confirmation, not just selection. “You’re on the team” is not enough — they need to actively say “I’ll be there.”
Send a reminder 2 hours before the match and again 30 minutes before
Track no-shows over time. A member who no-shows twice without explanation should not be selected for the next event.

Handling no-shows gracefully:

Do not call people out publicly. DM them after the event: “We missed you at BoC. Everything okay?”
If there is a pattern (3+ no-shows in a month), have a direct conversation about commitment
Use the no-show data in future team selection. Reliability matters as much as power.

What not to do:

Do not rage in Discord about no-shows during the event. It kills morale for the 19 people who did show up.
Do not permanently blacklist someone for one no-show. Life happens. Patterns matter, not isolated incidents.

Building the workflow without dedicated tools

If you are not ready for a dedicated management tool, here is the minimum viable workflow using Discord:

For BoC/BoG:

Create a dedicated #battlefield-team channel (only R4+ can post, everyone can read and react)
Post the availability poll when you learn the event is coming
Post the team selection with role assignments
Track confirmations via reactions
DM alternates individually when needed
After the event, note attendance and performance in a spreadsheet

For SvS:

Create a #svs-coordination channel
Post the shift schedule with shift lead assignments
Members react to shifts they can cover
Post daily objectives each morning
Shift leads post handoff notes at shift changes

This is labor-intensive but functional. When the R4 managing team selection spends more time coordinating in Discord than preparing strategy for the actual match, it is time for a dedicated system.

For the full pre-event workflow including how team selection feeds into BoC preparation, see the preparation checklist guide. For how SvS coordination works day by day, see the SvS preparation guide.