Before the next wave
Complete the current footprint and check movement/access. Decide what you are testing: a closed gap, an equipment position, an inner fallback or a teammate role. Let someone watch the approach while another changes the base. If the current UI offers wave-start or skip controls, read their labels and avoid speeding up while construction is unfinished; this is conditional advice, not a verified control binding.
Observe the first failure
Watch which approach is used and the first moment your plan stops working. Does an enemy enter an unfinished opening? Does your equipment fail to engage the approach? Do you lose the route to your second position? Change your player position if needed, but separate that active intervention from what the base did unaided. A late defeat after a successful first contact is a different problem from immediate entry through a gap.
Hold or expand?
Hold and fix the first failure when a gap, obstruction or inaccessible fallback remains. Expand only after the current footprint has a useful test result and the extra area has a purpose. If you change walls, equipment and boosts at once, you cannot tell which change helped. Pick one change and return to a comparable starting state when possible.
A short useful record
Date/version: ___ · Starting wave/state: ___
Changed part: ___ · First approach: ___
First failure: ___ · Active support/boosts: ___
Next single change: ___
Record: date/current visible version; starting wave/state; changed part; first approach; first failure; active support or boosts; next change. Example: 'I closed the left opening; enemy approached from the front; I could move inside; coverage missed the side; next test moves one defense.' This is an illustrative observation format, not a claimed gameplay run.
Use the right result
A better wave result can support your own build decision. It does not establish global HP scaling, a universal spawn order, a permanent boss wave or an offline income formula. When boss behavior is the failure, use the boss preparation guide; when leaving is the task, use the offline audit.