Sample risk report
Risk checklist before deeper testing.
A client-facing example of how FinLabe reviews paper-stage trading systems before any live execution is considered.
Scope
Safe Trading Bot
Safety Boundary
- No live trading was used.
- No exchange write access was used.
- No API keys, seed phrases, or environment files are requested.
- This is not financial advice and not a trading signal.
Checklist Summary
Area
Status
Notes
Mode separation
Pass
Paper/research mode is explicit. Live execution remains blocked.
Secrets handling
Pass
No exchange keys, .env files, or live credentials are required.
Fees and slippage
Needs review
Cost assumptions must be confirmed per exchange and instrument.
Position sizing
Missing
Max position size must be stated before deeper paper runs.
Daily loss limit
Missing
A daily loss stop or review threshold should be defined.
Entry diagnostics
Pass
Blocked-entry reasons are recorded and readable.
Main Findings
- The project has a clear paper/research safety boundary.
- Blocked-entry diagnostics are useful and client-readable.
- Risk controls need explicit position, daily loss, and exposure limits.
- Every report should include test window, data source, and sanitized config snapshot.
Next Safe Actions
- Define max position size, daily loss limit, and max exposure.
- Add or confirm exit-reason logging.
- Run a longer paper test before changing thresholds.
- Keep live trading disabled.