> ## Documentation Index
> Fetch the complete documentation index at: https://forexmasters.in/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Sharing Trade Ideas
> Learn how to share structured, educational trade ideas with the Forex Masters community while protecting risk discipline, privacy, and community trust.
## Share analysis, not signals
Forex Masters community discussions are designed for structured market learning—not copy trading, personalized financial advice, or guaranteed outcomes.
A high-quality trade idea explains **what you see**, **what would validate or invalidate the thesis**, and **how risk is controlled**. It gives other traders enough context to evaluate the setup independently, rather than asking them to follow an entry blindly.
A shared idea is an educational market thesis. Every member remains responsible for their own analysis, risk limits, broker decisions, and execution.
## Before you post
Use this quick filter before publishing an idea:
* Is this based on a defined setup rather than a feeling or headline?
* Have you identified the market, timeframe, and relevant session?
* Does the post explain invalidation—not only the expected direction?
* Is the risk framework clear and proportionate?
* Have you removed account numbers, broker credentials, personal data, and sensitive screenshots?
* Can another trader disagree with the thesis without being treated as wrong?
If the answer is no, refine the analysis before sharing it.
Do not present any post as a guaranteed trade, a “risk-free” setup, or an instruction for others to enter a position. Avoid pressure language such as “buy now,” “must enter,” “easy money,” or claims of certain returns.
## The trade idea structure
A consistent structure helps the community review ideas objectively. Use the following format for chart posts, written ideas, and trade-review discussions.
Name the instrument, timeframe, and current market condition.
Examples include a higher-timeframe trend, range, consolidation, liquidity event, major level, or upcoming market catalyst.
Explain the reasoning behind the idea in plain language. Reference observable conditions such as market structure, liquidity, displacement, session behavior, confluence, or a predefined setup rule.
State what needs to happen before the idea is actionable for you, and what evidence would prove the thesis wrong.
A thesis without invalidation is an opinion, not a controlled trading plan.
Describe risk in process terms: planned stop location, conditions for no trade, event risk, or why position sizing must remain within your own trading plan.
Do not publish account-sensitive sizing details unless you are comfortable making them public.
Ask a focused question that encourages analysis. For example: “What would invalidate this bullish structure?” or “Do you see a cleaner liquidity level?”
## Copyable post template
Use this template when creating a new discussion:
```text theme={"system"}
**Instrument:** EUR/USD
**Timeframe:** H1 / H4 context
**Market condition:** Trending / ranging / consolidating
**Thesis**
[Describe the market structure, level, liquidity event, or setup condition you are observing.]
**Confirmation I am waiting for**
[Describe the price action, structure shift, close, retest, or other rule-based confirmation.]
**Invalidation**
[Describe the level or condition that would invalidate the thesis.]
**Risk considerations**
[Note relevant news, session conditions, volatility, spread, or reasons to avoid the trade.]
**Question for the community**
[Ask for focused, constructive feedback.]
Educational analysis only. Not financial advice.
```
A trade idea can be valid even if no trade is taken. Sharing a well-reasoned **no-trade condition** is often more valuable than sharing a rushed setup.
## The Trade Card format
In addition to written posts, Forex Masters provides a structured **Trade Card** composer for sharing a setup with consistent, reviewable fields. Trade Cards are a distinct post type designed to make the key details of a setup immediately clear to other members.
When you open the Trade Card composer, you will be asked to fill in:
| Field | What to enter |
| - | - |
| **Instrument** | The currency pair or asset you are observing (e.g., EUR/USD, XAUUSD) |
| **Direction** | Whether the setup is a potential long (buy) or short (sell) idea |
| **Entry Price** | The price level at which you would consider entering |
| **Stop Loss** | The price level at which the trade is invalidated and risk is cut |
| **Take Profit** | The target price level if the thesis plays out |
| **Thesis / Rationale** | A brief explanation of the reasoning, confluence, or setup conditions |
All four core fields — instrument, direction, entry, stop loss, and take profit — are required before a Trade Card can be posted. The thesis field is optional but strongly encouraged: a setup without reasoning invites copying rather than learning.
A Trade Card is an educational market observation shared for peer review — not a signal or an instruction to enter a position. Every member remains responsible for their own analysis, risk decisions, and execution.
## What strong posts look like
“GBP/USD is approaching a prior H4 liquidity area after a bullish displacement. I am not entering at the level. I would need to see lower-timeframe confirmation and a reclaim of structure. A sustained move below the referenced swing would invalidate the idea.”
“GBP/USD is definitely going up. Buy now—this is guaranteed.”
“There is a potential setup, but a high-impact event is scheduled during the planned holding period. I may remain flat if volatility expands beyond my rules.”
“I made profit on this, so the setup works every time.”
## Include the information that changes a decision
The best community analysis makes its assumptions visible. When relevant, include:
| Include | Why it matters |
| - | - |
| Instrument and timeframe | Prevents ambiguity about the chart context. |
| Session or trading window | Liquidity and volatility can differ materially by session. |
| Higher-timeframe structure | Shows whether the idea aligns with, or deliberately trades against, broader context. |
| Key levels or liquidity zones | Helps readers understand where the thesis is expected to react or fail. |
| Confirmation criteria | Separates an observation from an execution decision. |
| Invalidation condition | Establishes the point at which the original idea is no longer valid. |
| Scheduled event risk | Encourages awareness of economic-calendar volatility and uncertainty. |
| Post-trade outcome and review | Turns the idea into a learning record instead of a victory post. |
## Share charts responsibly
Charts make a thesis easier to review, but annotations should clarify—not exaggerate—the setup.
### Recommended chart practices
* Mark the instrument and timeframe clearly.
* Keep annotations limited to the levels, structure, and conditions that matter.
* Use labels such as **context**, **confirmation**, **invalidation**, and **no-trade zone**.
* Show enough price history for other members to assess the structure.
* Explain whether the chart is pre-trade analysis, an active-trade update, or a completed review.
* Remove personal information, account identifiers, order IDs, balances, and broker-specific credentials before uploading.
### Avoid misleading chart posts
Do not:
* Crop a chart in a way that hides invalidation or adverse movement.
* Publish edited results as though they were live analysis.
* Claim that a chart pattern guarantees a future move.
* Share screenshots that expose private account, payment, or identity information.
* Use P\&L screenshots to pressure others into following a setup.
Past performance, screenshots, and isolated winning trades do not establish a reliable strategy or predict future results. Treat every chart as a discussion input, not evidence of a guaranteed outcome.
## Updating an idea as the market develops
Markets change. Updating or invalidating an idea is a sign of discipline, not a failure.
When you revisit a post, add an update that distinguishes the original thesis from the new information.
State which planned condition occurred. Explain whether you acted, remained flat, or are still waiting for additional confirmation. Keep the update focused on process rather than celebrating an unrealized outcome.
State the condition that invalidated it and close the loop. A concise update such as “The H1 close below the stated invalidation level removed my bullish thesis; no trade taken” is valuable learning material.
Be transparent about whether the entry followed the original plan. If execution differed from the plan, identify why. This helps separate a repeatable process from an impulsive decision.
Review the decision quality, not only profit or loss. Note whether the setup, timing, risk, and management followed your rules—and what you would retain or improve next time.
## Give feedback that improves the analysis
Community feedback should challenge ideas without attacking people.
### Useful responses
* “What would make you abandon the long thesis if price reaches that level?”
* “Which higher-timeframe swing is defining your current bias?”
* “How does the upcoming event affect your planned holding period?”
* “I see the same level, but I interpret the structure as range-bound. What evidence would distinguish the two cases?”
* “Would waiting for a close beyond the level better match your entry rules?”
### Feedback to avoid
* Personal criticism, ridicule, or public shaming.
* Dismissive replies with no analytical basis.
* Demands that another member reveal account balances or proprietary details.
* Pressure to enter, hold, add to, or close a trade.
* Messages that promise profits, promote paid signals, or solicit funds.
Disagreement is useful when it is specific. Explain the chart level, rule, timeframe, or risk assumption behind your alternative view.
## Protect your privacy and trading process
Community posts may be visible to other authorized members of the platform. Share deliberately.
Before posting, remove or avoid:
* Broker login details, API keys, recovery codes, or account credentials.
* Full account numbers, personal addresses, phone numbers, or identity documents.
* Private messages or identifiable information about another person.
* Payment information or subscription records.
* Sensitive strategy logic you do not intend to disclose.
* Anything you would not want preserved in a discussion record or screenshot.
If you connect broker or journal data elsewhere in the platform, do not assume that private records should be copied into a community post. Share only the minimum context needed for the educational discussion.
## Community standards for trade ideas
Forex Masters maintains a learning-first environment. Trade ideas should support independent thinking, disciplined risk management, and respectful peer review.
Posts may be reviewed, limited, removed, or escalated when they include:
* Financial advice framed as a personal recommendation or instruction.
* Promises of profit, certainty, or “guaranteed” returns.
* Signal-selling, solicitation, impersonation, or attempts to move members off-platform for payment.
* Harassment, discriminatory language, spam, or coordinated manipulation.
* Misleading performance claims or fabricated trade evidence.
* Personal, account, or confidential information shared without authorization.
Never send money, credentials, remote device access, or broker access to another community member. Forex Masters does not require members to transfer funds or disclose credentials in order to participate in community discussions.
## A better post-trade review
Closing the learning loop turns shared ideas into reusable insight. After an outcome is known, consider adding:
1. **Original thesis:** What did you expect and why?
2. **What happened:** Which conditions confirmed or invalidated the thesis?
3. **Execution quality:** Did your action follow your stated plan?
4. **Risk quality:** Did you respect your predefined risk and no-trade rules?
5. **Lesson:** What should you repeat, refine, or avoid in a similar context?
A losing trade can be a high-quality execution. A winning trade can still reveal poor process. Evaluate both.
## Quick checklist
Before publishing, confirm:
* [ ] The post identifies the instrument and timeframe.
* [ ] The thesis is based on observable market conditions.
* [ ] Confirmation and invalidation are stated.
* [ ] Risk and scheduled-event considerations are acknowledged.
* [ ] The content is educational and does not direct others to trade.
* [ ] Screenshots contain no sensitive or personal data.
* [ ] The tone invites respectful, evidence-based discussion.
* [ ] You are prepared to update the idea if market conditions change.
The goal is not to be right in public. The goal is to make your reasoning clear, testable, and disciplined—so every discussion improves the quality of your process.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.