Skip to content
NUKBORD / PRODUCT MANUAL12 practical guides

A clear way into the workstation

Know your tools.
Make them yours.

Start with an account, build your workspace, prepare deliberately and keep the record. Follow practical instructions for the controls in front of you.

3 of 12 practical guidesClear manual filters โ†’
01Choose a job02Follow the steps03Find account help
Published manual introduction

The guides below are the product manual. An optional published introduction can add context; it does not replace the search, instructions or account help.

01 / Find your next task

Choose a job.

Each guide includes preparation, ordered steps, checks and the limits that matter.

02 / Review & save

Understand a request, fill and slippage

Open the private per-trade review to separate what you requested, what the app observed and the available fill evidence. Practice reports identify their simulated execution policy.

A closer look

Find your way around the controls.

Watch the labelled visual guide, then inspect the captured controls. Select a numbered note to understand the pictured control, or enlarge the capture to inspect its details.

Visual guide / 1:00

Read the fill. Keep the evidence.

Edition 2026-10-09
Silent annotated guide made from an actual product still, not a screen recording. Synthetic Practice inputs; no account or broker connected and no live execution.

Silent guide. Use Play when ready, or read the transcript. Chapter buttons seek without starting playback.

Read the complete transcript 6 chapters
  1. 0:00 โ€” 0:08

    Request. Fill. Evidence.

    This is NukBordโ€™s actual Execution Review with synthetic Practice inputs. The sample request, fill and dispatch quote are fictional.

  2. 0:08 โ€” 0:20

    Keep request and fill separate

    The requested quantity is 0.50. The recorded fill is 0.50 at an average price of 1.08425. An accepted application response alone does not prove a fill.

  3. 0:20 โ€” 0:33

    Read the dispatch-side quote

    This buy compares its fill with the retained matching-feed dispatch ask of 1.08422. At the retained 0.00001 increment, the difference is three adverse ticks, not pips or an extra ledger charge.

  4. 0:33 โ€” 0:43

    Separate timing from fill quality

    The 36.0 ms pairs locally recorded application dispatch and response observations. It includes application transport and response handling; it does not isolate broker processing or network delay.

  5. 0:43 โ€” 0:51

    Unavailable does not mean zero

    The monetary estimate is unavailable because original instrument and conversion evidence is missing. No cash amount can be inferred from this gap.

  6. 0:51 โ€” 1:00

    Explore the Market example

    The desktop report does not compute pending-order comparisons. The websiteโ€™s separate Limit example is a request-price illustration. Explore the Market example, then check platform requirements.

Download MP4 โ†—English notes ยท VTT โ†—Transcript ยท TXT โ†—Original product still ยท new tab โ†—
Try the Market example Read the comparison Manual Check platform requirements
Inside the workstationSeparate the fill, timing and price comparison
Actual NukBord Execution Review with synthetic Practice data: 0.50 filled at 1.08425, 36.0 ms local response, three adverse ticks against the dispatch ask and an unavailable monetary estimate.
01 / 04Request and fill stay separate

This Practice example requests 0.50 and records 0.50 filled at an average price of 1.08425. Read the source evidence as well as the quantities. An accepted application response alone does not prove a fill. Original request and response opens the retained fields in the workstation.

Current Execution Review with synthetic Practice data. The sample request, fill and dispatch quote are fictional; no account or broker is connected.

Product screenshot with sample data. Pictured controls are not live.

Select a numbered marker. Arrow keys move through notes.

Product screenshotSeparate the fill, timing and price comparison
The full image, scaled to fit.
Actual NukBord Execution Review with synthetic Practice data: 0.50 filled at 1.08425, 36.0 ms local response, three adverse ticks against the dispatch ask and an unavailable monetary estimate.
01 / 04Request and fill stay separate

This Practice example requests 0.50 and records 0.50 filled at an average price of 1.08425. Read the source evidence as well as the quantities. An accepted application response alone does not prove a fill. Original request and response opens the retained fields in the workstation.

Product screenshot with sample data. Pictured controls are not live.

01

