How to turn repeated snapshots into useful timing decisions.

Activity history does not predict intent, but it reveals patterns. Use enough samples, choose the metric that matches the decision, inspect the members behind the percentage, and combine the result with Readiness before scheduling an operation.

Open Activity Tracker Read the screen guide Open Readiness

ShadowCore activity heatmap showing low-to-high color levels and ranked windows in Torn and local time — **Pattern before prediction**Use repeated green regions and stronger sample counts. One bright cell is not enough evidence to move a major operation.

The complete workflow

Let history accumulate

Automatic faction snapshots need time to build a dependable picture. A few days can reveal early patterns; several weeks is more useful for recurring schedules.

Choose the metric deliberately

Recent 15-minute activity answers “who is responding now?” Online average measures visible presence. Recent 60-minute activity captures broader participation. Okay/available coverage is closer to operational availability.

Read the color and the evidence count

Green means higher observed activity and red means lower observed activity. Compare the sample count before trusting the ranking.

Inspect the members behind a cell

Hover or select the cell. Review names, observed status, contribution count, TCT, and local time. The same percentage can come from very different member groups.

Compare Best windows

Use strong windows for chains, ranked-war pushes, major announcements, training events, or meetings that need broad participation.

Compare Quiet windows

Use low-coverage windows to plan officer coverage, avoid weak push times, identify recruitment needs, or schedule lower-priority work.

Convert time correctly

Coordinate faction-wide in TCT and use the displayed local time for personal scheduling. Watch for a previous-day or next-day local conversion.

Confirm current readiness

Historical activity identifies when members are usually present. Refresh Readiness before the actual event to check energy, cooldowns, travel, hospital state, and fresh Personal data.

Decision checklist

The selected metric matches the operational question.
The window is supported by enough snapshots.
The pattern appears across more than one week or day when possible.
The member detail matches the type of participation you need.
TCT and local dates are both understood.
Readiness is refreshed immediately before the operation.
Communication and member intent are still considered.

Useful applications

Chain timing

Choose a start that overlaps a repeated high-activity region, then confirm current Readiness and member availability.

Ranked-war pushes

Schedule planned pushes around stronger response windows, while keeping live target and readiness data current.

Recruiting strategy

Identify weak coverage periods and prioritize prospects whose normal schedule may strengthen those gaps.

Officer coverage

Use quiet periods to assign leadership coverage or avoid leaving the faction without a caller during known weak hours.