Heists: check stakes, Help and the timer before starting

Read the current requirements before committing

Open the Heists screen and inspect the proposed action before starting it. Record the displayed resource commitment, timer, participation requirements and possible outcome. If the plan depends on other players, confirm their availability first. Having enough cash does not establish that the whole plan is ready.

AllThingsHow’s September 10 report describes starting Heists, sending Help and a timer-based Help requirement. Those details are third-party reporting, not independently reproduced gameplay here. We do not treat the report’s unlock levels, payouts or timing values as permanent rules.

Starting and helping are different decisions

A starter evaluates the full commitment and whether enough support is available. A helper evaluates the cost and eligibility of the individual action offered to them. The cited report describes Favors and Stamina as relevant to helping and also describes Sabotage. Inspect the live controls for the cost, effect and availability of each option; do not assume that similarly placed buttons have equivalent consequences.

For either role, name your objective. Learning the interface, supporting a family and earning cash can justify different spending limits. Keep a learning attempt small enough that an unexpected result does not derail the purchase you were saving for.

A five-field plan before pressing Start

Use a dated time rather than “later tonight.” The time-zone converter helps coordinate people in different countries. It does not know the game’s event schedule; enter the date and time you have agreed.

Why cash alone is a poor readiness measure

Illustration: your available budget is 30,000 and an action asks for 10,000. That leaves 20,000, but says nothing about other required resources or support. If you also need 25,000 for a near-term purchase, the commitment delays it even when the action is affordable. Compare the remaining balance with your actual priority.

When reviewing a result, separate the returned stake, new cash reward and non-cash items. A gross payout is not automatically profit. If the game does not show enough information to distinguish them, record the uncertainty instead of publishing a precise return rate.

After a failed or unclear result

Keep the result message, before-and-after balances, elapsed time and any visible contribution total together. Missing rewards, an unmet requirement and an expired timer are different observations. Do not assume that another purchase or a higher stat would have fixed the attempt.

Review group coordination if support was the issue. Review the progression diagnostic if an account requirement blocked participation. For changed rules, trace the announcement through official links. This guide is a preparation and review framework, not a guaranteed Heist completion route.

How much did the Heist actually earn?

Record your wallet immediately before paying the stake, then record it after the result. Subtract unrelated income earned during the run and add back unrelated spending. That reconciled change measures cash gained or lost by this attempt. It does not value XP or items.

If a result panel’s “reward” already includes your returned stake, subtracting the stake again from a reconciled wallet change counts it twice. Conversely, treating the full result credit as profit ignores the initial cost. Record the actual movements if the label is ambiguous.

For planning, define success profit S and failure loss L as net cash changes, and let p be a probability you can justify. The simple model is p × S − (1 − p) × L. With hypothetical S = 3,000 and L = 5,000, break-even is p = 5,000 ÷ 8,000 = 62.5%. This is a threshold, not a measured success chance. Do not convert one successful run into a probability estimate.

Keep required Help, deadlines and account gates as separate readiness checks. Passing a cash calculation does not meet those conditions. Record the planned participants and dated time in the session planner.