Project specifications
- Market
- US30
- TF
- M5
- Platform
- MT5
- Client type
- Prop trader
- Delivery window
- 5 weeks
- Stack
- MQL5, settings files, a recorded walkthrough
- Strategy
- Structured handover + walkthrough
- Modules
- Settings document + change form
- Testing
- Pilot on a demo account
Who this was for
Hirad Prop Desk
- Role
- Three-person prop desk
- City
- Karaj
- Project reference
- TBT-1410-38
The client's idea
Hirad Prop Desk works US30 on M5; the opening brief was: Hand this over so all three of us know which settings we run and why.
Initial challenge
Three people ran one account, each with a different setting in their head, and on change days nobody knew which one was live.
Solution
A settings document explaining each parameter, a simple change log, a recorded walkthrough for new members, and a one-week demo pilot.
Why this design
The change form is deliberately simple so it still gets filled in on a busy day. It matches how US30 is actually traded and can be tested against the data already available.
Safeguards and risk control
Every first run happens on a demo account, and the pre-live checklist is filled in before the live connection.
Our next-step proposal
The next step is a quarterly settings review and keeping the documentation current with broker changes.
Portfolio
Measured results
These are the figures the test produced — not a promise about future performance.
- 9 scenarios Scenario test coverage
- 22 Configurable inputs
- 99.9 % Runtime stability in test
- 0 Regressions caught
Portfolio
How the delivery ran
Every project moves through these five phases, with the window for each agreed in the specification.
-
Discovery and problem framing
CompletedReviewing the client's environment: terminal build, broker and the account it runs on.
Day 1–3
-
Written specification
CompletedWriting the install checklist and fixing the starting parameters on US30.
Day 4–8
-
Implementation
CompletedPreparing the handover pack: files, set files and the parameter document.
Day 9–17
-
Testing and validation
CompletedA real run on a demo account, log review and watching the first days of behaviour.
Day 18–25
-
Handover and support
CompletedHandover of the documentation, a short walkthrough and the support path.
Day 26–29