Decide what the exercise can answer
A non-funded environment can help you inspect an interface before considering a real account. Useful questions are concrete: Where is the contract specification? What unit does the size field use? Where is a pending order shown? How do you export a statement? Those questions can be answered without predicting a market move.
It cannot establish whether live execution will be identical, whether a withdrawal will be processed in a particular time or whether a trading approach will be profitable. Keep your notes focused on what you actually observed. PipBriefing’s profiles are document-based; no demo sessions or live trades were performed for these profiles.
Record the environment
Write down the provider, country-specific site, platform version and demo account type. Keep it beside the legal-entity research rather than assuming the demo and an eventual live agreement have identical terms. A global download page can describe a different service from the one available to a Great Britain retail applicant.
Use a simple observation sheet with four columns: task, expected unit or control, observed behaviour, and document needed to confirm live terms. The last column keeps the exercise from becoming a verdict based on appearance.
Inspect the units before the buttons
- Find the specification. Record contract size, minimum size, size increment and pip convention for one currency pair.
- Inspect both prices. Check the bid, ask and displayed spread. Identify which price the chart plots.
- Read the size field. Determine whether it accepts units, lots, contracts or an amount per point. Do not assume these are equivalent.
- Inspect the order ticket. Check where it shows direction, size, margin information and any stop or limit settings. Cancel if anything is unclear.
A field labelled “1” is not meaningful without a unit. For a hypothetical instrument with 100,000 base units per lot, 0.1 lot is 10,000 base units. That convention must be confirmed for the instrument rather than imported from another screen.
Trace the record from order to statement
Within the demo, locate pending orders and distinguish them from open positions. Observe how a cancellation or modification is recorded. Inspect the confirmation and the account history. If a demo operation is performed, treat any resulting profit or loss as a software record, not evidence of achievable returns.
Find the statement export and look for transaction identifiers, execution timestamps, size units, price and separate charges. Note whether financing appears as a daily cash entry or accrual. Then check which live documents explain any missing fields. A clean chart does not compensate for an unclear record.
Write a narrow conclusion
A useful conclusion might say: “I located the contract size and could export a statement in this demo version; live fees and execution remain to be confirmed.” An unhelpful conclusion says: “The broker is reliable because the demo worked.” The first is reproducible. The second makes a larger claim than the evidence supports.
Use the platform comparison guide to organise the remaining account questions. Model only the fee structure you have actually identified in the cost calculator. Do not use a demo balance, a simulated streak or a promotional illustration as a reason to increase financial exposure.