Skip to main content

Overview dashboard

The overview is your alliance home screen. It answers three questions the moment you open it — what’s firing, what needs a decision, and what’s changed — then hands each person the single most useful thing they can do next.

What it is

The overview replaces the “where do I even start?” moment. It is organised around the events your alliance plays and the people who play them, and it's built to be a five-second morning glance rather than a page you study. The top band carries anything that needs attention; below a divider sit the daily-ritual surfaces people open the dashboard to check — today's train, the season clock, alliance power, the shield board, donations, and upcoming Desert Storm.

Everything on the page is state-dependent. A quiet day renders a quiet dashboard; a day with an unrostered match, an unrecorded result, or a shield window opening surfaces exactly those items near the top. If you are brand new, Getting started explains how the pieces fit together first.

The next-action engine

At the top of an officer's dashboard sits the Next up card — one prominent “do this now”. Behind it is a rules engine that reads the data the overview already has and fires an action whenever its condition holds. Actions are sorted by priority and the card shows the top of the list. There is no dismissing or snoozing: an action disappears on its own the instant the underlying state changes.

The rules span the whole officer workflow, roughly in priority order:

  • Desert Storm anchors — create this week's match when none exists, or lock the roster when match day is within two days. See the Desert Storm guide.
  • Perishable results — a finished Desert Storm or Canyon Storm match with no result recorded, prompted while the results mail is still in your in-game inbox.
  • Season rhythm — phase-aware nudges driven by the season clock: war-day prep, faction-choice windows, key deadlines, and the week-one checklist.
  • Daily rhythm — record today's VS scores and donations (or this week's, if your alliance records weekly), and scan scored events like Marshal's Guard or Zombie Siege the moment they wrap.
  • Shield days — open the shield board on a buster day when fewer than half the alliance is shielded.
  • Weekly upkeep — set or refresh the recommended tech (R5 only), calibrate Pulse expectations, and take a power snapshot.

// NOTE

A few rules are rank- or tier-gated. Setting the recommended tech is an R5-only write, so R4s never get sent to a locked form. Power snapshots and expectation calibration are Pro features. During the first two weeks of a new alliance the engine adds gentle onboarding steps — post a first announcement, bring real members onto the platform — and frames them as a starter ladder.

The attention layer

Under Next up, a set of compact cards make up the “what needs my attention” layer for officers:

  • Recording radar — a slim staleness line showing what you last uploaded per event type, so nothing quietly goes unrecorded. It stays hidden when everything is fresh.
  • Today across the alliance — a full-width banner of what is happening on the current game-day.
  • Signup gaps and Pending decisions — open rosters that still need filling and requests waiting on an officer.
  • Who needs a nudge and Last 24 hours — at-risk members and a recent-activity feed.
  • MVP of the week — a public recognition card visible to every rank, not just officers.

Daily rituals and standing

Below the attention layer, a “Daily rituals” block gathers the surfaces people habitually open the overview to check. You'll find the latest announcement, today's train conductor and VIP, the active season with its timeline strip and phase focus, the season-prep checklist progress, and total alliance power from the most recent snapshot.

Beneath those, quick-glance cards summarise standing — how many members are shielded today, how many have donated, General's Trial progress, and the list of upcoming Desert Storm matches. Each links straight through to its full surface. When there are no upcoming matches, the card explains that the next one auto-creates every Monday and offers a button to create one sooner.

Members vs officers

The overview is role-aware. Officers (R5/R4) get the run-this controls — the full next-action engine, recording radar, signup gaps, pending decisions, and the recruiting nudge. R3–R1 members get the contribute-this view: today's events, the season clock, standing, and their own next steps via My hub's “Your next” band.

For the personal side of the picture — your own trends across donations, attendance, and shield compliance — see My history.

// TIP

If your alliance has more than one active alliance on your account, opening the dashboard without an explicit pick sends you to the alliance hub to choose first, rather than dropping you into whichever one loads first.