A partner who congratulates your green sim week is an audience. A partner who asks why sitting four has no skip tags is useful. Most Indian “accountability” arrangements die in one of those two roles: cheerleader in a WhatsApp pair, or silent roommate who never opens the sheet. The fix is not finding a more motivated friend. It is a review protocol with a clock, five fields, and a ban on discussing practice P&L until the flags are done.
You are not hiring a mentor. You are swapping incomplete records so each of you can see the rows the other would rather not read.
What the partner is for
They are for blind spots you will not mark. Typical ones, from replay logs rather than from character analysis:
- Skip rows missing a reason code
- Window claims with midday timestamps
- Caps that moved after a win
- Identity sentences that do not match
setup_tag - Debriefs that skip the day a rule broke
They are not for picking your setup, calling Nifty, or deciding whether you are “ready to go live.” Those are separate questions, and a friend with a spreadsheet is not a substitute for writing testable rules you can run alone.
If you cannot show a log, you do not have a partner. You have a chat.
SWAP-5: the weekly protocol
Two traders. Same weekday, 25 minutes, camera optional. Each person sends the other a redacted log by a freeze time (example: Saturday 18:00 IST). Redact name, size in rupees, and any live account data. Keep: session ID, window, setup tag, intent (enter / skip / manage), process 0–2, urge tag, one-line next action. That is close to the ninety-second FIT-UN debrief on purpose. If a row cannot fill those fields, the row is the finding.
Minute 0–5 — inventory, not stories.
Each reader answers only: how many sittings, how many rows, how many skips, how many process-0s. If the sender’s memory of the week disagrees with the sheet, the sheet wins.
Minute 5–15 — five flags each, maximum.
Use this closed list. No sixth category until you have used five for a month.
| Flag | You mark it when | You do not mark it when |
|---|---|---|
missing-tag |
Intent, window, or process blank | You merely dislike their setup |
window-drift |
Timestamp outside the frozen window | The window is ugly but held |
cap-story |
Extra entry after the written cap | They took two allowed entries that lost |
outcome-edit |
Process score looks upgraded after the result | They scored 0 on a winner and left it |
identity-slip |
setup_tag not on their Friday list |
They skipped a lot and you find that boring |
Write the flag next to the row ID, not next to the person. “You lack discipline” is not a flag. cap-story on session 2026-11-02-B is a flag.
Minute 15–22 — owner responds with a verb.
For each flag: accept (will add a field or a stop rule next week), clarify (the log was incomplete; here is the missing tag), or defer (one defer per week, must be resolved next swap). No disagree without pointing at a cell. Feelings about the market are out of scope.
Minute 22–25 — one freeze for next week.
Each owner names one field they will not break: window, cap, or skip-reason completeness. Not a new strategy. Partners may not assign each other setups.
Do this for four weeks before you decide the pairing “doesn’t work.” Most pairings fail in week one because someone sends a highlight reel instead of a log.
How to flag without becoming a guru
The partner reads for completeness and contradiction, not for brilliance. Contradiction means the written plan and the row cannot both be true. Completeness means the journal would let a stranger reconstruct the decision. If you find yourself coaching entry technique, you have left the protocol.
Useful sentence stems:
- “Row 12 is a skip with no SQS / reason code.”
- “You claimed 09:15–10:30 and logged 14:10.”
- “Process is 2 on a sitting that peeked the date.”
Useless stems:
- “I would have taken that breakout.”
- “Your win rate needs work.”
- “Nifty looked like it wanted up.”
Reviewing practice trades without rewriting history is the solo version of the same ethic. SWAP-5 adds a second pair of eyes so rewriting is harder.
If you later count rule violations as the KPI, the partner’s job is to catch unlogged violations, not to argue about losses.
Failure modes
- Cheerleading. “Great week” before flags. Ban outcome talk until minute 22, then still keep it to one sentence, no rupees.
- Scoreboard. Shared win rates. Delete the column from the swap file.
- Delayed swap. “I’ll send Sunday night” becomes never. Missed freeze = sitting counts as
swap-miss. Two swap-misses in a month and you pause the pairing rather than pretend. - Hierarchy. One trader is “more experienced” and stops sending their own ugly rows. Protocol requires symmetric files. If one file is theatre, stop.
- Live leakage. Using the swap to discuss open live positions. Out of scope. This is replay-log hygiene.
Indian practicality: many pairings are two people with jobs, not two people on a dealing desk. Twenty-five minutes on Sunday evening is more realistic than a daily call at 08:45. Daily calls recreate the Telegram room. Weekly flags recreate a review.
Solo fallback if you cannot find a partner: freeze the log on Saturday, do not open it until Sunday, then flag yourself with the same five codes as if the sheet belonged to a stranger. It is weaker. It is still better than an audience.
Replay Trader can supply the sittings — historical NSE, hidden dates, candle-by-candle, optional AI analysis as a review aid after the fact. It cannot supply the second reader. The second reader is a calendar invite.
Swap redacted logs once a week and flag cells, not character. Join the waitlist.
Related reading
- A Debrief Template for Practice Trades
- How to Review Practice Trades Without Rewriting History
- How to Journal Practice Trades So You Actually Learn
- Writing Trading Rules Precise Enough to Test
Educational note
Educational practice content only. Not investment advice. No guaranteed returns. Practice ≠ live profitability.