An MT5 Setup Checklist Before You Commit
An MT5 setup becomes easier to discuss when the requirements are visible before the platform is configured. A short checklist helps both sides see what is essential, what is optional, and what still needs a decision. It also gives your team a reference for checking the handover.

Describe the intended accounts
Write down the account types you plan to offer and the expected number in each category. Distinguish live and demo needs. Identify the groups you expect to use and the reason for each one. Do not choose an arbitrary configuration simply because a package allows a particular number of groups.
Confirm access and working roles
List the staff who need administrative or reporting access and the tasks they perform. Ask the provider to explain which permissions are included in each role. Record who will approve new users, remove departing users, and request configuration changes. A login count is not a complete access policy.
Map the client-facing pieces
Confirm the branding requirements for the platform, website, and communications. Describe how a client moves from registration to an account request and then to support. If a CRM or API connection is needed, identify it as an integration requirement with its own scope, cost, and testing responsibilities.
Agree a demonstration and handover
Select a few representative journeys to demonstrate before acceptance: creating the agreed account type, checking its group, viewing the required report, and resolving a failed request. Record expected results and the owner of any open issue. Ask for support contacts, access ownership, and a practical handover plan. The checklist is complete when the agreed behavior can be shown, not just when credentials have been issued.
Why a checklist beats memory
A setup involves dozens of small decisions spread across a platform provider, a CRM, payment providers, legal documents and your own team. People forget things not because they are careless but because the tasks are scattered. A written checklist with an owner and a date for each item turns a vague project into a visible one.
The list below is organised by area so you can hand each section to the right person. It is a general example; adapt it to your own setup and the scope in your agreement.
Platform and configuration
- Account types and trading groups defined, named and approved.
- Symbol list and contract specifications confirmed.
- Leverage, margin and stop-out rules agreed.
- Spreads, markups and commissions set for each group.
- Trading hours and any special sessions confirmed.
- Demo and live server details received and tested.
- Manager and administrator accounts created with the right permissions.
Owner: operations lead, with sign-off from the person responsible for risk.
Client journey
- Website and registration forms live and tested on desktop and mobile.
- Verification steps and documents defined.
- Welcome email and account details message reviewed.
- Funding instructions clear for every method you offer.
- Withdrawal process defined, including timing and checks.
- Support contact route published and staffed.
Owner: client experience or compliance lead.
Integrations and systems
- CRM connected to the trading server and tested for account creation and balance operations.
- Payment providers integrated, with test transactions recorded.
- Liquidity or pricing connection confirmed where applicable.
- Reporting set up for deposits, withdrawals, trading activity and partner commissions.
- Backups, monitoring and access control confirmed with your provider.
Learn more about CRM connection in our CRM and API cost guide.
Business, legal and people
- Company, banking and licence position confirmed for your target markets.
- Terms, risk warning and privacy pages published.
- Roles assigned: support, risk, payments, compliance and management.
- Training completed for everyone who will touch client accounts.
- Incident and escalation contacts stored in one place.
See company formation and licence jurisdictions if this part is still open.
A pre-launch rehearsal
In the last week, run the full client journey with internal accounts, then with a few trusted outsiders. Open an account, verify it, fund it, trade, request a withdrawal and contact support. Time each step and note anything confusing.
Fix what you find, repeat the rehearsal and only then announce. The small cost of a rehearsal is far lower than a public launch with a broken funding step.
A sample task table
Turn the lists into a table the whole team can read at a glance. A simple version is enough:
| Task | Owner | Evidence | Due |
|---|---|---|---|
| Account types approved | Operations lead | Signed list of names and rules | Week 1 |
| Registration form tested | Client experience lead | Screenshots from desktop and mobile | Week 2 |
| Test deposit and withdrawal | Finance contact | Transaction records | Week 3 |
| Support rota published | Support lead | Rota and contact route | Week 3 |
| Incident contacts stored | Operations lead | One-page contact sheet | Week 4 |
The evidence column is the useful part. "Done" without proof is only an opinion, and opinions change under pressure.
Gaps that rehearsals commonly reveal
Teams that rehearse before launch tend to find the same kinds of problems: a verification email that lands in spam, a funding instruction that assumes knowledge new clients lack, a support mailbox nobody checks at weekends, a report that does not match the trading server, or a permission that lets the wrong person change a group setting.
None of these is dramatic, and all of them are cheaper to fix in private. Treat every rehearsal finding as a gift and record the fix next to the original task, so that the checklist improves each time you use it.
The first week after launch
The checklist does not end at launch. In week one, review the platform, bridge and payments each morning, read every support message, and compare registration, verification and funding numbers with your expectations.
Keep a short daily note of what happened and what you changed. After seven days you will have a clear picture of what to fix and which parts of the journey deserve more attention before you invest in acquisition.
Mistakes in setup checklists
- Having a list but no owners.
- Marking items done without evidence.
- Ignoring failure paths.
- Letting the list go stale after launch.
- Keeping the list in one person’s head.
A shared list with evidence is your project memory.
Frequently asked questions
How long does an MT5 setup take?
It depends on branding, integrations and third-party approvals such as banks and payment providers. Plan a dependency chain with owners and treat any end date as a target. See the launch timeline guide for an illustrative schedule.
Who should own the checklist?
One person should hold the master list, but each section needs its own owner. The master owner keeps dates and unblocks others.
What is the most commonly missed item?
Often it is the failure path: what happens when a payment fails, a document is rejected or an integration times out. Test failures as carefully as successes.
Do I need a CRM before launch?
Most brokers want one from the start because onboarding, funding and reporting depend on it. Check what your setup includes and what is quoted separately.