How to build a dependable “who can act now?” list.

Readiness works best as a repeatable process: current Personal data, one authoritative faction roster, clear blockers, and a concise call list.

Open Readiness Board Open Personal Read the screen guide

ShadowCore member readiness board with scores, bars, location, cooldown, HQ use and blockers — **Use the row, not only the score**Current bars and snapshot age explain data quality; the action and blocker columns explain what must happen next.

The complete workflow

Members refresh Personal

Before a major operation, ask members to open Personal and allow the automatic snapshot capture to complete. This updates energy, nerve, life, cooldowns, status, travel, and battle-stat coverage.

Leadership refreshes Readiness

Confirm the source line shows the expected faction roster count. The board should show one row per roster member and attach the newest valid snapshot to that identity.

Separate immediate groups

Start with Ready, then Standby. Review Limited members individually. API Missing means the member is known from the roster but lacks usable Personal data.

Check hard blockers

Travel, hospital, life, drug cooldown, stale data, no recent HQ use, and missing operational data can reduce availability even when a member appears active.

Verify unusual rows

If location, bars, or status contradict what the member reports, check snapshot age and refresh. Do not manually reinterpret unknown data as zero.

Copy the call list

Use the Discord summary for a fast call, then keep the board open during the operation so changes can be refreshed.

Readiness quality checklist

Roster member count matches the faction.
Each Torn ID appears only once.
No browser, extension, or placeholder label appears as a faction member.
Important members have recent Personal snapshots.
Blank bars are treated as unknown—not empty.
Travel and status come from the newest operational snapshot.
Leadership checks the listed blocker before making a call.

When to refresh

Before a ranked-war push

Refresh shortly before target calls so travel, hospital, energy, and cooldown information is useful.

Before a chain

Use the board with Activity windows to estimate both current usability and likely participation.

After a member fixes a blocker

Refresh after returning home, leaving hospital, clearing cooldown, refilling energy, or updating Personal data.

When a row looks impossible

Check timestamp and source first. Incorrect-looking rows are often stale or missing snapshots rather than scoring arithmetic.