Skip to main content

Performance expectations

Optional per-signal targets that define what good looks like in your alliance. When set, Officer Pulse scores members against these absolute bars; when blank, Pulse falls back to alliance-relative scoring. Mix and match — pin the signals you have a clear bar for, leave the rest in relative mode.

How it works

Each of the four signals — donations, Alliance Duel, Marshal's Guard, DS attendance — has a checkbox + value field. Tick the box and enter a number to set a target; leave unticked to fall back to relative scoring (members compared against the alliance distribution). Officer Pulse reads these values and uses them in the composite score. R5 edits; R4 can read but not change so the bar can't be quietly lowered to mask gaps.

Try it

// LIVE DEMO · SAMPLE DATA

// PERFORMANCE EXPECTATIONS

Optional targets for what good looks like in your alliance. When you set a target, Pulse marks each member as on track or below against it. When you leave a signal blank, Pulse falls back to comparing members against the alliance average instead. Mix and match — set the ones that matter, skip the rest.

per week
per day
%
The real form, running on demo data instead of your live alliance. Tick a signal to enable a target; type a value. Save is wired to a no-op so the form doesn't redirect.

Picking targets

Don't set targets pre-emptively. Relative scoring is the safer default for new alliances — Pulse marks members who are quietly drifting compared to peers, even without an absolute bar. Add targets only when you find yourself saying “this number should be higher than X” enough times that it would be useful to see the gap explicitly.

// TIP

A common starting point: weekly donations 50,000, daily VS 7M, DS attendance 80%. Watch the Pulse leaderboard for a couple of weeks; if 80% of the alliance lands below the bar, the bar is probably wrong, not the alliance.