Follow the original evidence

  1. Open Execution review

    Open it from a Logbook trade, position details or the Entry Pad where available. The report belongs to the selected account and trade.

  2. Compare the request with the fill

    Requested versus actual keeps requested quantity and protection separate from verified filled quantity and average fill price. Acceptance alone does not prove a fill. Expand Original request and response to inspect the retained fields.

  3. Inspect the timeline

    Select a recorded Event timeline observation to read its evidence and time basis. Keep local application clocks, source timestamps and fill evidence distinct; inspect receipt identities and raw fields when needed.

  4. Read costs, protection and coverage

    Recorded costs and protection observations are separate parts of the report. Read Evidence coverage for gaps in retained observations. Missing commission, swap or fees are unavailable, never an assumed zero.

Check your work

You can trace a displayed fact to its original request, observation or verified fill.

02

Read the comparison correctly

  1. Check whether slippage is qualified

    A market-order comparison needs one attributable attempt and a retained dispatch quote from the matching feed. If that quote is missing or ambiguous, slippage stays unavailable.

  2. Use the right quote and sign

    The report compares the volume-weighted fill to the dispatch ask for a buy or bid for a sell. Positive slippage is adverse; negative slippage is favourable. Ticks use the retained price increment; do not read them as pips. A monetary estimate needs its original instrument and conversion basis and is not an extra ledger charge.

  3. Keep pending-order benchmarks separate

    The current report does not use pending-order placement quotes as fill-time benchmarks. Original requested prices and available fills remain readable. The websiteโ€™s Limit improvement illustration teaches a separate request-price calculation, not a computed comparison in this desktop report.

  4. Interpret Application response

    The displayed duration pairs locally recorded dispatch and response observations. It includes application transport and response handling; it does not isolate broker latency or network latency.

Check your work

You know the baseline, direction and evidence limits of the comparison, rather than treating unavailable slippage as zero.

03 / Keep the definition handy

Workstation reference.

3 of 10 public references. The capability descriptions remain separate from the step-by-step guides.

Execution reviewReview and keep the record

A per-trade report separating your request, verified fills, slippage where evidence allows, recorded costs and missing observations.

  • The original request, as it was sent
  • Verified fills and recorded costs, listed separately from the request
  • Slippage against a retained matching-feed dispatch quote, when evidence allows
  • What was observed about the trade's protection
  • Missing evidence is marked as missing, never filled in
  • Opens from the Logbook, position details and the Entry Pad

An execution review answers a simple question about one trade: what did I ask for, and what actually happened? The report keeps the original request, the application's observations, and the available fill evidence in separate sections. Practice reports identify their simulated execution policy.

For a market order with one attributable attempt and a retained quote from the same feed, the report compares the volume-weighted fill with the dispatch ask for a buy or bid for a sell. Positive slippage is adverse; negative is favorable. Pending-order placement quotes are not treated as fill-time benchmarks, and missing or ambiguous quote evidence stays unavailable.

Costs appear only where they were recorded, and anything that was never observed is listed as missing evidence. Reviews are private to your account and can be reopened from your saved work.

Read the Execution review guide
LogbookReview and keep the record

The Day, The Log, Calendar & Results and journal notes keep a record of what you did and how it turned out.

  • The Day: the session's events in order
  • The Log: closed trades with your journal notes
  • Calendar & Results: calendar, graphs and comparisons of recorded results
  • Today, 7 day, 30 day and custom date ranges

The Logbook is the record of your trading. The Day lists what happened in the session, The Log keeps closed trades with your notes, and Calendar & Results shows your recorded results by day, as graphs, and compared between periods.

Results are calculated from the trades that were actually recorded, and the basis of each calculation is stated. Where history is missing, the Logbook says so instead of filling the gap.

Read the Logbook guide
Offline reviewReview and keep the record

Saved layouts, charts, drawings, journal and recordings reopen without a connection, and backups are verified before they restore.

  • Reopen saved layouts, chart history and drawings without a connection
  • Journal copies and session recordings come with them
  • Versioned backups, checked before a restore replaces anything
  • Offline review cannot trade; trading needs the online connection

Your saved workspace is kept on your computer, separated by account owner. When you are offline you can still open it to review charts, drawings, notes and recorded sessions.

Backups are versioned, and a restore is verified before it replaces what you have. Offline review is for looking back; placing trades always needs the live, signed-in connection.

Read the Offline review guide