Plan for IM777 Game Events: Format, Scoring and Session Notes

Build the Plan From the Instructions

List the actions that create points, the actions that create penalties, and the requirements for advancement. A strategy borrowed from another structure might reward the wrong behavior.

Select two or three repeatable priorities. A plan with ten moving parts is difficult to follow once the clock or live standings adds pressure.

• Identify advancement requirements.
• Select repeatable actions.
• Use a short plan.
• Map points and penalties.

Practice Under the Real Timing

Use the app event's stage length, break length, and review-in window during practice. Unlimited practice time can hide decisions that fail under the actual schedule.

Prepare the mobile device, connection, and a quiet space as part of the plan. Technical interruptions consume the same clock as strategic hesitation.

• Practice the review-in routine.
• Try the intended mobile device.
• Plan short breaks.
• Match the stage timer.

Use Position as Information, Not a Command

Review standings between stages and note which point system category changed. Don't throw away a steady plan because one provisional outcome moved the position.

Adjust only when the table shows that the latest priority cannot meet the advancement target. Know the penalty before choosing a higher-risk action.

• Look at category movement.
• Change one priority at a time.
• Price the penalty first.
• Review position at natural breaks.

Take a moment to take a moment to review the Plan Afterward

Keep a copy of the confirmed point total by category and compare it with the original priorities. Separate a strategy mistake from a mobile device problem or misunderstood instruction.

Write one change for the next app event rather than rewriting everything. A specific adjustment is more useful than a general promise to “play better.”

• Compare each point system category.
• Separate technical and strategic causes.
• Select one next improvement.
• Use the confirmed, not provisional, table.

Plan for Separate Point Total Positions

Write a simple response for three situations: comfortably above the advancement line, close to it, and clearly below it. Each response should still respect the published penalties and personal boundaries.

This keeps a live standings from making the decision for you. The plan can become more conservative when a position is secure and more selective when additional points are genuinely needed.

Don't treat every lower position as a reason to increase risk. First review if pending results or a tie-break are creating a temporary position.

• Prepare a near-cutoff adjustment.
• Limit higher-risk actions.
• Review pending results first.
• Define a secure-position response.

Manage Attention Between Stages

Use the break to review one or two useful facts: remaining schedule, point system category, mobile device state, and the next objective. Social messages and constant table refreshing rarely improve the plan.

If a mistake happened, write down the cause in one sentence and return to the next stage. Replaying it mentally uses attention without changing the settled outcome.

Make sure the phone is charged and cool, but steer clear of a major system or app change once the app event is underway unless the latest setup has genuinely failed.

• Leave settled mistakes behind.
• Review battery and temperature.
• Steer clear of mid-app event software changes.
• Review only decision-relevant facts.