Exit planning: decide why and how the position ends before entry

The short answer

An exit plan states which observable events require a reduction or close, what amount leaves at each event, which route and order settings are permitted, and how the trader responds when liquidity, technology, token controls, or market state prevent the preferred execution.

A target price alone is not an exit plan. It says nothing about thesis failure, position size, available depth, minimum output, partial fills, fees, transaction failure, residual tokens, or the authority to change the rule after entry.

Define several exit reasons separately

• Evidence invalidation: an assumption about identity, supply, authority, demand, catalyst, or participant behavior is contradicted.
• Price or loss boundary: the executable position loss reaches a precommitted limit under the stated measurement rule.
• Profit reduction: a price, return, liquidity, or thesis milestone authorizes a defined partial or full reduction.
• Time invalidation: the expected event does not occur within its window, or the position reaches the planned maximum holding period.
• Liquidity failure: intended-size depth, route quality, pool reserves, LP control, or quote reliability deteriorates beyond the rule.
• Security or operational failure: authorities change, a wallet or account may be compromised, signing behavior changes, or execution systems become unreliable.

State which rules are mandatory and which permit discretion. A profit target does not cancel an earlier security, loss, or liquidity exit.

Turn narrative invalidation into observable tests

“The community is weak,” “momentum faded,” or “something feels off” cannot be audited. Name the observation: creator wallet sold a defined amount, holder concentration rose under a stated denominator, executable depth fell below the position, promised launch did not occur by a timestamp, or a specified authority changed.

Save the source and confirmation rule. Decide whether one data source is enough, whether chain confirmation is required, and how delayed indexers are handled. The observation should be available without using the desired exit outcome as proof.

Plan exits in token amount and capital impact

Write the token quantity or portfolio fraction for each exit rule and the priority when several fire together. Estimate wallet proceeds using an intended-size quote, not the last chart price multiplied by balance. Include price impact, route fees, token fees, network costs, and minimum output.

Use the liquidity-depth guide to compare position size with executable depth. A position that can enter through growing demand may not be able to exit after that demand disappears.

Partial exits need a rule for the remainder

For every tranche, define trigger, quantity, route, minimum acceptable output, and the new rule governing what remains. State whether the next target uses the original entry, current position, realized proceeds, high-water mark, or another reference point.

A small successful sale does not prove that the remaining position is liquid. Thepartial-exit workflow shows how route state, depth, and residual accounting change after every slice. Re-quote the remainder instead of projecting the first fill across it.

Know what the exit instruction actually does

Document whether the terminal uses a local alert, server-side watcher, delegated wallet, signed conditional order, keeper, market-style swap, limit order, or custom program. Record the trigger source, polling or update behavior, expiry, slippage or limit, fee settings, wallet permissions, and confirmation method.

Test whether the tool supports the exact token program, extensions, route, and account type. A configured order can remain inactive, expire, reject a quote, or fail onchain. Monitoring and fallback responsibility remain part of the plan.

Write a fallback ladder before the primary route fails

Rank acceptable routes and venues, maximum costs, slippage or minimum output, transaction retries, priority settings, and the point where speed becomes more important than price protection. Include the response to unknown transaction status so a replacement does not accidentally double the exit.

Some events require a different action: revoke approvals after a malicious interaction, isolate assets after wallet compromise, wait for bridge finality, or preserve evidence before interacting further. Do not force every security incident through an ordinary sell workflow.

Changes after entry require new evidence

Preserve the original rule. If new information supports extending time, moving an invalidation, changing a target, or using another route, append the evidence, timestamp, effect on expected value and maximum loss, and authority to approve the change. “Give it more room” is not an evidence field.

Changes that increase maximum loss or holding time should face at least the same review as a new trade. If the revised position would not qualify as a fresh entry under current information, keeping it requires an explicit reason rather than the existence of an unrealized loss.

Reconcile the economic position after the exit

Check every wallet and token account for residual tokens, open orders, LP or claim positions, delegated approvals, withheld fees, bridge transfers, and pending or failed transactions. Record actual wallet proceeds and costs. “Sold” is not a complete status while material exposure remains elsewhere.

Separate planned residuals from dust, unsellable balances, and forgotten accounts. Assign an owner and monitoring rule to anything retained, then classify the exit's decision quality and execution quality independently.

An exit-plan workflow

1. Define the reasons. Write evidence, loss, profit, time, liquidity, security, and operational triggers before entry.
2. Attach quantities. Assign the amount reduced, priority, and rule for the remainder to every trigger.
3. Model the execution. Save intended-size routes, quotes, costs, minimum output, order behavior, permissions, and monitoring.
4. Build the fallback. Rank alternate routes and define failure, retry, unknown-status, and security-incident responses.
5. Control changes. Preserve the original plan and require timestamped evidence and approval for every revision.
6. Reconcile completion. Join all wallets and transactions, calculate actual proceeds, and assign every residual exposure.

What belongs in the journal

Record strategy and plan version, entry thesis, every exit reason and observable test, trigger source, tranche quantities, priority, intended-size quote and route, minimum output, all estimated costs, order mechanism and permissions, monitoring, fallback ladder, changes and supporting evidence, signatures and status, actual balance deltas, residual exposure, completion time, and separate decision and execution classifications.

Primary and official sources